[yocto] [Yocto] RPI WiFi not loading module

Hi I have problem to get my WiFi working on boot on Raspberry Pi 3. The problem is that wlan0 interface not showing up, if I manually run modprobe brcmfmac it works. To try to "force" the load of brcmfmac i added it to KERNEL_MODULE_AUTOLOAD and that generated an file in /etc/modules-load.d/ ->

Re: [yocto] distrodata documentation in 2.7 Mega Manual

On Thu, 23 May 2019 at 02:22, Scott Rifenbark wrote: > * In dev-manual's "Using the Auto Upgrade Helper (AUH)" section - > https://www.yoctoproject.org/docs/2.7/mega-manual/mega-manual.html#gs-using-the-auto-upgrade-helper: > Step 5 talks about making configurations in the local.conf file. Fir

[yocto] Fwd: /usr/share/common-license package/recipeinfo contains GPLv3 info

Hello team, I am trying to build yocto image without GPLv3 package, I have added below things in local.conf and enable meta-gplv2 layer. INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3. 0" in local.conf. After verifying from package.manifest and license.manifest file in build/tmp/deploy/license/

Re: [yocto] [Yocto] RPI WiFi not loading module

Hi, On Thu, May 23, 2019 at 11:15 AM Jonas Andersson wrote: > > Hi > > I have problem to get my WiFi working on boot on Raspberry Pi 3. for rpi issues I would suggest to open ticket on meta-raspberrypi github with stated which yocto branch and other details. Thanks. > > The problem is that wlan0

Re: [yocto] Building Out-of-Tree Modules on the BBB Target

After some tests (and I had other problems to take care of, as well), here is the following: > These have all been discussed off an on over the past 5 years. > I can't get at bugzilla right now, but all the details are logged in cases. > A survey of all the distros, their kernel package, etc, were

Re: [yocto] Building single package as image, respecting dependencies

On Wed, 22 May 2019 at 14:28, Norman Stetter wrote: > Is there a way to have dependencies between images? So I could have the > python-image build know which dependencies are already built into my OS > image and therefore not include them itself? > No. An image is a self-contained file system.

[yocto] Rocko broke down

I am developing system using raspberry and made a pull on every yocto metas. Chen I baked the Image there was a major problem. My system did not read config.txt and cmdline.txt anymore. So the resulting Image was totally unusable. Lucily I had a copy of yocto tree so I could go on building images.

Re: [yocto] PN is uppercase

Hi Ross, Thanks for your email. I am realising that I have not replied to your email earlier. Sorry. I guess it was partly because your answer put me slightly off. On the one hand, I thought that as a general approach, Linux was case sensitive, unlike its big rival Windows, and I was not aware o

Re: [yocto] Building Out-of-Tree Modules on the BBB Target

On Thu, May 23, 2019 at 6:32 AM Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > After some tests (and I had other problems to take care of, as well), > here is the following: > > > These have all been discussed off an on over the past 5 years. > > I can't get at bugzilla right now, b

Re: [yocto] Building single package as image, respecting dependencies

Hi Ross, thanks for clarifying that there are no dependencies between images. Von: Burton, Ross [mailto:ross.bur...@intel.com] Gesendet: Thursday, May 23, 2019 2:15 PM An: Norman Stetter Cc: yocto@yoctoproject.org Betreff: Re: [yocto] Building single package as image, respecting dependencies O

Re: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95

Hi, I have a question. How to add commands like "ubiattach" to /usr/bin of rootfs image. I struggling with the recipes. I do not want to write my own recipe but I need to edit some recipe and add the command. Which is the place? I am using yocto for my project on TI platform and Linux. Kind

Re: [yocto] Building single package as image, respecting dependencies

On Thu, 23 May 2019 at 13:46, Norman Stetter wrote: > That seems to be a misunderstanding. I want to keep the OS image as small > as possible to reduce boot time. We only use python for some test > scenarios, so it doesn’t have to be included in the OS image. I did some > measurements and includi

[yocto] kernel-devsrc used to be full source - not the case since thud

Hello, This might have been discussed before. I couldn't find a relevant thread, but if it is so, just link me to it. Since thud, more specific since commit 9af0f1a46bbb6ad9ee8b35957251f4aa826b023f Author: Bruce Ashfield Date:   Sat Aug 18 22:50:44 2018 -0400     kernel-devsrc: restructure for

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote: > Hello, > > This might have been discussed before. I couldn't find a relevant > thread, but if it is so, just link me to it. > > Since thud, more specific since > > commit 9af0f1a46bbb6ad9ee8b35957251f4aa826b023f > Author: Bruce Ashfield > D

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield wrote: > > > On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote: > >> Hello, >> >> This might have been discussed before. I couldn't find a relevant >> thread, but if it is so, just link me to it. >> >> Since thud, more specific since >> >> commi

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On 23/05/2019 15.32, Bruce Ashfield wrote: > > > On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan > wrote: > > Hello, > > This might have been discussed before. I couldn't find a relevant > thread, but if it is so, just link me to it. > > Since thud, more sp

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On Thu, May 23, 2019 at 10:39 AM Andrei Gherzan wrote: > On 23/05/2019 15.32, Bruce Ashfield wrote: > > > > On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote: > >> Hello, >> >> This might have been discussed before. I couldn't find a relevant >> thread, but if it is so, just link me to it. >>

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On 23/05/2019 15.39, Bruce Ashfield wrote: > > > On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield > mailto:bruce.ashfi...@gmail.com>> wrote: > > > > On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan > wrote: > > Hello, > > This might have been discuss

[yocto] prelink-cross with -fno-plt

Hi Everyone @ the Yocto project, I'm Shane Peelar, a PhD Candidate at the University of Windsor. I'm writing to you about prelink-cross, as part of the Yocto project. Specifically, I'm looking at using it with executables built using `-fno-plt` under GCC. I wasn't quite sure where to send this ema

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan wrote: > > On 23/05/2019 15.39, Bruce Ashfield wrote: > > > > On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield > wrote: > >> >> >> On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote: >> >>> Hello, >>> >>> This might have been discussed before. I

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On 23/05/2019 16.10, Bruce Ashfield wrote: > > > On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan > wrote: > > > On 23/05/2019 15.39, Bruce Ashfield wrote: >> >> >> On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield >> mailto:bruce.ashfi...@gmail.com>> wrote: >> >

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On Thu, May 23, 2019 at 11:24 AM Andrei Gherzan wrote: > On 23/05/2019 16.10, Bruce Ashfield wrote: > > > > On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan wrote: > >> >> On 23/05/2019 15.39, Bruce Ashfield wrote: >> >> >> >> On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield >> wrote: >> >>> >>>

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On 23/05/2019 17.11, Bruce Ashfield wrote: > > > On Thu, May 23, 2019 at 11:24 AM Andrei Gherzan > wrote: > > On 23/05/2019 16.10, Bruce Ashfield wrote: >> >> >> On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan >> mailto:and...@gherzan.ro>> wrote: >> >> >>

Re: [yocto] kernel-devsrc used to be full source - not the case since thud

On Thu, May 23, 2019 at 12:20 PM Andrei Gherzan wrote: > > On 23/05/2019 17.11, Bruce Ashfield wrote: > > > > On Thu, May 23, 2019 at 11:24 AM Andrei Gherzan wrote: > >> On 23/05/2019 16.10, Bruce Ashfield wrote: >> >> >> >> On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan >> wrote: >> >>> >>> O

Re: [yocto] distrodata documentation in 2.7 Mega Manual

Paul & Alexander, I have updated the YP doc set for the removal of the three classes. Changes apply to the 2.7 and "master" (2.8) trees. You see the effects in: * https://yoctoproject.org/docs/2.7/mega-manual/mega-manual.html * https://yoctoproject.org/docs/2.8/mega-manual/mega-manual.html Th

Re: [yocto] problem adding a user

