public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: atags: add support for Marvell's u-boot
Date: Tue, 4 Jun 2013 10:05:18 +0200	[thread overview]
Message-ID: <20130604100518.167484e1@skate> (raw)
In-Reply-To: <20130603183057.GA9868@1wt.eu>

Willy, Jason,

On Mon, 3 Jun 2013 20:30:57 +0200, Willy Tarreau wrote:

> I remember this discussion, but it is different and does not apply here.
> Sebastian fixed an issue with a properly configured NIC which used to
> lose its MAC, so the solution consisted in saving it early in the DT.
> 
> In the mv_neta case, the NICs are not configured yet and we need to
> find the MAC somewhere. I only found it in the ATAGs and nowhere else.
> Well, in fact u-boot sets it on the MAC used to boot from the network
> if such a boot is performed, but that's all. So in practice you boot
> without the MAC address anywhere but in the ATAGs. I'd be happy to
> find a way to parse non-standard atags in a board-specific file but
> they're lost early it seems :-(

I confirm this. Only the one NIC that was used for network booting gets
its MAC address assigned in the hardware registers, the other three NIC
have their MAC address left to zero by the bootloader. And of course,
if you don't do network booting, the four NICs will have their MAC left
to zero.

So Sebastian's approach does not work for mvneta.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2013-06-04  8:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 16:45 [PATCH] ARM: atags: add support for Marvell's u-boot Thomas Petazzoni
2013-06-03 16:57 ` Jason Cooper
2013-06-03 17:09   ` Thomas Petazzoni
2013-06-03 17:42     ` Jason Cooper
2013-06-03 17:10 ` Russell King - ARM Linux
2013-06-03 17:56   ` Willy Tarreau
2013-06-03 18:14     ` Jason Cooper
2013-06-03 18:26       ` Jason Cooper
2013-06-03 18:30       ` Willy Tarreau
2013-06-03 18:41         ` Jason Cooper
2013-06-03 19:07           ` Nicolas Pitre
2013-06-03 19:17             ` Jason Cooper
2013-06-03 19:46               ` Nicolas Pitre
2013-06-03 21:07               ` Willy Tarreau
2013-06-04  8:13               ` Thomas Petazzoni
2013-06-04  8:48                 ` Sebastian Hesselbarth
2013-06-04 10:50                   ` Jason Cooper
2013-06-04  8:10             ` Thomas Petazzoni
2013-06-04  8:43               ` Sebastian Hesselbarth
2013-06-03 19:01         ` Nicolas Pitre
2013-06-03 21:04           ` Willy Tarreau
2013-06-04  8:05         ` Thomas Petazzoni [this message]

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=20130604100518.167484e1@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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