Hi!But it does not work, and as you demonstrated, getting it to work w/o preloading is awful lot of work. Feel free to send a patch. Unless you are ready to do that, stop confusing driver authors. Firmware loader is complex userspace process. That's not silly. It is userland, and I'd hate to explain to its authors detailed rules. It could do 'find / -name "pcmcia-card-firmware"' for example. It could do dbus message to tell gnome-graphical-crap to display window to say that it is loading firmware. Maybe it also writes to syslog when syslogd is available. It is userland process, so it is allowed to do stupid stuff. [If you do not agree, please try to write up "Doc*/what-firmware-loader-must-do.txt" -- at that point you should realize how ugly the solution you are suggesting is.] Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -
| Jon Smirl | 463 kernel developers missing! |
| Nigel Cunningham | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Greg KH | Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interface for on access scan... |
| Jeff Garzik | Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series.. |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Linus Torvalds | Re: [GIT]: Networking |
| Evgeniy Polyakov | Re: [BUG] New Kernel Bugs |
