From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: Odroid-C2 solid green screen on "echo c > /proc/sysrq-trigger" on Arch 4.16/4.17rc6
Date: Tue, 05 Jun 2018 18:07:41 +0200 [thread overview]
Message-ID: <1528214861.10642.59.camel@baylibre.com> (raw)
In-Reply-To: <ca351a5029b843709950d8fe4be505d2@wppexc12.purdue.lcl>
On Tue, 2018-06-05 at 13:48 +0000, Swabey, Matthew A wrote:
> I'm not happy with the Raspberry Pi 3B, never really have been happy with any of their products due to their weird bootloader (just google netbooting Rpis - their implementation is badly broken), their overall hardware architecture etc. I much prefer the Odroid-c2, except for the 3.14 kernel. So when it went mainline I was very happy.
>
> However the reboot-greenscreen is problematic for my usecase, and I believe indicative of a possible race somewhere in the software stack, probably bootloader.
I don't think so.
My guess would be that your screen somehow read raw '0x00' on link while the
board resets. If your display is configured in YUV mode, you would see a green
screen. 0,0,0 is green in YUV
If you were using RGB instead YUV, I suspect you would have a black screen,
which is sad compared to 'funky green' but it is matter of taste I suppose.
next prev parent reply other threads:[~2018-06-05 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 2:19 Swabey, Matthew A
2018-05-25 7:53 ` Neil Armstrong
[not found] ` <CAERgokn-JU9JxHibaWF8w9-roz-wVukey2c7RKVNJoSV=Y+Q3g@mail.gmail.com>
2018-05-26 2:36 ` Swabey, Matthew A
2018-05-26 3:49 ` Swabey, Matthew A
2018-05-26 8:33 ` Neil Armstrong
2018-05-26 8:49 ` Michał Zegan
2018-05-26 22:20 ` Swabey, Matthew A
2018-06-04 21:22 ` Swabey, Matthew A
2018-06-05 9:17 ` Neil Armstrong
2018-06-05 13:48 ` Swabey, Matthew A
2018-06-05 16:07 ` Jerome Brunet [this message]
2018-06-05 16:25 ` Neil Armstrong
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=1528214861.10642.59.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@lists.infradead.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®