All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/13] Update Freescale packages to 3.10.53-1.1.0_GA
Date: Tue, 28 Jul 2015 10:41:02 +0200	[thread overview]
Message-ID: <2511281.mSghaPHi6x@sagittea> (raw)
In-Reply-To: <CAAMH-ytPb5ftuAWbYqnotZdWPH7h8Xv9f+-axc69Bs=QNGNCVQ@mail.gmail.com>

On Tuesday 28 July 2015 10:23:56 Gary Bisson wrote:
> Hi Jerome,
> 
> On Tue, Jul 28, 2015 at 10:12 AM, J?r?me Pouiller <jezz@sysmic.org> wrote:
> > Hello Gary, Carlos,
> >
> > On Monday 27 July 2015 19:42:08 Gary Bisson wrote:
> >> Hi Carlos,
> >>
> >> On Sat, Jul 18, 2015 at 10:06 PM, Carlos Soto <csotoalonso@gmail.com> 
wrote:
> >> >
> >> >
> >> > 2015-07-18 21:55 GMT+02:00 Thomas Petazzoni
> >> > <thomas.petazzoni@free-electrons.com>:
> >> >>
> >> >> Dear Carlos Soto,
> >> >>
> >> >> On Sat, 18 Jul 2015 21:36:04 +0200, Carlos Soto wrote:
> > [...]
> >> >> > Anyway, they seem to work except for the fact that as soon as a 
program
> >> >> > is
> >> >> > stopped (mainly I've tried with glxgears) the xserver crashes. 
That's
> >> >> > the
> >> >> > error log:
> >> >>
> >> >> I'm adding Gary in Cc, he can probably help about this, at least
> >> >> confirm whether he can reproduce the same problem or not.
> >> >
> >> >
> >> > Great! I'll also try it again once I update my local copy
> >>
> >> Yes I confirm I've built the master branch today and I see this error
> >> when closing the X app. I will let you know if I find what causes this
> >> error. Note that in my case it doesn't happen all the time. I suspect
> >> the vivante libraries...
> > As far as remember, by default X server terminate when the last client 
exit.
> > When you produce problem, are you closing the last client? You can try to 
pass
> > --noreset option when you launch X.
> 
> I was actually looking at the issue to the test was quick, yes the
> error disappears with the -noreset option. Seems that stopping the
> server is the problem. The log was saying that swrast was missing so I
> added but it didn't remove the error. The last message before the
> crash is:
> [3551284.259] (II) VIVANTE(0): Setting screen physical size to 338 x 211
> [3551284.297] (EE)
> [3551284.297] (EE) Backtrace:
> [3551284.297] (EE)
> [3551284.297] (EE) Segmentation fault at address 0x76fd10dc
As far as I remember, Xorg also crash on exit with Yocto. 


> On the swrast topic, should we add to as a select in the Config.in as
> it seems to the be case in Yocto?
> https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante.inc#L64
Enabling swrast allow to use GLX/OpenGL applications but using software 
rendering. IFAIK, swrast is not necessary if you only use EGL/GLESv2 
applications. Current Buildroot does not enforce swrast but allows user to 
select it if he want. I think it is correct behavior. 

In add, personally, I prefer swrast to be disabled so I am sure my GL 
applications are hardware accelerated.

[...]

-- 
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr

  reply	other threads:[~2015-07-28  8:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18 19:36 [Buildroot] [PATCH 00/13] Update Freescale packages to 3.10.53-1.1.0_GA Carlos Soto
2015-07-18 19:55 ` Thomas Petazzoni
2015-07-18 20:06   ` Carlos Soto
2015-07-27 17:42     ` Gary Bisson
2015-07-28  8:12       ` Jérôme Pouiller
2015-07-28  8:23         ` Gary Bisson
2015-07-28  8:41           ` Jérôme Pouiller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-20 10:12 Gary Bisson

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=2511281.mSghaPHi6x@sagittea \
    --to=jezz@sysmic.org \
    --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.