All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Setting RGB
Date: Thu, 11 Feb 2016 21:52:09 +0100	[thread overview]
Message-ID: <20160211215209.2f381cc0@gmx.net> (raw)
In-Reply-To: <1455203390156-125571.post@n4.nabble.com>

Hello Gabriel Andr?s Castillo,

On Thu, 11 Feb 2016 07:09:50 -0800 (PST), GabrielCastillo <gcastillo@controlnet.com.ar> wrote:

> Definitely the problem is with QT5. I read some places that could be
> littleendian problem. To run my app, i do:
> 
> > ./App -platform linuxfb
> 
> There are any form to tell that it has to be execute in littleendian or
> bigendian?
> 

No, no such option for qt5 (see [1] for linuxfb options).

Mind to run 'fbset -s' (or 'fbset -i') on your platform ?

Output gives the pixel defintion of the framebuffer, e.g.

rgba 5/11,6/5,5/0,0/16

for my adafruit display (and try to test if the given
pixel defintion is correct by writing color patterns
to the framebuffer (direct or with some framebuffer
test program)...

Or mind to try the following atmel qt5 patch ([2]) from
the OpenEmbedded/Yocto layer?

This patch gives you a hint for the place where to fix/adjust the
qt5 drawing to the framebuffer...

Regards,
Peter


[1] http://doc.qt.io/qt-5/embedded-linux.html
[2] https://github.com/linux4sam/meta-atmel/blob/master/qt5-layer/recipes-qt/qt5/files/atmel-color-format-force.patch

> 
> 
> --
> View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Setting-RGB-tp124903p125571.html
> Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2016-02-11 20:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 14:28 [Buildroot] Setting RGB Gabriel Andrés Castillo
2016-02-04 19:55 ` Peter Seiderer
2016-02-10 17:40   ` GabrielCastillo
2016-02-11 14:06     ` Ezequiel Garcia
2016-02-11 14:04       ` GabrielCastillo
2016-02-11 14:46         ` Ezequiel Garcia
2016-02-11 14:48           ` Ezequiel Garcia
2016-02-11 15:09       ` GabrielCastillo
2016-02-11 20:52         ` Peter Seiderer [this message]
2016-04-12 11:45           ` Leonardo Giordano
2016-04-13 13:35             ` Leonardo Giordano
2016-04-13 20:54               ` Peter Seiderer

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=20160211215209.2f381cc0@gmx.net \
    --to=ps.report@gmx.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.