Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] qt5, eglfs and xcb
Date: Tue, 01 Apr 2014 12:05:32 +0200	[thread overview]
Message-ID: <533A8F6C.1010606@gmail.com> (raw)
In-Reply-To: <20140330172128.06f1d5d2@skate>



Il 30/03/2014 17:21, Thomas Petazzoni ha scritto:
> As explained above, this requires more than just XCB, contrary to what 
> the company you requested support from is claiming. You need an OpenGL 
> implementation that works under X.org, and this implementation is 
> usually Mesa. And the support for making Mesa recognized as a proper 
> OpenGL implementation has only been merged since yesterday, and is not 
> yet completely ready. It would certainly be interesting to fix this in 
> Buildroot and allow Qt5 to build for X.org with OpenGL support. 


Ok, as far as I understand it means nobody has successfully compiled Qt5 
+ webkit + xcb + mesa yet.
Perhaps, people use only the framebuffer with buildroot.


> But if you want this to happen, you should either: 1) Do it yourself. 
> 2) Wait for someone else to do it, but then you can't expect any 
> particular deadline or guarantees. It may be something that will get 
> done this summer as part of the Google Summer of Code. 3) Hire a third 
> party to do it. Actually, it's a little bit strange that you've asked 
> a company who isn't able to fix the problem in Buildroot, rather than 
> a company that actually is able to do it. 


Unfortunately we have a dead-line for our project and my knowledge is 
too small to do it myself. I'm going for the third option, but with 
another company :-)


> BTW, what is your hardware platform? What type of graphics hardware 
> are you using? What X.org driver are you using? Anyway, thanks for the 
> report, this is definitely something that should be improved. Thomas 

We're using a Freescale iMX6 MARS board, with the modular X.org server.
As drivers, I selected:

xf86-input-evdev
xf86-input-keyboard
xf86-input-mouse
xf86-input-tslib
xf86-video-fbdev

because I don't know which other video driver I should select for my 
platform...

Best regards
Marco

  reply	other threads:[~2014-04-01 10:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30 13:47 [Buildroot] qt5, eglfs and xcb Marco Trapanese
2014-03-30 15:21 ` Thomas Petazzoni
2014-04-01 10:05   ` Marco Trapanese [this message]
2014-04-01 12:40     ` Thomas Petazzoni
2014-04-01 16:16     ` Jérôme Pouiller
2014-04-01 16:16       ` [Buildroot] [PATCH 1/2] qt5declarative: Reduce dependencies to GLes2 only Jérôme Pouiller
2014-04-20  9:18         ` Thomas Petazzoni
2014-07-15  8:26           ` Hadrien Boutteville
2014-07-15 14:03             ` Fatih Aşıcı
2014-07-15 16:24               ` Jérôme Pouiller
2014-07-15 17:03                 ` Thomas Petazzoni
2014-04-01 16:16       ` [Buildroot] [PATCH 2/2] Add supporit for Vivante xdriver Jérôme Pouiller
2014-04-20 10:13         ` Thomas Petazzoni
2014-09-16 14:46         ` Thomas Petazzoni
2014-09-16 17:07           ` Jérôme Pouiller
2014-09-16 17:59             ` Thomas Petazzoni
2014-04-01 16:18       ` [Buildroot] qt5, eglfs and xcb Marco Trapanese

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=533A8F6C.1010606@gmail.com \
    --to=marcotrapanese@gmail.com \
    --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