Messages in this thread | | | Date | Thu, 17 Apr 2003 13:48:25 +1000 | From | 'David Gibson' <> | Subject | Re: firmware separation filesystem (fwfs) |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |