On Thu, 12 Apr 2007, Paul Walmsley wrote: > Now, another implementation approach would be to get rid of the quirk > type names entirely, to use a path such as: > > /usbhid/quirks_runtime/<vendor_id>:<product_id> > > with the last component being a r/w configfs attribute containing the quirks > value. Is that what you are proposing? I considered it when I did the > initial implementation. The problem with it is that there seems to be no way > for userspace to create new configfs files/attributes -- only configfs > directories.
Yes, this was my very original thought - I really somehow don't think that having to duplicate every new quirk is a nice solution. Joel, is there any specific reason why configfs doesn't allow this please? Or we could reconsider going back to the idea of using sysfs. Thanks a lot, -- Jiri Kosina SUSE Labs
