From: Jiri Slaby <jirislaby@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
Anssi Hannula <anssi.hannula@gmail.com>,
linux-input@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
mit-devel@lists.printk.net, linux-kernel@vger.kernel.org
Subject: Re: HID bus
Date: Tue, 22 Apr 2008 01:05:28 +0200 [thread overview]
Message-ID: <480D1DB8.20109@gmail.com> (raw)
In-Reply-To: <20080421133621.GA27646@anvil.corenet.prv>
On 04/21/2008 03:36 PM, Dmitry Torokhov wrote:
> On Mon, Apr 21, 2008 at 11:25:43AM +0200, Jiri Kosina wrote:
>> On Sun, 20 Apr 2008, Anssi Hannula wrote:
>>
>>> Why not just do something like
>>>
>>> #define HID_DEVICE(vend, dev) \
>>> .match_flags = USB_DEVICE_ID_MATCH_DEVICE | \
>>> USB_DEVICE_ID_MATCH_INT_CLASS, \
>>> .idVendor = (vend), \
>>> .idProduct = (prod), \
>>> .bInterfaceClass = USB_INTERFACE_CLASS_HID
>>> (see linux/usb.h)
>>>
>>> and use USB hotplugging?
>>> Or do we plan to match against something else as well, such as hid
>>> reports or something?
>> No, we plan to do matching based solely on VID/PID. The report-specific
>> stuff is then handled between the specific driver and HID generic code.
>>
>
> Hmm, [ab]using USB modalias makes me a bit uneasy. What about bluetooth
> HID devices?
I do agree, it won't be nice and abstract enough. Working on it, give me some
time, please.
prev parent reply other threads:[~2008-04-21 23:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0804181333180.12972@jikos.suse.cz>
2008-04-19 22:38 ` Jiri Slaby
2008-04-20 11:57 ` Jiri Slaby
2008-04-22 0:00 ` Jiri Kosina
2008-04-27 11:22 ` Jiri Slaby
2008-05-09 21:24 ` Jiri Slaby
2008-04-20 16:15 ` Anssi Hannula
2008-04-20 18:07 ` Jiri Slaby
2008-04-21 9:25 ` Jiri Kosina
2008-04-21 13:36 ` Dmitry Torokhov
2008-04-21 23:05 ` Jiri Slaby [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=480D1DB8.20109@gmail.com \
--to=jirislaby@gmail.com \
--cc=anssi.hannula@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mit-devel@lists.printk.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome