From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:54482) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j3OYO-0005qb-OI for guix-patches@gnu.org; Sun, 16 Feb 2020 13:22:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j3OYN-0006Iu-ED for guix-patches@gnu.org; Sun, 16 Feb 2020 13:22:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:59916) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j3OYN-0006Ik-B8 for guix-patches@gnu.org; Sun, 16 Feb 2020 13:22:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j3OYN-0003fV-7Z for guix-patches@gnu.org; Sun, 16 Feb 2020 13:22:03 -0500 Subject: [bug#39617] Fw: [PATCH 0/2] Add initial Pinebook Pro support References: <87tv3rd6sz.fsf@gnu.org> In-Reply-To: <87tv3rd6sz.fsf@gnu.org> Resent-Message-ID: Date: Sun, 16 Feb 2020 19:21:41 +0100 From: Danny Milosavljevic Message-ID: <20200216192141.2c4530c8@scratchpost.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/QGjtLQiE/iA.pfrJNDrtQ2="; protocol="application/pgp-signature"; micalg=pgp-sha256 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: 39617@debbugs.gnu.org --Sig_/QGjtLQiE/iA.pfrJNDrtQ2= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Janneke, On Sat, 15 Feb 2020 19:49:48 +0100 Jan Nieuwenhuizen wrote: > A vanilla kernel does not work yet; apparently development to upstream > pinebook-pro patches lives here: > https://gitlab.manjaro.org/tsys/linux-pinebook-pro =20 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 acce= pted) * 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 vanill= a kernel. > Similarly, Das U-Boot has a pinebook-pro development branch > https://git.eno.space/pbp-uboot.git =20 (Not so sure whether that one will be upstreamed) > sudo sed 's,FDTDIR \([^ ]*\),FDT \1/rockchip/rk3399-pinebook-pro.dtb,' /b= oot/extlinux/extlinux.conf =20 It might make sense to find out why this is necessary. https://lists.denx.de/pipermail/u-boot/2014-January/171682.html describes t= hat it should be possible to set up u-boot environment variables (in uEnv.txt) to = make it find the correct FDT file anyway. If none is set up, it automatically g= enerates 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. Also, https://lists.denx.de/pipermail/u-boot/2016-May/254703.html kinda sounds like they dont support subdirs. Wanna try adding "/rockchip" to the end of FDTDIR in extlinux.conf ? Also, what's the value of CONFIG_[DEFAULT_]DEVICE_TREE in your u-boot configuration? > --8<---------------cut here---------------end--------------->8--- >=20 > 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? =20 I'm all for wip-pinebook-pro @ savannah, especially before losing a now-wor= king version by hacking further on it. Been there done that :) If you want we can collaborate in the next days on finding the cause of the weird FDT problem. > 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 when > these silly problems are resolved. =20 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) --Sig_/QGjtLQiE/iA.pfrJNDrtQ2= Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl5JiDUACgkQ5xo1VCww uqXRoQgAnENsTuQA6G0CWZQfcE1JFdsed+k6iPMZ4B8jzO2gCv5knprm2a1JQAFl JdOzMkg57j6BU45DwOWAfb4U0hIJHY7CgbZIOpuykWcvNPN2gPrSvdEW31yfvw/N MQRsuQKBa0XLmklsdC7kt6TftNUKsrk+URgHPaZ7GJtk5FS5oiVXq/Ctn0LDs+rm c17NEVI++LLB42NTEwwqmbxtPI2zSTykKgRo/zcUMWioT36iG10lxTNSvR+RQiP5 NrzqCAl+k91JvqIq6oxLKmyXleoroHXL21c73ql5xlndrj5aL+B1GjyHFS8aRqSS FKGzX47vghMqLPxqtljVilh+1Y9Kew== =ik3r -----END PGP SIGNATURE----- --Sig_/QGjtLQiE/iA.pfrJNDrtQ2=--