On Monday 04 February 2008 18:01:31 Greg KH wrote: > > LEDs -> These should conveniently be accessed in a standard way > > through the LED triggers. So you could map some crazy functions > > to the LEDs. Like your HDD LED, or your mail notification. > > I really like that. :) > > I think we have a LED subsystem already. Take a look at drivers/leds/
Yeah, I was talking about using exactly that existing LED subsystem. > > Firmware upload -> Not sure. Do we already have some generic device firmware > > update API/subsystem? > > Yes, we already have a firmware interface within the kernel, that's been > standard for a number of years now. See include/linux/firmware.h Yeah, well. But this is different. This interface is for devices that need to load a firmware on initialization. This mouse has the fw flashed onto the device. So the driver doesn't need it on init. We rather need an interface here, over which the user can reflash this firmware. So no request_firmware() interface is needed, which the driver has to call. So this is the other way around. The user will write the fw to the hardware and it will permanently be stored. -- Greetings Michael. - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
