From: Cort Dougan <cort@fsmlabs.com>
To: Eli Carter <eli.carter@inet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lance.c @ 100Mbit
Date: Tue, 16 Jan 2001 15:41:36 -0700 [thread overview]
Message-ID: <20010116154136.M28808@hq.fsmlabs.com> (raw)
In-Reply-To: <3A64CADF.17C9B9A3@inet.com>
In-Reply-To: <3A64CADF.17C9B9A3@inet.com>; from Eli Carter on Tue, Jan 16, 2001 at 04:27:43PM -0600
} Quick question: has anyone used the lance.c driver for a 100BaseT
} network PCI device? If so, what successes/failures did you run into?
}
} (I'm working with an Am79C973 chip.)
I'd recommend the pcnet32.c driver for that chip, instead. I was running
it for a little over a year at 100Mbps with no serious trouble. This was
under Linux/PPC, so there were some endian-ness problems at first but it's
clean now.
-
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/
next prev parent reply other threads:[~2001-01-16 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 22:27 lance.c @ 100Mbit Eli Carter
2001-01-16 22:41 ` Cort Dougan [this message]
2001-01-16 22:49 ` Richard B. Johnson
2001-01-16 22:53 ` Barry K. Nathan
-- strict thread matches above, loose matches on Subject: below --
2001-01-16 23:37 Eli Carter
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=20010116154136.M28808@hq.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=eli.carter@inet.com \
--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