From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] video: simple_panel: Add boe,nv101wxmn51 display
Date: Wed, 28 Oct 2020 01:59:32 +0300 [thread overview]
Message-ID: <6bf4951d-8f62-91f7-9fbd-9e7277789611@gmail.com> (raw)
In-Reply-To: <e94a533739dfb54f@bloch.sibelius.xs4all.nl>
On 28/10/2020 00:52, Mark Kettenis wrote:
>> From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
>> Date: Wed, 28 Oct 2020 00:41:55 +0300
>>
>> Add "boe,nv101wxmn51" to the compatible node. This is the panel for
>> chromebook_bob.
>
> I do have bob, and would be interested in testing chainloading u-boot
> on it. Can you give some guidance on how to test this? Which set of
> patches do I need?
>
By chainloading I mean the RW_LEGACY thing because I couldn't manage to
do it as a "Chrome OS kernel" yet.
For bob, you should get this branch:
https://github.com/alpernebbi/u-boot/commits/rk3399-gru-bob-edp/wip
I'm not putting my hacks in the bob branch since it should be possible
to flash it to SPI and boot from there as things are normally done.
So you might need to port my hacks (and other interesing changes) from
the other one if you want chainloading:
https://github.com/alpernebbi/u-boot/commits/rk3399-gru-kevin/wip
I've tried to explain how to build and use things in 'wip' commit
messages in the second one.
If things are unclear there I'd be glad to help, but it might be too
spammy to do it as replies to this patch.
next prev parent reply other threads:[~2020-10-27 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 21:41 [PATCH 1/2] video: simple_panel: Add sharp,lq123p1jx31 display Alper Nebi Yasak
2020-10-27 21:41 ` [PATCH 2/2] video: simple_panel: Add boe,nv101wxmn51 display Alper Nebi Yasak
2020-10-27 21:52 ` Mark Kettenis
2020-10-27 22:59 ` Alper Nebi Yasak [this message]
2020-11-03 15:11 ` Simon Glass
2021-02-22 18:41 ` Anatolij Gustschin
2020-11-03 15:11 ` [PATCH 1/2] video: simple_panel: Add sharp,lq123p1jx31 display Simon Glass
2021-02-22 18:40 ` Anatolij Gustschin
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=6bf4951d-8f62-91f7-9fbd-9e7277789611@gmail.com \
--to=alpernebiyasak@gmail.com \
--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 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.