Bug#839595: flash-kernel: Please add support for SolidRun Clearfog

[Karsten Merker <merker@debian.org>]

On Sun, Oct 02, 2016 at 04:53:58PM +0200, Christoph Egger wrote:

> Package: flash-kernel
> Version: 3.69
> Severity: wishlist
> 
> Hi!
> 
> Please consider adding clearfog support. The system works fine with
> mainline u-boot + kernel. Hopefully I have added all necessary
> information below:
> 
> | Machine: SolidRun Clearfog A1
> | Kernel-Flavors: armmp armmp-lpae
> | DTB-Id: armada-388-clearfog.dtb
> | Required-Packages: u-boot-tools
> 
> | # fw_printenv
> | baudrate=115200
> | bootargs=console=ttyS0,115200n8 rootdelay=10 bootwait=10 rootwait=10 root=/dev/mmcblk0p1
> | bootcmd=ext4load mmc 0:2 0x100000 dtb ; ext4load mmc 0:2 0x800000 vmlinuz-4.7.0-1-armmp ; ext4load mmc 0:2 0x1800000 initrd.img-4.7.0-1-armmp.uimage ; bootz 0x800000 0x1800000 0x100000

Hello Christoph,

is this the environment from mainline u-boot or the environment
from the original Marvell u-boot?  I ask because there are a few
things that look a bit uncommon to me:

- This environment doesn't seem to be based on the common boot
  environment that mainline u-boot uses on most (although not
  all) modern platforms since v2014.10.  I am not familiar with
  the armada-388 platform, so I currently don't know whether it
  has moved to the common boot environment or not.

- The bootcmd loads the kernel as a zImage but the initrd as a
  uImage, which is a very unusual combination and I am unsure
  whether that could even work properly.  The normal case is
  either loading the kernel as a zImage and the initrd as a plain
  initrd image and booting them with bootz, or loading both the
  kernel and the initrd as uImages and booting them with bootm.

Is mmc0 an SD card or an EMMC chip? Have you upgraded the system
from a marvell u-boot to a mainline u-boot or has it been set up
from scratch with a mainline u-boot?  I ask because mainline
u-boot by default keeps the existing environment on upgrade, so
if you have upgraded the system from a marvell u-boot to a
mainline u-boot, you might still have an old non-mainline
environment.

You could try running "env default -f -a" at the u-boot prompt,
which would reset your active environment to the default
environment of the u-boot version you are currently running.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.