public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Aaron Eppert <eppertan@rose-hulman.edu>
Cc: dhinds@zen.stanford.edu, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0 Patch for 3c575
Date: Wed, 10 Jan 2001 18:56:22 -0800	[thread overview]
Message-ID: <3A5D20D6.6090906@megapathdsl.net> (raw)
In-Reply-To: <20010110204420.A7699@rose-hulman.edu>

Huh.  Well, I have a 3CCFE575BT "3c575" card and I have
had success using the 3c59x driver to enable the card.

I only have one bug I am tracking:

If I have two cardbus cards active in my cardbus slots,
the 3c59x driver locks up.  I doubt this problem would
vanish if I were using your 3c575 driver, but I will give
it a try.

There's one other annoyance:

The config files for pcmcia-cs expect the 3c575_cb driver,
so I either have to hack the configuration files or load
the 3c59x driver by hand.

In case it isn't clear, I am only using the PCMCIA/Cardbus
drivers from the 2.4.0 kernel tree (yenta and friends).
I am only using pcmcia-cs utilities and configuration files
for PCMCIA support and to give me a decent /etc/pcmcia/config.opts
file.

	Miles

Aaron Eppert wrote:

> Attached is a patch against 2.4.0 to add the 3c575 driver 
> into the kernel.  Simple reasoning for the addition involves
> the rather broad use of this card and the need to have it
> in a standard kernel.
> 
> Aaron Eppert


-
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/

  reply	other threads:[~2001-01-11  2:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11  1:44 2.4.0 Patch for 3c575 Aaron Eppert
2001-01-11  2:56 ` Miles Lane [this message]
2001-01-11  4:15   ` David Hinds
2001-01-11  7:21     ` Miles Lane
2001-01-11  7:56       ` David Hinds
2001-01-11 11:55     ` Andrew Morton
2001-01-11 17:26       ` David Hinds
2001-01-11  7:32   ` Miles Lane

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=3A5D20D6.6090906@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=dhinds@zen.stanford.edu \
    --cc=eppertan@rose-hulman.edu \
    --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