lkml.org 
[lkml]   [2007]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [linux-usb-devel] [RFC] HID bus design overview.
    From
    Date
    Hi Jiri,

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

    at some point I thought it would be nice to have something like hiddump
    (like tcpdump), but that can be easily achieved with hcidump and usbmon
    on the lower level.

    So if hidraw claims a report id, the kernel should no longer handle it.

    Regards

    Marcel


    -
    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 16:57    [W:4.462 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site