From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: rk3399-gru-kevin: issues on bringup
Date: Tue, 23 Feb 2021 10:10:11 -0500 [thread overview]
Message-ID: <CAPnjgZ17+gu2pAOidmnYjmy+wEwc6ekmRRpw3hg_vXqZrduACA@mail.gmail.com> (raw)
In-Reply-To: <79736268-6cd1-ecab-950a-be05b1581765@gmail.com>
Hi Marty,
On Thu, 13 Aug 2020 at 13:35, Alper Nebi Yasak <alpernebiyasak@gmail.com> wrote:
>
> Hi Simon, Marty,
>
> I'm interested in getting U-Boot to work with Kevin as well, but don't
> have a Servo (or the willingness to open up the case yet), so I've been
> trying to boot from depthcharge as in README.chromium-chainload.
>
> I don't have a way to see serial output and I see no other signs of
> life. Can you give me a tested configuration that immediately powers-off
> or reboots a Kevin so I can confirm what I'm doing works on the
> chainloading side? I mean I can boot Linux, but trying the same with
> U-Boot just gives me a blank screen even after accounting for a lot of
> things.
>
> Meanwhile, I've wrote some code to automate making depthcharge partition
> images, and to enable the display on Kevin (and perhaps Bob). Since I
> don't know if chainloading works, I don't know if these are broken or
> not either. I'm unsure about sending untested patches to the list, so I
> put them up here if you want to take a look (and maybe test/fix them?):
>
> https://github.com/alpernebbi/u-boot/tree/rk3399-gru-kevin/wip
>
> They're not really things that'd make a non-booting Kevin boot, though.
> I hope at least some of it can be useful in some way.
I am just replying here as you asked for some details on IRC. What
details do you need?
I was intending to try out a kevin if I have one. I will add that to my list.
Regards,
Simon
next prev parent reply other threads:[~2021-02-23 15:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 17:35 rk3399-gru-kevin: issues on bringup Alper Nebi Yasak
2021-02-23 15:10 ` Simon Glass [this message]
2021-02-23 21:36 ` Marty E. Plummer
2021-02-24 16:31 ` Simon Glass
2021-02-24 17:35 ` Marty E. Plummer
2021-03-11 4:52 ` Simon Glass
2021-03-13 19:39 ` Marty E. Plummer
2021-03-14 1:00 ` Simon Glass
2021-11-01 23:25 ` Alper Nebi Yasak
2021-11-02 8:09 ` Peter Robinson
2021-11-02 11:58 ` Alper Nebi Yasak
2021-11-02 23:05 ` Simon Glass
2021-11-06 3:16 ` Simon Glass
2021-11-07 17:26 ` Alper Nebi Yasak
2021-11-25 0:12 ` Simon Glass
2021-11-25 17:18 ` Alper Nebi Yasak
-- strict thread matches above, loose matches on Subject: below --
2020-07-20 3:32 Marty E. Plummer
2020-07-21 16:21 ` Simon Glass
2020-07-22 3:06 ` Marty E. Plummer
2020-07-28 18:58 ` Simon Glass
2020-07-31 11:19 ` Marty E. Plummer
2020-07-31 18:30 ` Simon Glass
2020-08-03 3:02 ` Simon Glass
2020-08-03 13:49 ` Simon Glass
2020-08-04 2:13 ` Simon Glass
2020-08-07 3:03 ` Marty E. Plummer
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=CAPnjgZ17+gu2pAOidmnYjmy+wEwc6ekmRRpw3hg_vXqZrduACA@mail.gmail.com \
--to=sjg@chromium.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 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.