Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Jonas Smedegaard]

Quoting Vagrant Cascadian (2017-11-13 15:29:26)
> Control: moreinfo 881564
> 
> On 2017-11-13, Jonas Smedegaard wrote:
> > Quoting Karsten Merker (2017-11-13 07:34:49)
> >> On Sun, Nov 12, 2017 at 06:29:33PM -0800, Vagrant Cascadian wrote:
> >> > On 2017-11-12, Jonas Smedegaard wrote:
> >> The A64-Olinuxino by default has has wired ethernet enabled and 
> >> therefore u-boot needs to mux these pins to the ethernet function.  
> >> The Teres-I doesn't have wired ethernet and IIRC uses the internal RGB 
> >> LCD interface, so in consequence it would have to use a different 
> >> pinmux.  I don't know whether there is a way for u-boot to 
> >> differentiate between these two platforms at runtime, but if there 
> >> isn't, we would need two separate u-boot builds.
> >
> > Oh.  I was wrong to trust Olimex naming of the dtb they ship, then.
> >
> > Some "nedko" at the "olimex irc channel hinted about dts files here: 
> > https://github.com/OLIMEX/DIY-LAPTOP/tree/master/SOFTWARE/A64-TERES/blobs
> >
> > This is out of my league - hope someone can make use of this.
> >
> > @Vagrant: You'd better remove my name as tester of a64-olinuxino dtb, as 
> > I don't (yet) own such hardware - only what might become named 
> > a64-teres.
> 
> Ok, since there's no mention of TERES in mainline u-boot sources, I 
> will pospone inclusion until there is someone who can confirm that the 
> intended target(s) actually work(s) on the intended platform(s).

I think there is nothing to "confirm" yet, but instead I simply read too 
much into the sources and TERES-I is not yet supported.

This bug might make sense to keep open, not sure - you decide.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Vagrant Cascadian]

Control: moreinfo 881564

On 2017-11-13, Jonas Smedegaard wrote:
> Quoting Karsten Merker (2017-11-13 07:34:49)
>> On Sun, Nov 12, 2017 at 06:29:33PM -0800, Vagrant Cascadian wrote:
>> > On 2017-11-12, Jonas Smedegaard wrote:
>> The A64-Olinuxino by default has has wired ethernet enabled and 
>> therefore u-boot needs to mux these pins to the ethernet function.  
>> The Teres-I doesn't have wired ethernet and IIRC uses the internal RGB 
>> LCD interface, so in consequence it would have to use a different 
>> pinmux.  I don't know whether there is a way for u-boot to 
>> differentiate between these two platforms at runtime, but if there 
>> isn't, we would need two separate u-boot builds.
>
> Oh.  I was wrong to trust Olimex naming of the dtb they ship, then.
>
> Some "nedko" at the "olimex irc channel hinted about dts files here: 
> https://github.com/OLIMEX/DIY-LAPTOP/tree/master/SOFTWARE/A64-TERES/blobs
>
> This is out of my league - hope someone can make use of this.
>
> @Vagrant: You'd better remove my name as tester of a64-olinuxino dtb, as 
> I don't (yet) own such hardware - only what might become named 
> a64-teres.

Ok, since there's no mention of TERES in mainline u-boot sources, I will
pospone inclusion until there is someone who can confirm that the
intended target(s) actually work(s) on the intended platform(s).


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Vagrant Cascadian]

On 2017-11-12, Jonas Smedegaard wrote:
> I already compiled arm-trusted-firmware - and will probably package that 
> for Debian, as it seems noone else is planning to do that (yes, I am 
> aware a sunxi-specific fork is needed currently).

I've also looked into packaging arm-trusted-firmware, so that u-boot
could ship a simple image to just dd to a device, and not require
further processing by the end-user. Not sure how to handle vendor forks
of arm-trusted-firmware... I probably should file an RFP/ITP at this
point...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Jonas Smedegaard]

Quoting Karsten Merker (2017-11-13 07:34:49)
> On Sun, Nov 12, 2017 at 06:29:33PM -0800, Vagrant Cascadian wrote:
> > On 2017-11-12, Jonas Smedegaard wrote:
> > > Please build and include with binary arm64 package u-boot-sunxi 
> > > the a64-olinuxino target, covering both the development board by 
> > > that name and the TERES-I DIY laptop.
> > >
> > > I own a TERES-I and can offer to test
> > 
> > Didn't know the TERES-I was 100% compatible; nice!
> 
> Hello,
> 
> they are based on the same hardware design, but there is one point 
> that gives me doubts about whether they can be 100% compatible at the 
> u-boot level: the A64 SoC cannot use the wired ethernet and the RGB 
> LCD functions at the same time as they are multiplexed to the same 
> pins.
> 
> The A64-Olinuxino by default has has wired ethernet enabled and 
> therefore u-boot needs to mux these pins to the ethernet function.  
> The Teres-I doesn't have wired ethernet and IIRC uses the internal RGB 
> LCD interface, so in consequence it would have to use a different 
> pinmux.  I don't know whether there is a way for u-boot to 
> differentiate between these two platforms at runtime, but if there 
> isn't, we would need two separate u-boot builds.

Oh.  I was wrong to trust Olimex naming of the dtb they ship, then.

Some "nedko" at the "olimex irc channel hinted about dts files here: 
https://github.com/OLIMEX/DIY-LAPTOP/tree/master/SOFTWARE/A64-TERES/blobs

This is out of my league - hope someone can make use of this.

@Vagrant: You'd better remove my name as tester of a64-olinuxino dtb, as 
I don't (yet) own such hardware - only what might become named 
a64-teres.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Jonas Smedegaard]

Quoting Vagrant Cascadian (2017-11-13 04:09:11)
> On 2017-11-12, Vagrant Cascadian wrote:
> > On 2017-11-12, Jonas Smedegaard wrote:
> >> I own a TERES-I and can offer to test
> ...
> > so I can build and upload a package somewhere for you to test before
> > uploading to Debian, if you'd rather.
> 
>   deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
> 
> Should have a u-boot-sunxi:arm64 package with a64-olinuxino enabled, and
> /usr/share/doc/u-boot-sunxi/README.* describing what's needed to install
> u-boot.

Thanks.  Will test first thing tomorrow.

I already compiled arm-trusted-firmware - and will probably package that 
for Debian, as it seems noone else is planning to do that (yes, I am 
aware a sunxi-specific fork is needed currently).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Jonas Smedegaard]

Quoting Vagrant Cascadian (2017-11-13 03:29:33)
> On 2017-11-12, Jonas Smedegaard wrote:
>> Please build and include with binary arm64 package u-boot-sunxi the 
>> a64-olinuxino target, covering both the development board by that 
>> name and the TERES-I DIY laptop.
>>
>> I own a TERES-I and can offer to test
>
> Didn't know the TERES-I was 100% compatible; nice!

Seems so: Olimex use that dtb in the pre-installed system.


>> (but am not familiar with the packaging style of the u-boot source 
>> package (seems to not use common git-buildpackage style and no hints 
>> is provided in README.source), so I would prefer to leave to others 
>> to implement the change.
>
> Pretty standard package in some regards: dpkg-buildpackage, debuild, 
> sbuild, pbuilder should all work without any unusual incantations 
> (e.g. orig.tar.* in the upper directory). You will need 
> DEB_BUILD_PROFILES=cross if you want to cross-compile, and have the 
> appropriate (multi-arch) build dependencies installed... sbuild 
> generally does the right thing for me.

Right.  I meant git source maintenance style, however: Branches 
"upstream" and "pristine-tar" exist but apparently haven't been used for 
quite some time.


> Which... can be a bit of an adventure... and it also may need an 
> upstream version not yet uploaded to Debian... so I can build and 
> upload a package somewhere for you to test before uploading to Debian, 
> if you'd rather.
> 
> 
> This patch should do it, if you're willing to be listed as a tester:
> 
> diff --git a/debian/targets b/debian/targets
> index a35c559f77..c67a7a4adb 100644
> --- a/debian/targets
> +++ b/debian/targets
> @@ -176,6 +176,9 @@ arm64   qcomdragonboard410c u-boot.bin
>  # Ryan Finnie 
>  arm64  rpi rpi_3   u-boot.bin
>  
> +# Jonas Smedegaard 
> +arm64  sunxi   a64-olinuxino   u-boot.bin spl/sunxi-spl.bin 
> u-boot-nodtb.bin arch/arm/dts/sun50i-a64-olinuxino.dtb
> +
>  # Vagrant Cascadian 
>  arm64  sunxi   pine64_plus u-boot.bin spl/sunxi-spl.bin 
> u-boot-nodtb.bin arch/arm/dts/sun50i-a64-pine64-plus.dtb 
> arch/arm/dts/sun50i-a64-pine64.dtb

Ah, so the names listed there are testers.  Makes sense.

Yes, Please do add me there as tester.

I already built a test package - with _exactly_ the same patch as above 
(and your last commit in git applied too - which does more than just 
update the documentation so you might want to adjust when applying to 
changelog).

Not tested yet, though - Will do that tomorrow (it is getting late now).


> Unfortunately, arm-trusted-firmware is not packaged for Debian, and 
> the allwinner boards require using a vendor fork, so you will need to 
> build that yourself. The process is roughly documented in 
> board/sunxi/README.sunxi64 and debian/u-boot-sunxi.README.Debian in 
> git.

Right: After fighting blindly with several (stupid, in hindsight) 
attempts I checked out u-boot git and noticed your commit the 9th which 
I hope is the final missing piece to boot a purely Debian system for my 
TERES-I.


> I've recently successfully tested the non-legacy process on a Pine64+, 
> which is similar hardware.

Yes, I noticed some of your changes for that, and appreciate all your 
work on that: Obviously makes it far easier to then adapt to similar 
devices.


Any chance you can make a release to Debian soon?

I would love to be able to run pure Debian on my laptop when showing off 
my TERES-I at MiniDebconf in France next weekend.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Vagrant Cascadian]

On 2017-11-12, Vagrant Cascadian wrote:
> On 2017-11-12, Jonas Smedegaard wrote:
>> I own a TERES-I and can offer to test
...
> so I can build and upload a package somewhere for you to test before
> uploading to Debian, if you'd rather.

  deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main

Should have a u-boot-sunxi:arm64 package with a64-olinuxino enabled, and
/usr/share/doc/u-boot-sunxi/README.* describing what's needed to install
u-boot.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Vagrant Cascadian]

Control: tags 881564 +patch

On 2017-11-12, Jonas Smedegaard wrote:
> Please build and include with binary arm64 package u-boot-sunxi the
> a64-olinuxino target, covering both the development board by that name
> and the TERES-I DIY laptop.
>
> I own a TERES-I and can offer to test

Didn't know the TERES-I was 100% compatible; nice!


> (but am not familiar with the packaging style of the u-boot source
> package (seems to not use common git-buildpackage style and no hints
> is provided in README.source), so I would prefer to leave to others to
> implement the change.

Pretty standard package in some regards: dpkg-buildpackage, debuild,
sbuild, pbuilder should all work without any unusual incantations
(e.g. orig.tar.* in the upper directory). You will need
DEB_BUILD_PROFILES=cross if you want to cross-compile, and have the
appropriate (multi-arch) build dependencies installed... sbuild
generally does the right thing for me.

Which... can be a bit of an adventure... and it also may need an
upstream version not yet uploaded to Debian... so I can build and upload
a package somewhere for you to test before uploading to Debian, if you'd
rather.


This patch should do it, if you're willing to be listed as a tester:

diff --git a/debian/targets b/debian/targets
index a35c559f77..c67a7a4adb 100644
--- a/debian/targets
+++ b/debian/targets
@@ -176,6 +176,9 @@ arm64   qcomdragonboard410c u-boot.bin
 # Ryan Finnie 
 arm64  rpi rpi_3   u-boot.bin
 
+# Jonas Smedegaard 
+arm64  sunxi   a64-olinuxino   u-boot.bin spl/sunxi-spl.bin 
u-boot-nodtb.bin arch/arm/dts/sun50i-a64-olinuxino.dtb
+
 # Vagrant Cascadian 
 arm64  sunxi   pine64_plus u-boot.bin spl/sunxi-spl.bin 
u-boot-nodtb.bin arch/arm/dts/sun50i-a64-pine64-plus.dtb 
arch/arm/dts/sun50i-a64-pine64.dtb
 

Unfortunately, arm-trusted-firmware is not packaged for Debian, and the
allwinner boards require using a vendor fork, so you will need to build
that yourself. The process is roughly documented in
board/sunxi/README.sunxi64 and debian/u-boot-sunxi.README.Debian in git.

I've recently successfully tested the non-legacy process on a Pine64+,
which is similar hardware.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#881564: u-boot: please add a64-olinuxino target to [arm64] u-boot-sunxi binary package

[Jonas Smedegaard]

Source: u-boot
Version: 2017.09+dfsg1-3
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please build and include with binary arm64 package u-boot-sunxi the
a64-olinuxino target, covering both the development board by that name
and the TERES-I DIY laptop.

I own a TERES-I and can offer to test (but am not familiar with the
packaging style of the u-boot source package (seems to not use common
git-buildpackage style and no hints is provided in README.source), so I
would prefer to leave to others to implement the change.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAloI8BIACgkQLHwxRsGg
ASGJ4w//Xsdo9kfzcBFDaxWQZarWU1+aunhbY1ALNO2mBCGfH6BU9BfivXFQI+ml
fqWQgpdKtfOmLN/dQCgmDcNlqKIN9k9kCkgmYeeG/YlhiIHA6WAM5D5fVLFXeXTi
6YSGq7IHENRnH1bHcitRXUj0SmRPdmN+wU8TF234fuxjgF+IIPDBA/ouSOy4nWRM
uRdzWZtKu9dVnYG9mhlawLpQb5+AFZlslPB1ZyyzMfa4Xf4bKFGRW9n1T0MHLutN
wHUpEocbsYuKtVeT+IfltRZ78QUjDZ9U5HABKVZTCgax29o6OKsJ+ua9SC3bp3pB
WLINOsIDCIROiGHOg26qTT7x+1TJH8uRrkAdo9GRGbQuV1q2wHs8irzOzXA7UBSh
9NZeAMOq7dN0obfE4SfA66LAMEArk4AJRGAzk3RkUJzLxpHbaAWiWoDq6MP6FA5x
h4OckLcaaac7EogPVuCIl2dB2cvCkEmAOKXVtCr0TgzeA+73LtCrJ6iTMe74GtCr
K5+c1EkS1gufq3X4dyX33rK1E3hkTyUxux0ZZSBX+Y8SZf0K634KkaVA08kerGpq
c7bDnn0215tsM70dh3hTlPzkWRNW6TsGGRfStKoV4sOZIBYAiih2IA/J/bOiC6xR
imAQjFMLSWEUPwYkwqfcwG9qShH4jHMYmZyjpfUVjLI+u5GgNoc=
=kwnh
-END PGP SIGNATURE-