* How Kernel command line parameters passed to kernel.
@ 2017-06-01 5:37 Madhu K
2017-06-01 5:57 ` Amit Kumar
0 siblings, 1 reply; 4+ messages in thread
From: Madhu K @ 2017-06-01 5:37 UTC (permalink / raw)
To: kernelnewbies
Hi All,
I have a doubt, how kernel command line parameters are passed to kernel
space. Before device tree, we used to pass command line parameters using
ATAGS. But after device tree we are not using ATAGS. How we are passing
command line parameters to kernel space?
Thanks & regards,
Madhu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170601/4f668d64/attachment.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* How Kernel command line parameters passed to kernel.
2017-06-01 5:37 How Kernel command line parameters passed to kernel Madhu K
@ 2017-06-01 5:57 ` Amit Kumar
2017-06-01 6:15 ` Madhu K
0 siblings, 1 reply; 4+ messages in thread
From: Amit Kumar @ 2017-06-01 5:57 UTC (permalink / raw)
To: kernelnewbies
On Thu, Jun 1, 2017 at 11:07 AM Madhu K <madhu.sk89@gmail.com> wrote:
> Hi All,
>
> I have a doubt, how kernel command line parameters are passed to kernel
> space. Before device tree, we used to pass command line parameters using
> ATAGS. But after device tree we are not using ATAGS. How we are passing
> command line parameters to kernel space?
>
If you are using uboot, please consult uEnv.txt docs.
http://linux-sunxi.org/UEnv.txt
>
> Thanks & regards,
> Madhu
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170601/e9f7ce86/attachment-0001.html
-------------- next part --------------
kernel_file=zImage
fdtfile=am335x-boneblack.dtb
loadzimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} ${fdtfile}
console=ttyO0,115200n8
mmcroot=/dev/mmcblk0p2 ro
mmcrootfstype=ext4 rootwait
mmcargs=setenv bootargs console=${console} root=${mmcroot} rootfstype=${mmcrootfstype} ${optargs}
uenvcmd=run loadzimage; run loadfdt; run mmcargs; bootz ${loadaddr} - ${fdtaddr}
^ permalink raw reply [flat|nested] 4+ messages in thread
* How Kernel command line parameters passed to kernel.
2017-06-01 5:57 ` Amit Kumar
@ 2017-06-01 6:15 ` Madhu K
2017-06-01 7:00 ` Madhu K
0 siblings, 1 reply; 4+ messages in thread
From: Madhu K @ 2017-06-01 6:15 UTC (permalink / raw)
To: kernelnewbies
On Thu, Jun 1, 2017 at 11:27 AM, Amit Kumar <free.amit.kumar@gmail.com>
wrote:
>
> On Thu, Jun 1, 2017 at 11:07 AM Madhu K <madhu.sk89@gmail.com> wrote:
>
>> Hi All,
>>
>> I have a doubt, how kernel command line parameters are passed to kernel
>> space. Before device tree, we used to pass command line parameters using
>> ATAGS. But after device tree we are not using ATAGS. How we are passing
>> command line parameters to kernel space?
>>
>
> If you are using uboot, please consult uEnv.txt docs.
> http://linux-sunxi.org/UEnv.txt
>
>>
>>
This is at U-boot level. where u-boot will write this information?
> Thanks & regards,
>> Madhu
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170601/045bc02e/attachment.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* How Kernel command line parameters passed to kernel.
2017-06-01 6:15 ` Madhu K
@ 2017-06-01 7:00 ` Madhu K
0 siblings, 0 replies; 4+ messages in thread
From: Madhu K @ 2017-06-01 7:00 UTC (permalink / raw)
To: kernelnewbies
I Found the answer.
The chosen node does not represent a real device, but serves as a place
for passing data between firmware and the operating system, like boot
arguments. Data in the chosen node does not represent the hardware
In the above paragraph, boot arguments are nothing but "kernel command
line" arguments.
Thanks
Madhu
On Thu, Jun 1, 2017 at 11:45 AM, Madhu K <madhu.sk89@gmail.com> wrote:
>
>
> On Thu, Jun 1, 2017 at 11:27 AM, Amit Kumar <free.amit.kumar@gmail.com>
> wrote:
>
>>
>> On Thu, Jun 1, 2017 at 11:07 AM Madhu K <madhu.sk89@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> I have a doubt, how kernel command line parameters are passed to kernel
>>> space. Before device tree, we used to pass command line parameters using
>>> ATAGS. But after device tree we are not using ATAGS. How we are passing
>>> command line parameters to kernel space?
>>>
>>
>> If you are using uboot, please consult uEnv.txt docs.
>> http://linux-sunxi.org/UEnv.txt
>>
>>>
>>>
> This is at U-boot level. where u-boot will write this information?
>
>
>> Thanks & regards,
>>> Madhu
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170601/0df568d1/attachment.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-06-01 7:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-01 5:37 How Kernel command line parameters passed to kernel Madhu K
2017-06-01 5:57 ` Amit Kumar
2017-06-01 6:15 ` Madhu K
2017-06-01 7:00 ` Madhu K
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.