From: Jesper Krogh <jesper@krogh.cc>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Ryan Jackson <rjackson@lnxi.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Dave Olsen <dolsen@lnxi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.29-rc6
Date: Thu, 26 Feb 2009 20:46:52 +0100 [thread overview]
Message-ID: <49A6F1AC.4090305@krogh.cc> (raw)
In-Reply-To: <1235677008.8730.176.camel@macbook.infradead.org>
David Woodhouse wrote:
> On Thu, 2009-02-26 at 19:31 +0000, Jesper Krogh wrote:
>> 1) pick the distro .config
>> 2) make oldconfig
>
> So it should have been a module, not built-in?
It is a module.. and it somehow gets auto-loaded on my system. (not
listed in /etc/modules).
$ grep -i ck804xrom /boot/config-2.6.29-rc6
CONFIG_MTD_CK804XROM=m
Same in the distro .config
$ grep -i ck804xrom /boot/config-2.6.24-23-server
CONFIG_MTD_CK804XROM=m
>> 3) Let the kernel load what it think it needs.
>
> That part at least ought to be disabled -- we don't let this driver
> autoload, because unless you _know_ you need it, you don't need it.
>
> It's for overwriting your BIOS.
Oh. Thanks for your time... I'll just make sure to disable it from now on.
--
Jesper
next prev parent reply other threads:[~2009-02-26 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0902222023520.3111@localhost.localdomain>
[not found] ` <49A679E8.1010301@krogh.cc>
2009-02-26 17:17 ` MTD_CK804XROM warning (Was: Linux 2.6.29-rc6) Marcin Slusarz
2009-02-26 17:53 ` Linux 2.6.29-rc6 Linus Torvalds
2009-02-26 19:22 ` David Woodhouse
2009-02-26 19:31 ` Jesper Krogh
2009-02-26 19:36 ` David Woodhouse
2009-02-26 19:46 ` Jesper Krogh [this message]
2009-02-26 19:49 ` David Woodhouse
2009-02-26 20:53 ` Carl-Daniel Hailfinger
2009-02-26 20:32 ` Linus Torvalds
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=49A6F1AC.4090305@krogh.cc \
--to=jesper@krogh.cc \
--cc=dolsen@lnxi.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rjackson@lnxi.com \
--cc=torvalds@linux-foundation.org \
/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