All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10406] New: Beaglebone black: Buggy SGX driver version, swapped red and blue channels
Date: Fri, 13 Oct 2017 13:23:39 +0000	[thread overview]
Message-ID: <bug-10406-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=10406

            Bug ID: 10406
           Summary: Beaglebone black: Buggy SGX driver version, swapped
                    red and blue channels
           Product: buildroot
           Version: 2017.08
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: nikola.rajovic at zuehlke.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Hi,

I have built a buildroot image for BeagleBone Black using
beaglebone_qt5_defconfig config. The problem is with eglfs backend and SGX GPU
driver in turn swapping red and blue channels when rendering on 16-bit 7'' LCD
cape. Not tested with HDMI. It seems that SGX driver uses BGR instead of RGB
color mode (or vice versa).

fb-test application displays correct colors, everything matches. 

Any clue if it is possible to get an updated version of SGX driver which
resolves this issue. 


Thanks,
Nikola

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-10-13 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 13:23 bugzilla at busybox.net [this message]
2017-10-21 19:41 ` [Buildroot] [Bug 10406] Beaglebone black: Buggy SGX driver version, swapped red and blue channels bugzilla at busybox.net
2017-10-31 21:00 ` 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@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 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.