From: Thomas Duffy <Thomas.Duffy.99@alumni.brown.edu>
To: kernel@ddx.a2000.nu
Cc: Joel Jaeggli <joelja@darkwing.uoregon.edu>,
"David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: sun + gigabit nic
Date: 08 Oct 2001 09:44:13 -0700 [thread overview]
Message-ID: <1002559480.2837.11.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.40.0110061843230.12443-100000@ddx.a2000.nu>
In-Reply-To: <Pine.LNX.4.40.0110061843230.12443-100000@ddx.a2000.nu>
On Sat, 2001-10-06 at 09:44, kernel@ddx.a2000.nu wrote:
> so will the netgear gigabit adapter work with the ultrasparc linux kernel
> ?
> (the netgear ga622t ?)
this is netgear's gige over copper card. it does not use the acenic
chip. instead it uses the national semiconductor 83820 chip and a
different driver. this driver did not go into the kernel until ~2.4.10
(ns83820.c) and does not work under sparc64 so far -- it seems to
compile, load into the kernel, receive ethernet packets, but packets
never get to layer 3 AFAICT. if anybody has had better luck, please let
me know.
btw, anybody know where to get acenic gige copper cards anywhere? for
the life of me, I cannot find a place that sells them anymore.
-tduffy
next prev parent reply other threads:[~2001-10-08 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 11:22 sun + gigabit nic kernel
2001-10-05 23:10 ` David S. Miller
2001-10-06 14:05 ` kernel
2001-10-06 15:31 ` Joel Jaeggli
2001-10-06 16:44 ` kernel
2001-10-08 16:44 ` Thomas Duffy [this message]
2001-10-08 22:07 ` kernel
2001-10-08 22:11 ` David S. Miller
2001-10-08 22:27 ` kernel
2001-10-08 22:25 ` Joel Jaeggli
2001-10-08 22:32 ` kernel
2001-10-08 22:39 ` Benjamin LaHaise
2001-10-08 22:12 ` David S. Miller
2001-10-06 17:34 ` Jes Sorensen
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=1002559480.2837.11.camel@localhost.localdomain \
--to=thomas.duffy.99@alumni.brown.edu \
--cc=davem@redhat.com \
--cc=joelja@darkwing.uoregon.edu \
--cc=kernel@ddx.a2000.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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