Re: tristate and bool not enogh for Kconfig anymore
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Date: Mon, 22 Oct 2007 11:57:27 +0100
On Mon, Oct 22, 2007 at 04:32:19PM +0600, Alexander E. Patrakov wrote:
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.
Could you please explain how this is supposed to work?
As far as I understand, the kernel initializes all built-in drivers, and
only then starts /init in initramfs (which is then supposed to start
udevd and load firmware) - but that's too late.
populate_rootfs is a rootfs_initcall which happens before all the driver
initcalls.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: tristate and bool not enogh for Kconfig anymore
- From: Alexander E. Patrakov
- Re: tristate and bool not enogh for Kconfig anymore
- References:
- [PATCH] Kconfig bug
- From: Nick Warne
- tristate and bool not enogh for Kconfig anymore
- From: Henrik Carlqvist
- Re: tristate and bool not enogh for Kconfig anymore
- From: Christoph Hellwig
- Re: tristate and bool not enogh for Kconfig anymore
- From: Alexander E. Patrakov
- [PATCH] Kconfig bug
- Prev by Date: Re: 100% iowait on one of cpus in current -git
- Next by Date: Re: [kvm-devel] severe bug in 2.6.23+ kvm.git
- Previous by thread: Re: tristate and bool not enogh for Kconfig anymore
- Next by thread: Re: tristate and bool not enogh for Kconfig anymore
- Index(es):
Relevant Pages
|