From: "'David Gibson'" <david@gibson.dropbear.id.au>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
"'ranty@debian.org'" <ranty@debian.org>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: firmware separation filesystem (fwfs)
Date: Thu, 17 Apr 2003 13:48:25 +1000 [thread overview]
Message-ID: <20030417034825.GG9219@zax> (raw)
In-Reply-To: <A46BBDB345A7D5118EC90002A5072C780C262E38@orsmsx116.jf.intel.com>
On Wed, Apr 16, 2003 at 07:00:00PM -0700, Perez-Gonzalez, Inaky wrote:
>
> > From: David Gibson [mailto:david@gibson.dropbear.id.au]
> >
> > Incidentally another approach that also avoids nasty ioctl()s would be
> > to invoke the userland helper with specially set up FD 1, which lets
> > the kernel capture the program's stdout.
>
> I think this makes too many assumptions specially taking into
> account that most hotplug stuff are shell scripts - they are
> probably going to be writing all kinds of stuff to stdout.
>
> With the risk of repeating myself (again) and being a PITA,
> I really think it'd be easier to copy the firmware file to a
> /sysfs binary file registered by the device driver during
> initialization; then the driver can wait for the file to be
> written with a valid firmware before finishing the init
> sequence. The infrastructure is already there (or isn't ...
> is it?).
Well, I guess that would be basically what I mean by an equivalent
sysfs thing. I haven't looked at the binary file support in sysfs, as
yet.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
next prev parent reply other threads:[~2003-04-17 3:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 2:00 firmware separation filesystem (fwfs) Perez-Gonzalez, Inaky
2003-04-17 3:31 ` Manuel Estrada Sainz
2003-04-17 4:06 ` Greg KH
2003-04-17 3:48 ` 'David Gibson' [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-17 4:07 Perez-Gonzalez, Inaky
2003-04-17 0:17 Perez-Gonzalez, Inaky
2003-04-16 0:57 Manuel Estrada Sainz
2003-04-16 11:31 ` Alan Cox
2003-04-16 14:46 ` David Gibson
2003-04-16 16:36 ` Manuel Estrada Sainz
2003-04-16 15:47 ` Alan Cox
2003-04-16 16:57 ` Riley Williams
2003-04-17 13:43 ` Alan Cox
2003-04-17 13:43 ` Alan Cox
2003-04-17 1:23 ` David Gibson
2003-04-17 13:12 ` Alan Cox
2003-04-19 20:41 ` Manuel Estrada Sainz
2003-04-19 21:52 ` Alan Cox
2003-04-20 19:26 ` Manuel Estrada Sainz
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=20030417034825.GG9219@zax \
--to=david@gibson.dropbear.id.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranty@debian.org \
/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;
as well as URLs for NNTP newsgroup(s).