From: Nikolai Kondrashov <spbnick@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Alan Ott <alan@signal11.us>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] HID: Report Descriptor in Sysfs
Date: Fri, 21 Jan 2011 23:03:38 +0300 [thread overview]
Message-ID: <4D39E69A.5090107@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1101211607290.5725@pobox.suse.cz>
On 01/21/2011 06:09 PM, Jiri Kosina wrote:
> There were also efforts to make the report descriptor replaceable in a
> request_firmware() way, but that never converged to state in which it
> could be applied IIRC.
I remember seeing messages about it, but couldn't find it.
Do you have any pointers?
I'm interesting in seeing if it's worth it and maybe finishing it.
Thanks :)
Sincerely,
Nick
next prev parent reply other threads:[~2011-01-21 20:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 6:19 [PATCH 0/1] HID: Report Descriptor in Sysfs Alan Ott
2011-01-21 6:19 ` [PATCH 1/1] hid: Add HID Report Descriptor to sysfs Alan Ott
2011-01-22 13:55 ` Greg KH
2011-01-23 22:35 ` [PATCH v2 0/1] HID: Report Descriptor in Sysfs Alan Ott
2011-01-23 22:35 ` [PATCH v2 1/1] hid: Add HID Report Descriptor to sysfs Alan Ott
2011-01-23 22:59 ` Greg KH
2011-01-24 0:36 ` [PATCH v3 0/1] HID: Report Descriptor in Sysfs Alan Ott
2011-01-24 0:36 ` [PATCH v3 1/1] hid: Add HID Report Descriptor to sysfs Alan Ott
2011-01-24 3:50 ` [PATCH v4 0/1] HID: Report Descriptor in Sysfs Alan Ott
2011-01-24 3:50 ` Alan Ott
2011-02-16 4:11 ` Alan Ott
2011-02-17 12:26 ` Jiri Kosina
2011-01-24 3:50 ` [PATCH v4 1/1] hid: Add HID Report Descriptor to sysfs Alan Ott
2011-01-24 3:50 ` Alan Ott
2011-02-17 12:55 ` Antonio Ospite
2011-01-21 9:59 ` [PATCH 0/1] HID: Report Descriptor in Sysfs Jiri Kosina
2011-01-21 14:52 ` Alan Ott
2011-01-21 15:09 ` Jiri Kosina
2011-01-21 15:29 ` Alan Ott
2011-01-21 16:14 ` Jiri Kosina
2011-01-21 16:57 ` Alan Ott
2011-01-21 20:03 ` Nikolai Kondrashov [this message]
2011-01-24 15:17 ` Jiri Kosina
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=4D39E69A.5090107@gmail.com \
--to=spbnick@gmail.com \
--cc=alan@signal11.us \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.