All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 3 Oct 2008 16:01:30 -0600	[thread overview]
Message-ID: <200810031601.31322.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1219408985.20723.66.camel@lgn.site>

On Friday 22 August 2008 06:43:05 am Kay Sievers wrote:
> On Fri, 2008-08-22 at 06:06 -0600, Bjorn Helgaas wrote:
> > Since PNP currently doesn't generate any uevents or modalias files,
> > I expect that a non-ACPI system will be unable to autoload modules
> > for ISAPNP or PNPBIOS devices.  Right?
> 
> They do create events, but without modalias. The shell script hack,
> which udev runs, will make the event behave like it contained one.

I'm finally looking at this again; sorry for the long hiatus.  I'm
working on a patch to add PNP uevent support, modalias sysfs files
for PNP, and file2alias.c changes to match, and I just want to
make sure I'm understanding this correctly.

Before your file2alias.c changes[1], I think we generated this:
    alias pnp:dPNP0500* 8250_pnp

We relied on the udev shell hack to run "modprobe -a pnp:dPNP0500"
based on the contents of /sys/bus/pnp/devices/00:05/id.

With your file2alias.c changes, we now generate this:
    alias acpi*:PNP0500:* 8250_pnp
    alias pnp:dPNP0500* 8250_pnp

On ACPI systems, this works fine because "acpi*:PNP0500:*" matches
the ACPI-generated uevents like:
    MODALIAS=acpi:PNP0501:PNP0500:

We can load 8250_pnp without relying on the udev shell hack
*on ACPI systems*.

I thought the object of your file2alias.c changes was to remove the
need for the udev shell hack, but don't we still require it on
non-ACPI systems because they won't emit the ACPI uevents?

Bjorn

[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=22454cb99fc39f2629ad06a7eccb3df312f8830e
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5e4c6564c95ce127beeefe75e15cd11c93487436

  reply	other threads:[~2008-10-03 22:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 21:18 char/tpm: tpm_infineon no longer loaded for HP 2510p laptop Kay Sievers
2008-08-21 21:58 ` Bjorn Helgaas
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 [this message]
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=200810031601.31322.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 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.