From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: mxs: fix mac address of second interface
Date: Mon, 17 Aug 2015 22:55:27 +0200 [thread overview]
Message-ID: <201508172255.27760.marex@denx.de> (raw)
In-Reply-To: <1608021.ZiQEuijC0W@kerker>
On Monday, August 17, 2015 at 08:51:48 PM, Michael Heimpold wrote:
> Hi Marek,
Hi!
> Am Sonntag, 16. August 2015, 00:49:36 schrieb Marek Vasut:
> > On Sunday, August 16, 2015 at 12:16:21 AM, Michael Heimpold wrote:
> > > In the rare case that an overflow occurs, propagate it.
> >
> > Hi!
> >
> > > Signed-off-by: Michael Heimpold <mhei@heimpold.de>
> > > Cc: Stefano Babic <sbabic@denx.de>
> > > Cc: Marek Vasut <marex@denx.de>
> > > CC: Fabio Estevam <fabio.estevam@freescale.com>
> > > ---
> > >
> > > arch/arm/cpu/arm926ejs/mxs/mxs.c | 12 ++++++++++--
> > > 1 file changed, 10 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/arch/arm/cpu/arm926ejs/mxs/mxs.c
> > > b/arch/arm/cpu/arm926ejs/mxs/mxs.c index b1d8721..42057ad 100644
> > > --- a/arch/arm/cpu/arm926ejs/mxs/mxs.c
> > > +++ b/arch/arm/cpu/arm926ejs/mxs/mxs.c
> > > @@ -238,11 +238,19 @@ int cpu_eth_init(bd_t *bis)
> > >
> > > __weak void mx28_adjust_mac(int dev_id, unsigned char *mac)
> > > {
> > >
> > > + uint32_t data;
> > > +
> > >
> > > mac[0] = 0x00;
> > > mac[1] = 0x04; /* Use FSL vendor MAC address by default */
> > >
> > > - if (dev_id == 1) /* Let MAC1 be MAC0 + 1 by default */
> > > - mac[5] += 1;
> > > + if (dev_id == 1) { /* Let MAC1 be MAC0 + 1 by default */
> > > + data = (mac[3] << 16) | (mac[4] << 8) | mac[5];
> > > + data++;
> > > +
> > > + mac[3] = (data >> 16) & 0xff;
> > > + mac[4] = (data >> 8) & 0xff;
> > > + mac[5] = data & 0xff;
> > > + }
> >
> > I'm not very fond of the added complexity. If an overflow happens,
>
> At least for me, that would be the "algorithm of least surprise" and
> I don't feel that this is so complex but YMMV :-)
>
> > the last nibble just becomes 0x00, which should be okayish. In case
> > you need some sort of special handling of the ethernet address, I'd
> > suggest to implement your own thing in board file.
>
> If this is a NAK, then yes, I can handle this in every board file where
> needed because I've to adjust the vendor part anyway...
Let's hear from the others first.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-08-17 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 22:16 [U-Boot] [PATCH] arm: mxs: fix mac address of second interface Michael Heimpold
2015-08-15 22:49 ` Marek Vasut
2015-08-17 18:51 ` Michael Heimpold
2015-08-17 20:55 ` Marek Vasut [this message]
2015-08-23 15:38 ` Stefano Babic
2015-08-23 20:24 ` Michael Heimpold
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=201508172255.27760.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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