From: Vagrant Cascadian <vagrant@debian.org>
To: Danny Milosavljevic <dannym@scratchpost.org>,
Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 39617@debbugs.gnu.org
Subject: [bug#39617] [PATCH 0/2] Add initial Pinebook Pro support
Date: Thu, 27 Feb 2020 17:03:34 -0800 [thread overview]
Message-ID: <875zfr1q1l.fsf@yucca> (raw)
In-Reply-To: <20200216191911.26df0ad7@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
On 2020-02-16, Danny Milosavljevic wrote:
> On Sat, 15 Feb 2020 19:49:48 +0100
> Jan Nieuwenhuizen <janneke@gnu.org> 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
>
> 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 accepted)
> * 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 vanilla kernel.
Updated patches were sent today (by the same person working on the
manjaro kernel, I think):
https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=248535
>> 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)
I think the upstreaming for pinebook pro is delayed on the device tree
landing in upstream linux... Peter Robinson sent a patch series that
kind of worked for me, though I didn't yet have a working kernel at the
time to test:
https://patchwork.ozlabs.org/project/uboot/list/?series=142716&state=*
Combining that with the newer device-tree patches submitted to linux
might be fruitful!
I haven't done any recent tests, largely due to the issue with "guix
pull" being broken on aarch64... might only have limited ability to test
things the next week or so, or might just get a wild hair and go for it.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-02-28 1:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 18:49 [bug#39617] [PATCH 0/2] Add initial Pinebook Pro support Jan Nieuwenhuizen
2020-02-15 18:52 ` [bug#39617] [PATCH 1/2] gnu: Add linux-libre-pinebook-pro Jan Nieuwenhuizen
2020-02-15 18:52 ` [bug#39617] [PATCH 2/2] gnu: Add u-boot-pinebook-pro-rk3399 Jan Nieuwenhuizen
2020-02-20 4:04 ` [bug#39617] [PATCH 1/2] gnu: Add linux-libre-pinebook-pro Vagrant Cascadian
2020-02-20 6:26 ` Jan Nieuwenhuizen
2020-02-15 21:51 ` [bug#39617] [PATCH 0/2] Add initial Pinebook Pro support Mike Rosset
2020-02-16 18:19 ` Danny Milosavljevic
2020-02-16 18:22 ` Danny Milosavljevic
2020-02-16 19:04 ` Jan Nieuwenhuizen
2020-02-20 4:12 ` Vagrant Cascadian
2020-02-20 6:29 ` Jan Nieuwenhuizen
2020-02-28 1:03 ` Vagrant Cascadian [this message]
2020-02-16 18:21 ` [bug#39617] Fw: " Danny Milosavljevic
2020-02-16 18:27 ` [bug#39617] " Danny Milosavljevic
2020-02-18 21:48 ` Danny Milosavljevic
2020-05-20 6:29 ` Brian Woodcox
2020-05-20 7:15 ` Jan Nieuwenhuizen
2020-05-20 16:06 ` Brian Woodcox
2020-05-20 6:29 ` Brian Woodcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zfr1q1l.fsf@yucca \
--to=vagrant@debian.org \
--cc=39617@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).