public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Kay Sievers <kay.sievers@vrfy.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: Tue, 24 Nov 2009 08:29:21 +0100	[thread overview]
Message-ID: <200911240829.23067.linux@rainbow-software.org> (raw)
In-Reply-To: <ac3eb2510911230613w5543e98bg4203a1fbd7269931@mail.gmail.com>

On Monday 23 November 2009, Kay Sievers wrote:
> On Mon, Nov 23, 2009 at 09:40, Takashi Iwai <tiwai@suse.de> wrote:
> > At Mon, 23 Nov 2009 13:59:53 +1030,
> >
> > Rusty Russell wrote:
> >> On Mon, 23 Nov 2009 07:31:57 am Ondrej Zary wrote:
> >> > The problem is that
> >> > scripts/mod/file2alias.c simply ignores isapnp.
> >>
> >> AFAICT it always has, and noone has complained until now.  Perhaps
> >> something was still reading /lib/modules/`uname -r`/modules.isapnpmap?
> >
> > I don't think modules.isapnpmap is needed again.
> > The question came from the fact that the isapnp device wasn't loaded
> > automatically.
>
> All the map files are not uses for anything these days. Ideally,
> depmod should just stop creating these dead files.
>
> > But, I thought Kay already added isapnp support sometime ago, but it
> > didn't seem to get in...  Kay?
>
> No, we don't even have proper modaliases for the pnp bus
> (/sys/bus/pnp) and the alias string for pnp in the modules have a
> broken and unfixable format. PNP autoloading is all handled by the
> acpi modaliases these days. This is the first time in years I hear
> anybody asking for hotplug setups of plain old pnp devices. :)


Added these two lines to modules.alias (and deleted modules.alias.bin):
alias acpi*:RTL8019:* ne
alias pnp:dRTL8019* ne

and it works. This works too:
alias acpi*:PNP80d6:* ne
alias pnp:dPNP80d6* ne

The card has two IDs (as some PnP devices do) and both work.

-- 
Ondrej Zary

  reply	other threads:[~2009-11-24  7:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 21:01 MODULE_DEVICE_TABLE(isapnp, ...) does nothing 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 [this message]
2009-11-24  8:57         ` Kay Sievers
2009-11-24 21:23           ` Ondrej Zary
2009-11-25 12:05             ` Kay Sievers
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=200911240829.23067.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=gregkh@suse.de \
    --cc=jonathan@jonmasters.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.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