[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqL8B2ZY7ACXKX3J8VN5ukjKWuycgfDZpp4kYzBxg6BLmQ@mail.gmail.com>
Date: Thu, 17 Apr 2014 19:43:13 -0500
From: Rob Herring <robherring2@...il.com>
To: Leif Lindholm <leif.lindholm@...aro.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linaro Patches <patches@...aro.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH 0/3] of: dts: enable memory@0 quirk for PPC32 only
On Thu, Apr 17, 2014 at 12:41 PM, Leif Lindholm
<leif.lindholm@...aro.org> wrote:
> drivers/of/fdt.c contains a workaround for a missing memory type
> entry on longtrail firmware. Make that quirk PPC32 only, and while
> at it - fix up the .dts files in the tree currently working only
> because of that quirk.
But why do you need this?
>
> Cc: devicetree@...r.kernel.org
> Cc: linuxppc-dev@...ts.ozlabs.org
> Cc: linux-kernel@...r.kernel.org
> Cc: Mark Rutland <mark.rutland@....com>
>
> Leif Lindholm (3):
> arm: dts: add device_type="memory" for ste-ccu8540
> mips: dts: add device_type="memory" where missing
> of: Handle memory@0 node on PPC32 only
>
> arch/arm/boot/dts/ste-ccu8540.dts | 1 +
> arch/mips/lantiq/dts/easy50712.dts | 1 +
> arch/mips/ralink/dts/mt7620a_eval.dts | 1 +
> arch/mips/ralink/dts/rt2880_eval.dts | 1 +
> arch/mips/ralink/dts/rt3052_eval.dts | 1 +
> arch/mips/ralink/dts/rt3883_eval.dts | 1 +
I'm not worried about these MIPS dts files because they are all
built-in, but you are breaking compatibility with old dtbs for this
ARM board.
Rob
> drivers/of/fdt.c | 7 ++++++-
> 7 files changed, 12 insertions(+), 1 deletion(-)
>
> --
> 1.7.10.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists