How Kernel command line parameters passed to kernel.

[Madhu K]

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 at gmail.com> wrote:

>
>
> On Thu, Jun 1, 2017 at 11:27 AM, Amit Kumar <free.amit.kumar at gmail.com>
> wrote:
>
>>
>> On Thu, Jun 1, 2017 at 11:07 AM Madhu K <madhu.sk89 at 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