Re: [linux-yocto] [kernel-cache yocto-5.15] treewide: Drop the obsolete GPIO sysfs ABI
I've staged this on 5.15 and ported it to master (dropped the BSPs that aren't on that branch). It will be part of my next pull request to OE core. Bruce In message: [kernel-cache yocto-5.15] treewide: Drop the obsolete GPIO sysfs ABI on 28/06/2022 Kevin Hao wrote: > From: Kevin Hao > > The GPIO sysfs ABI has been marked as obsolete 6 years ago [1] and has > been scheduled to be removed in 2020. And then it is restricted to be > only available to expert users by commit [2]. This restriction triggers > config warning on several BSPs due to the CONFIG_EXPERT is not enabled. > Of course we can fix these warning by enabling the CONFIG_EXPERT, > but maybe it is the time to drop this obsolete option. > > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b > [2] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b4feb21158f8 > > Signed-off-by: Kevin Hao > --- > bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg | 1 - > bsp/hsdk/hsdk.cfg | 1 - > bsp/intel-socfpga/intel-socfpga-64.cfg | 1 - > bsp/intel-x86/intel-x86.cfg| 1 - > bsp/minnow/minnow.cfg | 1 - > bsp/nxp-imx6/nxp-imx6.cfg | 2 -- > bsp/nxp-imx8/nxp-imx8.cfg | 1 - > bsp/renesas-rcar/renesas-rcar.cfg | 1 - > bsp/ti-am335x/ti-am335x.cfg| 1 - > bsp/ti-j72xx/ti-j72xx.cfg | 1 - > bsp/xilinx/soc/drivers-softip.cfg | 1 - > bsp/xilinx/soc/drivers-zynq.cfg| 1 - > features/minnow-io/minnow-io.cfg | 1 - > features/soc/baytrail/baytrail.cfg | 1 - > features/soc/broxton/broxton.cfg | 1 - > 15 files changed, 16 deletions(-) > > diff --git a/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg > b/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg > index 82a28a4e8fe2..1bd56a058399 100644 > --- a/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg > +++ b/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg > @@ -255,7 +255,6 @@ CONFIG_SND_SOC_WM8960=m > # GPIO Support > CONFIG_MFD_CORE=y > CONFIG_MFD_STMPE=y > -CONFIG_GPIO_SYSFS=y > CONFIG_GPIO_BCM_VIRT=y > CONFIG_MFD_ARIZONA_I2C=m > CONFIG_GPIO_ARIZONA=m > diff --git a/bsp/hsdk/hsdk.cfg b/bsp/hsdk/hsdk.cfg > index 1d75fb929456..38e97fd978fd 100644 > --- a/bsp/hsdk/hsdk.cfg > +++ b/bsp/hsdk/hsdk.cfg > @@ -42,7 +42,6 @@ CONFIG_MICREL_PHY=y > > # GPIO > CONFIG_GPIOLIB=y > -CONFIG_GPIO_SYSFS=y > CONFIG_GPIO_DWAPB=y > > # Video > diff --git a/bsp/intel-socfpga/intel-socfpga-64.cfg > b/bsp/intel-socfpga/intel-socfpga-64.cfg > index 4cfd894fcf95..2fa2405544f6 100644 > --- a/bsp/intel-socfpga/intel-socfpga-64.cfg > +++ b/bsp/intel-socfpga/intel-socfpga-64.cfg > @@ -84,7 +84,6 @@ CONFIG_SERIAL_8250_DW=y > CONFIG_SERIAL_OF_PLATFORM=y > > CONFIG_GPIOLIB=y > -CONFIG_GPIO_SYSFS=y > CONFIG_GPIO_DWAPB=y > CONFIG_GPIO_ALTERA=y > > diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg > index 6b5d10463e4e..af528c39a8b4 100644 > --- a/bsp/intel-x86/intel-x86.cfg > +++ b/bsp/intel-x86/intel-x86.cfg > @@ -72,7 +72,6 @@ CONFIG_LPC_SCH=m > # GPIO drivers > # > CONFIG_GPIOLIB=y > -CONFIG_GPIO_SYSFS=y > CONFIG_GPIO_SCH=m > CONFIG_GPIO_ICH=m > CONFIG_GPIO_GENERIC_PLATFORM=m > diff --git a/bsp/minnow/minnow.cfg b/bsp/minnow/minnow.cfg > index 89a86e6df679..06d715f9cfa8 100644 > --- a/bsp/minnow/minnow.cfg > +++ b/bsp/minnow/minnow.cfg > @@ -48,7 +48,6 @@ CONFIG_SERIAL_PCH_UART_CONSOLE=y > ### Non-essential on-board features ### > > # GPIO Support > -CONFIG_GPIO_SYSFS=y > CONFIG_GPIOLIB=y > > CONFIG_GPIO_GENERIC=y > diff --git a/bsp/nxp-imx6/nxp-imx6.cfg b/bsp/nxp-imx6/nxp-imx6.cfg > index 3820031652c0..4a6382a6c17b 100644 > --- a/bsp/nxp-imx6/nxp-imx6.cfg > +++ b/bsp/nxp-imx6/nxp-imx6.cfg > @@ -84,8 +84,6 @@ CONFIG_SPI=y > CONFIG_SPI_IMX=y > CONFIG_SPI_GPIO=y > > -CONFIG_GPIO_SYSFS=y > - > CONFIG_POWER_SUPPLY=y > CONFIG_WATCHDOG=y > CONFIG_IMX2_WDT=y > diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg > index 2b31fc1567ba..775f7ed211ae 100644 > --- a/bsp/nxp-imx8/nxp-imx8.cfg > +++ b/bsp/nxp-imx8/nxp-imx8.cfg > @@ -129,7 +129,6 @@ CONFIG_PINCTRL=y > CONFIG_PINCTRL_IMX8QM=y > CONFIG_PINCTRL_IMX8MQ=y > CONFIG_GPIOLIB=y > -CONFIG_GPIO_SYSFS=y > CONFIG_GPIO_MAX732X=y > CONFIG_GPIO_PCA953X=y > CONFIG_GPIO_PCA953X_IRQ=y > diff --git a/bsp/renesas-rcar/renesas-rcar.cfg > b/bsp/renesas-rcar/renesas-rcar.cfg > index 9d5461a22940..9da5849c86cb 100644 > --- a/bsp/renesas-rcar/renesas-rcar.cfg > +++ b/bsp/renesas-rcar/renesas-rcar.cfg > @@ -155,7 +155,6 @@ CONFIG_VIDEO_ADV7604_CEC=y > # GPIO configuration > CONFIG_GPIOLIB=y > CONFIG_OF_GPIO=y > -CONFIG_GPIO_SYSFS=y > CONFIG_GPIO_RCAR=y > CONFIG_GPIO_PCA953X=y > CONFIG_GPIO_PCA953X_IRQ=y > diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg > index d5b9ee632185..bdf54c5d171e 100644 > --- a/bsp/ti-am335x/ti-am335x.cfg > +++ b/bsp/ti-am335x/ti-am335x.cfg > @@ -135,7 +135,6 @@ CONFIG_PINCTRL_SINGLE=y > CONFIG_GPIOLIB=y > CONFIG_OF_GPIO=y >
Re: [linux-yocto][linux-yocto v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc & v5.15/standard/nxp-sdk-5.15/nxp-soc][PATCH 1/1] crypto: caam: fix a build error 'needs_entropy_delay_adjustment' undefine
Sorry the delay, this was filtered by gmail and I didn't
see it!
This is now merged.
Bruce
In message: [linux-yocto][linux-yocto
v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc &
v5.15/standard/nxp-sdk-5.15/nxp-soc][PATCH 1/1] crypto: caam: fix a build error
'needs_entropy_delay_adjustment' undefined
on 29/06/2022 Xiaolei Wang wrote:
> Fix commit f816aa7947c7 merge conflict, refer to
> commit dd36037d4ae7 ("crypto: CAAM - fix i.mx6sx
> entry delay value"), needs_ entropy_ delay_ Adjustment
> function is referenced for this reason.
>
> Signed-off-by: Xiaolei Wang
> ---
> drivers/crypto/caam/ctrl.c | 25 ++---
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/crypto/caam/ctrl.c b/drivers/crypto/caam/ctrl.c
> index 6cd43ddb403b..37e01b0faf38 100644
> --- a/drivers/crypto/caam/ctrl.c
> +++ b/drivers/crypto/caam/ctrl.c
> @@ -612,6 +612,13 @@ static void caam_dma_dev_unregister(void *data)
> platform_device_unregister(data);
> }
>
> +static bool needs_entropy_delay_adjustment(void)
> +{
> +if (of_machine_is_compatible("fsl,imx6sx"))
> +return true;
> +return false;
> +}
> +
> static int caam_ctrl_rng_init(struct device *dev)
> {
> struct caam_drv_private *ctrlpriv = dev_get_drvdata(dev);
> @@ -666,6 +673,8 @@ static int caam_ctrl_rng_init(struct device *dev)
>* Also, if a handle was instantiated, do not change
>* the TRNG parameters.
>*/
> + if (needs_entropy_delay_adjustment())
> + ent_delay = 12000;
> if (!(ctrlpriv->rng4_sh_init || inst_handles)) {
> dev_info(dev,
>"Entropy delay = %u\n",
> @@ -682,6 +691,15 @@ static int caam_ctrl_rng_init(struct device *dev)
>*/
> ret = instantiate_rng(dev, inst_handles,
> gen_sk);
> + /*
> + * Entropy delay is determined via TRNG
> characterization.
> + * TRNG characterization is run across different
> voltages
> + * and temperatures.
> + * If worst case value for ent_dly is identified,
> + * the loop can be skipped for that platform.
> + */
> +if (needs_entropy_delay_adjustment())
> +break;
> if (ret == -EAGAIN)
> /*
>* if here, the loop will rerun,
> @@ -835,13 +853,6 @@ static bool check_version(struct fsl_mc_version
> *mc_version, u32 major,
> }
> #endif
>
> -static bool needs_entropy_delay_adjustment(void)
> -{
> - if (of_machine_is_compatible("fsl,imx6sx"))
> - return true;
> - return false;
> -}
> -
> /* Probe routine for CAAM top (controller) level */
> static int caam_probe(struct platform_device *pdev)
> {
> --
> 2.25.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11420):
https://lists.yoctoproject.org/g/linux-yocto/message/11420
Mute This Topic: https://lists.yoctoproject.org/mt/92059875/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto
I believe I have solved the issue. the key for me was needing to pass the
`--sysroot` flag to TARGET_*FLAGS variables since the sysroot flag being passed
to CC/CPP/CXX variables were being replaced during compilation for some reason.
Also including `--prefix=${RECIPE_SYSROOT}${prefix}` in the EXTRA_OECONF
variable ensured the appropriate include/lib paths were accessible. I think
this was a strange project because some of the other autoconf projects "just
worked".
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57425): https://lists.yoctoproject.org/g/yocto/message/57425
Mute This Topic: https://lists.yoctoproject.org/mt/91929966/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #make:https://lists.yoctoproject.org/g/yocto/mutehashtag/make
Mute #honister:https://lists.yoctoproject.org/g/yocto/mutehashtag/honister
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder2][PATCH] config.py: define workers for kirkstone
Signed-off-by: Steve Sakoman
---
config.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/config.py b/config.py
index c3c21f1..00f7e70 100644
--- a/config.py
+++ b/config.py
@@ -152,6 +152,7 @@ all_workers = workers + workers_bringup + workers_buildperf
+ workers_arm
# Worker filtering for older releases
workers_prev_releases = {
+"kirkstone" : ("alma8", "centos7", "centos8", "debian8", "debian9",
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32",
"fedora33", "fedora34", "fedora35", "opensuse150", "opensuse151",
"opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", "ubuntu1904",
"ubuntu2004", "ubuntu2110", "ubuntu2204", "perf-"),
"honister" : ("alma8", "centos7", "centos8", "debian8", "debian9",
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32",
"fedora33", "fedora34", "fedora35", "opensuse150", "opensuse151",
"opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", "ubuntu1904",
"ubuntu2004", "ubuntu2110", "ubuntu2204", "perf-"),
"hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10",
"debian11", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse152",
"ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"),
"gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10",
"fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151",
"opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57424): https://lists.yoctoproject.org/g/yocto/message/57424
Mute This Topic: https://lists.yoctoproject.org/mt/92065697/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto
Not sure how i missed this but the `--sysroot` is wrong. somehow its pulling the sysroot for a different package. it should be `--sysroot=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ *opal/3.18-beta9-r0* ` -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57423): https://lists.yoctoproject.org/g/yocto/message/57423 Mute This Topic: https://lists.yoctoproject.org/mt/91929966/21656 Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Mute #make:https://lists.yoctoproject.org/g/yocto/mutehashtag/make Mute #honister:https://lists.yoctoproject.org/g/yocto/mutehashtag/honister Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto
here is the same output using `--trace` with the LD snippet --- echo [ LD] lib_linux_aarch64/libopal.so.3.18-beta9 ; aarch64-linaro-linux-g++ -mcpu=cortex-a53 -march=armv8-a+crc --sysroot=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0/recipe-sysroot -o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/libopal.so.3.18-beta9 -shared -Wl,--build-id,-soname,libopal.so.3.18-beta9 -O2 -gdwarf-4 -O2 -rdynamic -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -fmacro-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0=/usr/src/debug/ptlib/2.18-beta9-r0 -fdebug-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0=/usr/src/debug/ptlib/2.18-beta9-r0 -fdebug-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0/recipe-sysroot= -fdebug-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0/recipe-sysroot-native= -rdynamic -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/lib -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/lib -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/lib/aarch64-linaro-linux/10.3.1 -O2 -rdynamic -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -fmacro-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0=/usr/src/debug/ptlib/2.18-beta9-r0 -fdebug-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0=/usr/src/debug/ptlib/2.18-beta9-r0 -fdebug-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0/recipe-sysroot= -fdebug-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/ptlib/2.18-beta9-r0/recipe-sysroot-native= -rdynamic -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/lib -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/lib -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/lib/aarch64-linaro-linux/10.3.1 -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/lib -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/lib -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/lib/aarch64-linaro-linux/10.3.1 /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/manager.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/endpoint.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/connection.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/call.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/mediafmt.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/mediatype.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/mediasession.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/mediastrm.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/patch.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/transcoders.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/transports.o /home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git/lib_linux_aarch64/obj/guid.o
Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.2.rc1)
On Wed, Jun 29, 2022 at 2:43 AM Richard Purdie wrote: > > On Wed, 2022-06-29 at 11:47 +, Pokybuild User wrote: > > A build flagged for QA (yocto-4.0.2.rc1) was completed on the autobuilder > > and is available at: > > > > > > https://autobuilder.yocto.io/pub/releases/yocto-4.0.2.rc1 > > > > > > Build hash information: > > > > bitbake: b8fd6f5d9959d27176ea016c249cf6d35ac8ba03 > > meta-agl: c4cc627f4d65da8c3b0860c791d9b9687ba8f5d6 > > meta-arm: af928569b421431347c84f5941cee7aaa9f0ac74 > > meta-aws: 8b8eec4bde3b1ff00783503bd77b3a5fb7d904ec > > meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a > > meta-intel: ef3aa3064b9bbfa19f600eafb1e7d3473f62af74 > > meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1 > > meta-openembedded: fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7 > > meta-virtualization: 320f44c6e9af463a85b58e0d87ca70273c6b87f6 > > oecore: eea52e0c3d24c79464f4afdbc3c397e1cb982231 > > poky: a5ea426b1da472fc8549459fff3c1b8c6e02f4b5 > > > > There were two failures in the build on the autobuilder, both are due > to known scp issues with fedora36. I thought we hadn't enabled > kirkstone on f36 but evidently we have :/. I think I see the issue - we never did an entry for kirkstone in workers_prev_releases, so the autobuilder is not restricting workers at all! I'll send a patch. Steve > I don't believe the two issues should block 4.0.2 testing or release. > > Cheers, > > Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57421): https://lists.yoctoproject.org/g/yocto/message/57421 Mute This Topic: https://lists.yoctoproject.org/mt/92063793/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto
DEBUG: Executing python function autotools_aclocals DEBUG: SITE files ['endian-little', 'bit-64', 'arm-common', 'arm-64', 'common-linux', 'common-glibc', 'aarch64-linux', 'common'] DEBUG: Python function autotools_aclocals finished DEBUG: Executing shell function do_compile NOTE: make -j 8 make[1]: Entering directory '/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/git' [DEP] src/h224/h281.cxx [DEP] src/t38/t38proto.cxx [DEP] src/h224/h224.cxx [DEP] src/asn/t38.cxx [DEP] src/h224/q922.cxx [DEP] src/codec/echocancel.cxx [DEP] src/codec/g711a1_plc.cxx [DEP] src/codec/opalpluginmgr.cxx [DEP] src/codec/opalwavfile.cxx [DEP] src/codec/silencedetect.cxx [DEP] src/codec/rfc2833.cxx [DEP] src/t38/t38mf.cxx [DEP] src/codec/opusmf.cxx [DEP] src/codec/speexmf.cxx [DEP] src/codec/iLBCmf.cxx [DEP] src/codec/gsmamrmf.cxx [DEP] src/codec/gsm0610mf.cxx [DEP] src/codec/g729mf.cxx [DEP] src/codec/g728mf.cxx [DEP] src/codec/g726mf.cxx [DEP] src/codec/g7231mf.cxx [DEP] src/codec/g7222mf.cxx [DEP] src/codec/g7221mf.cxx [DEP] src/codec/g722mf.cxx [DEP] src/codec/g711.c [DEP] src/codec/g711codec.cxx [DEP] src/im/sipim.cxx [DEP] src/im/msrp.cxx [DEP] src/im/rfc4103.cxx [DEP] src/im/im_mf.cxx [DEP] src/im/t140.cxx [DEP] src/rtp/dtls_srtp_session.cpp [DEP] src/rtp/srtp_session.cxx [DEP] src/lids/lidpluginmgr.cxx [DEP] src/lids/lidep.cxx [DEP] src/lids/lid.cxx [DEP] src/ep/skinnyep.cxx [DEP] src/sip/sippres.cxx [DEP] src/sip/handlers.cxx [DEP] src/sip/sippdu.cxx [DEP] src/sip/sipcon.cxx [DEP] src/sip/sipep.cxx [DEP] src/t38/sipt38.cxx [DEP] src/sdp/ice.cxx [DEP] src/sdp/sdp.cxx [DEP] src/sdp/sdphttpep.cxx [DEP] src/sdp/sdpep.cxx [DEP] src/iax2/transmit.cxx [DEP] src/iax2/specialprocessor.cxx [DEP] src/iax2/sound.cxx [DEP] src/iax2/safestrings.cxx [DEP] src/iax2/remote.cxx [DEP] src/iax2/regprocessor.cxx [DEP] src/iax2/receiver.cxx [DEP] src/iax2/processor.cxx [DEP] src/iax2/ies.cxx [DEP] src/iax2/iedata.cxx [DEP] src/iax2/iax2medstrm.cxx [DEP] src/iax2/iax2ep.cxx [DEP] src/iax2/iax2con.cxx [DEP] src/iax2/frame.cxx [DEP] src/iax2/callprocessor.cxx [DEP] src/rtp/h235_session.cxx [DEP] src/h323/h235dh.cxx [DEP] src/h224/h323h224.cxx [DEP] src/t38/h323t38.cxx [DEP] src/h323/h235auth1.cxx [DEP] src/h460/h460_std24.cxx [DEP] src/h460/h460_std23.cxx [DEP] src/h460/h460_std19.cxx [DEP] src/h460/h460_std18.cxx [DEP] src/h460/h46024b.cxx [DEP] src/h460/h460tm.cxx [DEP] src/h460/h460pres.cxx [DEP] src/h460/h460p.cxx [DEP] src/h460/h4609.cxx [DEP] src/h460/h46019.cxx [DEP] src/h460/h46018.cxx [DEP] src/h460/h4601.cxx [DEP] src/h323/peclient.cxx [DEP] src/h323/h323annexg.cxx [DEP] src/h323/h501pdu.cxx [DEP] src/h323/h235auth.cxx [DEP] src/h323/h323trans.cxx [DEP] src/h323/h225ras.cxx [DEP] src/h323/gkserver.cxx [DEP] src/h323/gkclient.cxx [DEP] src/h323/transaddr.cxx [DEP] src/h323/q931.cxx [DEP] src/h323/svcctrl.cxx [DEP] src/h323/channels.cxx [DEP] src/h323/h323rtp.cxx [DEP] src/h323/h323pdu.cxx [DEP] src/h323/h323neg.cxx [DEP] src/h323/h323caps.cxx [DEP] src/h323/h323.cxx [DEP] src/h323/h323ep.cxx [DEP] src/asn/h501.cxx [DEP] src/asn/h248.cxx [DEP] src/asn/h245_3.cxx [DEP] src/asn/h245_2.cxx [DEP] src/asn/h245_1.cxx [DEP] src/asn/h235_srtp.cxx [DEP] src/asn/h235.cxx [DEP] src/asn/h225_2.cxx [DEP] src/asn/h225_1.cxx [DEP] src/asn/h45011.cxx [DEP] src/asn/h45010.cxx [DEP] src/asn/h4509.cxx [DEP] src/asn/h4508.cxx [DEP] src/asn/h4507.cxx [DEP] src/asn/h4506.cxx [DEP] src/asn/h4505.cxx [DEP] src/asn/h4504.cxx [DEP] src/asn/h4503.cxx [DEP] src/asn/h4502.cxx [DEP] src/asn/h4501.cxx [DEP] src/asn/gcc.cxx [DEP] src/asn/mcs.cxx [DEP] src/asn/x880.cxx [DEP] src/h323/h450pdu.cxx [DEP] src/ep/pcss.cxx [DEP] src/ep/opalmixer.cxx [DEP] src/opal/recording.cxx [DEP] src/opal/console_mgr.cxx [DEP] src/opal/pres_ent.cxx [DEP] src/opal/opal_c.cxx [DEP] src/ep/sockep.cxx [DEP] src/ep/localep.cxx [DEP] src/rtp/rtpconn.cxx [DEP] src/rtp/rtpep.cxx [DEP] src/rtp/pcapfile.cxx [DEP] src/rtp/metrics.cxx [DEP] src/rtp/jitter.cxx [DEP] src/rtp/rtp_fec.cxx [DEP] src/rtp/rtp_stream.cxx [DEP] src/rtp/rtp_session.cxx [DEP] src/rtp/rtp.cxx [DEP] src/opal/guid.cxx [DEP] src/opal/transports.cxx [DEP] src/opal/transcoders.cxx [DEP] src/opal/patch.cxx [DEP] src/opal/mediastrm.cxx [DEP] src/opal/mediasession.cxx [DEP] src/opal/mediatype.cxx [DEP] src/opal/mediafmt.cxx [DEP] src/opal/call.cxx [DEP] src/opal/connection.cxx [DEP] src/opal/endpoint.cxx [DEP] src/opal/manager.cxx [CXX] src/opal/manager.cxx [CXX] src/opal/endpoint.cxx [CXX] src/opal/connection.cxx [CXX] src/opal/call.cxx [CXX] src/opal/mediafmt.cxx [CXX] src/opal/mediatype.cxx [CXX] src/opal/mediasession.cxx [CXX] src/opal/mediastrm.cxx [CXX] src/opal/patch.cxx [CXX] src/opal/transcoders.cxx [CXX] src/opal/transports.cxx [CXX] src/opal/guid.cxx [CXX] src/rtp/rtp.cxx [CXX] src/rtp/rtp_session.cxx [CXX] src/rtp/rtp_stream.cxx [CXX] src/rtp/rtp_fec.cxx [CXX] src/rtp/jitter.cxx [CXX] src/rtp/metrics.cxx [CXX] src/rtp/pcapfile.cxx [CXX] src/rtp/rtpep.cxx [CXX]
Re: [yocto] LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto
Post log.do_complile perhaps that will have the needed link line
On Tue, Jun 28, 2022 at 5:23 PM wrote:
> #!/bin/sh
>
> __BITBAKE_LAST_LINE=0
>
> # Emit a useful diagnostic if something fails:
> bb_sh_exit_handler() {
> ret=$?
> if [ "$ret" != 0 ]; then
> echo "WARNING: exit code $ret from a shell command."
> fi
> exit $ret
> }
>
> bb_bash_exit_handler() {
> ret=$?
> { set +x; } > /dev/null
> trap "" DEBUG
> if [ "$ret" != 0 ]; then
> echo "WARNING: ${BASH_SOURCE[0]}:${__BITBAKE_LAST_LINE} exit $ret
> from '$1'"
>
> echo "WARNING: Backtrace (BB generated script): "
> for i in $(seq 1 $((${#FUNCNAME[@]} - 1))); do
> if [ "$i" -eq 1 ]; then
> echo -e " #$((i)): ${FUNCNAME[$i]},
> ${BASH_SOURCE[$((i-1))]}, line ${__BITBAKE_LAST_LINE}"
> else
> echo -e " #$((i)): ${FUNCNAME[$i]},
> ${BASH_SOURCE[$((i-1))]}, line ${BASH_LINENO[$((i-1))]}"
> fi
> done
> fi
> exit $ret
> }
>
> bb_bash_debug_handler() {
> local line=${BASH_LINENO[0]}
> # For some reason the DEBUG trap trips with lineno=1 when scripts
> exit; ignore it
> if [ "$line" -eq 1 ]; then
> return
> fi
>
> # Track the line number of commands as they execute. This is so we can
> have access to the failing line number
> # in the EXIT trap. See
> http://gnu-bash.2382.n7.nabble.com/trap-echo-quot-trap-exit-on-LINENO-quot-EXIT-gt-wrong-linenumber-td3666.html
> if [ "${FUNCNAME[1]}" != "bb_bash_exit_handler" ]; then
> __BITBAKE_LAST_LINE=$line
> fi
> }
>
> case $BASH_VERSION in
> "") trap 'bb_sh_exit_handler' 0
> set -e
> ;;
> *) trap 'bb_bash_exit_handler "$BASH_COMMAND"' 0
> trap '{ bb_bash_debug_handler; } 2>/dev/null' DEBUG
> set -e
> shopt -s extdebug
> ;;
> esac
> export AR="aarch64-linaro-linux-gcc-ar"
> export AS="aarch64-linaro-linux-as "
> export BUILD_AR="ar"
> export BUILD_AS="as "
> export BUILD_CC="gcc "
> export BUILD_CCLD="gcc "
> export
> BUILD_CFLAGS="-isystem/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/usr/include
> -O2 -pipe"
> export BUILD_CPP="gcc -E"
> export
> BUILD_CPPFLAGS="-isystem/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/usr/include"
> export BUILD_CXX="g++ "
> export
> BUILD_CXXFLAGS="-isystem/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/usr/include
> -O2 -pipe"
> export BUILD_FC="gfortran "
> export BUILD_LD="ld "
> export
> BUILD_LDFLAGS="-L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/usr/lib
>
>
> -L/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/lib
>-Wl,--enable-new-dtags
>
> -Wl,-rpath-link,/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/usr/lib
>
>
> -Wl,-rpath-link,/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/lib
>
>
> -Wl,-rpath,/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/usr/lib
>
>
> -Wl,-rpath,/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot-native/lib
>-Wl,-O1"
> export BUILD_NM="nm"
> export BUILD_RANLIB="ranlib"
> export BUILD_STRIP="strip"
> export CC="aarch64-linaro-linux-gcc -mcpu=cortex-a53 -march=armv8-a+crc
> --sysroot=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot"
> export CCLD="aarch64-linaro-linux-gcc -mcpu=cortex-a53 -march=armv8-a+crc
> --sysroot=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot"
> export CC_FOR_BUILD="gcc "
> export CFLAGS="-D__ARMEL__
>
> -I/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/include/c++/10.3.1
>
>
> -I/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/include/c++/10.3.1/aarch64-linaro-linux
>
>
> -I/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0/recipe-sysroot/usr/include
> -O2 -pipe -g -feliminate-unused-debug-types
> -fmacro-prefix-map=/home/vagrant/oe_qcom_honister/build-cdil/tmp-cdil-glibc/work/cortexa53-linaro-linux/opal/3.18-beta9-r0=/usr/src/debug/opal/3.18-beta9-r0
>
>
Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.2.rc1)
On Wed, 2022-06-29 at 11:47 +, Pokybuild User wrote: > A build flagged for QA (yocto-4.0.2.rc1) was completed on the autobuilder and > is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-4.0.2.rc1 > > > Build hash information: > > bitbake: b8fd6f5d9959d27176ea016c249cf6d35ac8ba03 > meta-agl: c4cc627f4d65da8c3b0860c791d9b9687ba8f5d6 > meta-arm: af928569b421431347c84f5941cee7aaa9f0ac74 > meta-aws: 8b8eec4bde3b1ff00783503bd77b3a5fb7d904ec > meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a > meta-intel: ef3aa3064b9bbfa19f600eafb1e7d3473f62af74 > meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1 > meta-openembedded: fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7 > meta-virtualization: 320f44c6e9af463a85b58e0d87ca70273c6b87f6 > oecore: eea52e0c3d24c79464f4afdbc3c397e1cb982231 > poky: a5ea426b1da472fc8549459fff3c1b8c6e02f4b5 > There were two failures in the build on the autobuilder, both are due to known scp issues with fedora36. I thought we hadn't enabled kirkstone on f36 but evidently we have :/. I don't believe the two issues should block 4.0.2 testing or release. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57418): https://lists.yoctoproject.org/g/yocto/message/57418 Mute This Topic: https://lists.yoctoproject.org/mt/92063793/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] QA notification for completed autobuilder build (yocto-4.0.2.rc1)
A build flagged for QA (yocto-4.0.2.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.0.2.rc1 Build hash information: bitbake: b8fd6f5d9959d27176ea016c249cf6d35ac8ba03 meta-agl: c4cc627f4d65da8c3b0860c791d9b9687ba8f5d6 meta-arm: af928569b421431347c84f5941cee7aaa9f0ac74 meta-aws: 8b8eec4bde3b1ff00783503bd77b3a5fb7d904ec meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a meta-intel: ef3aa3064b9bbfa19f600eafb1e7d3473f62af74 meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1 meta-openembedded: fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7 meta-virtualization: 320f44c6e9af463a85b58e0d87ca70273c6b87f6 oecore: eea52e0c3d24c79464f4afdbc3c397e1cb982231 poky: a5ea426b1da472fc8549459fff3c1b8c6e02f4b5 This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57417): https://lists.yoctoproject.org/g/yocto/message/57417 Mute This Topic: https://lists.yoctoproject.org/mt/92063017/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Regression in rust-cross-canadian-aarch64
On 2022-06-28 17:54, Randy MacLeod wrote:
On 2022-06-28 07:38, Richard Purdie wrote:
On Tue, 2022-06-28 at 11:00 +0200, Peter Bergin wrote:
When building rust-cross-canadian-aarch64 the file
'tmp/work/x86_64-nativesdk-pokysdk-linux/rust-cross-canadian-aarch64/1.60.0-r0/targets/aarch64-poky-linux.json'
will be populated with the information '"llvm-target":
"x86_64-unknown-linux-gnu"'. This will lead to object files in wrong
format during 'Building stage2 std artifacts (x86_64-unknown-linux-gnu
-> aarch64-poky-linux)' in the do_compile step.
In 'meta/recipes-devtools/rust/rust-common.inc':
# build tspec
tspec = {}
if bb.data.inherits_class('cross-canadian', d):
tspec['llvm-target'] = d.getVar('RUST_HOST_SYS', arch_abi)
else:
tspec['llvm-target'] = d.getVar('RUST_TARGET_SYS', arch_abi)
So for some reason it seems intentional to set 'llvm-target' to
HOST_SYS
when 'cross-canadian'. The behavior has changed with this patch. Before
'llvm-target' was set to RUST_TARGET_SYS for all target archs other
than
x86_64 where it was set to RUST_HOST_SYS. I guess this change has to do
with the commit message 'This might even help cross-canadian work on
something which isn't x86-64.'? But unfortunately it seems to break the
case building on x86_64 for aarch64. It would be good to get some help
here to sort this out.
I've spent an age staring at this code this morning. I don't think
cross-canadian has ever worked properly. It might happen that some
combinations build but there are also some that don't and clearly never
have.
SDKMACHINE = "aarch64", MACHINE = "qemuarm64" certainly doesn't work.
It appears to be missing a ninja-native dependency and when that is
added, it can't find rust-llvm.
Looking at the do_configure from rust.inc, it considers BUILD triplets
and TARGET triplets but not HOST ones, which probably dooms cross-
canadian to failure since there, BUILD != HOST != TARGET.
Someone is going to have to step up and sort out the canadian cross
rust pieces properly. Whilst my patch probably did regress one config,
I think there are much deeper issues in there.
Sundeep and/or Naveen please take a look.
Peter,
Please open a Yocto bug and document the steps to reproduce the error.
I've sent a patch to oe-core to fix the regression in my setup:
https://lists.openembedded.org/g/openembedded-core/message/167368
Opened a bugzilla entry for rust cross-canadian:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14849
Great if you could look in to this.
Thanks!
/Peter
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57416): https://lists.yoctoproject.org/g/yocto/message/57416
Mute This Topic: https://lists.yoctoproject.org/mt/91864950/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] yocto support
On 28/06/2022 17:21:22+0530, Senthamilarasi mathiyan wrote: > Dear All > > Good Morning! > > In my project, I am trying to create one custom image recipe in my yocto > build system. > > The reason of creating custom image is -> having few specific > configurations for kernel and some specific driver Makefile changes to > enable coverage. > > I cannot go with .bbappend file, because we are maintaining a > recipes-append folder in our meta-layer which is common for all the > production build image recipes. > > My change is very specific it should not come as part of normal build > images because it will affect the production build. > > My use case: > > 1. I have one .cfg file for kernel - which has kernel specific > configurations. > > 2. I have Makefile changes for driver file. > > I should bring the above changes to kernel and driver Makefile during > build time without using .bbappend file. > > I want to create a custom image recipe with the specific changes. > > For example : custom_image.bb =( This recipes should have > core_image_minimal.bb + my specific changes) > > When i build bitbake custom_image.bb, it should build with > core_image_minimal.bb + my specific changes . > > Other images recipes also should not affect by this changes. > > My humble request. Can anyone please support how to proceed? > You can't, a recipe can't affect any other recipe. When building custom_image.bb, it is too late to introduce any kernel change. > Kindly share your suggestions. > > *Regards* > > *Senthamilarasi. M* > > > > > -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57415): https://lists.yoctoproject.org/g/yocto/message/57415 Mute This Topic: https://lists.yoctoproject.org/mt/92041991/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] Announcing pkgexp
Em ter., 28 de jun. de 2022 às 11:26, Michael Opdenacker via lists.openembedded.org escreveu: > > On 6/28/22 16:24, Ross Burton wrote: > > > >> On 28 Jun 2022, at 15:11, Michael Opdenacker < > michael.opdenac...@bootlin.com> wrote: > >> Hey, this looks very nice and very easy to use! > >> One minor complaint, though: the "What Depends on" button didn't > immediately catch my eye. > >> Would it be possible to show such reverse dependencies in the same way > you show RDEPENDS? The result may look better and everything would be on > the same page. > > The immediate problem with that is that for some packages, like libc, > the reverse depends list can be hge. If the page is redesigned to have > scrollable regions then sure. That would likely involve someone more > skilled in web design than me getting involved ;) > Ross, take a look on ye (https://github.com/OSSystemsEmbeddedLinux/ye) it does have some things worth adding as well. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57414): https://lists.yoctoproject.org/g/yocto/message/57414 Mute This Topic: https://lists.yoctoproject.org/mt/92044621/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc & v5.15/standard/nxp-sdk-5.15/nxp-soc][PATCH 1/1] crypto: caam: fix a build error 'needs_entropy_delay_adjustment' undefined
Fix commit f816aa7947c7 merge conflict, refer to
commit dd36037d4ae7 ("crypto: CAAM - fix i.mx6sx
entry delay value"), needs_ entropy_ delay_ Adjustment
function is referenced for this reason.
Signed-off-by: Xiaolei Wang
---
drivers/crypto/caam/ctrl.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/drivers/crypto/caam/ctrl.c b/drivers/crypto/caam/ctrl.c
index 6cd43ddb403b..37e01b0faf38 100644
--- a/drivers/crypto/caam/ctrl.c
+++ b/drivers/crypto/caam/ctrl.c
@@ -612,6 +612,13 @@ static void caam_dma_dev_unregister(void *data)
platform_device_unregister(data);
}
+static bool needs_entropy_delay_adjustment(void)
+{
+if (of_machine_is_compatible("fsl,imx6sx"))
+return true;
+return false;
+}
+
static int caam_ctrl_rng_init(struct device *dev)
{
struct caam_drv_private *ctrlpriv = dev_get_drvdata(dev);
@@ -666,6 +673,8 @@ static int caam_ctrl_rng_init(struct device *dev)
* Also, if a handle was instantiated, do not change
* the TRNG parameters.
*/
+ if (needs_entropy_delay_adjustment())
+ ent_delay = 12000;
if (!(ctrlpriv->rng4_sh_init || inst_handles)) {
dev_info(dev,
"Entropy delay = %u\n",
@@ -682,6 +691,15 @@ static int caam_ctrl_rng_init(struct device *dev)
*/
ret = instantiate_rng(dev, inst_handles,
gen_sk);
+ /*
+ * Entropy delay is determined via TRNG
characterization.
+ * TRNG characterization is run across different
voltages
+ * and temperatures.
+ * If worst case value for ent_dly is identified,
+ * the loop can be skipped for that platform.
+ */
+if (needs_entropy_delay_adjustment())
+break;
if (ret == -EAGAIN)
/*
* if here, the loop will rerun,
@@ -835,13 +853,6 @@ static bool check_version(struct fsl_mc_version
*mc_version, u32 major,
}
#endif
-static bool needs_entropy_delay_adjustment(void)
-{
- if (of_machine_is_compatible("fsl,imx6sx"))
- return true;
- return false;
-}
-
/* Probe routine for CAAM top (controller) level */
static int caam_probe(struct platform_device *pdev)
{
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11418):
https://lists.yoctoproject.org/g/linux-yocto/message/11418
Mute This Topic: https://lists.yoctoproject.org/mt/92059875/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
