Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-05-15 Thread Grant Likely
On Thu, 24 Apr 2014 10:26:42 +0100, Leif Lindholm wrote: > On Wed, Apr 23, 2014 at 02:10:58PM +0100, Grant Likely wrote: > > > Does anyone have a LongTrail DT to hand, and if so does the root have a > > > compatible string? From grepping through the kernel I could only find a > > > model string (

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-24 Thread Leif Lindholm
On Wed, Apr 23, 2014 at 02:10:58PM +0100, Grant Likely wrote: > > Does anyone have a LongTrail DT to hand, and if so does the root have a > > compatible string? From grepping through the kernel I could only find a > > model string ("IBM,LongTrail"). > > Actually, on LongTrail this can be removed f

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-23 Thread Grant Likely
On Wed, 23 Apr 2014 11:45:28 +0100, Mark Rutland wrote: > On Tue, Apr 22, 2014 at 02:35:15PM +0100, Grant Likely wrote: > > On Fri, 18 Apr 2014 13:59:24 +0100, Leif Lindholm > > wrote: > > > Hi Geert, > > > > > > On Fri, Apr 18, 2014 at 10:04:15AM +0200, Geert Uytterhoeven wrote: > > > > On Thu

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-23 Thread Geert Uytterhoeven
Hi Mark, On Wed, Apr 23, 2014 at 12:45 PM, Mark Rutland wrote: > Does anyone have a LongTrail DT to hand, and if so does the root have a > compatible string? From grepping through the kernel I could only find a > model string ("IBM,LongTrail"). It's compatible with "prep": http://users.telenet.

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-23 Thread Mark Rutland
On Tue, Apr 22, 2014 at 02:35:15PM +0100, Grant Likely wrote: > On Fri, 18 Apr 2014 13:59:24 +0100, Leif Lindholm > wrote: > > Hi Geert, > > > > On Fri, Apr 18, 2014 at 10:04:15AM +0200, Geert Uytterhoeven wrote: > > > On Thu, Apr 17, 2014 at 7:42 PM, Leif Lindholm > > > wrote: > > > > In orde

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-23 Thread Mark Rutland
Hi, > > diff --git a/drivers/of/Kconfig b/drivers/of/Kconfig > > index 889005f..230c747 100644 > > --- a/drivers/of/Kconfig > > +++ b/drivers/of/Kconfig > > @@ -77,4 +77,7 @@ config OF_RESERVED_MEM > > help > > Helpers to allow for reservation of memory regions > > > > +config OF

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-22 Thread Grant Likely
On Fri, 18 Apr 2014 13:59:24 +0100, Leif Lindholm wrote: > Hi Geert, > > On Fri, Apr 18, 2014 at 10:04:15AM +0200, Geert Uytterhoeven wrote: > > On Thu, Apr 17, 2014 at 7:42 PM, Leif Lindholm > > wrote: > > > In order to deal with an firmware bug on a specific ppc32 platform > > > (longtrail),

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-21 Thread Rob Herring
On Fri, Apr 18, 2014 at 7:59 AM, Leif Lindholm wrote: > Hi Geert, > > On Fri, Apr 18, 2014 at 10:04:15AM +0200, Geert Uytterhoeven wrote: >> On Thu, Apr 17, 2014 at 7:42 PM, Leif Lindholm >> wrote: >> > In order to deal with an firmware bug on a specific ppc32 platform >> > (longtrail), early_in

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-18 Thread Geert Uytterhoeven
Hei Leif, On Fri, Apr 18, 2014 at 2:59 PM, Leif Lindholm wrote: > On Fri, Apr 18, 2014 at 10:04:15AM +0200, Geert Uytterhoeven wrote: >> On Thu, Apr 17, 2014 at 7:42 PM, Leif Lindholm >> wrote: >> > In order to deal with an firmware bug on a specific ppc32 platform >> > (longtrail), early_init_

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-18 Thread Leif Lindholm
Hi Geert, On Fri, Apr 18, 2014 at 10:04:15AM +0200, Geert Uytterhoeven wrote: > On Thu, Apr 17, 2014 at 7:42 PM, Leif Lindholm > wrote: > > In order to deal with an firmware bug on a specific ppc32 platform > > (longtrail), early_init_dt_scan_memory() looks for a node called > > memory@0 on all

Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-18 Thread Geert Uytterhoeven
Hi Leif, On Thu, Apr 17, 2014 at 7:42 PM, Leif Lindholm wrote: > In order to deal with an firmware bug on a specific ppc32 platform > (longtrail), early_init_dt_scan_memory() looks for a node called > memory@0 on all platforms. Restrict this quirk to ppc32 kernels only. This breaks backwards com

[PATCH 3/3] of: Handle memory@0 node on PPC32 only

2014-04-17 Thread Leif Lindholm
In order to deal with an firmware bug on a specific ppc32 platform (longtrail), early_init_dt_scan_memory() looks for a node called memory@0 on all platforms. Restrict this quirk to ppc32 kernels only. Signed-off-by: Leif Lindholm Cc: linuxppc-...@lists.ozlabs.org Cc: Grant Likely Cc: Mark Rutla