lkml.org 
[lkml]   [2007]   [Apr]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [linux-usb-devel] [RFC] HID bus design overview.
Jiri Kosina wrote:
> Current implementation (as you can see it in -mm or in my hid.git tree) is
> creating hidraw interface for just every HID device/interface. But this
> will get changed before merge.
>
> Passing just everything to hidraw is not a good option, as this could lead
> to confusion and duplicating of input events (i.e. in-kernel hid driver
> processes the report and generates input_event(), and also userland driver
> obtains data from hidraw and generates input event through uinput ... not
> good).
>
>
After hearing your words, I change my implementation use hidraw as an
event filter, IOW, the HID core will handle these events which hidraw
can or need not handle. The modification is easy.

> BTW as soon as you have some presentable code, could you please send it so
> that we could see what aproach you have taken? Debating over code is
> usualy more efficient than just ranting random ideas :)
>
> Thanks,
>
>

Of course, It's no problem. but it must be tomorrow, two reasons:

1. The development PC is at my home, I am not SOHO.
2. After change from "flip-flopping", the patch need some cleaning.

Good luck.

- Li Yu

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-04-04 02:59    [W:0.188 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site