I have the same issue here, where i need to run pulseaudio without x11. My setup in yocto, is a follows, it compiles fine but dbus has a problem : IMAGE_INSTALL_append= " pulseaudio-server

After some tests, I found the following appearance: 1) When I add "enable_uart=1" to the /boot/config.txt, the brcm43438.service(use /dev/ttyAMA0) can start successfully *definitely*.

Everything's working :-) This is the first time I've seen graphics (x11) working with rpi3-64. mesa-demos, directfb-examples, chromium (accelerated!), qt5...

Reproducing with qemuarm would require both changing qemuarm to use a CPU with supports Thumb2 and then changing the kernel config to build a Thumb2 kernel. It's not going to be a trivial tweak.

<celledge@...> wrote: Thanks for bringing up this issue. Reading through the various bug reports etc it not clear what the fix should be. Upstream binutils has not reverted the change

On 04/02/2018 01:15 PM, Chris Elledge wrote: I will take a look. Can you provide a reproducer? ie qemuarm tweak?? - armin

FYI: Just sent out a pull request enabling dri3 for meta-raspberrypi. So whatever mushrooms oe-core guys are going to consume - we'll have dri3 :) Andreas

Hi Trevor, Right, you shouldn't need that at all. It's unlikely to do any good. If it does solve anything, we'd love to hear about what so we can try to fix it, like with this one. Right, Weston/etc

Yes, this is a very nice side effect of your digging into this apparently un-related issue! :-) In my own layers I had a .bbappend that was copying the chromium-built egl/gles libraries to the

On Mon, Apr 2, 2018 at 11:12 PM, Trevor Woerner <twoerner@...> wrote: Removed mesa-dev - this is oe specific only. > Even without the patch, simply adding: > >

Even without the patch, simply adding: PACKAGECONFIG_append_pn-mesa = "dri3" to my conf/local.conf has glmark2-es2 running, and chromium-x11 is running accelerated out-of-the-box (i.e. I don't have

Hi Daniel, Just sent out patches to oe-core * Apply your patch with dri2 modifier init * Prefer dri3 over dri2 for x11/opengl distro features See what happens... Cheers Andreas

I recently upgraded my Yocto based project to Yocto 2.4.2, and I encountered a problem when building my custom kernel for an AT91 SAMA5D3X platform. I've been using an ARM Thumb2 kernel for a while

Some addition information. It seems if I if I do this: IMAGE_NAME_SUFFIX_sdimg = "" do_image_sdimg[imgsuffix] = "" Then all steps are completed as expected (gz created and symlink is

Re-send, because my initial mail got stuck for moderator approval due to not being registered on the mailing-list with this email, I am now and bypassing moderators :). -- Med Vänliga Hälsningar /

Current Dev Position: YP 2.5 M3 final close out. Next Deadline: YP 2.5 M4 stabilization is 4/2/18 SWAT Team Rotation: SWAT lead is currently Juro. SWAT team rotation: Juro -> Paul on April 6,

Thanks - I was thinking same. OE-Core enables DRI3 for x11 AND vulcan only - and vulcan is not in my distro features (and does not make much sense for VC4) Added yocto mailing list to merge both

I did already [1]. My problem was that meta-raspi-light did not enable dri3 explicitly any more. meta-raspi-light uses more PACKAGECONFIG defaults coming from oe-core's mesa. There was a change in

Hi, I trying to build core-image-sato using yocto 2.5 with new package openssh. Added openssh entry in the local.conf file as follows: IMAGE_INSTALL_append = "openssh" But facing some conflicts

Hi , Please refer to my below steps to understand how OS components are included in the Qemu image for Yocto 2.5 1) Build core-image-sato for yocto 2.5 ( DISTRO_VERSION = 2.4+snapshot-20180402) 2) I