[Buildroot] Building system for the Marvell's ARMADA A385 borad to resolve the VLAN trunk issue

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Hello,

On Wed, 23 Sep 2015 10:58:15 -0700, Lee, Tommy wrote:

> Please view my in-line replies.

It would be nicer if you actually used an e-mail client that was
quoting properly the text you're replying to in the plain text version
of the e-mail (and avoid sending an HTML version).

> I received from my project management the Marvell's A385 package in
> July. Then I started the work on the board in the package -
> DB-88F6820-GP. What I have achieved is the success of building and
> booting the Linux-4.0.4 system on the DB-88F6820-GP board. The system
> is built with mvebu_v7_defconfig and armada-385-db-ap.dts.

This is not the correct Device Tree file. Use armada-388-gp.dts for the
DB-88F6820-GP. Using an incorrect Device Tree file might work
partially, but some devices may not work (especially network
interfaces, which are very often not configured in the same way between
different boards).

> My current problem, as I mentioned in my preceding email, is that the
> eth0 and eth1 interfaces cannot be enabled, but eth2 at the boot time.

Two things:

 * Remember what I already told you: the network interfaces are
   "inverted". eth0 is the second network interface, and eth1 is the
   first network interface.

 * Use "setenv fdt_skip_update yes" in U-Boot before booting, to tell
   the Marvell U-Boot to not do any magic fixup in the Device Tree
   before starting the kernel.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com