Hello Vijaykumar, On Fri, Mar 16, 2012 at 3:44 AM, Vijaykumar Dadmode <Vijaykumar.Dadmode@xxxxxxx> wrote: > Hi, > >>>>> <Vijaykumar.Dadmode@xxxxxxx> wrote: >>> > Hi Andre, >>> > >>> >>> Hi Vijay, >> >>>> Is this implementation public anywhere? >>> >>> No its not! >>> > >>> Are you planning to make it public, or is it just an internal >>> prototype or something like this? > > It was a internal prototype, yes I can submit the code if the design is approved. > If I understood correctly your design explanation, you are re-using the HIDP module to pass the HID reports from the userspace to the kernel. This is not the architecture we were discussing initially (where we = indt and ti guys, with the bluetooth and input community), because HIDP expect to deal with 2 dedicated L2CAP sockets, one for control and the other for interruptions. Could you explain better how do you extract HoG traffic from the LE L2CAP socket and make it available to the HIDP module (supposing I've understood your architecture correctly)? -- João Paulo Rechi Vita Openbossa Labs - INdT -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
