From: <mwester@dls.net>
To: Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.arm.linux.org.uk,
Russell King <rmk@arm.linux.org.uk>,
Bill Gatliff <bgat@billgatliff.com>
Cc: svs1957@gmail.com, bugme-daemon@bugzilla.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 9217] New: CONFIG_CMDLINE doesn't pass to kernel
Date: Thu, 25 Oct 2007 00:26:54 -0500 [thread overview]
Message-ID: <20071025052654.04A665C@demolition.dls.net> (raw)
In-Reply-To: <20071024195717.0de6a248.akpm@linux-foundation.org>
> On Wed, 24 Oct 2007 05:32:14 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=9217
> >
> >            Summary: CONFIG_CMDLINE doesn't pass to kernel
> >            Product: Other
> >            Version: 2.5
> >      KernelVersion: 2.6.23
> >           Platform: All
> >         OS/Version: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: high
> >           Priority: P1
> >          Component: Other
> >         AssignedTo: other_other@kernel-bugs.osdl.org
> >         ReportedBy: svs1957@gmail.com
> >
> >
> > Most recent kernel where this bug did not occur:2.6.24-rc1
> > Distribution: Debian Armel (arm with EABI)
> > Hardware Environment: Sharp Zaurus 750 (ARM pxa255)
> > Software Environment: Debian
> > Problem Description:
> > I try to upgrade kernel from 2.6.22.9 to 2.6.23.
> > 2.6.22.9 works correct. Kernel 2.6.23 doesn't use  CONFIG_CMDLINE and doesn't
> > pass bootparams:
> > CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd
> > root=/dev/mmcblk0p1 rootfstype=ext3 rw rootdelay=5"
> > But kernel still try to mount /dev/mtdblock2 using jffs2.
> > Steps to reproduce:
> > Compile kernel with CONFIG_CMDLINE and try to boot.
> >
> >
>
> Something broke CONFIG_CMDLINE of ARM (at least) between 2.6.22 and 2.6.23.
>
> I don't know whether it was an ARM patch one of those kernel-wide changes.
> We have futzed with the command-line parsing a bit recently, but the 2.6.23
> changelog doesn't suggest anything obvious.
I think the zaurus kernel deliberately ignored the bootparams passed in by the device's bootloader. The 2.6.23 kernel now honors the r2 setting from the bootloader, which is most likely pointing to those ATAGs that were being ignored earlier.
I suppose you can hack up the logic in setup.c where the ATAGs are parsed, but it seems to me that it would be better to work out some logic, perhaps in the fixup section for that machine, to do whatever is necessary to override or otherwise get along with the bootloader.
Mike (mwester)
prev parent reply other threads:[~2007-10-25 6:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9217-10286@http.bugzilla.kernel.org/>
2007-10-25 2:57 ` [Bugme-new] [Bug 9217] New: CONFIG_CMDLINE doesn't pass to kernel Andrew Morton
2007-10-25 3:35 ` Bill Gatliff
2007-10-25 12:23 ` Lennert Buytenhek
2007-10-25 13:43 ` Richard Purdie
2007-10-25 20:02 ` Andrew Morton
2007-10-25 21:54 ` Richard Purdie
2007-10-28 22:46 ` Richard Purdie
2007-10-28 22:53 ` Russell King
2007-10-25 5:26 ` mwester [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071025052654.04A665C@demolition.dls.net \
--to=mwester@dls.net \
--cc=akpm@linux-foundation.org \
--cc=bgat@billgatliff.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=svs1957@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox