From: Christoph Hellwig <hch@infradead.org>
To: Michael Chan <mchan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, andy@greyhouse.net,
mcarlson@broadcom.com
Subject: Re: [PATCH 2/4][TG3]: ASIC decoding and basic CPMU support.
Date: Mon, 8 Oct 2007 08:18:14 +0100 [thread overview]
Message-ID: <20071008071813.GA29669@infradead.org> (raw)
In-Reply-To: <1191641858.17453.7.camel@dell>
On Fri, Oct 05, 2007 at 08:37:38PM -0700, Michael Chan wrote:
> [TG3]: ASIC decoding and basic CPMU support.
>
> Newer products change the way the ASIC revision is obtained. This patch
> implements how the driver will extract the revision number.
Just curious: is there a diagram somewhere that shows the relation of
the various tg3 chips to each other and what families exist?
next prev parent reply other threads:[~2007-10-08 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 3:37 [PATCH 2/4][TG3]: ASIC decoding and basic CPMU support Michael Chan
2007-10-08 6:28 ` David Miller
2007-10-08 7:18 ` Christoph Hellwig [this message]
2007-10-08 18:26 ` Michael Chan
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=20071008071813.GA29669@infradead.org \
--to=hch@infradead.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).