From: Arnab Basu <arnab.basu@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Passing bootargs to arm64 kernel
Date: Thu, 14 Aug 2014 14:57:21 +0530 [thread overview]
Message-ID: <53EC80F9.3060303@freescale.com> (raw)
In-Reply-To: <CAA4m1tSOcLXt2C+q4itVyuv1C9rPUqomcGm0E_8Wd0+Zb5pnbg@mail.gmail.com>
On 08/14/2014 08:04 AM, Youngmin Nam wrote:
> Thank you for reply Tom,
> Let me ask you some questions.
>
> Can we set kernel's bootargs without re-compiling device tree on arm64
> kernel by u-boot?
>
> I mean, I want to set kernel's bootargs by u-boot without re-compiling
> device tree.
>
> Is it possible?
This is done anyway, whatever is defined in CONFIG_BOOTARGS will be
stored in the U-Boot environment variable bootargs and passed as
bootargs to the kernel via the "chosen" node.
See fdt_chosen in common/fdt-support.c.
So if you want the change the bootargs passed to the kernel, just do
> set bootargs '<whatever you want in bootargs>'
at the u-boot prompt and the boot the kernel.
Thanks
Arnab
> 2014. 8. 13. ?? 7:39? "Tom Rini" <trini@ti.com>?? ??:
>
>> On Wed, Aug 13, 2014 at 11:21:32AM +0900, Youngmin Nam wrote:
>>
>>> Hello.
>>> I'm trying to find a way how to pass bootargs to arm64 kernel.
>>>
>>> In arm32 kernel, we can pass bootargs with atag from u-boot to kernel.
>> So,
>>> we can overwrite kernel's bootargs with u-boot's bootargs.
>>>
>>> But from arm64 kernel, the dtb is the only argument that should be passed
>>> from bootloader which is mandatory.
>>> you can find this contents in kernel
>>> documentation.(Documentation/arm64/Booting.txt)
>>>
>>> So, is there any way how to set bootargs by u-boot?
>>
>> Yes, within the device tree, like we do today. There's a few issues we
>> have today, but I need to re-post the booti command support patches,
>> given what's coming in 3.17 in the kernel.
>>
>> --
>> Tom
>>
prev parent reply other threads:[~2014-08-14 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 2:21 [U-Boot] Passing bootargs to arm64 kernel Youngmin Nam
2014-08-13 10:39 ` Tom Rini
2014-08-14 2:34 ` Youngmin Nam
2014-08-14 9:27 ` Arnab Basu [this message]
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=53EC80F9.3060303@freescale.com \
--to=arnab.basu@freescale.com \
--cc=u-boot@lists.denx.de \
/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.