From: David Miller <davem@davemloft.net>
To: James.Bottomley@HansenPartnership.com
Cc: netdev@vger.kernel.org, linux-parisc@vger.kernel.org,
mcarlson@broadcom.com, mchan@broadcom.com
Subject: Re: [PATCH] tg3: fix big endian MAC address collection failure
Date: Mon, 13 Apr 2009 14:32:11 -0700 (PDT) [thread overview]
Message-ID: <20090413.143211.214694858.davem@davemloft.net> (raw)
In-Reply-To: <1239636594.3278.31.camel@mulgrave.int.hansenpartnership.com>
From: James Bottomley <James.Bottomley@HansenPartnership.com>
Date: Mon, 13 Apr 2009 15:29:54 +0000
> We noticed on parisc that our broadcoms all swapped MAC addresses going
> from 2.6.29 to 2.6.30-rc1:
>
> Apr 11 07:48:24 ion kernel: eth0: Tigon3 [partno(BCM95700A6) rev 0105] (PCI:66MHz:64-bit) MAC address 00:30:6e:4b:15:59
> Apr 13 07:34:34 ion kernel: eth0: Tigon3 [partno(BCM95700A6) rev 0105] (PCI:66MHz:64-bit) MAC address 00:00:59:15:4b:6e
>
> The problem patch is:
>
> commit 6d348f2c1e0bb1cf7a494b51fc921095ead3f6ae
> Author: Matt Carlson <mcarlson@broadcom.com>
> Date: Wed Feb 25 14:25:52 2009 +0000
>
> tg3: Eliminate tg3_nvram_read_swab()
>
> With the root cause being the use of memcpy to set the mac address:
>
> memcpy(&dev->dev_addr[0], ((char *)&hi) + 2, 2);
> memcpy(&dev->dev_addr[2], (char *)&lo, sizeof(lo));
>
> This might work on little endian machines, but it can't on big endian
> ones. You have to use the original setting mechanism to be correct on
> all architectures.
>
> The attached patch fixes parisc.
>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
I'm applying this, thanks a lot James!
next prev parent reply other threads:[~2009-04-13 21:32 UTC|newest]
Thread overview: 32+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2009-04-13 15:21 James Bottomley
2009-04-13 18:00 ` Matt Carlson
2009-04-13 18:04 ` Kyle McMartin
2009-04-13 18:13 ` Matt Carlson
2009-04-13 18:18 ` James Bottomley
2009-04-13 18:24 ` Matt Carlson
2009-04-13 18:15 ` James Bottomley
2009-04-13 18:37 ` Matt Carlson
2009-04-13 20:48 ` James Bottomley
2009-04-14 1:17 ` Matt Carlson
2009-04-14 15:39 ` Grant Grundler
2009-04-14 19:02 ` Matt Carlson
2009-04-18 23:00 ` Grant Grundler
2009-04-19 7:30 ` Michael Chan
2009-04-19 22:32 ` Grant Grundler
2009-04-20 20:46 ` Matt Carlson
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=20090413.143211.214694858.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-parisc@vger.kernel.org \
--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