From: Trevor Woerner <twoerner@gmail.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi] gles2 on raspi3
Date: Sun, 16 Apr 2017 20:45:10 -0400 [thread overview]
Message-ID: <20170417004510.GC5766@linux-uys3> (raw)
In-Reply-To: <CALbNGRRgHasv5rdG1SyPCogY8Az6ZowvoZc59XV=Jpmi4TMwvQ@mail.gmail.com>
On Mon 2017-04-17 @ 01:23:25 AM, Andreas Müller wrote:
> > I got chromium building with it (it was a simple DEPENDS) and on the image I
> > just built sound is already working!
> * You have chromium building (and running?). This is on my endless
> TODO-list (have firefox on my image but that crashes more or less
> immediately - wonder what other people do with it)
There's been a nice surge in interest/help with chromium lately (not to
mention getting people to push upstream!) The recipes in OE are still building
a rather old version (54.0.2810.2) but it builds and works for x11 on x86
(qemux86), x86-64 (minnow), armv7 (bbb, raspi3-32), and armv8 (dragon 410c);
it builds for a couple more (firefly and raspi3-64) but I can't get xorg
working so I can't test it running.
You'll probably want to set the following PACKAGECONFIGs:
PACKAGECONFIG_pn-chromium = "disable-api-keys-info-bar ignore-lost-context impl-side-painting"
And (as I've mentioned) you'll need to add "mesa" to the DEPENDS (although I'm
not sure why it's now needed nor how to make that change in a "nice" way since
the non-accelerated version doesn't need it).
I'm not fully up-to-date on the wayland side, but I believe it builds and
works on wayland for roughly the same list plus beagleX15 and hikey. The
wayland version is slightly older at 53.0.2785.143.
There are people working on newer versions up to 59, but so far nobody's
pushing upstream. I'm hoping to take a look and getting something working. The
way chromium is built changed around the late 53 early 54 timeframe so a new
procedure is needed.
I've been running and testing with vc4 on my raspi3 for the last two hours
or so. I've seen one crash once when I tried to full-screen youtube, but
subsequent attempts have succeeded, so I'm not sure if those two events are
related. I've been doodling around in youtobe for all this time and it's been
mostly working except for that one instance.
> * I have not tested that (I need low latency and plugs for playing music)
The sound came though the HDMI for me. It's the first time I've heard a board
make noise :-)
next prev parent reply other threads:[~2017-04-17 0:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 13:39 [meta-raspberrypi] gles2 on raspi3 Trevor Woerner
2017-04-15 14:46 ` Andreas Müller
2017-04-15 16:35 ` Trevor Woerner
2017-04-15 18:09 ` Andreas Müller
2017-04-15 23:16 ` Trevor Woerner
2017-04-16 23:23 ` Andreas Müller
2017-04-17 0:30 ` Trevor Woerner
2017-04-17 0:49 ` Andreas Müller
2017-04-17 0:45 ` Trevor Woerner [this message]
2017-04-16 23:52 ` Andreas Müller
2017-04-17 0:27 ` Trevor Woerner
2017-04-17 1:11 ` Andreas Müller
2017-04-18 4:16 ` Changhyeok Bae
2017-04-16 22:54 ` Trevor Woerner
2017-04-20 3:41 ` ***SPAM*** " Herve Jourdain
2017-04-20 7:13 ` Trevor Woerner
2017-04-20 11:56 ` Herve Jourdain
2017-04-20 12:58 ` Andreas Müller
2017-04-20 16:55 ` Khem Raj
2017-04-21 3:19 ` Gary Thomas
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=20170417004510.GC5766@linux-uys3 \
--to=twoerner@gmail.com \
--cc=schnitzeltony@googlemail.com \
--cc=yocto@yoctoproject.org \
/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.