[yocto] [meta-raspberrypi] No package 'wayland-egl' found

2018-05-14 Thread Bill Jenkins
Hi, I just sync'd to the head of the master branch in the poky and meta-raspberrypi repos today and tried a build that successfully completed last week, but now fails with the error message "No package 'wayland-egl' found" during the gtk+3_3.22.29.bb:do_configure task. I see some recent commit

Re: [yocto] [meta-raspberrypi] No package 'wayland-egl' found

2018-05-14 Thread Bill Jenkins
> On May 14, 2018, at 2:43 PM, Bill Jenkins wrote: > > Hi, > > I just sync'd to the head of the master branch in the poky and > meta-raspberrypi repos today > and tried a build that successfully completed last week, but now fails with > the error message >

Re: [yocto] [meta-raspberrypi] No package 'wayland-egl' found

2018-05-15 Thread Bill Jenkins
Hi Andrei, Thanks so much for confirming the issue. > On May 15, 2018, at 4:18 AM, Andrei Gherzan wrote: > > Hi, > > On Tue, May 15, 2018 at 1:48 AM, Bill Jenkins <mailto:b...@korgrd.com>> wrote: > > > On May 14, 2018, at 2:43 PM, Bill Jenkins > <mail

[yocto] raspberrypi3-64 target not booting

2017-08-25 Thread Bill Jenkins
I am trying to just get the simple 64-bit rpi-basic-image to work, but the Raspberry Pi 3 seems to hang with the rainbow screen at startup. If I build with MACHINE ?= raspberrypi3, the 32-bit image works just fine. Is there something special that needs to be set in order for the "MACHINE ?= raspb

Re: [yocto] raspberrypi3-64 target not booting

2017-08-26 Thread Bill Jenkins
> On Aug 26, 2017, at 12:36 AM, Herve Jourdain wrote: > > Hi, > > Are you using vc4 as graphics, or are you using the default userland? > If you want graphics with 64 bits, you need to use vc4. > The raspberrypi3-64.conf file has the line: MACHINE_FEATURES_append = " vc4graphics" I assume t

[yocto] [meta-raspberry-pi] needing newer or patched version of g++

2017-09-14 Thread Bill Jenkins
After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the following compiler error when compiling an application using the SDK: internal compiler error: Max. number of generated reload insns per insn is achieved (90) It turns out that a patch was submitted for g++ early last year

Re: [yocto] [meta-raspberry-pi] needing newer or patched version of g++

2017-09-15 Thread Bill Jenkins
> On Sep 15, 2017, at 6:54 AM, Khem Raj wrote: > > On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins wrote: >> After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the >> following compiler error when >> compiling an application using the SDK: >>

Re: [yocto] [meta-raspberry-pi] needing newer or patched version of g++

2017-09-15 Thread Bill Jenkins
> On Sep 15, 2017, at 7:43 AM, Khem Raj wrote: > > On Fri, Sep 15, 2017 at 7:35 AM, Bill Jenkins wrote: >> >>> On Sep 15, 2017, at 6:54 AM, Khem Raj wrote: >>> >>> On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins wrote: >>>> After creatin

Re: [yocto] [meta-raspberry-pi] needing newer or patched version of g++

2017-10-07 Thread Bill Jenkins
> On Sep 15, 2017, at 8:02 AM, Bill Jenkins wrote: > > >> On Sep 15, 2017, at 7:43 AM, Khem Raj wrote: >> >> On Fri, Sep 15, 2017 at 7:35 AM, Bill Jenkins wrote: >>> >>>> On Sep 15, 2017, at 6:54 AM, Khem Raj wrote: >>>>

[yocto] [meta-raspberrypi] Cannot see /dev/ttyS0 on CM3+ with 4.19.66 yocto build.

2019-09-02 Thread Bill Jenkins
The 4.14.112 yocto builds that we have been using show both /dev/ttyS0 and /dev/ttyAMA0 initialization strings in dmesg and both can be successfully used. After updating to the latest to try out the 4.19.66 kernel, we see the initialization message for /dev/ttyAMA0 and can use it, but there is