public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel PRO/1000 NIC
Date: Fri, 26 Sep 2003 00:01:43 +0200	[thread overview]
Message-ID: <20030925220143.GE7919@werewolf.able.es> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E010124F04A@orsmsx402.jf.intel.com> (from scott.feldman@intel.com on Mon, Sep 15, 2003 at 22:04:14 +0200)


On 09.15, "Feldman, Scott" wrote:
> > I am sending UDP data from one PC to another PC directly 
> > through a cross cable. The NIC of sender is Intel(r) PRO/1000 
> > MT Server Adapter, and the NIC of receiver is on-board Intel 
> > PRO/1000 (Dell PowerEdge 1600SC).
> 
> A dump of lspci -vvv, ethtool -i eth<x>, and ethtool -d eth<x> will tell
> us the 8254x controller version you're using; the driver version; if
> you're running PCI or PCI-X, and at what speed; and what you're sharing
> the bus with.
> 
> Ethtool version 1.8: http://sf.net/projects/gkernel.
> Latest e1000: http://sf.net/projects/e1000.
> 

Are there any patches available for 2.4 without all the compat things ?

-- 
J.A. Magallon <jamagallon()able!es>     \                 Software is like sex:
werewolf!able!es                         \           It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.23-pre5-jam1 (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk))

  reply	other threads:[~2003-09-25 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 20:04 Intel PRO/1000 NIC Feldman, Scott
2003-09-25 22:01 ` J.A. Magallon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-25 23:05 Feldman, Scott
2003-09-15 14:35 Lisong Xu

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=20030925220143.GE7919@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott.feldman@intel.com \
    /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