[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0704051034100.4173@jikos.suse.cz>
Date: Thu, 5 Apr 2007 10:36:43 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: Adam Kropelin <akropel1@...hester.rr.com>
Cc: Li Yu <raise.sail@...il.com>, yanghong@...ss.com.cn,
linux-usb-devel <linux-usb-devel@...ts.sourceforge.net>,
hongzhiyi@...ss.com.cn, Marcel Holtmann <marcel@...tmann.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] [RFC] HID bus design overview.
On Wed, 4 Apr 2007, Adam Kropelin wrote:
> > hiddev will have to stay for quite some time, exactly because of
> > backward compatibility with userspace applications/drivers that use it
> > (I am not aware of many of them though, but apparently there are
> > some).
> Apcupsd is the one on my mind, but I believe there are others.
I am aware only of apcupsd, nut and hid2hci.
> On Apcupsd we've recently introduced a libusb-based driver that does all
> HID parsing in userspace. Not only does that free us from hiddev, it
> also frees us from the umpteen other proprietary HID interfaces across
> various platforms. Although the hiddev-based driver is still the default
> for Linux platforms, I plan to change that in the next major release and
> thus begin migrating folks off of hiddev.
Great. Do you use libusb to obtain raw hid events? Could you by any chance
look at current implementation of hidraw (it's in -mm or I can send it to
you as a separate patch) and check whether you have any comments on this?
It would be good if you could use hidraw rather than reading raw usb data
through libusb.
Thanks.
--
Jiri Kosina
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists