Re: [yocto] kernel module and drivers missing in final image
On 9/27/19, Maciej Pijanowski wrote: > > On 27.09.2019 14:01, JH wrote: >> Hi, >> >> I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers >> and kernel modules in emmy-w1-driver-sdiosdio are missing in the >> deploy image, any clues why, how to debug it, how to fix it? > It is not clear to me what do you mean by including it in packagegroup.bb > and what stuff are you installing into the image. The packagegroup.bb is the one defined in image FEATURE_PACKAGES, that is usually all package in packagegroup.bb would be included in the image. > If you wish to install all modules which were built, simply add > kernel-modules to your image via IMAGE_INSTALL variable. I added IMAGE_INSTALL += " emmy-w1-driver-sdiosdio" to my image.bb, but did not work unfortunately. Let me clarify it, I can see emmy-w1-driver-sdiosdio and all its kernel modules are in my build directory, but just could not be added to the image. How should I add package to the image? Thank you. - jh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel module and drivers missing in final image
On 9/28/19, JH wrote: > On 9/27/19, Maciej Pijanowski wrote: >> >> On 27.09.2019 14:01, JH wrote: >>> Hi, >>> >>> I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers >>> and kernel modules in emmy-w1-driver-sdiosdio are missing in the >>> deploy image, any clues why, how to debug it, how to fix it? >> It is not clear to me what do you mean by including it in packagegroup.bb >> and what stuff are you installing into the image. > > The packagegroup.bb is the one defined in image FEATURE_PACKAGES, that > is usually all package in packagegroup.bb would be included in the > image. > >> If you wish to install all modules which were built, simply add >> kernel-modules to your image via IMAGE_INSTALL variable. > > I added IMAGE_INSTALL += " emmy-w1-driver-sdiosdio" to my image.bb, > but did not work unfortunately. > > Let me clarify it, I can see emmy-w1-driver-sdiosdio and all its > kernel modules are in my build directory, but just could not be added > to the image. How should I add package to the image? Tried to add IMAGE_INSTALL_append = " emmy-w1-driver-sdiosdio" in local.conf, did not work either :-(. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel module and drivers missing in final image
On 9/28/19, JH wrote: > On 9/28/19, JH wrote: >> On 9/27/19, Maciej Pijanowski wrote: >>> >>> On 27.09.2019 14:01, JH wrote: Hi, I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers and kernel modules in emmy-w1-driver-sdiosdio are missing in the deploy image, any clues why, how to debug it, how to fix it? >>> It is not clear to me what do you mean by including it in >>> packagegroup.bb >>> and what stuff are you installing into the image. >> >> The packagegroup.bb is the one defined in image FEATURE_PACKAGES, that >> is usually all package in packagegroup.bb would be included in the >> image. >> >>> If you wish to install all modules which were built, simply add >>> kernel-modules to your image via IMAGE_INSTALL variable. >> >> I added IMAGE_INSTALL += " emmy-w1-driver-sdiosdio" to my image.bb, >> but did not work unfortunately. >> >> Let me clarify it, I can see emmy-w1-driver-sdiosdio and all its >> kernel modules are in my build directory, but just could not be added >> to the image. How should I add package to the image? > > Tried to add IMAGE_INSTALL_append = " emmy-w1-driver-sdiosdio" in > local.conf, did not work either :-(. Sorry IMAGE_INSTALL_append += " emmy-w1-driver-sdiosdio" did not work either. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel module and drivers missing in final image
On 9/28/19, JH wrote: > On 9/28/19, JH wrote: >> On 9/28/19, JH wrote: >>> On 9/27/19, Maciej Pijanowski wrote: On 27.09.2019 14:01, JH wrote: > Hi, > > I included emmy-w1-driver-sdiosdio in packagegroup.bb, but all drivers > and kernel modules in emmy-w1-driver-sdiosdio are missing in the > deploy image, any clues why, how to debug it, how to fix it? It is not clear to me what do you mean by including it in packagegroup.bb and what stuff are you installing into the image. >>> >>> The packagegroup.bb is the one defined in image FEATURE_PACKAGES, that >>> is usually all package in packagegroup.bb would be included in the >>> image. >>> If you wish to install all modules which were built, simply add kernel-modules to your image via IMAGE_INSTALL variable. >>> >>> I added IMAGE_INSTALL += " emmy-w1-driver-sdiosdio" to my image.bb, >>> but did not work unfortunately. >>> >>> Let me clarify it, I can see emmy-w1-driver-sdiosdio and all its >>> kernel modules are in my build directory, but just could not be added >>> to the image. How should I add package to the image? >> >> Tried to add IMAGE_INSTALL_append = " emmy-w1-driver-sdiosdio" in >> local.conf, did not work either :-(. > > Sorry IMAGE_INSTALL_append += " emmy-w1-driver-sdiosdio" did not work > either. That package emmy-w1-driver-sdiosdio is in a different layer, all packages from my image layer work fine, it is the first time to add packages from another layer, how could make it work? Thank you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] Xilinx/meta-jupyter layer
On 9/27/19 4:12 PM, Chandana Kalluri wrote: Hello all, https://github.com/Xilinx/meta-jupyter is a meta-jupyter layer containing recipes for jupyter notebook. The initial recipes are based of Dmitry Kargin's meta-jupyter layer https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/. This layer has not been updated for a while. The Xilinx/meta-jupyter layer also adds recipes for python3 based notebooks apart from existing python2 based notebooks. This layer has been tested using Yocto thud layer and by running jupyter notebooks on Ultra96 community boards. We would like to maintain Xilinx/meta-jupyter layer actively and welcome contributions to this layer either through pull requests or via patches sent to meta-xilinx mailing list until a mailing list for meta-jupyter is in place. In the next cycle we will deprecate python2 recipes. A question to community, - Would you recommend maintaining this layer separately in the current github.com/Xilinx location or be included under meta- openembedded layers. I suppose a seperate layer since jupyter isn't typically used but I don't have a strong opinion either way. - Would you suggest having a separate mailing list ? Using the Yocto email list would be my preference. That way, I'd keep on eye on Jupyter from time to time whereas if it's a separate list, I likely would not subscribe. I'm assuming that there will be less than few 100 emails per year. ../Randy Thanks, Chandana -- # Randy MacLeod # Wind River Linux -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
