From: Ondrej Zary <linux@rainbow-software.org>
To: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: MODULE_DEVICE_TABLE(isapnp, ...) does nothing
Date: Sun, 22 Nov 2009 22:01:57 +0100 [thread overview]
Message-ID: <200911222201.59471.linux@rainbow-software.org> (raw)
Hello,
just found that Linux does not automatically load "ne" module for ISA PnP
NE2000 cards (RTL8019AS). ne.c contains this:
static struct isapnp_device_id isapnp_clone_list[] __initdata = {
{ ISAPNP_CARD_ID('A','X','E',0x2011),
ISAPNP_VENDOR('A','X','E'), ISAPNP_FUNCTION(0x2011),
(long) "NetGear EA201" },
{ ISAPNP_ANY_ID, ISAPNP_ANY_ID,
ISAPNP_VENDOR('E','D','I'), ISAPNP_FUNCTION(0x0216),
(long) "NN NE2000" },
{ ISAPNP_ANY_ID, ISAPNP_ANY_ID,
ISAPNP_VENDOR('P','N','P'), ISAPNP_FUNCTION(0x80d6),
(long) "Generic PNP" },
{ } /* terminate list */
};
MODULE_DEVICE_TABLE(isapnp, isapnp_clone_list);
but "modinfo ne" does not show any aliases. The ne.mod.c file produced during
build does not contain aliases too. The problem is that
scripts/mod/file2alias.c simply ignores isapnp.
ne.c is not the only file using MODULE_DEVICE_TABLE(isapnp, ...):
drivers/pcmcia/i82365.c
drivers/net/3c515.c
drivers/net/ne.c
drivers/net/smc-ultra.c
drivers/isdn/hisax/hisax_fspcipnp.c
drivers/media/radio/radio-sf16fmi.c
drivers/scsi/aha1542.c
drivers/scsi/aha152x.c
drivers/scsi/sym53c416.c
drivers/scsi/g_NCR5380.c
sound/oss/ad1848.c
How is (was) this supposed to work?
--
Ondrej Zary
next reply other threads:[~2009-11-22 21:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 21:01 Ondrej Zary [this message]
2009-11-23 3:29 ` MODULE_DEVICE_TABLE(isapnp, ...) does nothing 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
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=200911222201.59471.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.