From: Kay Sievers <kay.sievers@vrfy.org>
To: Pozsar Balazs <pozsy@uhulinux.hu>
Cc: Sergey Vlasov <vsu@altlinux.ru>,
Bill Nottingham <notting@redhat.com>,
Pierre Ossman <drzeus-list@drzeus.cx>,
Andrew Morton <akpm@osdl.org>,
ambx1@neo.rr.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PNP] 'modalias' sysfs export
Date: Fri, 12 May 2006 13:09:51 +0200 [thread overview]
Message-ID: <20060512110951.GA4183@vrfy.org> (raw)
In-Reply-To: <20060509174143.GA2320@ojjektum.uhulinux.hu>
On Tue, May 09, 2006 at 07:41:44PM +0200, Pozsar Balazs wrote:
> Basically I implemented the above things, to be precise:
> - the alias for the pnp device drivers are in the form "pnp:*dXXXYYYY*"
> instead of the old "pnp:dXXXYYYY*"
> - the alias for the pnp card drivers are in the form
> "pnp:cXXXYYYY*dXXXYYYY*dXXXYYYY*"
> instead of the old
> "pnp:cXXXYYYYdXXXYYYYdXXXYYYY*"
> _and_ the device id part are ordered
> - add a "modalias" file under sysfs for each pnp device, containing
> "pnp:dXXXYYYYdXXXYYYY..."
> where "dXXXYYYY" is appended for each pnp id the device has
> - add a "modalias" file under sysfs for each pnp card, containing
> "pnp:cXXXYYYYdXXXYYYYdXXXYYYY..."
> where "cXXXYYYY" is the card_id, and the device ids are appended
> after it, _ordered_.
>
>
> With this applied, I think we are close to be able to drop
> special-casing the pnp bus in udev rules.
That looks promising.
> What still needs to be done is exporting the MODALIAS env variable.
> (Sorry, I do not see how it could be added elegantly.)
Yeah, we really want the environment variable. You may do the composition
of the string in a separate function, that just writes to a bufferi, and use
it to fill the buffer of the uevent environment and the page of the sysfs
attribute. Like we did for input:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bd37e5a951ad2123d3f51f59c407b5242946b6ba
Thanks,
Kay
next prev parent reply other threads:[~2006-05-12 11:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 21:40 [PATCH] [PNP] 'modalias' sysfs export Pierre Ossman
2006-03-01 19:45 ` Kay Sievers
2006-03-02 8:39 ` Pierre Ossman
2006-03-02 16:58 ` Kay Sievers
2006-03-03 11:52 ` Pierre Ossman
2006-03-11 16:05 ` Pierre Ossman
2006-03-11 16:15 ` Arjan van de Ven
2006-03-11 16:21 ` Pierre Ossman
2006-03-12 1:38 ` Andrew Morton
2006-03-12 4:05 ` Kay Sievers
2006-03-12 4:29 ` Adam Belay
2006-03-12 5:09 ` Kay Sievers
2006-03-12 6:01 ` Adam Belay
2006-03-12 11:17 ` Pierre Ossman
2006-03-12 11:33 ` Matthieu CASTET
2006-03-12 17:23 ` Kay Sievers
2006-03-12 22:55 ` Andrew Morton
2006-03-13 4:14 ` Kay Sievers
2006-03-13 6:02 ` Adam Belay
2006-03-13 6:21 ` Kay Sievers
2006-03-13 7:04 ` Adam Belay
2006-03-13 7:26 ` Adam Belay
2006-03-13 7:36 ` Kay Sievers
2006-03-14 1:25 ` Adam Belay
2006-03-13 16:57 ` Bill Nottingham
2006-03-13 19:24 ` Kay Sievers
2006-03-13 22:26 ` Bill Nottingham
2006-03-14 12:29 ` Sergey Vlasov
2006-03-14 12:47 ` Pierre Ossman
2006-03-14 15:00 ` Sergey Vlasov
2006-05-09 17:41 ` Pozsar Balazs
2006-05-12 11:09 ` Kay Sievers [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-11 17:07 Andrey Borzenkov
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=20060512110951.GA4183@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=akpm@osdl.org \
--cc=ambx1@neo.rr.com \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.com \
--cc=pozsy@uhulinux.hu \
--cc=vsu@altlinux.ru \
/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