On Mon, 2013-12-30 at 14:13 +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2013-12-19 at 08:42 +0400, Nikita Yushchenko wrote:
> > No, this does not help.
> >
> > I've dumped the actual content of 'range' and 'addr' at the failure
> > point
> > (i.e. ar point that returns error with e38c0a1f but
On Thu, 2013-12-19 at 08:42 +0400, Nikita Yushchenko wrote:
> No, this does not help.
>
> I've dumped the actual content of 'range' and 'addr' at the failure
> point
> (i.e. ar point that returns error with e38c0a1f but passes without
> e38c0a1f ):
>
> OF: default map, cp=0, s=1, da=70
> ra
On Wed, Dec 18, 2013 at 12:40:21PM -0600, Rob Herring wrote:
> [fixed DT maillist address]
>
> On 12/17/2013 01:35 AM, Nikita Yushchenko wrote:
> > Hi
> >
> > While trying to make freescale p2020ds and mpc8572ds boards working with
> > mainline kernel, I faced that commit
> > e38c0a1f (Handle
> Reverting would break Tegra PCIe, but you should not have to change the
> DT either. So we need a solution.
>
> Is this something like this sufficient to fix it?
>
> diff --git a/drivers/of/address.c b/drivers/of/address.c
> index 4b9317b..378aebd 100644
> --- a/drivers/of/address.c
> +++ b/drive
[fixed DT maillist address]
On 12/17/2013 01:35 AM, Nikita Yushchenko wrote:
> Hi
>
> While trying to make freescale p2020ds and mpc8572ds boards working with
> mainline kernel, I faced that commit
> e38c0a1f (Handle #address-cells > 2 specially) breaks things with these
> boards.
Good to se
Hi
While trying to make freescale p2020ds and mpc8572ds boards working with
mainline kernel, I faced that commit
e38c0a1f (Handle #address-cells > 2 specially) breaks things with these boards.
Both these boards have uli1575 chip.
Corresponding part in device tree is something like
