From: Sebastian Heidl <heidl@zib.de>
To: "David S. Miller" <davem@redhat.com>
Cc: nick@snowman.net, linux-kernel@vger.kernel.org,
jgarzik@mandrakesoft.com, linux-net@vger.kernel.org
Subject: Re: [BETA] First test release of Tigon3 driver
Date: Tue, 26 Feb 2002 12:39:49 +0100 [thread overview]
Message-ID: <20020226123949.C8471@csr-pc6.local> (raw)
In-Reply-To: <Pine.LNX.4.21.0202252243360.18586-100000@ns> <20020225.204022.62649663.davem@redhat.com> <20020226122205.B8471@csr-pc6.local> <20020226.032453.41634091.davem@redhat.com>
In-Reply-To: <20020226.032453.41634091.davem@redhat.com>; from davem@redhat.com on Tue, Feb 26, 2002 at 03:24:53AM -0800
On Tue, Feb 26, 2002 at 03:24:53AM -0800, David S. Miller wrote:
> From: Sebastian Heidl <heidl@zib.de>
> Date: Tue, 26 Feb 2002 12:22:05 +0100
>
> I think these are 3C996-T. Is there any information about the
> compatibility of TG3 to TG2 ?
>
> Totally different chip, but there are subtle similarities all over
> the place. Ie. if you knew how to program the tg2, or even were just
> familiar with the acenic driver, the tg3 stuff looks familiar.
That's what I noticed looking at tg3.c ;-)
I guess nobody was crazy enough yet to try to load a tg2-firmware on a tg3 ?
Only as there are some utils to build a customized firmware for the tg2.
just guessing wildly ;-)
_sh_
next prev parent reply other threads:[~2002-02-26 11:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 0:59 [BETA] First test release of Tigon3 driver David S. Miller
2002-02-26 3:43 ` nick
2002-02-26 4:40 ` David S. Miller
2002-02-26 11:22 ` Sebastian Heidl
2002-02-26 11:24 ` David S. Miller
2002-02-26 11:39 ` Sebastian Heidl [this message]
2002-02-26 13:13 ` David S. Miller
2002-02-26 13:57 ` Thomas Langås
2002-02-26 14:59 ` David S. Miller
2002-02-26 15:40 ` Thomas Langås
2002-02-26 16:09 ` __skb_dequeue irq race ? Bjorn Wesen
2002-02-27 2:56 ` [BETA] First test release of Tigon3 driver David S. Miller
[not found] ` <20020227102450.B23121@stud.ntnu.no>
2002-02-27 9:31 ` David S. Miller
2002-02-27 11:05 ` Thomas Langås
2002-02-27 11:34 ` David S. Miller
2002-02-27 11:56 ` Thomas Langås
2002-02-27 12:06 ` David S. Miller
2002-02-27 12:24 ` Thomas Langås
2002-02-27 12:28 ` David S. Miller
2002-02-27 16:03 ` Thomas Langås
2002-02-27 16:10 ` Arjan van de Ven
2002-02-27 17:25 ` Thomas Langås
2002-02-27 18:37 ` Zach Brown
2002-02-27 18:46 ` Zach Brown
2002-02-27 19:42 ` Thomas Langås
2002-02-27 16:30 ` Chris Friesen
2002-02-26 17:22 ` Greg KH
2002-02-27 4:13 ` David S. Miller
2002-02-26 18:08 ` Pasi Kärkkäinen
2002-02-27 2:12 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 0:57 Timothy Ngo
2002-03-12 1:21 ` Alan Cox
2002-03-12 6:47 ` David S. Miller
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=20020226123949.C8471@csr-pc6.local \
--to=heidl@zib.de \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=nick@snowman.net \
/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