Greg KH wrote:
On Tue, Aug 29, 2006 at 05:14:30AM +0200, Oleg Verych wrote:On Mon, Aug 28, 2006 at 06:51:03PM -0700, Greg KH wrote:On Tue, Aug 29, 2006 at 04:15:49AM +0200, Oleg Verych wrote:request_firmware() is dead also. YMMV, but three years, and there are still big chunks of binary in kernel. And please don't add new useless info _in_ it.Hell, what can be as easy as this: ,- |modprobe $drv |(dd </lib/firmware/$drv.bin>/dev/blobs && echo OK) || echo Error `- where /dev/blobs is similar to /dev/port or even /dev/null char device. if synchronization is needed, add `echo $drv >/dev/blobs`, remove modprobe,
...
I'm nether a CS nor software engineer, just wondering why simple thing isn't simple _in_ the Kernel. I'm reading list "just for fun (C)" and any good word about this (IMHO) unix-way design *may* lead professional programmers to do tiny worthy things (think about kevent discussion). If it's (i'm) stupid, please, say so (in the way Nicholas Miell did ;).I don't think it's workable, and goes against the current way the kernel does things. But please, feel free to prove me wrong with a patch otherwise. I don't want to debate it otherwise.
Thanks, and OK, this is my last reply on this.
I think the current way we handle firmware works quite well, especially given the wide range of different devices that it works for (everything from BIOS upgrades to different wireless driver stages).
Oh, come on, even skilled developers (not particular kernel's) having difficulties with current hotplug-sysfs-modprobe thing; in this case one couldn't easily figure out problems and way to solve them <http://permalink.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/5444> Goodbye. -- -o--=O`C /. .\ (+) #oo'L O o | <___=E M ^-- | (you're barking up the wrong tree)