All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Peter <st3fanp3t3r@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building system for the Marvell's ARMADA A385 borad to resolve the VLAN trunk issue
Date: Fri, 25 Sep 2015 09:39:35 +0200	[thread overview]
Message-ID: <5604FA37.7040205@gmail.com> (raw)
In-Reply-To: <944894A3EB1D044A9003B2F944389BB20474C34C8C@svr-wa-exch1.atg.lc>

Hi Tommy

Am 25.09.2015 um 00:53 schrieb Lee, Tommy:
> Hi,
> Yesterday I used one of four Marvell's DTB files with my 4.0.4 system zImage built with mvebu_v7_defconfig. The boot process automatically enabled only eth0.
> 
> Unfortunately I do not have the DTS file for building that DTB file. I am reviewing the relevant DTS files, in the 2015.05 and Marvell's 2012.11 file systems, to try to resolve the eth1 enabling issue now.

dtc, the device tree compiler, can decompile dtb to dts. If memory
serves right, you can use something along

dtc -I DTB -O DTS yourfile.dtb

With kind regards

Stefan Peter

  reply	other threads:[~2015-09-25  7:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 18:20 [Buildroot] Building system for the Marvell's ARMADA A385 borad to resolve the VLAN trunk issue Lee, Tommy
2015-09-21 19:57 ` Arnout Vandecappelle
2015-09-21 22:28   ` Lee, Tommy
2015-09-21 22:49     ` Arnout Vandecappelle
2015-09-21 23:47       ` Lee, Tommy
2015-09-23 15:06   ` Thomas Petazzoni
2015-09-23 17:58     ` Lee, Tommy
2015-09-24  7:26       ` Thomas Petazzoni
2015-09-24 21:27         ` Lee, Tommy
2015-09-24  0:24     ` Lee, Tommy
2015-09-24 21:48     ` Peter Korsgaard
2015-09-24 22:53       ` Lee, Tommy
2015-09-25  7:39         ` Stefan Peter [this message]
2015-09-25 16:07           ` Lee, Tommy
2015-09-25  7:34       ` Thomas Petazzoni
2015-09-25  7:41         ` Peter Korsgaard
2015-09-25  7:53           ` Thomas Petazzoni
2015-09-25  8:57             ` Peter Korsgaard

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=5604FA37.7040205@gmail.com \
    --to=st3fanp3t3r@gmail.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 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.