From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: xircom cbem56g-100 support
Date: Sat, 18 Aug 2001 15:03:43 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99814710102367@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99808033518406@msgid-missing>
> > so, i download and install the latest hotplug stuff. and, here is what i
> > find in the /etc/hotplug/blacklist:
> >
> > # tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
> > de4x5
> > xircom_tulip_cb
> > dmfe
> >
> > so, can somebody please help me before i just give up (again) and go back
> > to the pcmcia-cs stuff?
>
> I am not really familiar with things under hotplug, but I think that
> this has got to be a bug.
Seems like the xircom_tulip_cb driver got updated sometime after it
got added to the blacklist ... I see a big "#if 0...#endif" in the device
table to get rid of the overlap with other drivers.
Workaround: comment it out of that blacklist. Anyone know how
long that "#if 0" has been there? I'll putback a fix to the blacklist,
but that's the sort of fix that can benefit from a kernel version number.
> > one last question: how do the two interoperate? because now i have some
> > cardbus cards and some not.
>
> The answer is "basically, they don't". Cards are either hotplug or
> not; hotplug cards use the hotplug subsystem, and non-hotplug ones use
> the PCMCIA configuration system.
>
> -- Dave
>
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-08-18 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 20:30 xircom cbem56g-100 support beldridg
2001-08-18 3:50 ` David Hinds
2001-08-18 15:03 ` David Brownell [this message]
2001-08-18 15:36 ` beldridg
2001-08-18 16:49 ` David Brownell
2001-08-19 0:19 ` David Hinds
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=marc-linux-hotplug-99814710102367@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).