Date   

Re: virtual/egl on Raspberry Pi 4

Khem Raj
 

that should have worked well for userland recipe to provide it. Maybe
you need to set

VC4GRAPHICS = ""

in local.conf

On Tue, Oct 5, 2021 at 8:53 AM Greg Wilson-Lindberg
<GWilson@...> wrote:

I am compiling in 32 bit mode.



From: Khem Raj <raj.khem@...>
Sent: Monday, October 4, 2021 5:15 PM
To: Greg Wilson-Lindberg <GWilson@...>
Cc: yocto@...
Subject: Re: [yocto] virtual/egl on Raspberry Pi 4



It should have automatically found user land package as one of providers but if it is not doing so that means it’s being ignored because it’s not compatible arch or something

Are you compiling 32bit mode ?





On Mon, Oct 4, 2021 at 4:08 PM Greg Wilson-Lindberg <GWilson@...> wrote:

Hi Khem,
Yes, the Raspberry Pi boards do use closed source drivers. What I need is how do I include the proper package that will bring in the necessary virtual/egl for the Raspberry Pi 4.

Greg
-----Original Message-----
From: Khem Raj <raj.khem@...>
Sent: Monday, October 4, 2021 14:17
To: Greg Wilson-Lindberg <GWilson@...>;
yocto@...
Subject: Re: [yocto] virtual/egl on Raspberry Pi 4



On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:
Hello list,

I'm working on a Qt supplied boot2qt Yocto build currently based on
Zeus that is running on a Raspberry Pi 4. I recently updated the qt
version to 5.15.6 and Qt changed something in the Yocto configuration
that they are using and now one of the recipes that we use is failing
saying that in needs 'virtual/egl' but that it is not provided by any recipe.

In the searching that I have done I have found that the raspberry pi 4
is particular on which package supplies the virtual/egl but I haven't
seen anything that indicates what I should do to re-enable it.

Can anyone tell me what I need to do to enable the correct driver to
get virtual/egl provided on the Raspberry Pi 4? Or maybe even better,
how I could search through the packages that are enabled on the old
and new Yocto trees so that I can figure out what changed between the
releases and re-enable the virtual/egl.
it should be provided by userland package if you are using closed source
graphics driver.

Best Regards,

Greg Wilson-Lindberg





Re: virtual/egl on Raspberry Pi 4

Greg Wilson-Lindberg
 

I am compiling in 32 bit mode.

 

From: Khem Raj <raj.khem@...>
Sent: Monday, October 4, 2021 5:15 PM
To: Greg Wilson-Lindberg <GWilson@...>
Cc: yocto@...
Subject: Re: [yocto] virtual/egl on Raspberry Pi 4

 

It should have automatically found user land package as one of providers but if it is not doing so that means it’s being ignored because it’s not compatible arch or something 

Are you compiling 32bit mode ? 

 

 

On Mon, Oct 4, 2021 at 4:08 PM Greg Wilson-Lindberg <GWilson@...> wrote:

Hi Khem,
Yes, the Raspberry Pi boards do use closed source drivers. What I need is how do I include the proper package that will bring in the necessary virtual/egl for the Raspberry Pi 4.

Greg
> -----Original Message-----
> From: Khem Raj <raj.khem@...>
> Sent: Monday, October 4, 2021 14:17
> To: Greg Wilson-Lindberg <GWilson@...>;
> yocto@...
> Subject: Re: [yocto] virtual/egl on Raspberry Pi 4
>
>
>
> On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:
> > Hello list,
> >
> > I'm working on a Qt supplied boot2qt Yocto build currently based on
> > Zeus that is running on a Raspberry Pi 4. I recently updated the qt
> > version to 5.15.6 and Qt changed something in the Yocto configuration
> > that they are using and now one of the recipes that we use is failing
> > saying that in needs 'virtual/egl' but that it is not provided by any recipe.
> >
> > In the searching that I have done I have found that the raspberry pi 4
> > is particular on which package supplies the virtual/egl but I haven't
> > seen anything that indicates what I should do to re-enable it.
> >
> > Can anyone tell me what I need to do to enable the correct driver to
> > get virtual/egl provided on the Raspberry Pi 4? Or maybe even better,
> > how I could search through the packages that are enabled on the old
> > and new Yocto trees so that I can figure out what changed between the
> > releases and re-enable the virtual/egl.
> >
>
> it should be provided by userland package if you are using closed source
> graphics driver.
>
> > Best Regards,
> >
> > Greg Wilson-Lindberg
> >
> >
> >
> >
> >


