Messages in this thread |  | | | From | Kay Sievers <> | | Date | Wed, 29 Apr 2009 03:42:08 +0200 | | Subject | Re: Class device namespaces |
| |
On Tue, Apr 28, 2009 at 23:58, Doug Warzecha <Douglas_Warzecha@dell.com> wrote: > On Tue, Apr 28, 2009 at 07:46:57PM +0200, Kay Sievers wrote: >> On Tue, Apr 28, 2009 at 19:39, Doug Warzecha <Douglas_Warzecha@dell.com> wrote: >> >> > /sys/class/firmware/dell_rbu/loading >> > /sys/class/firmware/dell_rbu/data >> >> These pathes only ever exist for a fraction of a second, during a >> kernel initiated firmware request. This request is usually only >> handled by the udev firmware loader script, and not interesting for >> anything else. Are you replacing the udev firmware script here? Are >> you sure you do something else here? > > A Dell library writes data to those paths when a Dell BIOS Update Package is run and requests the BIOS image to be loaded into memory.
How do you do this? These paths exist for a short time only. How do you get udev out of your way handling the firmware request for you? How do you plug into the event processing with a custom tool?
Thanks, Kay
|  |