[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200805252053.36854.mb@bu3sch.de>
Date: Sun, 25 May 2008 20:53:36 +0200
From: Michael Buesch <mb@...sch.de>
To: Marcel Holtmann <marcel@...tmann.org>
Cc: Johannes Berg <johannes@...solutions.net>,
David Woodhouse <dwmw2@...radead.org>,
Sam Ravnborg <sam@...nborg.org>, linux-kernel@...r.kernel.org,
aoliva@...hat.com, alan@...rguk.ukuu.org.uk,
Abhay Salunke <Abhay_Salunke@...l.com>, kay.sievers@...y.org,
Takashi Iwai <tiwai@...e.de>
Subject: Re: [PATCH 2/3] firmware: Add CONFIG_BUILTIN_FIRMWARE option
On Sunday 25 May 2008 20:46:00 Marcel Holtmann wrote:
> we can change these things. We do it all the time.
Doing something stupid all the time is not that of a good idea.
> Again, I don't plan to break any setup. I actually do think it is a
> good idea to group firmware files in subdirectories in /lib/firmware,
> but this subdirectory name doesn't belong in the kernel.
>
> We will update udev to read the driver name and look into /lib/
> firmware/<driver>/<filename> and /lib/firmware/<filename> for the
> firmware file.
>
> Then we will set a date and note it in the future remove document.
> Something like 12 month after an updated udev has been released. This
> gives the distribution two generations time to update udev and kernel
> packages.
How are you going to handle multiple versions of the firmware for one driver?
How does one switch between versions (changing config files is not acceptable)?
--
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists