Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers.

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Theodore Tso <tytso@...>, Linus Torvalds <torvalds@...>, <david@...>, Marcel Holtmann <marcel@...>, David Woodhouse <dwmw2@...>, Frans Pop <elendil@...>, <jeff@...>, <arjan@...>, <akpm@...>, <alan@...>, <linux-kernel@...>
Date: Tuesday, July 15, 2008 - 9:36 pm

On Tue, Jul 15, 2008 at 08:51:33PM -0400, Theodore Tso wrote:
 > For one reason, because there's more than one mkinitrd.  FC9 ships
 > with mkinitrd 6.0.52; OpenSuSE ships with mkinitrd 2.1, and the
 > sources don't look even vaguely similar to one another.

Right. Other than name, they've historically shared nothing.
Both have grown through the evolution of multiple distros, requiring
different workarounds in each due to differences in CONFIG_ options
in the kernel between vendors for eg.

Whilst it would be great for unified development on the tools that
create the early boot process, I think it's a non-starter due to the
fact that you can't really do it without throwing out everything you
already have today.  The same reason imo, that hpa's klibc work hasn't
gained mass-appeal from vendors.

Even if we had a 'reference' mkinitrd in the kernel, it would be pretty much
useless until it reached feature parity with every distros existing tools,
and if everyone uses those instead of furthering the reference implementation,
it fails on the starting blocks.

	Dave

-- 
http://www.codemonkey.org.uk
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Dave Jones, (Tue Jul 15, 9:36 pm)
Prosaic firmware issues, Alexey Dobriyan, (Tue Jul 15, 9:11 pm)
Re: Prosaic firmware issues, Linus Torvalds, (Tue Jul 15, 9:45 pm)
Re: Prosaic firmware issues, David Woodhouse, (Wed Jul 16, 1:54 am)
Re: Prosaic firmware issues, Alexey Dobriyan, (Wed Jul 16, 10:19 am)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Henrique de Moraes Holschuh..., (Tue Jul 15, 2:05 pm)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Arjan van de Ven, (Tue Jul 15, 12:04 pm)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Benjamin Herrenschmidt, (Tue Jul 15, 1:05 am)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Benjamin Herrenschmidt, (Tue Jul 15, 1:15 am)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Arjan van de Ven, (Tue Jul 15, 12:56 am)
Re: [GIT *] Allow request_firmware() to be satisfied , Oliver Neukum, (Tue Jul 15, 2:23 am)
Re: [GIT *] Allow request_firmware() to be satisfied , Oliver Neukum, (Tue Jul 15, 12:52 pm)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Rafael J. Wysocki, (Tue Jul 15, 4:45 pm)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Rafael J. Wysocki, (Wed Jul 16, 5:28 pm)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Rafael J. Wysocki, (Thu Jul 17, 4:42 pm)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Rafael J. Wysocki, (Thu Jul 17, 6:25 pm)
Re: [GIT *] Allow request_firmware() to be satisfied from in..., Rafael J. Wysocki, (Tue Jul 15, 7:45 pm)