From: "Matt Carlson" <mcarlson@broadcom•com>
To: "David Miller" <davem@davemloft•net>
Cc: "Matthew Carlson" <mcarlson@broadcom•com>,
"James.Bottomley@HansenPartnership•com"
<James.Bottomley@HansenPartnership•com>,
"Michael Chan" <mchan@broadcom•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"linux-parisc@vger•kernel.org" <linux-parisc@vger•kernel.org>
Subject: Re: [PATCH] tg3: fix big endian MAC address collection failure
Date: Mon, 13 Apr 2009 19:00:15 -0700 [thread overview]
Message-ID: <20090414020015.GC11615@xw6200.broadcom.net> (raw)
In-Reply-To: <20090413.184035.137905532.davem@davemloft.net>
On Mon, Apr 13, 2009 at 06:40:35PM -0700, David Miller wrote:
> From: "Matt Carlson" <mcarlson@broadcom•com>
> Date: Mon, 13 Apr 2009 18:25:48 -0700
>
> > Michael noticed that your NVRAM signature is byteswapped in NVRAM. (!)
> > That also explains why the driver is trying to obtain the MAC address
> > through NVRAM, rather than getting it from shared memory. The device's
> > bootcode is not working correctly.
>
> If this problem is pervasive, which it seems it is since we
> have at least two people hitting this problem, we'll need
> to find a way to handle it without saying "update your
> BIOS or system firmware"
Well, Robin's problem looks distinctly different than James'. I believe
Robin's problem has to do with the legacy EEPROM access routines. The
patchset may have overlooked something in that area. I just need to
gather evidence to prove it.
I did run some tests this afternoon on a similar IA64 HP machine and
they ran fine. Consequently, I'm optimistic that James' problem is local
to his machine. If this turns out to be a wider problem, then I agree
we'll need to find an appropriate solution.
next prev parent reply other threads:[~2009-04-14 2:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 15:29 [PATCH] tg3: fix big endian MAC address collection failure James Bottomley
2009-04-13 21:32 ` David Miller
2009-04-13 21:42 ` James Bottomley
2009-04-13 21:44 ` David Miller
2009-04-13 22:17 ` Michael Chan
2009-04-13 22:32 ` James Bottomley
2009-04-14 1:25 ` Matt Carlson
2009-04-14 1:40 ` David Miller
2009-04-14 2:00 ` Matt Carlson [this message]
2009-04-14 2:19 ` Kyle McMartin
2009-04-14 2:51 ` David Miller
2009-04-14 3:56 ` Michael Chan
2009-04-14 3:51 ` James Bottomley
2009-04-14 4:11 ` Michael Chan
2009-04-14 15:26 ` James Bottomley
2009-04-14 15:31 ` Robin Holt
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=20090414020015.GC11615@xw6200.broadcom.net \
--to=mcarlson@broadcom$(echo .)com \
--cc=James.Bottomley@HansenPartnership$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=mchan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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