public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael D. Crawford" <crawford@goingware.com>
To: linux-kernel@vger.kernel.org
Subject: tulip works in 2.4.5 on Compaq Presario 1800T (was broken)
Date: Mon, 04 Jun 2001 07:14:02 +0000	[thread overview]
Message-ID: <3B1B353A.CCD03B34@goingware.com> (raw)

With a number of previous kernel versions, the tulip driver would not
work with the digital DS21143 ethernet controller that comes bundled
with the Compaq Presario 1800T laptop.

Fortunately, the de4x5 driver would work with it, however the situation
was confusing because the config doc supplied for the de4x5 driver
doesn't mention that it supports tulip chips now also, while the tulip
driver claimed that it should work.  Further if one compiled both into
the kernel, the tulip driver would initialize first and claim control of
the chip and prevent the de4x5 from working.

I hadn't tried the tulip driver on my laptop for a few kernel versions
so I don't know when it started working.  But it works now, with 2.4.5. 
de4x5 also works.  So you can use either one.

Curiously, when I first installed Linux on my laptop, I think it was
Slackware 4.0, I couldn't get any driver to work, but I got a
development version of the author's site, and it worked OK in a 2.2
kernel.  But later versions that were actually rolled into the kernel
didn't work.

I have a page about linux on my Compaq Presario 1800T at

http://www.goingware.com/laptop/linux/

I've gotten quite a few emails from confused 1800T owners in the time
I've had that page up, I think this will make things much easier.

Regards,

Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford@goingware.com

   Tilting at Windmills for a Better Tomorrow.

                 reply	other threads:[~2001-06-04 11:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B1B353A.CCD03B34@goingware.com \
    --to=crawford@goingware.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