public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rob" <rwideman@austin.rr.com>
To: <linux-kernel@vger.kernel.org>
Subject: FW: tulip.o during 2.4.7 compile
Date: Wed, 8 Aug 2001 18:10:07 -0500	[thread overview]
Message-ID: <LHEGJICMMCCGOHKDFALMEENFCAAA.rwideman@austin.rr.com> (raw)

n/m wrong mailing list AND i found out the answer, in the description it is
labeled as tulip.o
Rob

-----Original Message-----
From: Rob [mailto:rwideman@austin.rr.com]
Sent: Wednesday, August 08, 2001 6:06 PM
To: linux-kernel@vger.kernel.org
Subject: tulip.o during 2.4.7 compile


I am currently running RH 7.1 and trying to compile the 2.4.7 kernel. My
Linksys (lne100tx) NIC is currently running the tulip module. In the Nic
section of the "make menuconfig" of the configuration i can only find an
option of "DECchip Tulip (dc21x4x) PCI support" which states that "some"
Linksys cards use.  It never specifies the name of the module other than
config_tulip in the description.  Is this the correct module for the NIC?
Rob


                 reply	other threads:[~2001-08-08 23:08 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=LHEGJICMMCCGOHKDFALMEENFCAAA.rwideman@austin.rr.com \
    --to=rwideman@austin.rr.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