bitbake

Apply and commit a patch from bitbake recipe

孤街浪徒 提交于 2020-07-20 04:19:11
问题 I am observing that the yocto build system is just applying my patch instead of applying and committing the patch on the cloned git repo. Original bitbake ( u-boot-ti-staging_2018.01.bb ) file. require u-boot-ti.inc PR = "r19" BRANCH = "ti-u-boot-2018.01" SRCREV = "8b2f1df4b55bc0797399a21d42ac191d44f99227" Modified bitbake file, added SRC_URI to the file. require u-boot-ti.inc PR = "r19" BRANCH = "ti-u-boot-2018.01" SRCREV = "8b2f1df4b55bc0797399a21d42ac191d44f99227" SRC_URI += "file://0001

How do you properly build gpiod applications from Yocto?

淺唱寂寞╮ 提交于 2020-07-10 07:26:47
问题 I am trying to incorporate a CPLD programming utility on Github available at https://github.com/kontron/altera-stapl into my Yocto build but am getting undefined references to gpiod functions. I have that it depends on libgpiod in my recipe. Am I specifying the dependency correctly? Here is my recipe: SUMMARY = "CPLD STAPL Programming" DESCRIPTION = "A userspace port of the Altera Jam STAPL Bytecode Player." MAINTAINER = "Michael Walle <michael.walle@kontron.com>" HOMEPAGE = "https://github

bitbake: how does the build system choose the recipe provided by more than one layer

蹲街弑〆低调 提交于 2020-07-02 15:54:17
问题 The meta layer provide recipe: meta/recipes-graphics/x11-common/xserver-nodm-init.bb The meta-oe layer provide recipe: meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb My question is: How the build system select the xserver-nodm-init from the multi-layers? Does it select the xserver-nodm-init recipe according to the layers order in conf/bblayers? 回答1: Layer priority ( BBFILE_PRIORITY ) and recipe version number ( PV , often automated from filename) will decide which recipe

bitbake: how does the build system choose the recipe provided by more than one layer

别来无恙 提交于 2020-07-02 15:53:51
问题 The meta layer provide recipe: meta/recipes-graphics/x11-common/xserver-nodm-init.bb The meta-oe layer provide recipe: meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb My question is: How the build system select the xserver-nodm-init from the multi-layers? Does it select the xserver-nodm-init recipe according to the layers order in conf/bblayers? 回答1: Layer priority ( BBFILE_PRIORITY ) and recipe version number ( PV , often automated from filename) will decide which recipe

bitbake: how does the build system choose the recipe provided by more than one layer

梦想的初衷 提交于 2020-07-02 15:52:35
问题 The meta layer provide recipe: meta/recipes-graphics/x11-common/xserver-nodm-init.bb The meta-oe layer provide recipe: meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb My question is: How the build system select the xserver-nodm-init from the multi-layers? Does it select the xserver-nodm-init recipe according to the layers order in conf/bblayers? 回答1: Layer priority ( BBFILE_PRIORITY ) and recipe version number ( PV , often automated from filename) will decide which recipe

PIN muxing in embedded Linux kernel

♀尐吖头ヾ 提交于 2020-06-28 03:57:34
问题 I am using SAMA5D27-SOM1-EK1 Microchip embedded board. I am using Linux kernel 4.14.73 version that I build using Yocto project. That board has a J27 connector that is used as Image Sensor Interface as shown in 4.3.2 Title, page 31 from the board user guide document, besides, Table 4-16. ISC Connector J27 Pin Assignment, page 32 , shows the connector PIN features. This is a link to the board document : SAMA5D27_User_guide My goal is to change some PIN features of this connector, in order to

PIN muxing in embedded Linux kernel

最后都变了- 提交于 2020-06-28 03:57:00
问题 I am using SAMA5D27-SOM1-EK1 Microchip embedded board. I am using Linux kernel 4.14.73 version that I build using Yocto project. That board has a J27 connector that is used as Image Sensor Interface as shown in 4.3.2 Title, page 31 from the board user guide document, besides, Table 4-16. ISC Connector J27 Pin Assignment, page 32 , shows the connector PIN features. This is a link to the board document : SAMA5D27_User_guide My goal is to change some PIN features of this connector, in order to