From: Rob Herring <robherring2@gmail.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: tony@atomide.com, devicetree-discuss@lists.ozlabs.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 2/3] arm/dts: OMAP: Remove bootargs node from board files
Date: Tue, 06 Dec 2011 12:06:48 -0600 [thread overview]
Message-ID: <4EDE59B8.1070808@gmail.com> (raw)
In-Reply-To: <1323190149-6492-3-git-send-email-b-cousson@ti.com>
Benoit,
On 12/06/2011 10:49 AM, Benoit Cousson wrote:
> Since 3.2, the CONFIG_ARM_ATAG_DTB_COMPAT config allows
> an old bootloader to still use ATAG to provide cmdline.
>
> Remove chosen/bootargs from the DTS board files.
>
> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Rob Herring <rob.herring@calxeda.com>
Acked-by: Rob Herring <rob.herring@calxeda.com>
Rob
> ---
> arch/arm/boot/dts/omap3-beagle.dts | 9 ---------
> arch/arm/boot/dts/omap4-panda.dts | 9 ---------
> arch/arm/boot/dts/omap4-sdp.dts | 9 ---------
> 3 files changed, 0 insertions(+), 27 deletions(-)
>
> diff --git a/arch/arm/boot/dts/omap3-beagle.dts b/arch/arm/boot/dts/omap3-beagle.dts
> index 9486be6..9f72cd4 100644
> --- a/arch/arm/boot/dts/omap3-beagle.dts
> +++ b/arch/arm/boot/dts/omap3-beagle.dts
> @@ -13,15 +13,6 @@
> model = "TI OMAP3 BeagleBoard";
> compatible = "ti,omap3-beagle", "ti,omap3";
>
> - /*
> - * Since the initial device tree board file does not create any
> - * devices (MMC, network...), the only way to boot is to provide a
> - * ramdisk.
> - */
> - chosen {
> - bootargs = "root=/dev/ram0 rw console=ttyO2,115200n8 initrd=0x81600000,20M ramdisk_size=20480 no_console_suspend debug earlyprintk";
> - };
> -
> memory {
> device_type = "memory";
> reg = <0x80000000 0x20000000>; /* 512 MB */
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index c702657..9755ad5 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -13,15 +13,6 @@
> model = "TI OMAP4 PandaBoard";
> compatible = "ti,omap4-panda", "ti,omap4430", "ti,omap4";
>
> - /*
> - * Since the initial device tree board file does not create any
> - * devices (MMC, network...), the only way to boot is to provide a
> - * ramdisk.
> - */
> - chosen {
> - bootargs = "root=/dev/ram0 rw console=ttyO2,115200n8 initrd=0x81600000,20M ramdisk_size=20480 no_console_suspend debug";
> - };
> -
> memory {
> device_type = "memory";
> reg = <0x80000000 0x40000000>; /* 1 GB */
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 066e28c..63c6b2b 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -13,15 +13,6 @@
> model = "TI OMAP4 SDP board";
> compatible = "ti,omap4-sdp", "ti,omap4430", "ti,omap4";
>
> - /*
> - * Since the initial device tree board file does not create any
> - * devices (MMC, network...), the only way to boot is to provide a
> - * ramdisk.
> - */
> - chosen {
> - bootargs = "root=/dev/ram0 rw console=ttyO2,115200n8 initrd=0x81600000,20M ramdisk_size=20480 no_console_suspend debug";
> - };
> -
> memory {
> device_type = "memory";
> reg = <0x80000000 0x40000000>; /* 1 GB */
WARNING: multiple messages have this Message-ID (diff)
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] arm/dts: OMAP: Remove bootargs node from board files
Date: Tue, 06 Dec 2011 12:06:48 -0600 [thread overview]
Message-ID: <4EDE59B8.1070808@gmail.com> (raw)
In-Reply-To: <1323190149-6492-3-git-send-email-b-cousson@ti.com>
Benoit,
On 12/06/2011 10:49 AM, Benoit Cousson wrote:
> Since 3.2, the CONFIG_ARM_ATAG_DTB_COMPAT config allows
> an old bootloader to still use ATAG to provide cmdline.
>
> Remove chosen/bootargs from the DTS board files.
>
> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Rob Herring <rob.herring@calxeda.com>
Acked-by: Rob Herring <rob.herring@calxeda.com>
Rob
> ---
> arch/arm/boot/dts/omap3-beagle.dts | 9 ---------
> arch/arm/boot/dts/omap4-panda.dts | 9 ---------
> arch/arm/boot/dts/omap4-sdp.dts | 9 ---------
> 3 files changed, 0 insertions(+), 27 deletions(-)
>
> diff --git a/arch/arm/boot/dts/omap3-beagle.dts b/arch/arm/boot/dts/omap3-beagle.dts
> index 9486be6..9f72cd4 100644
> --- a/arch/arm/boot/dts/omap3-beagle.dts
> +++ b/arch/arm/boot/dts/omap3-beagle.dts
> @@ -13,15 +13,6 @@
> model = "TI OMAP3 BeagleBoard";
> compatible = "ti,omap3-beagle", "ti,omap3";
>
> - /*
> - * Since the initial device tree board file does not create any
> - * devices (MMC, network...), the only way to boot is to provide a
> - * ramdisk.
> - */
> - chosen {
> - bootargs = "root=/dev/ram0 rw console=ttyO2,115200n8 initrd=0x81600000,20M ramdisk_size=20480 no_console_suspend debug earlyprintk";
> - };
> -
> memory {
> device_type = "memory";
> reg = <0x80000000 0x20000000>; /* 512 MB */
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index c702657..9755ad5 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -13,15 +13,6 @@
> model = "TI OMAP4 PandaBoard";
> compatible = "ti,omap4-panda", "ti,omap4430", "ti,omap4";
>
> - /*
> - * Since the initial device tree board file does not create any
> - * devices (MMC, network...), the only way to boot is to provide a
> - * ramdisk.
> - */
> - chosen {
> - bootargs = "root=/dev/ram0 rw console=ttyO2,115200n8 initrd=0x81600000,20M ramdisk_size=20480 no_console_suspend debug";
> - };
> -
> memory {
> device_type = "memory";
> reg = <0x80000000 0x40000000>; /* 1 GB */
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 066e28c..63c6b2b 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -13,15 +13,6 @@
> model = "TI OMAP4 SDP board";
> compatible = "ti,omap4-sdp", "ti,omap4430", "ti,omap4";
>
> - /*
> - * Since the initial device tree board file does not create any
> - * devices (MMC, network...), the only way to boot is to provide a
> - * ramdisk.
> - */
> - chosen {
> - bootargs = "root=/dev/ram0 rw console=ttyO2,115200n8 initrd=0x81600000,20M ramdisk_size=20480 no_console_suspend debug";
> - };
> -
> memory {
> device_type = "memory";
> reg = <0x80000000 0x40000000>; /* 1 GB */
next prev parent reply other threads:[~2011-12-06 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 16:49 [PATCH 2/3] arm/dts: OMAP: Remove bootargs node from board files Benoit Cousson
2011-12-06 16:49 ` Benoit Cousson
2011-12-06 18:06 ` Rob Herring [this message]
2011-12-06 18:06 ` Rob Herring
2011-12-09 0:55 ` Tony Lindgren
2011-12-09 0:55 ` Tony Lindgren
2012-01-04 20:08 ` Grant Likely
2012-01-04 20:08 ` Grant Likely
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=4EDE59B8.1070808@gmail.com \
--to=robherring2@gmail.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.