Yocto Project Status WW40`21

Stephen Jolley
 

Current Dev Position: YP 3.4 M4

Next Deadline: 4th Oct. 2021 YP 3.4 M4 build

 

Next Team Meetings:

 

Key Status/Updates:

  • The final 3.4 build is now due.
  • We should be in a reasonable position and ready for the 3.4 build, except for the SOURCE_DATE_EPOCH corruption issues we’re seeing. Once those issues and the related sstate reuse issues are fixed, we’ll build 3.4. At this point there are other patches but they’re causing failures and clearly aren’t ready for merging.
  • There continues to be an sstate reuse issue where native sstate on aarch64 and x86_64 hosts isn’t generating correct hashes when combined with hash equivalence.
  • Intermittent issues took a significant rise last week as SWAT caught up with the backlog of issues. Help is very much welcome on these issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

 

Ways to contribute:

 

YP 3.4 Milestone Dates:

  • YP 3.4 M4 build date 2021/10/04
  • YP 3.4 M4 Release date 2021/10/29

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: [meta-zephyr 0/2] add support of the zephyr-openamp-rsc-table sample on STM32MP157

Arnaud Pouliquen <arnaud.pouliquen@...>
 

Hello Saini,

On 10/5/21 9:08 AM, Saini, Naveen Kumar wrote:
This is only cover letter, I do not see patches on mailing list..
Yes something strange, they are not listed on same page of the archive on
https://lists.yoctoproject.org/

Patch 1/2 and patch 2/2 associated with this one are visible in the Yocto archive:

link to the patches on mail-archive.com:
https://www.mail-archive.com/yocto@lists.yoctoproject.org/msg07088.html
https://www.mail-archive.com/yocto@lists.yoctoproject.org/msg07089.html

Please tell me if you need that I resend the series.

Regards,
Arnaud



Regards,
Naveen

-----Original Message-----
From: yocto@... <yocto@...> On
Behalf Of Arnaud Pouliquen
Sent: Wednesday, September 29, 2021 5:41 PM
To: yocto@...
Cc: Kumar Gala <kumar.gala@...>; Kevin Townsend
<kevin.townsend@...>
Subject: [yocto] [meta-zephyr 0/2] add support of the zephyr-openamp-rsc-
table sample on STM32MP157

Add capability to genereate the "zephyr-openamp-rsc-table" sample in yocto
build.

This example demonstrates inter-processor communication based on a
resource table, with the objective of responding to the Linux kernel rpmsg
sample.

This sample is compatible with the stm32mp157c_dk2 board.
The support of the board is also added in this series.

Arnaud Pouliquen (2):
conf: machine: add stm32mp157c-dk2 support
zephyr-kernel: add openamp-rsc-table sample

conf/machine/stm32mp157c-dk2.conf | 8 ++++++++
.../zephyr-kernel/zephyr-openamp-rsc-table.bb | 10 ++++++++++
2 files changed, 18 insertions(+)
create mode 100644 conf/machine/stm32mp157c-dk2.conf create mode
100644 recipes-kernel/zephyr-kernel/zephyr-openamp-rsc-table.bb

--
2.17.1


#dunfell Path to sources in debugfs #dunfell

bohdan.shubenok@...
 

Hi all,

I`m trying to debug coredump generated on embedded system running dunfel. The issue I`m facing is with the source files path in "-dbg.rootfs" archive and within dedug portion of a package.
When loaded in QtCreator some sources can`t be found :