Greg, It eluded me earlier but in both instances the variable containing the password does not seem to be expanded. First version without the single quotes: SAKURA_PASS = "$1$QVO3K6Ii$fvkoDKnlzz3d5uVoL7KcM0" EXTRA_USERS_PARAMS = "\ usermod -p ${SAKURA_PASS} ${SAKURA_USER}; \ usermod -a

[yocto] [opkg-utils][PATCH] opkg-list-fields: fix to print the fields again

* printing opkg.Package directly doesn't return anything useful now * we need to call Package.print() function and specify which checksums to print, we can include both md5 and sha256 for opkg-list-fields * it was changed in this commit: commit 601d691dd80ef494aef069017edc5bf80aa883a1 Au

Re: [yocto] problem adding a user

Hello Rudolf, Greg, On Thu, 23 May 2019 at 22:43, Rudolf Streif wrote: > > It eluded me earlier but in both instances the variable containing the > password does not seem to be expanded. > Could it be the spaces around the = equal sign must be removed? https://unix.stackexchange.com/questions/

Re: [yocto] Rocko broke down

On 5/18/19 12:56 AM, Ari-Pekka Sihvonen wrote: I am developing system using raspberry and made a pull on every yocto metas. Chen I baked the Image there was a major problem. My system did not read config.txt and cmdline.txt anymore. So the resulting Image was totally unusable. Lucily I had a

Re: [yocto] problem adding a user

Hi Leon & Rudolf, I first changed to SAKURA1_1PASS, with no change in symptoms, I then deleted the spaces, again not change. Next I just copied the hash into the usermod line: usermod -p '$1$QVO3K6Ii$fvkoDKnlzz3d5uVoL7KcM0' ${SAKURA_USER}; \ And again I get nothing in the output just the

Re: [yocto] PN is uppercase

On 5/21/19 12:50 AM, Ralf Spiwoks wrote: Hi Ross, Thanks for your email. I am realising that I have not replied to your email earlier. Sorry. I guess it was partly because your answer put me slightly off. On the one hand, I thought that as a general approach, Linux was case sensitive, unlike i

Re: [yocto] Fwd: /usr/share/common-license package/recipeinfo contains GPLv3 info

On 5/23/19 2:42 AM, virendra kumar thakur wrote: Hello team, I am trying to build yocto image without GPLv3 package, I have added below things in local.conf and enable meta-gplv2 layer. INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3. 0" in local.conf. Can you try adding GPLv3+ to INCOM

Re: [yocto] [Yocto] RPI WiFi not loading module

On 5/23/19 2:14 AM, Jonas Andersson wrote: Hi I have problem to get my WiFi working on boot on Raspberry Pi 3. The problem is that wlan0 interface not showing up, if I manually run modprobe brcmfmac it works. To try to "force" the load of brcmfmac i added it to KERNEL_MODULE_AUTOLOAD and

Re: [yocto] Building Out-of-Tree Modules on the BBB Target

On 5/23/19 3:32 AM, Zoran Stojsavljevic wrote: After some tests (and I had other problems to take care of, as well), here is the following: These have all been discussed off an on over the past 5 years. I can't get at bugzilla right now, but all the details are logged in cases. A survey of a

Re: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95

On 5/23/19 5:59 AM, Tg, Harish wrote: Hi, I have a question. How to add commands like "ubiattach" to /usr/bin of rootfs image. I struggling with the recipes. I do not want to write my own recipe but I need to edit some recipe and add the command. Which is the place? I am using yocto fo

Re: [yocto] prelink-cross with -fno-plt

On 5/23/19 8:05 AM, Shane Peelar wrote: Hi Everyone @ the Yocto project, I'm Shane Peelar, a PhD Candidate at the University of Windsor. I'm writing to you about prelink-cross, as part of the Yocto project. Specifically, I'm looking at using it with executables built using `-fno-plt` under GC

Re: [yocto] problem adding a user

On 5/23/19 1:40 PM, Rudolf Streif wrote: Greg, It eluded me earlier but in both instances the variable containing the password does not seem to be expanded. First version without the single quotes: SAKURA_PASS = "$1$QVO3K6Ii$fvkoDKnlzz3d5uVoL7KcM0" EXTRA_USERS_PARAMS = "\     usermod -p

