From: Jiri Kosina <jkosina@suse.cz>
To: Paul Walmsley <paul@booyaka.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
Joel Becker <joel.becker@oracle.com>
Subject: Re: [PATCH 0/7] usbhid: quirks cleanup, add dynamic quirks, ConfigFS interface
Date: Thu, 12 Apr 2007 18:51:03 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0704121832020.19492@jikos.suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0704120945571.9207@utopia.booyaka.com>
On Thu, 12 Apr 2007, Paul Walmsley wrote:
> Now, another implementation approach would be to get rid of the quirk
> type names entirely, to use a path such as:
>
> /usbhid/quirks_runtime/<vendor_id>:<product_id>
>
> with the last component being a r/w configfs attribute containing the quirks
> value. Is that what you are proposing? I considered it when I did the
> initial implementation. The problem with it is that there seems to be no way
> for userspace to create new configfs files/attributes -- only configfs
> directories.
Yes, this was my very original thought - I really somehow don't think that
having to duplicate every new quirk is a nice solution. Joel, is there any
specific reason why configfs doesn't allow this please?
Or we could reconsider going back to the idea of using sysfs.
Thanks a lot,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2007-04-12 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 6:49 [PATCH 0/7] usbhid: quirks cleanup, add dynamic quirks, ConfigFS interface Paul Walmsley
2007-04-11 12:49 ` Jiri Kosina
2007-04-11 14:37 ` Jiri Kosina
2007-04-11 18:43 ` Paul Walmsley
2007-04-12 15:39 ` Jiri Kosina
2007-04-12 16:14 ` Paul Walmsley
2007-04-12 16:51 ` Jiri Kosina [this message]
2007-04-12 20:27 ` Paul Walmsley
2007-04-11 18:30 ` Paul Walmsley
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=Pine.LNX.4.64.0704121832020.19492@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=joel.becker@oracle.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=paul@booyaka.com \
/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;
as well as URLs for NNTP newsgroup(s).