From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Starting network...
Date: Wed, 2 Sep 2015 00:12:13 +0200 [thread overview]
Message-ID: <20150902001213.6aa70acb@free-electrons.com> (raw)
In-Reply-To: <944894A3EB1D044A9003B2F944389BB20474C345D2@svr-wa-exch1.atg.lc>
Hello,
On Tue, 1 Sep 2015 15:03:58 -0700, Lee, Tommy wrote:
> In the buildroot-2015.05 folder the armada-385-gp.dts file does not exist but the armada-385-db-ap.dts one.
Buildroot does *not* contain any armada-*.dts file. Those files come
with the kernel sources. You are confusing things, it seems.
There is indeed no armada-385-gp.dts file in the kernel, as it's called
armada-388-gp.dts.
> Last week I built armada-385-db-ap.dtb using the following .config DTS and eth0 with no problems:
>
>
>
> BR2_SYSTEM_DHCP="eth0"
>
> BR2_LINUX_KERNEL_DTS_SUPPORT=y
>
> BR2_LINUX_KERNEL_USE_INTREE_DTS=y
>
> # BR2_LINUX_KERNEL_USE_CUSTOM_DTS is not set
>
> BR2_LINUX_KERNEL_INTREE_DTS_NAME="armada-385-db-ap"
>
>
>
> I just used the settings again and built zImage and armada-385-db-ap. This time the armada-385-db-ap.dtb has the same md5sum value as the one I built last week.
And? I don't see where your question is here. Also, I don't understand
why you're sometimes referring to the Armada 388 GP and sometimes to
the Armada 385 DB AP. Those are completely different boards, so you
cannot use the Device Tree for one platform on the other platform.
> On the board, the boot process shows:
>
>
>
> Starting network...
>
> udhcpc (v1.23.2) started
>
> Sending discover...
>
> [ 4.732186] mvneta f1070000.ethernet eth2: Link is Up - 100Mbps/Half - flow f
>
> Sending discover...
>
> Sending select for 10.28.1.47...
>
> Lease of 10.28.1.47 obtained, lease time 1209600
>
> deleting routers
>
> adding dns 10.28.5.20
>
> adding dns 10.4.5.7
>
> ssh-keygen: generating new host keys: RSA1 RSA DSA ECDSA ED25519
>
> Starting sshd: OK
>
> Starting network management serv[ 11.715258] NET: Registered protocol family 0
>
> ices:.
>
>
>
> Welcome to Buildroot
>
> buildroot login:
>
>
>
> After login, the ifconfig result is:
>
>
>
> # ifconfig
Use ifconfig -a to see all interfaces.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-01 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 23:36 [Buildroot] Starting network Lee, Tommy
2015-08-25 17:54 ` Thomas Petazzoni
2015-09-01 18:33 ` Lee, Tommy
2015-09-01 19:14 ` Thomas Petazzoni
2015-09-01 22:03 ` Lee, Tommy
2015-09-01 22:12 ` Thomas Petazzoni [this message]
2015-09-01 22:36 ` Lee, Tommy
-- strict thread matches above, loose matches on Subject: below --
2015-08-24 23:38 Lee, Tommy
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=20150902001213.6aa70acb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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