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, 06 Feb 2015 11:00:30 +0100 [thread overview]
Message-ID: <54D490BE.9040201@gmail.com> (raw)
In-Reply-To: <54D48711.8060903@gmail.com>
On 06.02.2015 10:19, Gabriel Dobato wrote:
> On 05/02/15 23:13, Sebastian Hesselbarth wrote:
>> great you can boot a recent kernel. I guess you had to quite heavily
>> modify current dove-cm-a510.dts? Can you upload the one you use now
>> to any pastebin and send the link?
>
> Not, I only had to include eth (as Mr. Moine told me) and mdio because I
> mount rootfs via NFS.
Ok, I think we can work out the most obvious stuff (mmc, pcie), too.
>> You didn't mention if you really use the sb-a510, i.e. the Compulab
>> reference baseboard. Is it what you are using with your cm-a510?
>
> Yes, sorry for that, I am using SB-A510.
Ok. Then for the first some versions, I'll stick with the manual.
That should be sufficient to create a working sb-a510 dts.
FWIW, is there any Compulab kernel or u-boot source available online?
It would help to figure out the GPIO pins and undocumented connections.
> I wonder if it will there be driver support for the second ethernet
> (PCIE attached NIC), and the rest of features remained, for DT...
AFAIR it was some realtek PCIe NIC.. we have PCIe working on Dove, so
I guess it shouldn't be a real problem.
> Before using DT, I tried to boot a simple uImage (without DT), but it
> did not boot
>
> the last ouput in the kernel trade was:
> ...
> /uncompressing linux... done, booting the kernel./
>
> nothing else.... I wonder if there is a problem with the ID machine, I
> don't know...
Hard to tell. Could be anything.
> The U-Boot used was the one provided by Compulab (Maybe the problem is
> on Uboot...)
If you know how to append the dtb to the zImage it should work on any
u-boot. If it doesn't support bootz, you'll have to make a uImage of
the dtb-appended zImage or simply try to "go" to the zImage address.
Sebastian
next prev parent reply other threads:[~2015-02-06 10:00 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
[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 [this message]
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=54D490BE.9040201@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).