All of lore.kernel.org
 help / color / mirror / Atom feed
From: <beldridg@best.com>
To: linux-hotplug@vger.kernel.org
Subject: xircom cbem56g-100 support
Date: Fri, 17 Aug 2001 20:30:53 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-99808033518406@msgid-missing> (raw)

hi,

i'm very confused. today i decided to test the in-kernel pcmcia support.

after a few hours of fiddling, i got my wavelan card to work, no problem
there.

then i tried to get my xircom cbem56g-100 to work.

the pcmcia-cs documentation says:

  "Xircom CardBus cards are supported by a separate driver ('Xircom
   Tulip-like CardBus', xircom_tulip_cb, CONFIG_PCMCIA_XIRTULIP).  Hot
   plug PCI drivers are not managed by cardmgr; they are managed by the
   "hotplug" subsystem."

and i've even seen david hinds post that "cardmgr recognized that this is
a hot plug PCI driver, so it is the responsibility of the Linux hotplug
subsystem to load the driver."

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?

one last question: how do the two interoperate? because now i have some
cardbus cards and some not.


- brett


_______________________________________________
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

             reply	other threads:[~2001-08-17 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 20:30 beldridg [this message]
2001-08-18  3:50 ` xircom cbem56g-100 support David Hinds
2001-08-18 15:03 ` David Brownell
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-99808033518406@msgid-missing \
    --to=beldridg@best.com \
    --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 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.