Touchscreen not working if keyboard or mouse plugged in
Greg Wilson-Lindberg
We are building yocto Zeus for the Raspberrypi 4. We are using a touchscreen on the system, and it works just fine. But if a keyboard or mouse is plugged in when the system boots then the touchscreen is disabled.
I am wondering if there is a configuration somewhere that can be set to allow both the touchscreen and an external keyboard at the same time?
I’m sorry if this is the wrong forum to ask this, please point me in the right direction if not.
Regards, Greg Wilson-Lindberg
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Help with Inclusive Language in OpenEmbedded/Yocto Project
Michael Opdenacker
Hi Jon,
On 12/7/21 2:01 AM, Jon Mason wrote: This email is a follow-up from the session held on Friday at the Definitely interested. I had already started contributing to https://wiki.yoctoproject.org/wiki/Inclusive_language. Count me in. Thanks Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Is there any recipe for
#frr
check
toggle quoted messageShow quoted text
https://layers.openembedded.org/layerindex/branch/master/recipes/ if its not there then perhaps no one published it yet.
On Mon, Dec 6, 2021 at 11:24 PM <mousavy.system2005@gmail.com> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: ls command
On Tue, Dec 7, 2021 at 1:45 AM <msabood2014@gmail.com> wrote:
try to see if /bin/ls exists. if its not there then maybe its deleted somehow. best is to flash a new rootfs
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yocto Project Status WW49`21
Stephen Jolley
Current Dev Position: YP 3.5 M1 Next Deadline: 6th Dec. 2021 YP 3.5 M1 build
Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 3.5 Milestone Dates:
Upcoming dot releases:
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: Setting BUILDNAME to a string broke in 3.1.12
Steve Sakoman
On Tue, Dec 7, 2021 at 12:21 AM Henrik Riomar <henrik.riomar@gmail.com> wrote:
I think Richard was suggesting that you add REPRODUCIBLE_TIMESTAMP_ROOTFS to "" to your local.conf. I did so and confirmed that /etc/version now has BUILDNAME for its contents as expected. Richard is correct that the patch was setting REPRODUCIBLE_TIMESTAMP_ROOTFS incidentally. This part of Mark's patch seems to be the cause: -inherit ${@oe.utils.ifelse(d.getVar('BUILD_REPRODUCIBLE_BINARIES') == '1', 'reproducible_build_simple', '')} +inherit reproducible_build_simple And reproducible_build_simple does: BUILD_REPRODUCIBLE_BINARIES = "1" export PYTHONHASHSEED = "0" export PERL_HASH_SEED = "0" export SOURCE_DATE_EPOCH ??= "1520598896" REPRODUCIBLE_TIMESTAMP_ROOTFS ??= "1520598896" So it is now overwriting what you've set in local.conf for BUILD_REPRODUCIBLE_BINARIES. And if you look at your rootfs, you'll probably see that all of the files are dated March 2019. Master branch has restructured the code, but retained this behavior. I'm not sure what the right answer is for dealing with the BUILDNAME issue. Richard and Mark understand the reproducible build code far better than I, perhaps they can offer an opinion on what to do here. Steve
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-rockchip][PATCH] README: Add intstructions to add patch template
Trevor Woerner
On Tue 2021-11-30 @ 06:27:53 PM, Khem Raj wrote:
Signed-off-by: Khem Raj <raj.khem@gmail.com>Applied to meta-rockchip master branch. Thanks!
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Setting BUILDNAME to a string broke in 3.1.12
Henrik Riomar
Hi
On Tue, Dec 7, 2021 at 1:34 AM Richard Purdie <richard.purdie@linuxfoundation.org> wrote: # Perform any additional adjustments needed to make rootf binary reproducibleconfirmed by commenting out the echo above that that "solves the issue", so it's in fact this code that is now wrongfully triggered. / Henrik
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ls command
msabood2014@...
Hi Guys i am new in YOCTO project. i have build images before and the images were included the "ls" and "clear" and all busybox commands. i do not know what happend now the image does not have anymore the "ls" or "clear" and all that commands and also there is a folder named && in the root directory ? What to do ?
Sorry if my question is stupid but i am just a new in Yocto and linux
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to log inside a recipe
#yocto
tomzy
This is not something I do a lot but from what I know, you should be able
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to log inside a recipe
#yocto
SAM
Thanks a lot. That works perfectly, but do you know how to use the log commands inside the recipe? It seems they work inside functions only (`do_install` e.g.)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Is there any recipe for
#frr
SAM
Hi
There is an old discussion regarding this in this link: https://lists.frrouting.org/pipermail/frog/2019-January/000445.html But I can't find any updated one. Is there an updated recipe to build FRR? Thanks
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to log inside a recipe
#yocto
tomzy
Hi To get a value of some variable added in recipe it is best to use bitbake
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How to log inside a recipe
#yocto
SAM
Hi
There is a variable (or what ever it's called) inside a recipe. I want to know its value. I've used `bbnote "something"` but this gives a parse error. How to properly log?
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Help with Inclusive Language in OpenEmbedded/Yocto Project
Jon Mason
This email is a follow-up from the session held on Friday at the
OpenEmbedded Developer's Virtual Meeting (see https://www.openembedded.org/wiki/OEDVM_Nov_2021) The session was not recorded, but the slides can be found at https://docs.google.com/presentation/d/146ueVVTMeA8JI43wqv5kFmdYEygqqmfGH0z1VRL2bDA/edit?usp=sharing The outcome from the discussion was that inclusive language changes are something that we want to accomplish in the kirkstone release timeframe (with an exception for the "master" branch name, which will be handled at a future date). There has already been a pass at collecting the needed changes at https://wiki.yoctoproject.org/wiki/Inclusive_language This is not as simple as a find/replace of offending words. There is a desire for backward compatibility or to provide some kind of "you want X, which is now Y" (which complicates things). The intention of this email is to see who is interested in helping out. Once we know how many people are available and what time frames, we can plan out a roadmap. So, please email me (or respond to this thread publicly) and I'll add you to the list. There will then be a follow-up zoom call in the next week or so to plan out the roadmap. We will document the roadmap and everything else on the YP wiki page above. Questions and comments are welcome, but not interested in debating the necessity or timeframe of this task. It has already been decided. Thanks, Jon
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Setting BUILDNAME to a string broke in 3.1.12
Richard Purdie
On Mon, 2021-12-06 at 14:27 -1000, Steve Sakoman wrote:
On Mon, Dec 6, 2021 at 6:40 AM Henrik Riomar <henrik.riomar@gmail.com> wrote:rootfs-postcommands.bbclass says:After doing a bit of bisecting it appears that this commit is the culprit: # Perform any additional adjustments needed to make rootf binary reproducible rootfs_reproducible () { if [ "${REPRODUCIBLE_TIMESTAMP_ROOTFS}" != "" ]; then # Convert UTC into %4Y%2m%2d%2H%2M%2S sformatted=`date -u -d @${REPRODUCIBLE_TIMESTAMP_ROOTFS} +%4Y%2m%2d%2H%2M%2S` echo $sformatted > ${IMAGE_ROOTFS}/etc/version bbnote "rootfs_reproducible: set /etc/version to $sformatted" if [ -d ${IMAGE_ROOTFS}${sysconfdir}/gconf ]; then find ${IMAGE_ROOTFS}${sysconfdir}/gconf -name '%gconf.xml' -print0 | xargs -0r \ sed -i -e 's@\bmtime="[0-9][0-9]*"@mtime="'${REPRODUCIBLE_TIMESTAMP_ROOTFS}'"@g' fi fi } so I'd try setting REPRODUCIBLE_TIMESTAMP_ROOTFS to "". I suspect the change above started setting that to some value incidentally. Cheers, Richard
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Setting BUILDNAME to a string broke in 3.1.12
Steve Sakoman
On Mon, Dec 6, 2021 at 6:40 AM Henrik Riomar <henrik.riomar@gmail.com> wrote:
After doing a bit of bisecting it appears that this commit is the culprit: reproducible_build: Remove BUILD_REPRODUCIBLE_BINARIES checking https://git.yoctoproject.org/poky/commit/?h=dunfell&id=0d6ebaf8ff3232248ebf0e859cd09aefaee54a8a Since this was cherry-picked from master to fix some reproducibililty errors I suspected that the issue might also exist in the master branch. A quick test with: BUILD_REPRODUCIBLE_BINARIES = "0" BUILDNAME = "my custom name" added to local.conf confirmed that /etc/version was indeed "20180309123456" instead of the expected "my custom name" I'm out of time to work on this today, but perhaps Richard might have some ideas on how to address this. Steve
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
spdx: Extending SPDX SBOMs for SDKs
Andres Beltran
Hello,
I've been working on extending SPDX SBOMs for SDKs. In poky/meta/classes/create-spdx.bbclass I added:
do_populate_sdk[recrdeptask] += "do_create_spdx do_create_runtime_spdx"
I ran into a dependency loop when I try to build an SDK that contains nativesdk-clang (it works fine for other SDKs):
ERROR: Dependency loop #1 found: Task mc:lnx-sdk:/__w/1/s/sources/poky/../meta-clang/recipes-devtools/clang/clang-crosssdk_git.bb:do_create_spdx (dependent Tasks ['glibc_2.31.bb:do_create_spdx', 'binutils-crosssdk_2.34.bb:do_create_spdx', 'clang_git.bb:do_create_spdx', 'quilt-native_0.66.bb:do_populate_sysroot', 'nativesdk-clang-glue.bb:do_create_spdx'])
Task mc:lnx-sdk:virtual:nativesdk:/__w/1/s/sources/poky/../meta-clang/recipes-devtools/clang/clang_git.bb:do_create_spdx (dependent Tasks ['clang_git.bb:do_packagedata', 'cmake-native_3.16.5.bb:do_create_spdx', 'swig_3.0.12.bb:do_create_spdx', 'libedit_20191231-3.1.bb:do_create_spdx', 'binutils-crosssdk_2.34.bb:do_create_spdx', 'chrpath_0.16.bb:do_create_spdx', 'libffi_3.3.bb:do_create_spdx', 'clang-crosssdk_git.bb:do_create_spdx', 'zlib_1.2.11.bb:do_create_spdx', 'clang_git.bb:do_package', 'python3_3.8.2.bb:do_create_spdx', 'libxml2_2.9.10.bb:do_create_spdx', 'python3_3.8.2.bb:do_create_spdx', 'pkgconfig_git.bb:do_create_spdx', 'binutils_2.34.bb:do_create_spdx', 'quilt-native_0.66.bb:do_populate_sysroot', 'libedit_20191231-3.1.bb:do_create_spdx', 'libxml2_2.9.10.bb:do_create_spdx', 'ninja_1.10.0.bb:do_create_spdx'])
Task mc:lnx-sdk:/__w/1/s/sources/poky/../meta-clang/recipes-devtools/clang/nativesdk-clang-glue.bb:do_create_spdx (dependent Tasks ['gcc-runtime_9.3.bb:do_create_spdx', 'glibc_2.31.bb:do_create_spdx', 'nativesdk-clang-glue.bb:do_package', 'gcc-crosssdk_9.3.bb:do_create_spdx', 'chrpath_0.16.bb:do_create_spdx', 'quilt-native_0.66.bb:do_populate_sysroot', 'nativesdk-clang-glue.bb:do_packagedata', 'clang_git.bb:do_create_spdx'])
Any help on this would be appreciated.
Thanks, Andres
Beltran
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enhancements/Bugs closed WW49!
Stephen Jolley
All,
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.5
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|