GNU bug report logs - #31308
[PATCH 0/3] Support u-boot on wandboard and mx6cuboxi

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 31308 in the body.
You can then email your comments to 31308 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Vagrant Cascadian <vagrant <at> debian.org>
To: guix-patches <at> gnu.org
Subject: [PATCH 0/3] Support u-boot on wandboard and mx6cuboxi
Date: Sun, 29 Apr 2018 00:28:26 -0700

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

The following patches enable u-boot builds for wandboard and mx6cuboxi.

Both u-boot builds require the inclusion of the "SPL" file.

Tested on Wandboard Solo and Hummingboard-i1.

live well,
  vagrant

Vagrant Cascadian (3):
  gnu: make-u-boot-package: Install 'SPL' files also.
  gnu: Add u-boot-wandboard.
  gnu: Add u-boot-mx6cuboxi.

 gnu/packages/bootloaders.scm | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

[0001-gnu-make-u-boot-package-Install-SPL-files-also.patch (text/x-diff, inline)]

From 1e1705ae3167c1e3eb149a7e30837b6fdca2aed1 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant <at> debian.org>
Date: Sun, 29 Apr 2018 04:33:00 +0000
Subject: [PATCH 1/3] gnu: make-u-boot-package: Install 'SPL' files also.

* gnu/packages/bootloaders.scm (make-u-boot-package)[arguments]: Add 'SPL'
files to the files installed during custom 'install phase.
---
 gnu/packages/bootloaders.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnu/packages/bootloaders.scm b/gnu/packages/bootloaders.scm
