On Mon, May 17, 2010 at 10:58 PM, sunil pillai <sunilpillai....@gmail.com> wrote: > 1. So I hope it's clear that userspace is not creating any hid event. > We are still talking about USB HID REPORTS received in the userspace > BT stack. > 2. So I hope it makes it obvious now that once my userspace BT stack > parses the BT packet and gets the USB HID CLASS REPORT, it needs to be > sent to the kernel for further parsing.
Ok, that makes sense. But why not just use the Bluez Bluetooth stack instead of your own? That would solve your problem, right? If not, then you will need to add such an interface to the kernel, if the input maintainers accept it. But note that you are doing something that duplicates an already-present functionality in the kernel, you will probably not get it accepted. So try to use the in-kernel bluetooth stack instead, that will solve your issue. Also note that the Linux input mailing list would have been the proper place for this query. That is where the proper developers are for this subsystem. Just look in the MAINTAINERS file in the kernel for the email address. good luck, greg k-h -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
