From: Kay Sievers <kay.sievers@vrfy.org>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>,
Jaroslav Kysela <perex@perex.cz>, Greg KH <gregkh@suse.de>
Subject: Re: MODULE_DEVICE_TABLE(isapnp, ...) does nothing
Date: Wed, 25 Nov 2009 13:05:40 +0100 [thread overview]
Message-ID: <ac3eb2510911250405j6551150eu4b68261a2e03514f@mail.gmail.com> (raw)
In-Reply-To: <200911242223.33206.linux@rainbow-software.org>
On Tue, Nov 24, 2009 at 22:23, Ondrej Zary <linux@rainbow-software.org> wrote:
> On Tuesday 24 November 2009 09:57:28 Kay Sievers wrote:
>> Oh, your box has acpi mapped pnp aliases for this device? You can see
>> your ID string somewhere in this list?
>> grep . /sys/bus/acpi/devices/*/modalias
>>
>> If not, is it in the pnp bus list?
>> grep . /sys/bus/pnp/devices/*/id
>
> It's listen in the pnp bus only:
>
> $ grep -i 80d6 /sys/bus/acpi/devices/*/modalias
> $ grep -i 80d6 /sys/bus/pnp/devices/*/id
> /sys/bus/pnp/devices/01:01.00/id:PNP80d6
> $ cat /sys/bus/pnp/devices/01\:01.00/id
> RTL8019
> PNP80d6
>
> So the acpi alias was useless (I just copied another entry). This alone works:
> alias pnp:dPNP80d6* ne
I see. Plain upstream udev would not load anything here, as the pnp
bus has no modalias support because of the non-working aliases. We
rely on acpi mapping all the pnp entries. Your system probably runs
the shell script which iterates over the "id" file and calls modprobe
for all it finds in there.
Kay
next prev parent reply other threads:[~2009-11-25 12:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 21:01 Ondrej Zary
2009-11-23 3:29 ` Rusty Russell
2009-11-23 8:40 ` Takashi Iwai
2009-11-23 14:13 ` Kay Sievers
2009-11-24 7:29 ` Ondrej Zary
2009-11-24 8:57 ` Kay Sievers
2009-11-24 21:23 ` Ondrej Zary
2009-11-25 12:05 ` Kay Sievers [this message]
2009-11-25 13:21 ` Ondrej Zary
2009-11-25 14:42 ` Matthieu CASTET
2009-11-25 15:23 ` Kay Sievers
2009-11-23 21:51 ` Rusty Russell
2009-11-24 8:53 ` Kay Sievers
2009-11-24 23:51 ` Rusty Russell
2009-11-25 11:39 ` Kay Sievers
2009-11-25 17:17 ` Ondrej Zary
2009-12-18 19:52 ` Ondrej Zary
2009-12-21 10:24 ` Rusty Russell
2010-03-22 13:44 ` Ondrej Zary
2010-03-31 3:50 ` Rusty Russell
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=ac3eb2510911250405j6551150eu4b68261a2e03514f@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=gregkh@suse.de \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=perex@perex.cz \
--cc=rusty@rustcorp.com.au \
--cc=tiwai@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®