From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Faux Pas III <fauxpas@temp123.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Weird PCMCIA behavior
Date: Sun, 18 Nov 2001 18:44:17 -0500 [thread overview]
Message-ID: <3BF847D1.54532522@mandrakesoft.com> (raw)
In-Reply-To: <20011118180656.A18252@temp123.org> <3BF84297.7FB77B3B@mandrakesoft.com> <20011118182903.A18291@temp123.org>
Faux Pas III wrote:
>
> On Sun, Nov 18, 2001 at 06:21:59PM -0500, Jeff Garzik wrote:
>
> > pcmcia-cs problems are reported to http://pcmcia-cs.sourceforge.net/
> > We encourage you to use the kernel's cardbus code instead :)
> > (CONFIG_PCMCIA and CONFIG_CARDBUS)
>
> That's what I'm using to get these errors. I think, although I haven't
> fully tested yet, that pcmcia-cs's core works fine in all power states.
>
> > As a side note, with kernel cardbus support, you should no longer need
> > external utilities or external drivers. It should Just Work(tm).
>
> Do I not still need the cardmgr and all that rot from pcmcia-cs ? That's
> what I've been using for detection, bind cards to specific modules, etc.
Nope. CardBus looks like hotplug PCI to the kernel, so all normal PCI
drivers automagically work as CardBus drivers. You actually need no
userspace tools at all..
Also note there is a kernel cardbus PM fix in the latest 2.4.15-preXX
patches...
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-11-18 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 23:06 Weird PCMCIA behavior Faux Pas III
2001-11-18 23:21 ` Jeff Garzik
2001-11-18 23:29 ` Faux Pas III
2001-11-18 23:44 ` Jeff Garzik [this message]
2001-11-19 11:26 ` christophe barbé
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=3BF847D1.54532522@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=fauxpas@temp123.org \
--cc=linux-kernel@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