Messages in this thread | | | Subject | Re: [PATCH 2/3] firmware: Add CONFIG_BUILTIN_FIRMWARE option | From | Johannes Berg <> | Date | Sun, 25 May 2008 16:22:16 +0200 |
| |
On Sun, 2008-05-25 at 15:18 +0100, David Woodhouse wrote: > On Sun, 2008-05-25 at 16:13 +0200, Johannes Berg wrote: > > If Michael wants to serve his firmware blobs from an SQL database, > > he'd use a simple table like this: > > > > CREATE TABLE firmware ( > > ID INTEGER, > > name VARCHAR(100), > > data BLOB > > ); > > That's fairly much what the in-kernel firmware support does (just > serving firmware from a flat table using the string as a key, that is. > If I tried using SQL in-kernel you should take me out back and shoot me, > of course).
Yeah, and only that makes sense, if you ask me. And as you said in the other mail, adding a module name disambiguation policy in userspace would mean that two different modules would be allowed to both request the firmware key "foobar" and not have a problem, while it would be pretty hard to support it with the built-in firmware option.
johannes [unhandled content-type:application/pgp-signature] | |