From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:58833) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j3PEx-00015b-LV for guix-patches@gnu.org; Sun, 16 Feb 2020 14:06:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j3PEw-0006jg-7v for guix-patches@gnu.org; Sun, 16 Feb 2020 14:06:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:59944) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j3PEw-0006jT-4j for guix-patches@gnu.org; Sun, 16 Feb 2020 14:06:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j3PEw-0004ix-0R for guix-patches@gnu.org; Sun, 16 Feb 2020 14:06:02 -0500 Subject: [bug#39617] [PATCH 0/2] Add initial Pinebook Pro support Resent-Message-ID: Received: from eggs.gnu.org ([2001:470:142:3::10]:58724) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j3PDu-0000wd-2L for guix-patches@gnu.org; Sun, 16 Feb 2020 14:04:59 -0500 From: Jan Nieuwenhuizen References: <87tv3rd6sz.fsf@gnu.org> <20200216191911.26df0ad7@scratchpost.org> Date: Sun, 16 Feb 2020 20:04:54 +0100 In-Reply-To: <20200216191911.26df0ad7@scratchpost.org> (Danny Milosavljevic's message of "Sun, 16 Feb 2020 19:19:11 +0100") Message-ID: <87mu9i4all.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Danny Milosavljevic Cc: vagrant@debian.org, 39617@debbugs.gnu.org Danny Milosavljevic writes: Hi Danny, >> A vanilla kernel does not work yet; apparently development to upstream >> pinebook-pro patches lives here: >> https://gitlab.manjaro.org/tsys/linux-pinebook-pro > > Yeah, but LKML has some of the patches there in review, for example: > > * http://lkml.iu.edu/hypermail/linux/kernel/2001.1/01899.html (already ac= cepted) > * https://patchwork.kernel.org/patch/11325531/ (pending changes) > [...] > * https://www.spinics.net/lists/kernel/msg3367972.html (pending changes) > > So all in all I think the Pinebook Pro will eventually work with the vani= lla kernel. Oh, great! I was pretty lost about all this. I finally got some feedback on this; I'll update my post. I was told "use mainline Manjaro kernel here, take branch v5.5". I did that but got confused a bit by the lack of any tags. I fetched tags from linus and got git describe =3D> v5.5-5246-g9564c96de3d1 WTF? Just today I looked at v5.5-rc7, an older manjaro branch and saw git describe =3D> v5.5-rc7-75-g2335a564ec8f Then, I found that the v5.5 branch has probably ~85 extra commits. We could try applying those patches onto a recent kernel, v5.5 or v5.6 (when it's released?). >> Similarly, Das U-Boot has a pinebook-pro development branch >> https://git.eno.space/pbp-uboot.git > > (Not so sure whether that one will be upstreamed) Okay, I'm also not sure yet if this is required; but I'm glad it works now and we can work from here. >> sudo sed 's,FDTDIR \([^ ]*\),FDT \1/rockchip/rk3399-pinebook-pro.dtb,' /= boot/extlinux/extlinux.conf > > It might make sense to find out why this is necessary. > > https://lists.denx.de/pipermail/u-boot/2014-January/171682.html describes= that it > should be possible to set up u-boot environment variables (in uEnv.txt) t= o make > it find the correct FDT file anyway. If none is set up, it automatically= generates > the file name to use using $soc and $board. But that's for PXE booting > (booting empty machine via network)--not sure where the normal case is in= U-Boot, > if any. U-Boot sometimes has some weird blind spots like that. Ah, possibly some softcoding mechanism like this (we use a patched u-boot!) is going astray. Hmm. > Also, https://lists.denx.de/pipermail/u-boot/2016-May/254703.html kinda > sounds like they dont support subdirs. Wanna try adding "/rockchip" to t= he > end of FDTDIR in extlinux.conf ? > Also, what's the value of CONFIG_[DEFAULT_]DEVICE_TREE in your u-boot > configuration? I am pretty sure it is $ grep DEFAULT_FDT /gnu/store/zxb488q5l9c6j5pnazvp5s30z1p18gnm-u-boot-p= inebook-pro-rk3399-2020.01-pinebook-pro-1.365495a/libexec/.config=20 CONFIG_DEFAULT_FDT_FILE=3D"rockchip/rk3399-pinebook-pro.dtb" So yeah, strange. >> Because of the aarch64 guix pull problem, the separate repositories for >> kernel and u-boot, the weird MMC numbering changes /dev/mmcblk0 <-> >> /dev/mmcblk1 and this ugly extlinux.conf fixup I am not sure where to >> share this code, maybe wip-pinebook-pro @ savannah. WDYT? > > I'm all for wip-pinebook-pro @ savannah, especially before losing a now-w= orking > version by hacking further on it. Been there done that :) Okay, pushed! > If you want we can collaborate in the next days on finding the cause of > the weird FDT problem. Ah thank you...that would (have been???) so nice. This morning, my pinebook pro did not want to start and hasn't all day. :-( :-( :-( Could running a wrong kernel brick the thing, I don't think so...but I'm pretty lost. I'll wait a couple of days to see if it comes to life again. >> For more details, see >>=20 >> https://joyofsource.com/guix-system-on-the-pinebook-pro.html >>=20 >> I think it would be nice to have an updated this blog on guix.gnu.org wh= en >> these silly problems are resolved. > > Sure! > > As a general remark, make-u-boot-package was not public because > I didn't want to commit to its interface yet. > I think we don't need to export it even now. (We can if we have to) Ah; I needed that before when I had a separate pinebook-pro.scm; and may have kept the export... Sure, let's remove it if it's not needed. Greetings, janneke --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com