From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:470:142:3::10]:53419)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1j4Ajn-0004S3-F7
 for guix-patches@gnu.org; Tue, 18 Feb 2020 16:49:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1j4Ajm-0002nv-8h
 for guix-patches@gnu.org; Tue, 18 Feb 2020 16:49:03 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:35424)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1j4Ajm-0002nG-5G
 for guix-patches@gnu.org; Tue, 18 Feb 2020 16:49:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1j4Ajm-0005TG-2u
 for guix-patches@gnu.org; Tue, 18 Feb 2020 16:49:02 -0500
Subject: [bug#39617] [PATCH 0/2] Add initial Pinebook Pro support
Resent-Message-ID: <handler.39617.B39617.158206252320995@debbugs.gnu.org>
Date: Tue, 18 Feb 2020 22:48:36 +0100
From: Danny Milosavljevic <dannym@scratchpost.org>
Message-ID: <20200218224836.49555de6@scratchpost.org>
In-Reply-To: <20200216192741.16e7a4ae@scratchpost.org>
References: <87tv3rd6sz.fsf@gnu.org> <20200216192741.16e7a4ae@scratchpost.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/=hQpZn81nBo1YTaAXk/gs+v";
 protocol="application/pgp-signature"; micalg=pgp-sha256
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
 <mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-patches>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
 <mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, 39617@debbugs.gnu.org

--Sig_/=hQpZn81nBo1YTaAXk/gs+v
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Janneke,

On Sun, 16 Feb 2020 19:27:41 +0100
Danny Milosavljevic <dannym@scratchpost.org> wrote:

> It should be possible (and much less weird) for the vendor to just enable=
 the
> TFT display in u-boot and display stuff there.
>=20
> (linux-sunxi, the dev group for another ARM SoC vendor, does it just fine=
 in
> mainline u-boot--so it is possible and can maybe be copied)

I came across an example u-boot configuration for LCD screen:

https://github.com/Openvario/meta-openvario/blob/warrior/recipes-bsp/u-boot=
/files/openvario-57-lvds/openvario_defconfig

especially=20

CONFIG_VIDEO_LCD_MODE=3D"x:640,y:480,depth:18,pclk_khz:25000,hs:1,vs:1,le:1=
57,ri:2,up:42,lo:2,sync:3,vmode:0"
CONFIG_VIDEO_LCD_PANEL_LVDS=3Dy
CONFIG_VIDEO_LCD_BL_PWM=3D"PB2"
CONFIG_VIDEO_LCD_BL_PWM_ACTIVE_LOW=3Dn

We'd still need to get the timing parameters (CONFIG_VIDEO_LCD_MODE) for th=
e Pinebook Pro (from the panel datasheet).
And that's if that thing is connected via LVDS in the first place.

But that's all moot if your Pinebook Pro is bricked for good.

--Sig_/=hQpZn81nBo1YTaAXk/gs+v
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl5MW7QACgkQ5xo1VCww
uqVn/ggAm0/9hZPPBpbdgPLWWfGpuOK2wPUcxzzf90qWLbrMJ3B+C66YuI5uLEln
LDB+ghg9kI0c44PeqACUNVuCdmZgba46sE8xo2cr24wquxqs9VDVMbjeasC8dtNg
sNmzi5pWJ186zG7pKtznhwaG0EsCZd8W9aB8uc8WLzWPcHwlKgwqbkoQmB1i5YvI
F/ER0h8s00hqTKNOocTWYGbV8859c8sNoVfeS/iLmTcZ47yxXFfRqOwH2LOmtTRG
3bih3ZUuX6as7adunBU4zx6TmkmhY8I+h9RVfyQcq2cVjOzDLycX+OFcOQawjODp
yxy9IccEqTgeVSJy2UvhnIH2mXRQdQ==
=jlUn
-----END PGP SIGNATURE-----

--Sig_/=hQpZn81nBo1YTaAXk/gs+v--