From: Miles Lane <miles@megapathdsl.net>
To: dhinds@sonic.net, linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: Adding PCMCIA support to the kernel tree -- developers needed.
Date: Sun, 04 Feb 2001 18:43:17 -0800 [thread overview]
Message-ID: <3A7E1345.6080005@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1010203040618.29269C-100000@mandrakesoft.mandrakesoft.com> <3A7C9BAE.45DB2F09@megapathdsl.net> <3A7DFE77.E055BC14@mandrakesoft.com>
As we look into developing PCMCIA support in the
2.4/2.5 kernel trees, in addition to reading the
pcmcia-cs code to learn about problems with specific
devices that need to be handled, David Hinds also
a reference page that lists some a bunch of issues
that are in varying degrees of resolution:
http://pcmcia-cs.sourceforge.net/ftp/BUGS
This may be a useful resource. I'll see whether
David has time to update this page with a bit more
detailed explanations of the problems. Some of the
items are pretty vague. For example,
the Asix AX88190 chipset, which has
several serious bugs and incompatibilities
that render the regular pcnet_cs driver
unusable
It would be nice to know exactly what those bugs
and incompatibilities are. :-)
Anyhow, I hope this helps,
Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-05 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A711BB1.C5B8BCFB@megapathdsl.net>
[not found] ` <3A711CB1.62757B52@megapathdsl.net>
[not found] ` <20010131200621.F29731@sonic.net>
[not found] ` <3A78E3EC.8050605@megapathdsl.net>
[not found] ` <20010202183642.F30100@sonic.net>
2001-02-03 7:28 ` Adding PCMCIA support to the kernel tree -- developers needed Miles Lane
2001-02-03 10:07 ` Jeff Garzik
2001-02-04 0:00 ` Miles Lane
2001-02-05 1:14 ` Jeff Garzik
2001-02-05 2:43 ` Miles Lane [this message]
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=3A7E1345.6080005@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=dhinds@sonic.net \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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