The part is missing is "build/..". Such notation is obviosly cancels itself and adding empty "build" folder manually helps.
This path allings with how it builds. Here is a part of Makefile found in build path for sqlite:

   build/Makefile:20:VPATH = ../sqlite-autoconf-3310100
   build/Makefile:313:abs_srcdir = /home/bohdan/noah/noah/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/sqlite3/3_3.31.1-r0/build/../sqlite-autoconf-3310100
   build/Makefile:315:abs_top_srcdir = /home/bohdan/noah/noah/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/sqlite3/3_3.31.1-r0/build/../sqlite-autoconf-3310100
   build/Makefile:358:srcdir = ../sqlite-autoconf-3310100

So I tried to disable out-of-tree build for sqlite by replacing  'inherit autotools' with 'inherit autotools-brokensep'. After building and loading new debugfs QtCreator was able to found required sources:


Is this a known issue or me doing something wrong with build setup?


file package dependency

Timur
 

Hi, I'm building a yocto release from the thud branch. The size of the OS image is very critical, so I need to remove as much as I can. Looking at the dependency information, I can see that the "file" package is not required by any other package, but yet it is installed. I really have to remove this package because it is quite large with its magic database, but I can't find who is installing it and why.

--
Timur Aydın
TEL: 536 939 65 88


Re: Enabling Websockets in Mosquitto in yocto zeus #zeus

Nicolas Jeker
 

On Fri, 2021-10-01 at 03:45 -0700, poornesh@... wrote:
Greetings !

I could able to add Mosquitto in Yocto Zeus , but as default websockets
is disabled in Mosquitto . Can anyone help me how to enable websockets
in Mosquitto in yocto zeus.
There's a 'websockets' PACKAGECONFIG for the mosquitto recipe. You can
read more about how to change PACKAGECONFIGs in the documentation [1].

Be aware that since yocto dunfell, the websockets PACKAGECONFIG is
enabled by default, so you can remove it if you update to a newer
version in the future.

[1]:
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-PACKAGECONFIG

Thanks in Advance


Re: [meta-zephyr 0/2] add support of the zephyr-openamp-rsc-table sample on STM32MP157

Naveen Saini
 

This is only cover letter, I do not see patches on mailing list..

Regards,
Naveen

-----Original Message-----
From: yocto@... <yocto@...> On
Behalf Of Arnaud Pouliquen
Sent: Wednesday, September 29, 2021 5:41 PM
To: yocto@...
Cc: Kumar Gala <kumar.gala@...>; Kevin Townsend
<kevin.townsend@...>
Subject: [yocto] [meta-zephyr 0/2] add support of the zephyr-openamp-rsc-
table sample on STM32MP157

Add capability to genereate the "zephyr-openamp-rsc-table" sample in yocto
build.

This example demonstrates inter-processor communication based on a
resource table, with the objective of responding to the Linux kernel rpmsg
sample.

This sample is compatible with the stm32mp157c_dk2 board.
The support of the board is also added in this series.

Arnaud Pouliquen (2):
conf: machine: add stm32mp157c-dk2 support
zephyr-kernel: add openamp-rsc-table sample

conf/machine/stm32mp157c-dk2.conf | 8 ++++++++
.../zephyr-kernel/zephyr-openamp-rsc-table.bb | 10 ++++++++++
2 files changed, 18 insertions(+)
create mode 100644 conf/machine/stm32mp157c-dk2.conf create mode
100644 recipes-kernel/zephyr-kernel/zephyr-openamp-rsc-table.bb

--
2.17.1


Re: [meta-security,dunfell][PATCH] recipes-security/fscrypt: Add fscrypt .bb file

Bhupesh Sharma
 

Hello Armin,

Many thanks for your review.

On Sun, 26 Sept 2021 at 03:01, akuster808 <akuster808@...> wrote:



On 9/19/21 12:19 PM, Bhupesh Sharma wrote:
fscrypt is a high-level tool for the management of Linux
filesystem encryption. fscrypt manages metadata, key generation,
key wrapping, PAM integration, and provides a uniform interface
for creating and modifying encrypted directories.

Add recipe for the same in 'recipes-security'.
Was this a double post? or a V2?
Sorry for the double post, but since I had some issues subscribing to
the OE-list, my first attempt to post was not accepted by the mailing
list server.

I follow the OE/YP Stable process and this appears to be adding a new
package to a stable release which is not allowed.. I have no issue
taking it for Master.
Sure. I realized my mistake later-on. I should have sent it for the
'master' branch and not stable / dunfell. Can you please consider
taking this into the 'master' branch, or should I send the patch
separately.

Thanks and sorry for the late reply,
Bhupesh

-armin

Signed-off-by: Bhupesh Sharma <bhupesh.sharma@...>
---
recipes-security/fscrypt/fscrypt_1.0.0.bb | 49 +++++++++++++++++++++++
1 file changed, 49 insertions(+)
create mode 100644 recipes-security/fscrypt/fscrypt_1.0.0.bb

diff --git a/recipes-security/fscrypt/fscrypt_1.0.0.bb b/recipes-security/fscrypt/fscrypt_1.0.0.bb
new file mode 100644
index 0000000..a70d310
--- /dev/null
+++ b/recipes-security/fscrypt/fscrypt_1.0.0.bb
@@ -0,0 +1,49 @@
+SUMMARY = "fscrypt is a high-level tool for the management of Linux filesystem encryption"
+DESCIPTION = "fscrypt manages metadata, key generation, key wrapping, PAM integration, \
+and provides a uniform interface for creating and modifying encrypted directories. For \
+a small, low-level tool that directly sets policies, see fscryptctl \
+(https://github.com/google/fscryptcl)."
+HOMEPAGE = "https://github.com/google/fscrypt"
+SECTION = "base"
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://src/${GO_IMPORT}/LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
+
+BBCLASSEXTEND = "native nativesdk"
+
+# fscrypt depends on go and libpam
+DEPENDS += "go-dep-native libpam"
+
+SRCREV = "92b1e9a8670ccd3916a7d24a06cab1e4c9815bc4"
+SRC_URI = "git://github.com/google/fscrypt.git"
+GO_IMPORT = "import"
+
+S = "${WORKDIR}/git"
+
+inherit go
+inherit goarch
+
+do_compile() {
+ export GOARCH=${TARGET_GOARCH}
+ export GOROOT="${STAGING_LIBDIR_NATIVE}/${TARGET_SYS}/go"
+ export GOPATH="${WORKDIR}/git"
+
+ # Pass the needed cflags/ldflags so that cgo
+ # can find the needed headers files and libraries
+ export CGO_ENABLED="1"
+ export CGO_CFLAGS="${CFLAGS} --sysroot=${STAGING_DIR_TARGET}"
+ export CGO_LDFLAGS="${LDFLAGS} --sysroot=${STAGING_DIR_TARGET}"
+
+ cd ${S}/src/${GO_IMPORT}
+ oe_runmake
+
+ # Golang forces permissions to 0500 on directories and 0400 on files in
+ # the module cache which prevents us from easily cleaning up the build
+ # directory. Let's just fix the permissions here so we don't have to
+ # hack the clean tasks.
+ chmod -R u+w ${S}/pkg/mod
+}
+
+do_install() {
+ install -d ${D}/${bindir}
+ install ${S}/src/${GO_IMPORT}/bin/fscrypt ${D}/${bindir}/fscrypt
+}


M+ & H bugs with Milestone Movements WW40

Stephen Jolley
 

All,

YP M+ or high bugs which moved to a new milestone in WW40 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

14263

AB-INT PTEST: lttng-tools ptest intermittent failure

randy.macleod@...

unassigned@...

3.4

3.4 M4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW40!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

richard.purdie@...

7