index 4350ff3a5..fc4570c2e 100644
--- a/gnu/packages/bootloaders.scm
+++ b/gnu/packages/bootloaders.scm
@@ -408,7 +408,7 @@ also initializes the boards (RAM etc).")
                       (libexec (string-append out "/libexec"))
                       (uboot-files (append
                                     (find-files "." ".*\\.(bin|efi|img|spl|itb|dtb)$")
-                                    (find-files "." "^MLO$"))))
+                                    (find-files "." "^(MLO|SPL)$"))))
                  (mkdir-p libexec)
                  (install-file ".config" libexec)
                  (for-each
-- 
2.17.0

[0002-gnu-Add-u-boot-wandboard.patch (text/x-diff, inline)]

From 30a21d289cf6a49f2a80ff66fb969b3bac511a08 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant <at> debian.org>
Date: Sun, 29 Apr 2018 04:38:05 +0000
Subject: [PATCH 2/3] gnu: Add u-boot-wandboard.

* gnu/packages/bootloaders.scm (u-boot-wandboard): New variable.
---
 gnu/packages/bootloaders.scm | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gnu/packages/bootloaders.scm b/gnu/packages/bootloaders.scm
index fc4570c2e..6a9fa36f2 100644
--- a/gnu/packages/bootloaders.scm
+++ b/gnu/packages/bootloaders.scm
@@ -463,6 +463,9 @@ also initializes the boards (RAM etc).")
 (define-public u-boot-nintendo-nes-classic-edition
   (make-u-boot-package "Nintendo_NES_Classic_Edition" "arm-linux-gnueabihf"))
 
+(define-public u-boot-wandboard
+  (make-u-boot-package "wandboard" "arm-linux-gnueabihf"))
+
 (define-public vboot-utils
   (package
     (name "vboot-utils")
-- 
2.17.0

[0003-gnu-Add-u-boot-mx6cuboxi.patch (text/x-diff, inline)]

From d86d0b14a4885328f09b4454d078a2b0df6c041a Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant <at> debian.org>
Date: Sun, 29 Apr 2018 06:39:10 +0000
Subject: [PATCH 3/3] gnu: Add u-boot-mx6cuboxi.

* gnu/packages/bootloaders.scm (u-boot-mx6cuboxi): New variable.
---
 gnu/packages/bootloaders.scm | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gnu/packages/bootloaders.scm b/gnu/packages/bootloaders.scm
index 6a9fa36f2..0db6ad3f6 100644
--- a/gnu/packages/bootloaders.scm
+++ b/gnu/packages/bootloaders.scm
@@ -466,6 +466,9 @@ also initializes the boards (RAM etc).")
 (define-public u-boot-wandboard
   (make-u-boot-package "wandboard" "arm-linux-gnueabihf"))
 
+(define-public u-boot-mx6cuboxi
+  (make-u-boot-package "mx6cuboxi" "arm-linux-gnueabihf"))
+
 (define-public vboot-utils
   (package
     (name "vboot-utils")
-- 
2.17.0

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

Message #10 received at 31308-done <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Vagrant Cascadian <vagrant <at> debian.org>
Cc: 31308-done <at> debbugs.gnu.org
Subject: Re: [bug#31308] [PATCH 0/3] Support u-boot on wandboard and mx6cuboxi
Date: Sun, 29 Apr 2018 17:26:16 +0200

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

Hi,

thanks!

I've applied these patches to master.

Just a heads-up, there are now files "SPL" and "spl" (with different contents) being installed.  That's fine as long as we are using a case-sensitive filesystem, which we probably are.

Let's just keep an eye on it.

[Message part 2 (application/pgp-signature, inline)]

Message #13 received at 31308 <at> debbugs.gnu.org (full text, mbox):

From: Vagrant Cascadian <vagrant <at> debian.org>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 31308 <at> debbugs.gnu.org
Subject: Re: [bug#31308] [PATCH 0/3] Support u-boot on wandboard and mx6cuboxi
Date: Sun, 29 Apr 2018 22:41:15 -0700

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

On 2018-04-29, Danny Milosavljevic wrote:
> I've applied these patches to master.

Thanks for being the one to apply my first contribution to guix! :)


> Just a heads-up, there are now files "SPL" and "spl" (with different
> contents) being installed.  That's fine as long as we are using a
> case-sensitive filesystem, which we probably are.

I think the two matches are against files the ending in .spl and files
that are exactly "SPL", so this shouldn't be much of an issue, even with
a case-insensitive filesystem. I imagine many other things would break
with a case-insensitive filesystem, too...


live well,
  vagrant

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

Message #16 received at 31308 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Vagrant Cascadian <vagrant <at> debian.org>
Cc: 31308 <at> debbugs.gnu.org
Subject: Re: [bug#31308] [PATCH 0/3] Support u-boot on wandboard and mx6cuboxi
Date: Mon, 30 Apr 2018 23:01:01 +0200

Hi Vagrant,

Vagrant Cascadian <vagrant <at> debian.org> skribis:

> The following patches enable u-boot builds for wandboard and mx6cuboxi.
>
> Both u-boot builds require the inclusion of the "SPL" file.
>
> Tested on Wandboard Solo and Hummingboard-i1.

Did you install these U-Boot packages on these boards, or did you go as
far as running GuixSD on them?

Thank you for these first patches!  :-)

Ludo’.

Message #19 received at 31308 <at> debbugs.gnu.org (full text, mbox):

From: Vagrant Cascadian <vagrant <at> debian.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 31308 <at> debbugs.gnu.org
Subject: Re: [bug#31308] [PATCH 0/3] Support u-boot on wandboard and mx6cuboxi
Date: Mon, 30 Apr 2018 14:18:11 -0700

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

On 2018-04-30, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant <at> debian.org> skribis:
>> The following patches enable u-boot builds for wandboard and mx6cuboxi.
>>
>> Both u-boot builds require the inclusion of the "SPL" file.
>>
>> Tested on Wandboard Solo and Hummingboard-i1.
>
> Did you install these U-Boot packages on these boards, or did you go as
> far as running GuixSD on them?

I only went as far as using guix to build the bootloaders and manually
install them, and tested that they successfully booted... Debian. :)

The boards I tested on were only single-core with 512MB of ram, so would
be a bit difficult to run GuixSD on.

However, this u-boot build should also work on the Wandboard Quad or
CuBox-i4, which have quad-core CPUs and 2-4GB of ram, which might
actually be useable with GuixSD. There's also been recent good progress
on free graphics drivers for this family of SoC.


> Thank you for these first patches!  :-)

Thanks for having such a nice project to contribute patches to!

I've got some work-in-progress on a few more boards, but haven't had a
chance to boot test them, and some with non-trivial changes (at least
with my rank beginner guile skills)... will submit eventually. :)


live well,
  vagrant

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

Message #22 received at 31308 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Vagrant Cascadian <vagrant <at> debian.org>
Cc: 31308 <at> debbugs.gnu.org
Subject: Re: [bug#31308] [PATCH 0/3] Support u-boot on wandboard and mx6cuboxi
Date: Tue, 01 May 2018 21:55:12 +0200

Hello,

Vagrant Cascadian <vagrant <at> debian.org> skribis:

> On 2018-04-30, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant <at> debian.org> skribis:
>>> The following patches enable u-boot builds for wandboard and mx6cuboxi.
>>>
>>> Both u-boot builds require the inclusion of the "SPL" file.
>>>
>>> Tested on Wandboard Solo and Hummingboard-i1.
>>
>> Did you install these U-Boot packages on these boards, or did you go as
>> far as running GuixSD on them?
>
> I only went as far as using guix to build the bootloaders and manually
> install them, and tested that they successfully booted... Debian. :)

Heh, not too bad!  ;-)

> The boards I tested on were only single-core with 512MB of ram, so would
> be a bit difficult to run GuixSD on.

Yeah.  I hope we’ll do better in the future in that regard.

> However, this u-boot build should also work on the Wandboard Quad or
> CuBox-i4, which have quad-core CPUs and 2-4GB of ram, which might
> actually be useable with GuixSD. There's also been recent good progress
> on free graphics drivers for this family of SoC.

[...]

> I've got some work-in-progress on a few more boards, but haven't had a
> chance to boot test them, and some with non-trivial changes (at least
> with my rank beginner guile skills)... will submit eventually. :)

Heh, sounds exciting.  :-)

Thank you,
Ludo’.

Message #25 received at 31308 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Vagrant Cascadian <vagrant <at> debian.org>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 31308 <at> debbugs.gnu.org
Subject: Re: [bug#31308] [PATCH 0/3] Support u-boot on wandboard and mx6cuboxi
Date: Tue, 1 May 2018 22:42:29 +0200

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

For an eventual u-boot-installer, how do you install u-boot on wandboard?

And how do we detect that we have to use this kind of installation method based on u-boot's .config ?

For comparison, for sunxi, it's:

.config contains CONFIG_SYS_SOC="sunxi" => install via "dd if=u-boot-sunxi-with-spl.bin of=/dev/sdX bs=1024 seek=8".

[Message part 2 (application/pgp-signature, inline)]

Message #28 received at 31308 <at> debbugs.gnu.org (full text, mbox):

From: Vagrant Cascadian <vagrant <at> debian.org>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 31308 <at> debbugs.gnu.org
Subject: Re: [bug#31308] [PATCH 0/3] Support u-boot on wandboard and mx6cuboxi
Date: Tue, 01 May 2018 14:41:38 -0700

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

On 2018-05-01, Danny Milosavljevic <dannym <at> scratchpost.org> wrote:
> For an eventual u-boot-installer, how do you install u-boot on wandboard?
>
> And how do we detect that we have to use this kind of installation method based on u-boot's .config ?

An interesting idea... I had thought about making an SD image either as
a separate target, or integrating it into u-boot-BOARD for targets that
support booting from SD.


> For comparison, for sunxi, it's:
>
> .config contains CONFIG_SYS_SOC="sunxi" => install via "dd if=u-boot-sunxi-with-spl.bin of=/dev/sdX bs=1024 seek=8".

I've been using:

  https://salsa.debian.org/debian/u-boot/blob/master/debian/u-boot-imx.README.Debian

Which pretty much comes down to:

  dd conv=fsync,notrunc if=SPL of=DEVICE|IMAGEFILE bs=1k seek=1
  dd conv=fsync,notrunc if=u-boot.img of=DEVICE|IMAGEFILE bs=1k seek=69

That works on wandboard and mx6cuboxi, as well as several other imx6
targets.

The novena target requires u-boot.img to be copied to the first
partition with a fat or ext filesystem, and only the SPL is written to
the raw device.

With usbarmory (imx5), only the u-boot.img portion is installed directly
to the raw device at the offset above; there is no SPL.

CONFIG_SPL=y seems to be the best indicator that it needs SPL, and as
far as I know with CONFIG_MX[5,6]=y SPL is always installed to the same
offset.

It's less obvious to me comparing other configuration options what
determines which method is needed for u-boot.img. Maybe with recent
u-boot versions, it's possible to use either an offset or read it from a
filesystem with a single image; I didn't have much luck with that in the
past.

I'll experiment a little more and see what I can figure out.


live well,
  vagrant

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.