Debian Bug report logs - #848911
u-boot: add support for cubox i4x4

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: peter green <peter.green-3@manchester.ac.uk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: u-boot: add support for cubox i4x4

Date: Tue, 20 Dec 2016 18:21:40 +0000

Package: u-boot

The cubox i4x4 is a version of the cubox i4pro but with 4 gigabytes of 
ram (3.8 usable due to address space limitations) instead of two. It 
seems to be reasonablly popular among Debian folks. Currently Debian 
u-boot can boot the box but only leaves 2 gigabytes of ram usable.

More specifically it seems that the i4 uses four chips each four 
gigabits in size while the i4x4 also uses four chips but they are 8 
gigabits in size. Changing the ram setting is trivial but obviously 
breaks support for the cubox i4 (which is also popular among Debian folks).

Ideally we would have runtime autodetection but it doesn't seem anyone 
has stepped forward to implement/forward port it for mainline u-boot. So 
I spoke to vagrantc on irc about whether it was ok to build a seperate 
flavour for the i4x4

He seemed ok with the idea I wrote a quick patch to make it a build time 
option and build both flavours.

Interestingly the changes only seem to affect spl not u-boot itself. I'm 
not sure if it's possible to build just spl for a variant and if-so 
whether it would be a good idea.

I have tested the builds on my cubox i4x4 and they see the expected 
ammounts of ram.

Debdiff attatched.

P.S. the instructions in the u-boot readme reffer to mmcblk0 but on 
recent kernels the SD card slot on the cubox seems to come up as mmcblk1

Message #10 received at 848911@bugs.debian.org (full text, mbox, reply):

From: Peter Green <plugwash@debian.org>

To: 848911@bugs.debian.org

Subject: Re: u-boot: add support for cubox i4x4

Date: Tue, 20 Dec 2016 18:49:26 +0000

[Message part 1 (text/plain, inline)]

On 20/12/16 18:21, peter green wrote:
>
> Debdiff attatched.
>
Really attatched this time.

[u-boot.debdiff (text/plain, attachment)]

Message #15 received at 848911@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: peter green <peter.green-3@manchester.ac.uk>, 848911@bugs.debian.org

Subject: Re: Bug#848911: u-boot: add support for cubox i4x4

Date: Tue, 20 Dec 2016 12:44:11 -0800

[Message part 1 (text/plain, inline)]

Control: tags 848911 pending

On 2016-12-20, peter green wrote:
> The cubox i4x4 is a version of the cubox i4pro but with 4 gigabytes of 
> ram (3.8 usable due to address space limitations) instead of two.
...
> Ideally we would have runtime autodetection but it doesn't seem anyone 
> has stepped forward to implement/forward port it for mainline u-boot.
...
> Interestingly the changes only seem to affect spl not u-boot itself. I'm 
> not sure if it's possible to build just spl for a variant and if-so 
> whether it would be a good idea.
>
> I have tested the builds on my cubox i4x4 and they see the expected 
> ammounts of ram.

Thanks for the patch!

Works for me on both the cubox-i4x4 and cubox-i4pro, so I'll add it to
the u-boot package soon.

Might make some minor changes to the patch as not sure all 4GB capable
variants use the 4x4 name, and will see if i can figure out a clever way
to only distribute a single u-boot.img file since they're identical
(thanks to reproducible builds).


> P.S. the instructions in the u-boot readme reffer to mmcblk0 but on 
> recent kernels the SD card slot on the cubox seems to come up as mmcblk1

Still come up as mmcblk0 for my cubox-i4x4 running 3.16.x from
jessie. My guess is it's kernel version specific, and so I'm going to
rely on people figuring that much out on their own...

live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 848911-close@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: 848911-close@bugs.debian.org

Subject: Bug#848911: fixed in u-boot 2016.11+dfsg1-3

Date: Thu, 22 Dec 2016 05:04:37 +0000

