From: Michael Buesch <mb@bu3sch.de>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: [PATCH] MODULE_FIRMWARE for binary firmware(s)
Date: Tue, 29 Aug 2006 18:30:25 +0200 [thread overview]
Message-ID: <200608291830.26033.mb@bu3sch.de> (raw)
In-Reply-To: <44F3A355.6090408@flower.upol.cz>
On Tuesday 29 August 2006 04:15, Oleg Verych wrote:
> James Bottomley wrote:
> > On Tue, 2006-08-29 at 02:35 +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.
> >
> >
> > I er don't think so.
> >
> 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,
Please tell me how this is going to work, if we don't
know which firmware (version) is needed before be actually
initialize the device?
--
Greetings Michael.
next prev parent reply other threads:[~2006-08-29 16:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 22:08 [PATCH] MODULE_FIRMWARE for binary firmware(s) James Bottomley
2006-08-28 22:11 ` James Bottomley
2006-08-28 23:04 ` Sven Luther
2006-08-28 23:50 ` James Bottomley
2006-08-29 0:35 ` Oleg Verych
2006-08-28 23:55 ` James Bottomley
2006-08-29 2:15 ` Oleg Verych
[not found] ` <20060829015103.GA28162@kroah.com>
[not found] ` <20060829031430.GA9820@flower.upol.cz>
2006-08-29 2:49 ` Greg KH
2006-08-29 4:19 ` Oleg Verych
2006-08-29 15:46 ` David Lang
2006-08-29 18:32 ` Greg KH
2006-08-29 19:04 ` Michael Buesch
2006-08-29 20:13 ` Olaf Hering
2006-08-29 20:42 ` David Lang
2006-08-29 20:52 ` Greg KH
2006-08-30 5:44 ` Olaf Hering
2006-08-30 17:52 ` David Lang
2006-08-30 18:13 ` Sven Luther
2006-08-30 18:20 ` David Lang
2006-08-30 19:15 ` Sven Luther
2006-08-30 19:34 ` David Lang
2006-08-30 20:57 ` Sven Luther
2006-08-30 21:11 ` David Lang
2006-08-31 1:16 ` Jim Crilly
2006-09-15 19:48 ` Olaf Hering
2006-08-29 16:30 ` Michael Buesch [this message]
2006-08-29 13:13 ` Marcel Holtmann
2006-08-29 20:16 ` Greg KH
2006-08-30 13:49 ` Marcel Holtmann
[not found] <6OXsW-4pW-7@gated-at.bofh.it>
[not found] ` <6Peat-82q-17@gated-at.bofh.it>
[not found] ` <6PgFh-53l-7@gated-at.bofh.it>
[not found] ` <6Ph8l-61I-9@gated-at.bofh.it>
2006-08-29 22:10 ` Bodo Eggert
-- strict thread matches above, loose matches on Subject: below --
2006-04-18 23:41 Jon Masters
2006-04-18 23:01 ` David Lang
2006-04-19 0:15 ` Jon Masters
2006-04-18 23:41 ` David Lang
2006-04-19 1:07 ` Jon Masters
2006-04-19 9:07 ` Duncan Sands
2006-04-19 12:41 ` Jon Masters
2006-04-19 15:32 ` Duncan Sands
2006-04-19 15:45 ` Jon Masters
2006-07-29 19:05 ` Jon Masters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608291830.26033.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox