On Friday, March 16, 2012 10:57:38 AM Marcel Holtmann wrote: > Hi Joao, > > > > I have hacked together a small driver which allows user-space I/O > > > drivers to provide HID devices. This is needed for > > > Bluetooth-Low-Energy HID devices as the Bluetooth-LE protocol is > > > parsed in user-space. > > > > > > I have only compile-tested this driver, I haven't run it yet. It's > > > just an proposal how this could be implemented. It should also work > > > as hint to the BT-LE developers how such an interface will > > > look-like. > > > > First of all, thanks for your effort. I haven't looked at the code > > yet, but thinking again about the problem and since it's very similar > > to uinput, would adding another ioctl to uinput that receives the HID > > descriptor and put uinput in a "HID mode" be sufficient? This way we > > could increase code reuse and ease maintainance, I guess. What do you > > think? > > I am really against this. Input subsystem and HID subsystem are two > different things. Don't try to combine them. > > You would also mess up the layering here. HID uses input, but input does > not require HID. > Completely agree with Marcel here. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
