On Thu, 4 Mar 2010, Stéphane Chatty wrote: > > > 2. the addition of the device's (VendorID, ProductID) couple to a > > > black list in the hid subsystem's core, so that the new driver can > > > manage it. This involves changes in hid-ids.h and hid-core.c, for > > > every new driver. > > > > If the non upstream drivers are sucked into staging I'm not sure how > > this could be handled. Staging drivers have kconfig entries so perhaps > > those can be used to add new entries to hid, not sure if that would be > > acceptable upstream. > > Er, I'm not expert enough in kernel inclusion processes to answer this > one. I add Jiri Kosina to this reply, hoping he can help. Hi, I probably don't have full context here. Do I understand it correctly that there are HID drivers which are not upstream yet, and you are planning to have them merged into drivers/staging first, because of their code quality? If so, we'll indeed have to sort out the blacklist question somehow. Either some ifdef magic, or let userspace to unbind the driver through sysfs, or introduce some API to actually do the rebind ... What are the drivers in question anyway? Maybe we could fix them quickly instead :) Thanks, -- Jiri Kosina SUSE Labs, Novell Inc. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
