From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10406] Beaglebone black: Buggy SGX driver version, swapped red and blue channels
Date: Sat, 21 Oct 2017 19:41:21 +0000 [thread overview]
Message-ID: <bug-10406-163-ttTfLYLwQp@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10406-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10406
--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
The am335x has a known hw bug regarding red/blue swap when configuring the RGB
output for 16 bit mode, so it is probably related to that.
Why things are working for SW rendering and not for GPU rendering I don't know,
but you will probably have more luck asking on the beaglebone list:
https://groups.google.com/forum/#!categories/beaglebone/beagleboardorg-beaglebone-black
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-10-21 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 13:23 [Buildroot] [Bug 10406] New: Beaglebone black: Buggy SGX driver version, swapped red and blue channels bugzilla at busybox.net
2017-10-21 19:41 ` bugzilla at busybox.net [this message]
2017-10-31 21:00 ` [Buildroot] [Bug 10406] " bugzilla at busybox.net
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=bug-10406-163-ttTfLYLwQp@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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