From: Andrew Lunn <andrew@lunn.ch>
To: Brian Masney <bmasney@redhat.com>
Cc: irusskikh@marvell.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, cth451@gmail.com
Subject: Re: [PATCH] net: atlantic: fix check for invalid ethernet addresses
Date: Wed, 30 Nov 2022 22:32:54 +0100 [thread overview]
Message-ID: <Y4fMBl6sv+SUyt9Z@lunn.ch> (raw)
In-Reply-To: <Y4fGORYQRfYTabH1@x1>
> > > - return !(addr[0] == 0 && addr[1] == 0 && addr[2] == 0);
> > > + return !(addr[0] == 0 && addr[1] == 0 && addr[2] == 0) &&
> > > + !(addr[3] == 0 && addr[4] == 0 && addr[5] == 0);
> >
> > Hi Brian
> >
> > is_valid_ether_addr()
>
> aq_nic_ndev_register() already calls is_valid_ether_addr():
>
> if (is_valid_ether_addr(addr) &&
> aq_nic_is_valid_ether_addr(addr)) {
> (self->ndev, addr);
> } else {
> ...
> }
>
> That won't work for this board since that function only checks that the
> MAC "is not 00:00:00:00:00:00, is not a multicast address, and is not
> FF:FF:FF:FF:FF:FF." The MAC address that we get on all of our boards is
> 00:17:b6:00:00:00.
Which is a valid MAC address. So i don't see why the kernel should
reject it and use a random one.
Maybe you should talk to Marvell about how you can program the
e-fuses. You can then use MAC addresses from A8-97-DC etc.
Andrew
next prev parent reply other threads:[~2022-11-30 21:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 17:42 [PATCH] net: atlantic: fix check for invalid ethernet addresses Brian Masney
2022-11-30 17:57 ` Brian Masney
2022-11-30 18:26 ` Tianhao Chai
2022-11-30 18:47 ` Brian Masney
2022-11-30 19:41 ` Andrew Lunn
2022-11-30 21:08 ` Brian Masney
2022-11-30 21:32 ` Andrew Lunn [this message]
2022-11-30 23:12 ` David Laight
2022-12-01 2:22 ` Andrew Lunn
2022-12-01 8:07 ` [EXT] " Igor Russkikh
2022-12-01 13:55 ` Brian Masney
2022-12-01 14:14 ` Andrew Lunn
2022-12-01 15:18 ` Igor Russkikh
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=Y4fMBl6sv+SUyt9Z@lunn.ch \
--to=andrew@lunn.ch \
--cc=bmasney@redhat.com \
--cc=cth451@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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