From: "Michael Chan" <mchan@broadcom.com>
To: "Christoph Hellwig" <hch@infradead.org>
Cc: davem@davemloft.net, jgarzik@redhat.com, netdev@oss.sgi.com,
ffan@broadcom.com, lusinsky@broadcom.com
Subject: Re: A new driver for Broadcom bcm5706
Date: Fri, 27 May 2005 08:58:23 -0700 [thread overview]
Message-ID: <1117209503.4584.11.camel@rh4> (raw)
In-Reply-To: <20050527074115.GA28208@infradead.org>
On Fri, 2005-05-27 at 08:41 +0100, Christoph Hellwig wrote:
> On Fri, May 20, 2005 at 10:15:29AM -0700, Michael Chan wrote:
> > A new driver bnx2 for Broadcom bcm5706 is available. Since the patch is
> > over 500K, I've put it on the ftp server:
> >
> > ftp://Net_sys_anon@ftp1.broadcom.com/bnx2-2.patch
> >
> > The patch also includes new 1000BASE-X advertisement bit definitions in
> > mii.h
>
> These defintions overlap older 10MB/s defintions. I don't think the number
> space is scare enough to need this hack. If we absolutely want to keep it
> you should at least add some big comments explaining it.
>
>
Yes they do. But these overlapping bit definitions are defined by the
802.3 standard for 1000Base-X. These are not Broadcom proprietary
definitions.
next prev parent reply other threads:[~2005-05-27 15:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 17:15 A new driver for Broadcom bcm5706 Michael Chan
2005-05-20 19:42 ` Jeff Garzik
2005-05-20 20:51 ` Jeff Garzik
2005-05-20 21:07 ` Ben Greear
2005-05-20 21:09 ` Jeff Garzik
2005-05-20 20:17 ` Michael Chan
2005-05-20 21:58 ` Ben Greear
2005-05-20 22:28 ` David S. Miller
2005-05-20 23:04 ` Michael Chan
2005-05-21 4:35 ` David S. Miller
2005-05-21 4:36 ` David S. Miller
2005-05-20 23:30 ` Jeff Garzik
2005-05-20 23:45 ` David S. Miller
2005-05-21 0:01 ` Jeff Garzik
2005-05-20 23:11 ` Michael Chan
2005-05-21 4:28 ` David S. Miller
2005-05-20 21:18 ` Jeff Garzik
2005-05-27 7:41 ` Christoph Hellwig
2005-05-27 15:58 ` Michael Chan [this message]
2005-05-27 17:15 ` Christoph Hellwig
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=1117209503.4584.11.camel@rh4 \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=ffan@broadcom.com \
--cc=hch@infradead.org \
--cc=jgarzik@redhat.com \
--cc=lusinsky@broadcom.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).