From: david.goodenough@btconnect.com (David Goodenough)
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:32:47 +0000 [thread overview]
Message-ID: <3064359.D6vvF0Rimq@stargate> (raw)
In-Reply-To: <54CB822B.8080809@gmail.com>
On Friday 30 January 2015 14:07:55 Sebastian Hesselbarth wrote:
> [Re-adding the most obvious People to Cc]
>
> On 30.01.2015 13:44, David Goodenough wrote:
> > On Friday 30 January 2015 13:03:59 Sebastian Hesselbarth wrote:
> >> On 30.01.2015 12:41, Jean-Francois Moine wrote:
> >>> On Fri, 30 Jan 2015 12:00:16 +0100
> >>
> >>> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> >> That what dtsi's are made for with one exception: the dtsi cannot "run"
> >> on its own but needs at least one baseboard.dts that includes it. We
> >> could create a "bare"-baseboard that represents what is (easily)
> >> accessible on the SoM itself. Given the fact that even UART0 needs a
> >> baseboard that grabs it from the SoM connector, I see no value in that.
> >>
> >>> In any case, any real cm-a510 board should work with the
> >>> generic/full .dts even if some hardware modules are lacking. No?
> >>
> >> 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.
> >
> > This sounds like capes on the BeagleBoard. Are these extension boards
> > self-identifying? If so then the approach used with the capes might work
> > here too.
>
> David,
>
> IMHO capes are a different thing. The BB can run just fine without any
> cape installed, the cm-a510 cannot run without a baseboard. Also, once
> you have your SoM installed it cannot change over runtime, there is no
> need for any dynamic overlays and such.
>
> You can build some 5 or 10 different configurations given the SoM and
> a specific baseboard but not hundreds of possible combinations.
> Besides, Gabriel is the first in almost 2 years that actually has an
> cm-a510 - so, I doubt we'll have to mainline dozens of baseboards
> using the cm-a510 in the near future.
>
> Regarding the self-identification, it would be great if the actual SoM
> configuration would be stored in the (always available) SPI flash, but
> from my experience with the boards I have seen so far, I have a bad
> feeling about it ;) A quick look at the sb-a510 (the compulab baseboard
> for cm-a510) suggests that there is more configuration available but
> by jumpers that (hopefully) can be read out by GPIOs at least.
>
> The best similar board available in mainline I can remember is the
> SolidRun Hummingboard, i.e. one baseboard that can be equipped with
> 3-4 different SoMs.
Ah this sounds like history repeating itself. I have some old PC-104
Compulab boards which had pluggable CPUs.
They were x86 based, so DTS was not a question. I guess that the
only approach is to start with the plugin, and then add the baseboard
as a standard include.
David
>
> Sebastian
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2015-01-30 13:32 UTC|newest]
Thread overview: 47+ 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 9:44 ` Sebastian Hesselbarth
2015-01-30 9:44 ` Sebastian Hesselbarth
2015-01-30 10:31 ` Jean-Francois Moine
2015-01-30 10:31 ` Jean-Francois Moine
2015-01-30 11:00 ` Sebastian Hesselbarth
2015-01-30 11:00 ` Sebastian Hesselbarth
2015-01-30 11:00 ` Sebastian Hesselbarth
2015-01-30 11:41 ` Jean-Francois Moine
2015-01-30 11:41 ` Jean-Francois Moine
2015-01-30 11:41 ` Jean-Francois Moine
2015-01-30 12:03 ` Sebastian Hesselbarth
2015-01-30 12:03 ` Sebastian Hesselbarth
2015-01-30 12:03 ` Sebastian Hesselbarth
2015-01-30 12:39 ` Jean-Francois Moine
2015-01-30 12:39 ` Jean-Francois Moine
2015-01-30 12:50 ` Sebastian Hesselbarth
2015-01-30 12:50 ` Sebastian Hesselbarth
2015-01-30 12:50 ` Sebastian Hesselbarth
2015-02-01 14:12 ` Gabriel Dobato
2015-02-01 14:16 ` Gabriel Dobato
2015-02-05 22:13 ` Sebastian Hesselbarth
2015-02-05 22:13 ` Sebastian Hesselbarth
2015-02-06 7:58 ` Jean-Francois Moine
2015-02-06 7:58 ` Jean-Francois Moine
2015-02-06 7:58 ` Jean-Francois Moine
2015-02-06 10:05 ` Sebastian Hesselbarth
2015-02-06 10:05 ` Sebastian Hesselbarth
2015-02-06 10:05 ` Sebastian Hesselbarth
2015-02-06 10:50 ` Jean-Francois Moine
2015-02-06 10:50 ` Jean-Francois Moine
2015-02-06 10:52 ` Russell King - ARM Linux
2015-02-06 10:52 ` Russell King - ARM Linux
2015-02-06 10:48 ` Russell King - ARM Linux
2015-02-06 10:48 ` Russell King - ARM Linux
2015-02-06 9:19 ` Gabriel Dobato
2015-02-06 10:00 ` Sebastian Hesselbarth
2015-02-06 10:00 ` Sebastian Hesselbarth
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:07 ` Sebastian Hesselbarth
2015-01-30 13:32 ` David Goodenough [this message]
2015-01-30 6:06 Jean-Francois Moine
-- strict thread matches above, loose matches on Subject: below --
2015-01-30 6:06 Jean-Francois Moine
2015-01-30 6:06 Jean-Francois Moine
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=3064359.D6vvF0Rimq@stargate \
--to=david.goodenough@btconnect.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.