oobitots@...

1

alexandre.belloni@...

1

Grand Total

9

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.4

Stephen Jolley
 

All,

Below is the list as of top 50 bug owners as of the end of WW40 of who have open medium or higher bugs and enhancements against YP 3.4.   There are 18 possible work days left until the final release candidates for YP 3.4 needs to be released.

Who

Count

michael.opdenacker@...

35

ross@...

31

david.reyna@...

22

randy.macleod@...

16

trevor.gamblin@...

14

bruce.ashfield@...

11

richard.purdie@...

10

timothy.t.orling@...

9

kai.kang@...

7

bluelightning@...

6

mhalstead@...

4

kiran.surendran@...

4

Qi.Chen@...

4

hongxu.jia@...

3

JPEWhacker@...

3

chee.yang.lee@...

3

thomas.perrot@...

2

akuster808@...

2

mingli.yu@...

2

mshah@...

2

saul.wold@...

2

raj.khem@...

1

tony.tascioglu@...

1

yi.zhao@...

1

sangeeta.jain@...

1

jay.shen.teoh@...

1

pokylinux@...

1

alexandre.belloni@...

1

alejandro@...

1

yf3yu@...

1

open.source@...

1

weaverjs@...

1

jaewon@...

1

fransmeulenbroeks@...

1

kergoth@...

1

mickael.laventure+yocto@...

1

ydirson@...

1

devendra.tewari@...

1

jeanmarie.lemetayer@...

1

diego.sueiro@...

1

aehs29@...

1

sakib.sajal@...

1

matthewzmd@...

1

douglas.royds@...

1

paul.gortmaker@...

1

paul@...

1

alex.kanavin@...

1

vinay.m.engg@...

1

shachar@...

1

pgowda.cve@...

1

mister_rs@...

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 392 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.4”, “3.5, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

Stephen Jolley
 

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (10/5) 

 

Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: https://web.libera.chat/#yocto 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

When            Monthly from 8am to 9am on the first Tuesday Pacific Time

Where           Zoom Meeting: https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09

 

We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them.  The world should have view access.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: virtual/egl on Raspberry Pi 4

Khem Raj
 

It should have automatically found user land package as one of providers but if it is not doing so that means it’s being ignored because it’s not compatible arch or something 
Are you compiling 32bit mode ? 


On Mon, Oct 4, 2021 at 4:08 PM Greg Wilson-Lindberg <GWilson@...> wrote:
Hi Khem,
Yes, the Raspberry Pi boards do use closed source drivers. What I need is how do I include the proper package that will bring in the necessary virtual/egl for the Raspberry Pi 4.

Greg
> -----Original Message-----
> From: Khem Raj <raj.khem@...>
> Sent: Monday, October 4, 2021 14:17
> To: Greg Wilson-Lindberg <GWilson@...>;
> yocto@...
> Subject: Re: [yocto] virtual/egl on Raspberry Pi 4
>
>
>
> On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:
> > Hello list,
> >
> > I'm working on a Qt supplied boot2qt Yocto build currently based on
> > Zeus that is running on a Raspberry Pi 4. I recently updated the qt
> > version to 5.15.6 and Qt changed something in the Yocto configuration
> > that they are using and now one of the recipes that we use is failing
> > saying that in needs 'virtual/egl' but that it is not provided by any recipe.
> >
> > In the searching that I have done I have found that the raspberry pi 4
> > is particular on which package supplies the virtual/egl but I haven't
> > seen anything that indicates what I should do to re-enable it.
> >
> > Can anyone tell me what I need to do to enable the correct driver to
> > get virtual/egl provided on the Raspberry Pi 4? Or maybe even better,
> > how I could search through the packages that are enabled on the old
> > and new Yocto trees so that I can figure out what changed between the
> > releases and re-enable the virtual/egl.
> >
>
> it should be provided by userland package if you are using closed source
> graphics driver.
>
> > Best Regards,
> >
> > Greg Wilson-Lindberg
> >
> >
> >
> >
> >


