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.
    On Tue, 3 Apr 2007, Li Yu wrote:

    > What's the position of hidraw? It only is used when all other driver is
    > not usable on some report? or, it should be stick every working device.

    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).

    > PS: In last broken "flip-flopping" resolution, the USBHID work also need
    > some changes ;)

    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,

    --
    Jiri Kosina
    -
    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-03 10:57    [W:5.660 / U:0.172 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site