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: Wed, 19 Feb 2020 20:12:32 -0800 [thread overview]
Message-ID: <87tv3lew27.fsf@yucca> (raw)
In-Reply-To: <20200216191911.26df0ad7@scratchpost.org>
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?
> 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) to make
> it find the correct FDT file anyway.
uEnv.txt is not necessarily widely supported; some arbitrary boards
implement it, but I wouldn't rely on it.
live well,
vagrant
next prev parent reply other threads:[~2020-02-20 4:13 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 [this message]
2020-02-20 6:29 ` Jan Nieuwenhuizen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv3lew27.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.