Hi Ivan, Tom, Felix and all other iSight users. On Thursday 08 November 2007, Felix Möller wrote: > Hi, > > >> But as we currently stand everything works so nicely as it is. Why > >> should we have to spend precious time to port all of it to user > >> land, read on how to write udev rules, bash scripts and what the > >> best solution for distributions will be in terms of all of that. > >> > >> :-( > > > > I think usability is also an argument. For a user it is already > > complex enough to install the driver without firmware, scripts etc. I > > think it is better to have a solution, that "just works" and can be > > handled by users easily in contrast to an very clean solutions noone > > understands. > > yes I think so too. > > And I think firmware loading from the kernel is not that uncommon the > new intel wlan driver iwlwifi loads its firmware too.
EZ-USB firmware loading have traditionally been done in userspace. The fxload utility has been designed for that purpose. I'm also not keen on adding a dependency on SHA1 to the Linux UVC driver, especially if only one buggy device requires it. Moving code from userspace to kernelspace doesn't really goes in the general direction Linux is taking today. I'm however ready to consider kernelspace EZ-USB firmware loading, but that should be made generic as other drivers might then be interested. If you're ok with this approach, I think the issue should be raised on the linux-usb-devel mailing list. People there are more aware of the USB firmware loading issues than I am, and I'll trust their judgement regarding this issue. Cheers, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
