Bug#739976: add device support: mirabox

2014-03-02 Thread Jasmin Schnatterbeck
Hi,

On Sat, 2014-03-01 at 02:42 +, Ian Campbell wrote:
 On Mon, 2014-02-24 at 14:41 +0100, Jasmin Schnatterbeck wrote:
  Package: flash-kernel
  Version: 3.13
  Severity: important
  
  The device DB is missing support for the Mirabox.
  
  Proposal:
 
 Thanks for this.
 
 Perhaps you could also add some information to
 http://wiki.debian.org/DebianOn ?
 

The process is very similar to the one of the Dreamplug - may I can
integrate this as soon as kernel support/package is determined:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739972

  Machine: Globalscale Mirabox
  Kernel-Flavors: armmp
  DTB-Id: armada-370-mirabox.dtb
  DTB-Append: yes
 
 Is this really required on new platform like this?
 
 I would expect that a newish system would have a u-boot which supports
 FDT natively rather that via appending. Does loading the dtb at some
 address and adding that address as a third argument to the bootz or
 bootm command work?
 
 On the other hand you say the u-boot is quite old so maybe this is
 correct, I just wanted to check that you didn't just copy this bit from
 an older platform.

yes, unfortunately the bootloader is old and does not support FDT.
May there will be a DT-capable bootloader from the manufacturer in the
future, but I am not sure about that.

 
  U-Boot-Kernel-Address: 0x8000
  U-Boot-Initrd-Address: 0x0
  Boot-Device: /dev/sdb1
  Boot-Kernel-Path: uImage
  Boot-Initrd-Path: uInitrd
  Boot-DTB-Path: dtb
  Required-Packages: u-boot-tools
  Bootloader-Sets-Root: no
 
 This is now called Bootloader-Sets-Incorrect-Root.

OK; found in commit 850c8fc323bbab52a6264035d11edd372ce2596f

The bootloader sets some UBI device on internal NAND as root without
changes... but as the u-boot env variables need to be adapted anyway for
booting from the SD Card, it is preferred, that the kernel
command-line-parameter for root works as expected.

 
 OOI do you know if mainline u-boot getting any support for this device
 (whether based on the vendor's version or not)?
 

As far as I know, there are no efforts to mainline the u-boot-support.
There are some experiments regarding the barebox bootloader, but
currently with serial port support only.
http://free-electrons.com/blog/barebox-2013-07/

The old u-boot seems to be the only bootloader that works reasonable in
order to boot the device...

Jasmin


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#739972: missing kernel config options for support of mirabox

2014-02-24 Thread Jasmin Schnatterbeck
Source: linux-image-3.13-trunk-armmp
Version: 3.13-1~exp1
Severity: important

the mentioned multiplatform kernel ist intended to run on armada 370
SOCs. A system using this SOC is the Mirabox.

I noticed, that the following modules are missing in the armmp kernel to
support the device properly:

xhci controller:
CONFIG_USB_XHCI_HCD=m

mwifiex wifi:
CONFIG_MWIFIEX=m
CONFIG_MWIFIEX_SDIO=m

Futhermore hctosys-on-boot does not work. As the /etc/init.d/hwlock.sh
script does not run in rcS, because udev is already active, the system
time relies on the kernel, that needs to set it from rtc on boot time.
In order to make this work, the rtc driver must be compiled-in (as far
as I investigated the situation):

RTC_DRV_MV=y

Furthermore the PCI-Controller of the device needs the following kernel
option to make it work:

CONFIG_PCI_MVEBU=y

The mentioned modifications are tested locally and work.

If the options for RTC and PCI (non-module) conflict with other options
(related to another device), a separated flavour would still be
necessary.

Cheers
Jasmin


smime.p7s
Description: S/MIME cryptographic signature


Bug#739976: add device support: mirabox

2014-02-24 Thread Jasmin Schnatterbeck
Package: flash-kernel
Version: 3.13
Severity: important

The device DB is missing support for the Mirabox.

Proposal:

Machine: Globalscale Mirabox
Kernel-Flavors: armmp
DTB-Id: armada-370-mirabox.dtb
DTB-Append: yes
U-Boot-Kernel-Address: 0x8000
U-Boot-Initrd-Address: 0x0
Boot-Device: /dev/sdb1
Boot-Kernel-Path: uImage
Boot-Initrd-Path: uInitrd
Boot-DTB-Path: dtb
Required-Packages: u-boot-tools
Bootloader-Sets-Root: no

Even kernel 3.13. does not support the device's internal
NAND chip -  /dev/sdb is the microsd-slot of the device which can be used
as rootfs.
Bootloader is u-boot (heavily modified by the manufacturer and fairly
old) with unusable ext2load (at least for ext4), so separate boot
partition /dev/sdb1 for fatload makes sense.

Cheers
Jasmin


smime.p7s
Description: S/MIME cryptographic signature