From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Danny Milosavljevic <dannym@scratchpost.org>, 39617@debbugs.gnu.org
Subject: [bug#39617] [PATCH 0/2] Add initial Pinebook Pro support
Date: Thu, 20 Feb 2020 07:29:15 +0100 [thread overview]
Message-ID: <87pne9bwlg.fsf@gnu.org> (raw)
In-Reply-To: <87tv3lew27.fsf@yucca> (Vagrant Cascadian's message of "Wed, 19 Feb 2020 20:12:32 -0800")
Vagrant Cascadian writes:
> On 2020-02-16, Danny Milosavljevic wrote:
>> On Sat, 15 Feb 2020 19:49:48 +0100
>> Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>>> sudo sed 's,FDTDIR \([^ ]*\),FDT \1/rockchip/rk3399-pinebook-pro.dtb,' /boot/extlinux/extlinux.conf
>
> I didn't do this manually and mine booted without it; is this
> implemented in the patches directly?
The need for this was a big puzzle to me -- I have no idea what happened
ovor at my side. Could it be a firmware thing, you may have an earlier
badge?
I did build some packages on an intel box, possibly using qemu; as soon
as I have a working pinebook again I'll try to do a whole fresh install.
Thanks!
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-02-20 6:30 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 [this message]
2020-02-28 1:03 ` Vagrant Cascadian
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=87pne9bwlg.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=39617@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=vagrant@debian.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).