From: Christoph Hellwig <hch@infradead.org>
To: Henrik Carlqvist <hc1@poolhem.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tristate and bool not enogh for Kconfig anymore
Date: Mon, 22 Oct 2007 11:11:08 +0100 [thread overview]
Message-ID: <20071022101107.GA20690@infradead.org> (raw)
In-Reply-To: <20071020144238.4f258c8c.hc1@poolhem.se>
On Sat, Oct 20, 2007 at 02:42:38PM +0200, Henrik Carlqvist wrote:
> I think there is a need for Kconfig to specify that a functionality could
> be built as a module or not built at all.
>
> Some drivers require that firmware is loaded when the driver is
> initialized. The kernel has functionalities for this by using a userspace
> program. However, this userspace program is only usable from modules and
> not during boot while any initrd or any other file system has not yet been
> mounted and yet less any processes started.
That's wrong. You can load firmware from the initramfs even if the
driver is built in. There is no valid reason why a driver shouldn't
be allowed to be built in.
next prev parent reply other threads:[~2007-10-22 10:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 11:57 [PATCH] Kconfig bug Nick Warne
2007-10-20 12:42 ` tristate and bool not enogh for Kconfig anymore Henrik Carlqvist
2007-10-20 19:17 ` Sam Ravnborg
2007-10-20 21:56 ` Randy Dunlap
2007-10-21 4:47 ` Valdis.Kletnieks
2007-10-21 10:24 ` Henrik Carlqvist
2007-10-21 16:45 ` Randy Dunlap
2007-10-21 20:42 ` Henrik Carlqvist
2007-10-21 21:03 ` Sam Ravnborg
2007-10-22 0:47 ` Randy Dunlap
2007-10-22 3:14 ` Randy Dunlap
2007-10-22 4:42 ` Randy Dunlap
2007-10-27 23:37 ` Roman Zippel
2007-10-22 10:11 ` Christoph Hellwig [this message]
2007-10-22 10:32 ` Alexander E. Patrakov
2007-10-22 10:57 ` Christoph Hellwig
2007-10-22 11:27 ` Alexander E. Patrakov
2007-10-22 12:53 ` Christoph Hellwig
2007-10-22 13:18 ` Alexander E. Patrakov
2007-10-22 11:46 ` Helge Hafting
2007-10-22 21:50 ` Henrik Carlqvist
2007-10-27 12:26 ` [PATCH] Kconfig bug Nick Warne
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=20071022101107.GA20690@infradead.org \
--to=hch@infradead.org \
--cc=hc1@poolhem.se \
--cc=linux-kernel@vger.kernel.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