linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board
Date: Fri, 30 Jan 2015 13:50:59 +0100	[thread overview]
Message-ID: <54CB7E33.3080909@gmail.com> (raw)
In-Reply-To: <20150130133913.083d1ade@armhf>

On 30.01.2015 13:39, Jean-Francois Moine wrote:
> On Fri, 30 Jan 2015 13:03:59 +0100
> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
>> Nope. The cm-a510 is just an add-on for a baseboard, it does not make
>> a working board. Just think of it as a feature-improved SoC.
>
> Well, I understand a bit, but I don't see clearly the physical system,
> nor how each part gets its configuration for booting.

TBH, I completely missed that the cm-a510 can come in different
configurations, e.g. with or without WiFi. Nevertheless, considering
that there are only a handful of configurations available, IMHO the
right thing would be a dtsi with all possible options described by
corresponding but disabled nodes.

The actual physical system has to be determined at runtime in any
way and it should be done by the bootloader. However, even the
bootloader would be happy to find the right nodes to enable instead
of creating them from scratch.

> As you know better than I, it seems that you are the right person to
> create the .dtsi/.dts's :) and to explain Gabriel how to use them!

Well, nothing that should stop you from improving your skills :)

I'd be happy to take over, but I admit that my current lack of spare
time would only allow me to support Gabriel and you.

Let's wait for Gabriel's response on how he can help improving
Dove mainline with his cm-a510 and baseboard.

Sebastian

  reply	other threads:[~2015-01-30 12:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1YH5bU-0005mG-3L@bombadil.infradead.org>
2015-01-30  9:44 ` [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board Sebastian Hesselbarth
2015-01-30 10:31   ` Jean-Francois Moine
2015-01-30 11:00     ` Sebastian Hesselbarth
2015-01-30 11:41       ` Jean-Francois Moine
2015-01-30 12:03         ` Sebastian Hesselbarth
2015-01-30 12:39           ` Jean-Francois Moine
2015-01-30 12:50             ` Sebastian Hesselbarth [this message]
     [not found]               ` <54CE354F.5090106@gmail.com>
2015-02-05 22:13                 ` Sebastian Hesselbarth
2015-02-06  7:58                   ` Jean-Francois Moine
2015-02-06 10:05                     ` Sebastian Hesselbarth
2015-02-06 10:50                       ` Jean-Francois Moine
2015-02-06 10:52                       ` Russell King - ARM Linux
2015-02-06 10:48                     ` Russell King - ARM Linux
     [not found]                   ` <54D48711.8060903@gmail.com>
2015-02-06 10:00                     ` Sebastian Hesselbarth
2015-01-30 12:44           ` David Goodenough
2015-01-30 13:07             ` Sebastian Hesselbarth
2015-01-30 13:32               ` David Goodenough
2015-01-30  6:06 Jean-Francois Moine

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=54CB7E33.3080909@gmail.com \
    --to=sebastian.hesselbarth@gmail.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;
as well as URLs for NNTP newsgroup(s).