From: Val Henson <val@nmt.edu>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Yellowfin bug fix for Symbios cards
Date: Fri, 19 Oct 2001 12:06:44 -0600 [thread overview]
Message-ID: <20011019120644.D21008@boardwalk> (raw)
In-Reply-To: <20011018210416.D17208@boardwalk> <3BCF9FDD.D6586538@mandrakesoft.com> <20011018215429.A18593@boardwalk> <3BCFAB6F.15D345B7@mandrakesoft.com>
In-Reply-To: <3BCFAB6F.15D345B7@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Fri, Oct 19, 2001 at 12:26:23AM -0400
On Fri, Oct 19, 2001 at 12:26:23AM -0400, Jeff Garzik wrote:
> Val Henson wrote:
> > Hm, good point. I should figure out why read_eeprom isn't working and
> > fix that instead. Maybe the driver should be changed to attempt to
> > read the MAC from the eeprom and then read from the registers if that
> > fails, instead of relying on flags.
>
> Yeah. There is at least one other driver (pcnet32?) that does something
> like this...
>
> probe:
> dev->dev_addr[] = read_eeprom();
> if (!is_valid_ether_addr(dev->dev_addr))
> { read from card registers }
Well, I asked our hardware engineers, and the reason read the MAC
address from the EEPROM is that we don't have an EEPROM on our
boards. Instead, the bootloader reads some stuff out of NVRAM and
writes it into the MAC address registers of the ethernet chip.
I think the above scheme is a good way to read the MAC, but I'd want
to test it on an actual Yellowfin gigabit card before submitting it.
Anyone out here willing to test?
-VAL
prev parent reply other threads:[~2001-10-19 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 3:04 [PATCH] Yellowfin bug fix for Symbios cards Val Henson
2001-10-19 3:37 ` Jeff Garzik
2001-10-19 3:54 ` Val Henson
2001-10-19 4:26 ` Jeff Garzik
2001-10-19 18:06 ` Val Henson [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=20011019120644.D21008@boardwalk \
--to=val@nmt.edu \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@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