From: David Woodhouse <dwmw2@infradead.org>
To: Ryan Mack <rmack@mackman.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [QUESTIONS] Transision from pcmcia-cs to 2.4 built-in PCMCIA
Date: Mon, 09 Apr 2001 10:04:00 +0100 [thread overview]
Message-ID: <12964.986807040@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0104081846460.16728-100000@mackman.net>
In-Reply-To: <Pine.LNX.4.30.0104081846460.16728-100000@mackman.net>
rmack@mackman.net said:
> First, why have I stopped needing cs and cb_enabler?
cs is built into pcmcia_core.o, cb_enabler should still be there though.
It's feasible that you only need cb_enabler for the old CardBus drivers,
though - I'm not sure.
> Second, why is yenta_socket only compiled if I enable CardBus support
> in the kernel? I'm running an Orinoco card on another machine, and
> since I don't think it's CardBus (am I wrong?), I didn't enable CB in
> the kernel. The i82365 driver is the only one compiled, but it seems
> to work fine on that machine. Should I enable CardBus support and use
> yenta_socket instead?
yenta_socket is the driver for CardBus i82365-compatible sockets.
i82365 no longer drives CardBus sockets, only PCMCIA.
> Third, on the first machine with both cards, neither card works if I
> use i82365 instead of yenta_socket, why? The Orinoco gets Tx timeouts
> on every packet, and inserting the 3c595 causes the controller
> (socket) to time out waiting for reset and it doesn't recognize the
> 3c595.
The PCMCIA card ought to work. It's probably screwed up the IRQ routing -
it no longer knows about some of the differences between CardBus and PCMCIA
bridges. What exactly is the bridge in this machine?
--
dwmw2
next prev parent reply other threads:[~2001-04-09 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 0:54 Zero Copy IO Douglas Gilbert
2001-04-09 1:53 ` [QUESTIONS] Transision from pcmcia-cs to 2.4 built-in PCMCIA Ryan Mack
2001-04-09 9:04 ` David Woodhouse [this message]
2001-04-09 12:25 ` Zero Copy IO Jeremy Jackson
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=12964.986807040@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmack@mackman.net \
/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