From: dev@lynxeye.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: rpi: Device tree modifications for U-Boot
Date: Tue, 11 Aug 2015 19:05:01 +0200 [thread overview]
Message-ID: <1439312701.2451.3.camel@lynxeye.de> (raw)
In-Reply-To: <1439303153-12171-1-git-send-email-sjg@chromium.org>
Hi Simon,
why did you send this to the Tegra ML?
Am Dienstag, den 11.08.2015, 08:25 -0600 schrieb Simon Glass:
> This updates the device tree from the kernel version to something suitable
> for U-Boot:
>
> - Add stdout-path alias for console
> - Mark the /soc node to be available pre-relocation so that the early
> serial console works (we need the 'ranges' property to be available)
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> arch/arm/boot/dts/bcm2835.dtsi | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/bcm2835.dtsi b/arch/arm/boot/dts/bcm2835.dtsi
> index 301c73f..bd6bff6 100644
> --- a/arch/arm/boot/dts/bcm2835.dtsi
> +++ b/arch/arm/boot/dts/bcm2835.dtsi
> @@ -8,6 +8,7 @@
>
> chosen {
> bootargs = "earlyprintk console=ttyAMA0";
> + stdout-path = &uart;
> };
>
> soc {
> @@ -16,6 +17,7 @@
> #size-cells = <1>;
> ranges = <0x7e000000 0x20000000 0x02000000>;
> dma-ranges = <0x40000000 0x00000000 0x20000000>;
> + u-boot,dm-pre-reloc;
Why do you need this and why should upstream carry your favourite
bootloaders configuration? This is in no way hardware description.
Regards,
Lucas
next prev parent reply other threads:[~2015-08-11 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 14:25 [PATCH] arm: rpi: Device tree modifications for U-Boot Simon Glass
2015-08-11 17:05 ` Lucas Stach [this message]
2015-08-11 17:29 ` Stephen Warren
2015-08-11 19:38 ` Lucas Stach
2015-08-12 13:21 ` Simon Glass
2015-08-14 18:34 ` Simon Glass
2015-08-14 20:29 ` Rob Herring
2015-08-15 13:46 ` Simon Glass
2015-08-25 16:22 ` Rob Herring
2015-08-28 18:27 ` Simon Glass
2015-09-09 18:08 ` Simon Glass
2015-09-16 3:54 ` Stephen Warren
2015-08-15 3:46 ` Stephen Warren
2015-08-15 13:47 ` Simon Glass
2015-10-08 15:50 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1439312701.2451.3.camel@lynxeye.de \
--to=dev@lynxeye.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).