linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wd@denx.de (Wolfgang Denk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mxs: m28evk: Disable OCOTP OUI loading
Date: Thu, 20 Sep 2012 17:10:21 +0200	[thread overview]
Message-ID: <20120920151021.7307C203A17@gemini.denx.de> (raw)
In-Reply-To: <505B1FC2.2090609@free-electrons.com>

Dear Maxime,

In message <505B1FC2.2090609@free-electrons.com> you wrote:
> 
> > Fix it and send patch, so this problem doesn't spread.
> 
> I'm sorry, but you still miss the point.

I'm not so sure about this.

> If someone wants to use another bootloader than U-boot (or a possible
> patched barebox), or none other than the bootlets to boot directly the
> Linux (with an appended device tree), you will still have no way to get
> the NIC from the OCOTP, and I'm sorry, but it is just wrong.

With device tree supoort enabled, the regular way to pass the MAC
address to a network interface (that needs one) is through the device
tree.

There are several options how such information gets there.  Boot
loaders with built-in DT support may fill in the MAC address
information into the DT before passing it to the Linux kernel.

If your boot method does not allow such dynamic adjustment, you ould
provide a statically configured device tree, which already includes
the MAC address.

> The kernel shouldn't rely on a particular feature of a given bootloader.

100% agreed.  And it does not.  It always uses the respective
information from the device tree.


So when you use bootlets, all you need to do is to insert the
respective MAC address entry to your device tree definition.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Every program has at least one bug and can be shortened by  at  least
one  instruction  --  from  which,  by induction, one can deduce that
every program can be reduced to one instruction which doesn't work.

  parent reply	other threads:[~2012-09-20 15:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 22:37 [PATCH] ARM: mxs: m28evk: Disable OCOTP OUI loading Marek Vasut
2012-09-19  3:15 ` Shawn Guo
2012-09-19  9:43   ` Marek Vasut
2012-09-19 10:33   ` Maxime Ripard
2012-09-19 10:50     ` Marek Vasut
2012-09-19 11:02       ` Maxime Ripard
2012-09-19 11:25         ` Marek Vasut
2012-09-19 11:44           ` Maxime Ripard
2012-09-19 11:51             ` Marek Vasut
2012-09-20 10:47           ` Wolfram Sang
2012-09-20 12:20             ` Marek Vasut
2012-09-20 12:56               ` Wolfram Sang
2012-09-20 13:10                 ` Marek Vasut
2012-09-20 13:53                   ` Maxime Ripard
2012-09-20 14:24                     ` Marek Vasut
2012-09-20 15:10                     ` Wolfgang Denk [this message]
2012-09-20 15:24                       ` Gregory CLEMENT
2012-09-20 15:31                         ` Marek Vasut
2012-09-20 17:09                         ` Wolfgang Denk
2012-09-20 16:33                     ` Marek Vasut
2012-09-20 17:01                       ` Maxime Ripard
2012-09-20 17:31                         ` Marek Vasut
2012-09-19 14:17 ` Shawn Guo

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=20120920151021.7307C203A17@gemini.denx.de \
    --to=wd@denx.de \
    --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;
as well as URLs for NNTP newsgroup(s).