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 don't see such code in the kernel at this time. So it's not a
> solution, sorry.
>
I know. return -ENOPATCH
"No amount of clever coding can ever make up for a poor design.
Conversely, a well-architected system can tolerate a lot of sloppy
coding. In a society where organizations are increasingly filled with
more inexperienced workers whose salaries don't frag down the bottom
line, you have to expect some sloppy coding, so the design becomes
even more important."
-- rbsjrx <[EMAIL PROTECTED]>
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 ;).
Thanks.
--
-o--=O`C /. .\ (+)
#oo'L O o |
<___=E M ^-- | (you're barking up the wrong tree)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
