Re: Converting MIPS to Device Tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 8, 2011 at 01:02, David VomLehn <dvomlehn@xxxxxxxxx> wrote:
> I took a look at the issue of passing device trees to the kernel and started
> by surveying the methods currently in use for passing information from the
> bootloader to the kernel. I came up with the ten approaches:
>
> How MIPS Bootloaders Pass Information to the Kernel
> ---------------------------------------------------
> Apologies for any errors; this was meant more to be a quick survey
> rather than a detailed analysis.

> 6. Â Â Âa0 - argc
> Â Â Â Âa1 - argv
> Â Â Â Âa2 - non-standard envp
> Â Â Â ÂCommand line created by concatenating argv strings, starting at
> Â Â Â Âargv[1]. The envp is a pointer to a list of char ptr to name/char
> Â Â Â Âptr pairs.
> Â Â Â ÂPlatforms: txx9

This depends on the actual boot loader. My rbtx4927 has a VxWorks boot loader,
which just doesn't pass anything.

Cfr. commit 97b0511ce125b0cb95d73b198c1bdbb3cebc4de2 ("MIPS: TXx9:
Make firmware parameter passing more robust").

Gr{oetje,eeting}s,

            Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
             Â Â -- Linus Torvalds



[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux