Hi, about 2 months ago I installed armbian[1] on my Pinebook. Everything works well. That would be great to integrate everything (Pinebook support) what have armbian to us TW images. But here we have to decide: do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it? I would like to help, but need to be supported from coordinator, who has more experience. Cheers, Alex [1] https://www.armbian.com/ On Sun, Aug 13, 2017 at 2:27 AM, Stefan Bruens wrote:

On Samstag, 12. August 2017 20:20:03 CEST Alex Naumov wrote:

...

Hello,

yesterday I finally got my 14'' Pinebook [1]. There is Ubuntu 16.04 MATE as a default OS, but I would like to use openSUSE TW on it of course.

So, I found raw.xz XFCE-image for aarch64 [2] and used this command "to burn" image on the microSD card:

All Aarch64 SBCs (Single board computer) I am aware of do not support UEFI boot, but require a (more or less) board specific boot image. For the Pinebook, your best bet is with the Pine64 Contrib image:

https://en.opensuse.org/HCL:Pine64

But although this will likely boot, you will get much less than you might expect:

1. No graphics on LCD 2. No graphics via HDMI 3. Wireless may work - probably not

With some luck, HDMI will be ready end of the year, but this will *not* include 2D/3D acceleration nor hardware video decoding.

For the current state of the A64 support, see here:

http://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix

Kind regards,

Stefan

-- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 11 December 2017 at 20:23, Andreas Färber wrote:

Hi Alex,

Am 11.12.2017 um 14:22 schrieb Alex Naumov:

...

do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it?

I don't think it's possible to combine the Pinebook into an existing image, as it likely needs its own U-Boot with matching Device Tree.

That leaves us with two options:

a) Derive a new separate image once all needed packages are in place. As long as arm-trusted-firmware is not in Tumbleweed, such an image can only live in some Contrib repository, not officially part of Tumbleweed.

Is there a particular reason why arm-trusted-firmware isn't in Tumbleweed yet? Sorry but I missed any previous discussion on ATF.

b) Use pine64-instsd [*] as inspiration to build a bootable SD image and then install interactively from an .iso on USB stick.

Regards, Andreas

[*] https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Pine64/pin...

-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 11.12.2017 um 21:47 schrieb Andrew Wafaa:

On 11 December 2017 at 20:23, Andreas Färber wrote:

...

Am 11.12.2017 um 14:22 schrieb Alex Naumov:

...

do we want to integrate everything what Pinebook needs to our TW images OR we would like to have separate images for it?

I don't think it's possible to combine the Pinebook into an existing image, as it likely needs its own U-Boot with matching Device Tree.

That leaves us with two options:

a) Derive a new separate image once all needed packages are in place. As long as arm-trusted-firmware is not in Tumbleweed, such an image can only live in some Contrib repository, not officially part of Tumbleweed.

Is there a particular reason why arm-trusted-firmware isn't in Tumbleweed yet? Sorry but I missed any previous discussion on ATF.

Short summary: U-Boot is in Base:System devel project and for some boards now has a soft dependency on ATF - builds okay but won't work. Base:System has so few maintainers and keeps blocking and rebuilding packages (due to core packages such as glibc), that we've already resorted to Base:System:Staging for actually being able to test new sub-packages and updates. So I really don't want to submit my ATF packages to Base:System. Additionally, Andre did not yet get his Allwinner A64/H5 support merged into upstream ATF, so an arm-trusted-firmware package today would only help e.g. Firefly-RK3399 and Geekbox, not Pine64 or Orange Pi PC 2. One proposed idea was a new sub-project under "hardware" (where u-boot or arm-trusted-firmware don't fit 100%, I'm surprised vboot was accepted despite not being about peripherals), but so far we haven't discussed any names or alternative locations. Opinions? Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org