RE: firmware separation filesystem (fwfs)

Perez-Gonzalez, Inaky (inaky.perez-gonzalez@intel.com)
Wed, 16 Apr 2003 19:00:00 -0700


> 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?).

CU,

Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own
(and my fault)
-
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/