On Tue, Mar 10, 2009 at 18:27, Leandro Dorileo <ldorileo@xxxxxxxxx> wrote: > I wrote a small kernel module to test my future implementations for > firmware loading udev ext, but I`m having problems in that regard(code > in end of the body message). > > In my module I do: > 1 - register a class(ufw_cls); > 2 - register a char device(ufwloader); > 3 - make a dev(major 240, minor 0); > 4 - create a device; > 5 - request firmware; > > When request_firmware is run the value set to $DEVPATH is > /devices/virtual/ufw_cls/ufwloader/ufwloader, shouldn`t that be > /devices/virtual/ufw_cls/ufwloader? The firmware class creates its own child device which creates the actual loading event and carries the attributes you write to. The device is named after the parent device. Usually "bus" devices, not "class" devices request firmware, and then you would also see a "/firmware/ directory in-between the bus device and the firmware-class device. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