Re: [yocto] prelink-cross with -fno-plt

Any of them on the system pretty much, and yes they are also built with -fno-plt. On Thu, May 23, 2019 at 9:59 PM Khem Raj wrote: > > > On 5/23/19 8:05 AM, Shane Peelar wrote: > > Hi Everyone @ the Yocto project, > > > > I'm Shane Peelar, a PhD Candidate at the University of Windsor. > > I'm wri

Re: [yocto] prelink-cross with -fno-plt

On 5/23/19 7:53 PM, Shane Peelar wrote: Any of them on the system pretty much, and yes they are also built with -fno-plt. OK, I think its better to them conditionally check for .plt section, can you describe more of whats going on when sections are checked. On Thu, May 23, 2019 at 9:59 PM

Re: [yocto] Building Out-of-Tree Modules on the BBB Target

> I think this is a fair suggestion. Having prebuilt kernel available > that contains the configuration and header files used in the build is > all that is required for external modules to build in addition to > toolchain, so maybe its worth a try to create such a package and then > have kernel-sou

Re: [yocto] PN is uppercase

On Thu, May 23, 2019 at 4:55 PM Khem Raj wrote: > > > On 5/21/19 12:50 AM, Ralf Spiwoks wrote: > > Hi Ross, > > > > Thanks for your email. I am realising that I have not replied to your > > email earlier. Sorry. I guess it was partly because your answer put > > me slightly off. On the one hand, I

Re: [yocto] Building Out-of-Tree Modules on the BBB Target

On 5/23/19 9:14 PM, Zoran Stojsavljevic wrote: > I think this is a fair suggestion. Having prebuilt kernel available > that contains the configuration and header files used in the build is > all that is required for external modules to build in addition to > toolchain, so maybe its worth a

Re: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95

Hi Raj, My ubiattach is separate one which works for our project. Its not part of ubifs package. I need to place that in /usr/bin rootfs image. Also I couldn’t find the place where I need to copy this ubiattach command. You can take this as custom ubiattach command. I could locate l

Re: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95

That could be done by writing a recipe to build and/or package your version. So look how to write a new recipe, if its prebuilt you just might be able to package it using do_install() step in your recipe and then add that package to IMAGE_INSTALL see https://wiki.yoctoproject.org/wiki/Buildin

Re: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95

Please keep the thread on list and avoid pm. as I said you need 1. Write a recipe for your package 2. in do_install of the recipe you want to mention where it should be placed e.g. install -D -m 0755 ${D}${bindir}/ would put it in /usr/bin on target when this package is included in image 3

Re: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95

Hi Raj, What I am asking you is that how the yocto picks up components for /usr/bin folder of rootfs. Where do they exist before copying? I am sorry but I feel I do not need to write a recipe for adding just one of the commands. It is just that I need to add "ubiattach" to target /us

Re: [yocto] Building single package as image, respecting dependencies

For the OS image I use cpio.gz as file system. It gets booted as a RAMdisk. Sorry, forgot to mention that. Building two different images doesn’t suit our use case. We install the image on a device and run different automated test suites on it, some of which need python. But for all of the testi

[yocto] FW: EXT SENDER - yocto Digest, Vol 104, Issue 95

Mailing it to the thread. -Original Message- From: Tg, Harish Sent: Friday, May 24, 2019 11:17 AM To: Khem Raj ; yocto@yoctoproject.org Subject: RE: [yocto] EXT SENDER - yocto Digest, Vol 104, Issue 95 Hi Raj, What I am asking you is that how the yocto picks up components for

Re: [yocto] Fwd: /usr/share/common-license package/recipeinfo contains GPLv3 info

Thank you khem raj for your input, I have already tried with INCOMPATIBLE_LICENSE = "GPLv3+ LGPLv3+ AGPLv3+" And this also INCOMPATIBLE_LICENSE = "GPLv3* LGPLv3* AGPLv3*" But no luck, still I can see same output rootfs/usr/share/common-license/package/libgcrypt-lic/recipeinfo LICENSE: GPLV2+