public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: kilobyte@angband.pl (Adam Borowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add ethernet0 alias for several A64 boards
Date: Tue, 25 Jul 2017 05:18:19 +0200	[thread overview]
Message-ID: <20170725031819.ryllvq5a3tdwyblj@angband.pl> (raw)
In-Reply-To: <f4016e61dbe4655a0e672c3377f35dd2@aosc.io>

On Tue, Jul 25, 2017 at 11:04:24AM +0800, icenowy at aosc.io wrote:
> ? 2017-07-24 15:58?Maxime Ripard ???
> > On Sat, Jul 22, 2017 at 10:28:49AM +0800, Icenowy Zheng wrote:
> > > Allwinner A64 SoC has an EMAC which is used to provide Ethernet
> > > function on several boards.
> > > 
> > > The EMAC itself doesn't have a fixed MAC address, but the sunxi
> > > mainline U-Boot have the ability to generate one based on the eFUSE
> > > SID in the chip, and add the generated MAC address to the device
> > > tree when booting.
> > > 
> > > The MAC address setting step is based on the device tree's aliases,
> > > and device tree nodes prefixed "ethernet" will get the MAC address
> > > added. However, in several A64 boards' device tree, the alias is not
> > > set up, so that the U-Boot won't set the MAC address.
> > > 
> > > Add the ethernet0 aliases to these boards.
> > > 
> > > I hope this patchset can be queued in 4.13, otherwise 4.13 kernels
> > > won't get non-volatile MAC addresses, and will use random ones
> > > instead, which is annoying to many users.
> > > 
> > > Icenowy Zheng (3):
> > >   arm64: allwinner: a64: add ethernet0 alias for BPi M64 EMAC node
> > >   arm64: allwinner: a64: add ethernet0 alias for Pine64 EMAC node
> > >   arm64: allwinner: a64: add ethernet0 alias for SoPine EMAC node
> > 
> > Applied all three, thanks!
> 
> Sorry, but could you queue them to 4.13?
> 
> Otherwise 4.13 kernel release will have annoying random MAC problem,
> which heavily affects headless usages.

Perhaps it would be better to reword the commit subject as "fix missing
ethernet0 alias ..."?  That'd convey that the previous behaviour is a defect
that needs these patches as a fix.


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable and Non-Discriminatory prices.

  reply	other threads:[~2017-07-25  3:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22  2:28 [PATCH 0/3] Add ethernet0 alias for several A64 boards Icenowy Zheng
2017-07-22  2:28 ` [PATCH 1/3] arm64: allwinner: a64: add ethernet0 alias for BPi M64 EMAC node Icenowy Zheng
2017-08-10  3:56   ` [linux-sunxi] " Chen-Yu Tsai
2017-08-10  4:40     ` Icenowy Zheng
2017-08-10  7:04       ` Chen-Yu Tsai
2017-07-22  2:28 ` [PATCH 2/3] arm64: allwinner: a64: add ethernet0 alias for Pine64 " Icenowy Zheng
2017-07-22  2:28 ` [PATCH 3/3] arm64: allwinner: a64: add ethernet0 alias for SoPine " Icenowy Zheng
2017-07-24  7:58 ` [PATCH 0/3] Add ethernet0 alias for several A64 boards Maxime Ripard
2017-07-25  3:04   ` icenowy at aosc.io
2017-07-25  3:18     ` Adam Borowski [this message]
2017-07-25 14:31       ` Maxime Ripard
2017-07-25 23:54         ` Icenowy Zheng
2017-07-26  4:12           ` [linux-sunxi] " Chen-Yu Tsai

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=20170725031819.ryllvq5a3tdwyblj@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=linux-arm-kernel@lists.infradead.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