From: Jean-Francois Moine <moinejf@free.fr>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Gabriel Dobato <dobatog@gmail.com>
Subject: Re: [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board
Date: Fri, 30 Jan 2015 11:31:18 +0100 [thread overview]
Message-ID: <20150130113118.5523ed68@armhf> (raw)
In-Reply-To: <54CB5267.5060004@gmail.com>
On Fri, 30 Jan 2015 10:44:07 +0100
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> I had a closer look on the Compulab website of the SoM [1] and think
> that we'll have to convert it to dove-cm-a510.dtsi and the baseboard
> Gabriel is using (maybe SBC-A510 [2]).
Sebastian,
I don't understand why the A510 contained in the cm-a510 should be
different from the one of the other boards (I just noticed a second
ethernet and a WiFi device - but, is the Compulab document up to date?).
If it is the same, the dove.dtsi should work (and it seems to work for
Gabriel).
The only difference with the cm-a510 is the presence or not of the
connectors. So, all the Dove devices could be enabled in the DT, and,
if some room is needed in the board, the .config could be adapted
removing the useless drivers and have a minimal kernel.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2015-01-30 10:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YH5bU-0005mG-3L@bombadil.infradead.org>
[not found] ` <E1YH5bU-0005mG-3L-PfSpb0PWhxZc2C7mugBRk2EX/6BAtgUQ@public.gmane.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 [this message]
2015-01-30 11:00 ` Sebastian Hesselbarth
[not found] ` <54CB6440.1010002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
2015-02-01 14:12 ` Gabriel Dobato
2015-02-01 14:16 ` Gabriel Dobato
2015-02-05 22:13 ` Sebastian Hesselbarth
[not found] ` <54D3EB26.9020909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
2015-02-06 9:19 ` Gabriel Dobato
[not found] ` <54D48711.8060903-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-06 10:00 ` Sebastian Hesselbarth
[not found] ` <1507191.iMZ4oC8rrr@stargate>
2015-01-30 13:07 ` Sebastian Hesselbarth
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
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=20150130113118.5523ed68@armhf \
--to=moinejf@free.fr \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=dobatog@gmail.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/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).