Re: virtual/egl on Raspberry Pi 4

Greg Wilson-Lindberg
 

Hi Khem,
Yes, the Raspberry Pi boards do use closed source drivers. What I need is how do I include the proper package that will bring in the necessary virtual/egl for the Raspberry Pi 4.

Greg

-----Original Message-----
From: Khem Raj <raj.khem@...>
Sent: Monday, October 4, 2021 14:17
To: Greg Wilson-Lindberg <GWilson@...>;
yocto@...
Subject: Re: [yocto] virtual/egl on Raspberry Pi 4



On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:
Hello list,

I'm working on a Qt supplied boot2qt Yocto build currently based on
Zeus that is running on a Raspberry Pi 4. I recently updated the qt
version to 5.15.6 and Qt changed something in the Yocto configuration
that they are using and now one of the recipes that we use is failing
saying that in needs 'virtual/egl' but that it is not provided by any recipe.

In the searching that I have done I have found that the raspberry pi 4
is particular on which package supplies the virtual/egl but I haven't
seen anything that indicates what I should do to re-enable it.

Can anyone tell me what I need to do to enable the correct driver to
get virtual/egl provided on the Raspberry Pi 4? Or maybe even better,
how I could search through the packages that are enabled on the old
and new Yocto trees so that I can figure out what changed between the
releases and re-enable the virtual/egl.
it should be provided by userland package if you are using closed source
graphics driver.

Best Regards,

Greg Wilson-Lindberg





Re: Meta-raspberrypi - how to configure device tree for MCP251x

Chris Tapp
 

Hi Khem,

There is nothing in /boot once the system has started, but if I mount /dev/mmcblk0p1 I can see a config.txt that includes:

     dtparam=spi=on 
     dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25 
     dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=23 

This is what I could expect.

On a quick scan, this appears to be the same as the one in tmp/deploy/images/raspberrypi4/bootfiles - the timestamp for this file indicated it was old, so I had manually cleaned and rebuilt rpi-bootfiles for changes to RPI_EXTRA_CONFIG to propagate.

However, if I bring the CAN interface up:

ip link set can1 up type can bitrate 100000

and look in /proc/interrupts, I see:

 66:          0          0          0          0  pinctrl-bcm2835  25 Level     spi0.0

even though can1 is on spi0.1.

--

On 4 Oct 2021, at 17:49, Khem Raj <raj.khem@...> wrote:

can you check boot/config.txt and see fi your changes are there in your target ?

On Mon, Oct 4, 2021 at 1:21 AM Chris Tapp <opensource@...> wrote:

Sorry, I meant to add that I have tried adding the following to local.conf:

RPI_EXTRA_CONFIG = ' \n \
   dtparam=spi=on \n \
   dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25 \n \
   dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=23 \n \
   '

However, this did not make any difference to the interrupts.

Since then, I have manually changed mcp2515-can1-overlay.dts in the kernel build tree (after running bitbake - c do_configure virtual/kernel) and rebuilt the kernel / image. This does result in the interrupt mapping changing, and both CAN channels then operate correctly.

Does anyone know why RPI_EXTRA_CONFIG doesn’t appear to be taking effect?

--

Chris Tapp
opensource@...
www.keylevel.com

----
You can tell you're getting older when your car insurance gets real cheap!

On 1 Oct 2021, at 22:38, Chris Tapp <opensource@...> wrote:

