From: Bill Gatliff <bgat@billgatliff.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
Russell King <rmk@arm.linux.org.uk>,
bugme-daemon@bugzilla.kernel.org, svs1957@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 9217] New: CONFIG_CMDLINE doesn't pass to kernel
Date: Wed, 24 Oct 2007 22:35:33 -0500 [thread overview]
Message-ID: <47200F05.2050305@billgatliff.com> (raw)
In-Reply-To: <20071024195717.0de6a248.akpm@linux-foundation.org>
Andrew Morton wrote:
> 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.
>
What does the affected system's bootloader pass in r2? If it's nonzero,
ARM's 2.6.23 may interpret it as being an ATAGS pointer. And when that
happens, the system prefers the ATAGS over CONFIG_CMDLINE.
There's sanity checking in __vet_atags, but maybe it isn't enough.
Other than that, I can't see anything yet.
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2007-10-25 4:08 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 [this message]
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
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=47200F05.2050305@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=akpm@linux-foundation.org \
--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