From: Benjamin LaHaise <bcrl@redhat.com>
To: Michael Clark <michael@metaparadigm.com>
Cc: Rob Myers <rob.myers@gtri.gatech.edu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] - 2.4.16 ns83820 optical support (Netgear GA621)
Date: Wed, 5 Dec 2001 17:50:17 -0500 [thread overview]
Message-ID: <20011205175017.B25214@redhat.com> (raw)
In-Reply-To: <3C0CED3B.7030409@metaparadigm.com> <1007501048.14051.28.camel@ransom> <3C0D7CEA.2050307@metaparadigm.com>
In-Reply-To: <3C0D7CEA.2050307@metaparadigm.com>; from michael@metaparadigm.com on Wed, Dec 05, 2001 at 09:48:26AM +0800
On Wed, Dec 05, 2001 at 09:48:26AM +0800, Michael Clark wrote:
> The code reads a 64bit detect flag from the ns chip - so I guess it
> must be bogus with some motherboards. Mine is okay. Ben??
Actually, it's 64 bit addressing that it detects. I'll change the
message to reflect this.
> Okay, so i'll move the register_netdev call earlier on in the
> initialisation and add any necessary unregister call for failures.
Thanks for the patch -- I've now just got to add subsystem id support to
catch an odd 83820 on a motherboard setup that has different polarity for
the duplex + speed inputs. Why do hardware vendors have to be different?
-ben
prev parent reply other threads:[~2001-12-05 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 15:35 [PATCH] - 2.4.16 ns83820 optical support (Netgear GA621) Michael Clark
2001-12-04 21:24 ` Rob Myers
2001-12-04 21:31 ` Jeff Garzik
2001-12-05 1:48 ` Michael Clark
2001-12-05 5:02 ` Michael Clark
2001-12-05 12:55 ` Jeff Garzik
2001-12-05 14:37 ` Michael Clark
2001-12-05 16:56 ` Rob Myers
2001-12-05 22:50 ` Benjamin LaHaise [this message]
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=20011205175017.B25214@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.com \
--cc=rob.myers@gtri.gatech.edu \
/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