I am having trouble getting the Waveshare 2-CH CAN HAT working with an RPI4. Channel 0 does not come up, channel 1 does, but it will only send one message (eventually reporting "write: No buffer space available”) and not receive anything.

Looking at the mcp2515-can0-overlay.dts and mcp2515-can1-overlay.dts device tree files in /tmp/work-shared/raspberrypi4/kernel-source/arch/arm/boot/dts/overlays/, it looks as if the interrupts are not mapped as required for the board.

     DTS               HAT
CAN0  brcm,pins = <25>  PIN23
CAN1  brcm,pins = <25>  PIN25

This doesn’t look right, and seems consistent with the behaviour I am seeing.

I would also like to check the device chip select signals, but I can't see how (if) they are mapped in the dts files.

How can I override these settings when I build the image?

--

Chris Tapp
opensource@...
www.keylevel.com










Re: virtual/egl on Raspberry Pi 4

Khem Raj
 

On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:
Hello list,
I'm working on a Qt supplied boot2qt Yocto build currently based on Zeus that is running on a Raspberry Pi 4. I recently updated the qt version to 5.15.6 and Qt changed something in the Yocto configuration that they are using and now one of the recipes that we use is failing saying that in needs 'virtual/egl' but that it is not provided by any recipe.
In the searching that I have done I have found that the raspberry pi 4 is particular on which package supplies the virtual/egl but I haven't seen anything that indicates what I should do to re-enable it.
Can anyone tell me what I need to do to enable the correct driver to get virtual/egl provided on the Raspberry Pi 4? Or maybe even better, how I could search through the packages that are enabled on the old and new Yocto trees so that I can figure out what changed between the releases and re-enable the virtual/egl.
it should be provided by userland package if you are using closed source graphics driver.

Best Regards,
Greg Wilson-Lindberg


virtual/egl on Raspberry Pi 4

Greg Wilson-Lindberg
 

Hello list,

I'm working on a Qt supplied boot2qt Yocto build currently based on Zeus that is running on a Raspberry Pi 4. I recently updated the qt version to 5.15.6 and Qt changed something in the Yocto configuration that they are using and now one of the recipes that we use is failing saying that in needs 'virtual/egl' but that it is not provided by any recipe.

 

In the searching that I have done I have found that the raspberry pi 4 is particular on which package supplies the virtual/egl but I haven't seen anything that indicates what I should do to re-enable it.

 

Can anyone tell me what I need to do to enable the correct driver to get virtual/egl provided on the Raspberry Pi 4? Or maybe even better, how I could search through the packages that are enabled on the old and new Yocto trees so that I can figure out what changed between the releases and re-enable the virtual/egl.

 

Best Regards,

Greg Wilson-Lindberg

 


Building a native package that includes tools + u-boot binaries

jpdoyon@...
 

I am trying to create a first install package for our device, which would contain an install tool binary, and the required files to install.  In our case, that would be

 

From imx-usb_loader recipe:

imx_usb

imx_usb.conf

mx6_usb_rom.conf

mx6_usb_sdp_spl.conf

 

From u-boot recipe:

u-boot.img

SPL

uEnv.txt

 

The idea would be for the recipe to generate a tarball with all of that  and a script, that would automate the USB download project (the script: “install.sh” is already done, and is obviously out of scope for this question)

 

So I created a new recipe (box1-usb-loader.bb) which depends on both u-boot and imx-usb-loader.  But I can’t seem to get the u-boot target files listed above to appear in my recipe-sysroot directory. 

 

I’ve been scouring the web for a day now, and I’ve found plenty of people asking about seemingly related issues, but nothing that actually gets me nearer.  From what I could find, I’m missing something in my u-boot.bbappend to stage the three files I need, but everything I’ve tried has failed.  The most promising post got me to add this:

 

 

SYSROOT_DIRS += "${D}/boot"

 

do_stage () {

                install -d ${D}/boot

    install -m 0644 ${WORKDIR}/package/boot/u-boot.img ${D}/boot

    install -m 0644 ${WORKDIR}/package/boot/SPL ${D}/boot

    install -m 0644 ${WORKDIR}/package/boot/uEnv.txt ${D}/boot

}

 

sysroot_stage_all_append () {                                    

    sysroot_stage_dir ${D}/boot ${SYSROOT_DESTDIR}/boot

}

 

 

But it didn’t succeed.

 

Thanks for any help you may provide.

 

Sincerely,

 

Jean-Pierre Doyon

2461 - 2480 of 57385