From: Jeff Garzik <jgarzik@pobox.com>
To: Dominik Brodowski <linux@brodo.de>
Cc: linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk
Subject: Re: [PATCHES 2.5.67] PCMCIA hotplugging, in-kernel-matching and depmod support
Date: Tue, 08 Apr 2003 19:01:39 -0400 [thread overview]
Message-ID: <3E9354D3.8090805@pobox.com> (raw)
In-Reply-To: <20030408213403.GA5250@brodo.de>
Dominik Brodowski wrote:
> On Tue, Apr 08, 2003 at 05:20:59PM -0400, Jeff Garzik wrote:
>>Will we see pcmcia id lists making their way into low-level drivers?
> In the drivers I converted (~20 or so...) this is done already. You can
> find them at http://www.brodo.de/pcmcia/ , for example the network drivers
> (all of them should be converted) at
> http://www.brodo.de/pcmcia/pcmcia-2.5.67-drivers_network .
>
> For example, a part of pcnet_cs.c looks like this now:
>
> static struct pcmcia_device_id pcnet_ids[] = {
> { PCMCIA_DEVICE_VERS1("2412LAN", 0x67f236ab) },
> { PCMCIA_DEVICE_VERS12("ACCTON", "EN2212", 0xdfc6b5b2, 0xcb112a11) },
> ...
> { PCMCIA_MFC_DEVICE_MANF_CARD(0, 0x0105, 0xea15) },
> { },
> };
> MODULE_DEVICE_TABLE(pcmcia, pcnet_ids);
Very cool...
> As strings can't be passed to userspace in file2alias.c, I've chosen the
> crc32 value of the string as the matching identifier for the userspace
> hotplug script.
This sounds like a problem to be solved, not worked around... the
source should have the strings presented directly, and I'm sure a
creative and smart person such as yourself can conceive of at least
one... ;-)
Jeff
next prev parent reply other threads:[~2003-04-08 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 20:56 [PATCHES 2.5.67] PCMCIA hotplugging, in-kernel-matching and depmod support Dominik Brodowski
2003-04-08 21:20 ` Jeff Garzik
2003-04-08 21:34 ` Dominik Brodowski
2003-04-08 23:01 ` Jeff Garzik [this message]
2003-04-09 19:48 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 22:31 Jean Tourrilhes
2003-04-08 22:56 ` Jeff Garzik
2003-04-09 0:05 ` Jean Tourrilhes
2003-04-09 6:38 ` Dominik Brodowski
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=3E9354D3.8090805@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=rmk@arm.linux.org.uk \
/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