From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: ambx1@neo.rr.com, elendil@planet.nl, trenn@suse.de,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
tpm@selhorst.net, rjw@sisk.pl, greg@kroah.com
Subject: Re: char/tpm: tpm_infineon no longer loaded for HP 2510p laptop
Date: Thu, 21 Aug 2008 15:58:23 -0600 [thread overview]
Message-ID: <200808211558.23725.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <24565067.73831219353513508.JavaMail.servlet@kundenserver>
On Thursday 21 August 2008 03:18:33 pm Kay Sievers wrote:
> Bjorn Helgaas wrote:
> >Is there a "complete idiot's guide to modules
> >and udev"? There's precious little in Documentation/ other than a bunch
> >of sample rules for various subsystems.
>
> I don't know of any specific documentation, but it's pretty easy:
> ...
Thanks for the tutorial.
> >Could I fix this by implementing pnp_device_uevent()?
>
> Only if we change the format of the current pnp device aliases
> to something like:
> pnp*:XYZ2324:*
> pnp*:ABC1234:*
>
> and create a "modalias" file at every pnp device, and add MODALIAS to
> the uevent. The modalias must contains all ID's which belong to that
> device in one single string, separated and terminated by a special
> character, something like:
> pnp:ABC1234:XYZ2324:RST3445:
This all sounds like good stuff that I'd like PNP to have. Is there
any reason I shouldn't implement pnp_device_uevent()? Any backwards-
compatibility issues?
I think that sounds like a better solution than doing this PNP ID
mangling.
Bjorn
next prev parent reply other threads:[~2008-08-21 21:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 21:18 Kay Sievers
2008-08-21 21:58 ` Bjorn Helgaas [this message]
2008-08-22 8:40 ` Kay Sievers
2008-08-22 12:06 ` Bjorn Helgaas
2008-08-22 12:43 ` Kay Sievers
2008-10-03 22:01 ` Bjorn Helgaas
2008-10-04 12:09 ` Kay Sievers
2008-10-04 15:31 ` Bjorn Helgaas
2008-10-04 16:27 ` Kay Sievers
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 13:40 Frans Pop
2008-08-20 15:56 ` Bjorn Helgaas
2008-08-21 12:40 ` Rafael J. Wysocki
2008-08-21 13:28 ` Kay Sievers
2008-08-21 15:14 ` Bjorn Helgaas
2008-08-21 15:38 ` Kay Sievers
2008-08-21 16:31 ` Bjorn Helgaas
2008-08-21 20:30 ` Frans Pop
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=200808211558.23725.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@linux-foundation.org \
--cc=ambx1@neo.rr.com \
--cc=elendil@planet.nl \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tpm@selhorst.net \
--cc=trenn@suse.de \
/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
all inboxes | Powered by JetHome®