Source: u-boot
Source-Version: 2016.11+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
u-boot, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 848911@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian <vagrant@debian.org> (supplier of updated u-boot package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 21 Dec 2016 20:44:44 -0800
Source: u-boot
Binary: u-boot u-boot-imx u-boot-qcom u-boot-tegra u-boot-omap u-boot-sunxi u-boot-exynos u-boot-rockchip u-boot-rpi u-boot-tools
Architecture: source
Version: 2016.11+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian <vagrant@debian.org>
Changed-By: Vagrant Cascadian <vagrant@debian.org>
Description:
 u-boot     - A boot loader for embedded systems
 u-boot-exynos - A boot loader for exynos systems
 u-boot-imx - A boot loader for imx systems
 u-boot-omap - A boot loader for omap systems
 u-boot-qcom - A boot loader for qcom systems
 u-boot-rockchip - A boot loader for rockchip systems
 u-boot-rpi - A boot loader for Raspberry PI systems
 u-boot-sunxi - A boot loader for sunxi systems
 u-boot-tegra - A boot loader for NVIDIA Tegra systems
 u-boot-tools - companion tools for Das U-Boot bootloader
Closes: 848557 848911
Changes:
 u-boot (2016.11+dfsg1-3) unstable; urgency=medium
 .
   [ Peter Michael Green ]
   * u-boot-imx: Add patch to add an mx6cuboxi4x4 target, supporting boards
     with 4GB of ram (Closes: #848911).
 .
   [ Vagrant Cascadian ]
   * u-boot-sunxi: Add patches to support orangepi_zero.
     (Closes: #848557). Thanks to Mateusz Łukasik.
   * Add Rick Thomas to mx6cuboxi testers.
Checksums-Sha1:
 02886deac402c804acf89a9afbe88c5d72e7309f 2693 u-boot_2016.11+dfsg1-3.dsc
 04f9264f70e8b62c1a34757e5b375e468cdad02b 37716 u-boot_2016.11+dfsg1-3.debian.tar.xz
Checksums-Sha256:
 5b4e28b46037690501ce4a8320a328ac0a0ddf4f4cb8731ce446bccc40adecc7 2693 u-boot_2016.11+dfsg1-3.dsc
 192519239159d558f6017ff5f464aa44b81ed7acf98ee240475a444a5a954f1b 37716 u-boot_2016.11+dfsg1-3.debian.tar.xz
Files:
 dca5419d331994132eed38f2dd77126f 2693 admin optional u-boot_2016.11+dfsg1-3.dsc
 723e4a94577a0ab818f9cb7e0ed2579f 37716 admin optional u-boot_2016.11+dfsg1-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEEcDardHbDotegGFCHt4uC1IFLkbYFAlhbW+MTHHZhZ3JhbnRA
ZGViaWFuLm9yZwAKCRC3i4LUgUuRtpuxEACZb9KOW688c2zNjao/kKbNBruDAm5i
SPbL5bVZCx29fJYYmHOy1qR0w+/crV2YtqZh/CiiyKS+oruymvJmdN6tioVQHUMF
Tq1s2d1mZtnJkNxf853rDES+lD8n+8QmNgaFkGHqPgtZN826naah0r98etXIoQOB
L8gcL5HyAS2loGYxgywOLi1QBejjKzG59S38ybiPlWqEGjcugcE4wFBPOsJ8gIDf
Xnm1eJ03VzyIdroRVj2H2wrPRJ9ZQPVHaYlgnNcyKoS+NX2jSBP/VCiKmUYZ2Sri
IN9Nxlg3ilZt6p2xtVH+VgRJJ0t7RCLLp7JG5AXLfcvtTIhHo0e9xIolb0HQmJK2
ND4zLCZx1x0oFNDyPIkIz+/0dE9TEPgVUEJfeaL4m9RB5uAjM3jDSdvCdCq30SCN
sP3TVi3vfc6PGrN6sBF+IyTS6gNuGVcBeBzT+fKzPOSEfDOdQHARbc19OuG5VVEn
7I/bEnhSxGoD4+GXJC+p+Jv2ndcffX+cBniWaEzZOr8EwVh0RqQPbHdd50NsUy1j
1fIKKfoF27K7SzkdZZfqcl7OVOjR4l7KkYZMEBw9ZBuZz5iSEKDwxwhxwurqQJ8X
hpfQYYVkdEcXadajHIrS2MrxlKFhY390S2XVQIRfXdjuNcOhxxSFadTekp//YylN
P3rH66bAma56dw==
=c04z
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.