On Thu, 2007-10-25 at 22:54 +0100, Richard Purdie wrote:
quoted text
> On Thu, 2007-10-25 at 13:02 -0700, Andrew Morton wrote:
> > It was in the inital report, at
> > http://bugzilla.kernel.org/show_bug.cgi?id=9217 :
>
> This is the commandline they wanted to use, not the one that was
> actually used. The one that was used should appear on the console, on
> the serial console if they have the lead or in dmesg when the device
> boots. We know it probably contained root=/dev/mtdblock2 but thats it.
> 
> I'd like to confirm which commandline is appearing since if we know
> which one it is we might stand a chance of knowing where it came from,
> until then this is just a guessing game.

There was a followup in the bugzilla:

quoted text
> I use u-boot to boot kernel.
> When kernel >=2.6.23 boot it use u-boot default bootparam:
> console=ttyS0,115200 console=tty1 root=/dev/mtdblock2 rootfstype=jffs2
> Now I try to change it in u-boot source.
>
> kernel 2.6.22.9 change default u-boot boot params to what I set in
> CONFIG_CMDLINE But 2.6.23 and later doesn't

So its not the standard bootloader, its one which passes an ATAG
commandline and 2.6.23 onwards uses an ATAG commandline if present over
the compiled in commandline.

My opinion is that this is a feature. Recompile the bootloader without
the commandline if you want to use the one compiled into the kernel.

This is going to be useful in the future when booting Zaurus kernels
with kexec since it means we can customise the commandline through the
ATAGs.

Cheers,

Richard

-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/