Date: Mon, 22 Oct 2007 11:57:27 +0100
From: Christoph Hellwig <hch@infradead.org>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
Cc: Christoph Hellwig <hch@infradead.org>, Henrik Carlqvist <hc1@poolhem.se>,
       linux-kernel@vger.kernel.org
Subject: Re: tristate and bool not enogh for Kconfig anymore
Message-ID: <20071022105727.GA22181@infradead.org>
References: <200710201257.55616.nick@ukfsn.org> <20071020144238.4f258c8c.hc1@poolhem.se> <20071022101107.GA20690@infradead.org> <471C7C33.4090003@ums.usu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <471C7C33.4090003@ums.usu.ru>
User-Agent: Mutt/1.4.2.3i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 835
Lines: 18

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/