From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alper Nebi Yasak Date: Wed, 28 Oct 2020 01:59:32 +0300 Subject: [PATCH 2/2] video: simple_panel: Add boe,nv101wxmn51 display In-Reply-To: References: <20201027214155.17246-1-alpernebiyasak@gmail.com> <20201027214155.17246-2-alpernebiyasak@gmail.com> Message-ID: <6bf4951d-8f62-91f7-9fbd-9e7277789611@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 28/10/2020 00:52, Mark Kettenis wrote: >> From: Alper Nebi Yasak >> 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.