From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] rockchip: rk3399: Add Pinebook Pro laptop support
Date: Sat, 28 Mar 2020 13:28:34 -0700 [thread overview]
Message-ID: <87mu80gr65.fsf@ponder> (raw)
In-Reply-To: <87bls5pdyh.fsf@yucca>
On 2019-12-18, Vagrant Cascadian wrote:
> On 2019-11-14, Peter Robinson wrote:
>> Add initial support for Pinebook Pro laptop.
Now that the device-tree is in linux-next (should land in linux 5.7),
anyone have a chance to take a stab at a v2 of this patch series? I did
a quick-and-dirty attempt, and the TPL/SPL layers worked, but failed to
load the main u-boot/atf binaries (mmc issues, I think).
live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200328/c7cd40b4/attachment.sig>
next prev parent reply other threads:[~2020-03-28 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 0:51 [U-Boot] [PATCH] rockchip: rk3399: Add Pinebook Pro laptop support Peter Robinson
2019-11-14 7:22 ` Kever Yang
2019-11-14 20:51 ` Vasily Khoruzhick
2019-12-18 20:37 ` Vagrant Cascadian
2020-03-28 20:28 ` Vagrant Cascadian [this message]
2020-03-28 21:04 ` Peter Robinson
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=87mu80gr65.fsf@ponder \
--to=vagrant@debian.org \
--cc=u-boot@lists.denx.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox