I set the branch to "next", I set kernel repository to anarsoul's kernel (contains latest patches for A64 and also for Pinebook & Sopine devices) and deleted all patches from sunxi-next (all that patches has been for 4.14), I just kept and add some of patches.

But this is probably terrible idea. @Igor or anyone, can you please me suggest better way to support "next" kernel (The task is to support latest anarsoul's kernel)? I was thinking about changing KERNELFAMILY variable, but really dunno, I'm using Armbian build environment for first time.

P.S. the beta automatical build for Pinebook boots u-boot, then kernel, but in kernel is something messed up (the LCD shutdowns after few second of kernel booted), but I will try to fix it, to have "dev" support too

Share this post

Link to post

Share on other sites

the beta automatical build for Pinebook boots u-boot, then kernel, but in kernel is something messed up (the LCD shutdowns after few second of kernel booted),﻿ but I will try to fix it, to have "dev" support too

Share this post

Link to post

Share on other sites

Great job Igor. I have working Bluetooth and Audio, it works pretty good (shown on video lower) (Note that this my build uses Anarsoul's kernel with no patches (Only some I kept)). I will make Pull Requests for Bluetooth and Audio support for A64, probably this weekend (Should work also on Teres). Also please, it's possible to add support for test "bleeding edge" images (like this one)?

We need to keep one kernel for many hw and that's why patches are a must. Current situation is still messy and I only find out that some of my additional patches are causing Pinebook to hang at boot. I also plan to merge a dozent of patches, some sent upstream to make it easier to maintain.

I was working whole day yesterday and the day before and the day before ... I can add new updated test image, but it is much better for me to do nothing for a few days. When things are merged in, images can be produced automatically. No need to rush anywhere. Production ready images shell go out when DEV branch is tested very well and is moved to NEXT. We still miss suspend / resume, right? This is a must function for notebooks. I haven't saw if there is a solution developed for that?