On Sun, Feb 27, 2011 at 01:30:40AM +0800, Shawn Guo wrote:
> I'm still a little bit new to dt. I thought the bootargs in chosen
> node will always apply when dt is enabled. It just took me some time
> to figure out that u-boot 'bootargs' env will anyway overwrite the
> one from chosen.
Correct;
Dear Shawn Guo,
In message <20110228013558.ga3...@s2100-06.ap.freescale.net> you wrote:
>
> Yes, understood. Usually, we have u-boot bootargs env saved to play
> with non-dt kernel, so it is there for most cases. And I
> instinctively thought that bootargs from chosen node will be applied
> when
On Sun, Feb 27, 2011 at 05:09:13PM +0100, Wolfgang Denk wrote:
> Dear Shawn Guo,
>
Hi Wolfgang,
> In message <20110226173040.gd2...@s2100-06.ap.freescale.net> you wrote:
> > I'm still a little bit new to dt. I thought the bootargs in chosen
> > node will always apply when dt is enabled. It just
Dear Shawn Guo,
In message <20110226173040.gd2...@s2100-06.ap.freescale.net> you wrote:
> I'm still a little bit new to dt. I thought the bootargs in chosen
> node will always apply when dt is enabled. It just took me some time
> to figure out that u-boot 'bootargs' env will anyway overwrite the
I'm still a little bit new to dt. I thought the bootargs in chosen
node will always apply when dt is enabled. It just took me some time
to figure out that u-boot 'bootargs' env will anyway overwrite the
one from chosen.
static int bootm_linux_fdt(int machid, bootm_headers_t *images)
{
..
