[yocto] Yocto Image Build for NXP i.MX8M
Hello, I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I am getting some error when I execute the bitmake command. I'd appreciate if you could guide me with next steps. Any Guide or url will be helpful. Thanks Ajith -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47442): https://lists.yoctoproject.org/g/yocto/message/47442 Mute This Topic: https://lists.yoctoproject.org/mt/63894854/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] QA notification for completed autobuilder build (yocto-3.0.1.rc3)
Hello All, Intel and WR YP QA is planning for QA execution for YP build yocto-3.0.1.rc3. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw 3. BSP-Qemu Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. MPC8315e-rdb 7. Beaglebone ETA for completion is next Tuesday, December 3. Thanks & Regards, Sangeeta Jain >-Original Message- >From: Poky Build User >Sent: Thursday, 28 November, 2019 11:56 AM >To: yo...@yoctoproject.org >Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv >; Yeoh, Ee Peng ; Chan, >Aaron Chun Yew ; Ang, Chin Huat >; richard.pur...@linuxfoundation.org; >akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta > >Subject: QA notification for completed autobuilder build (yocto-3.0.1.rc3) > > >A build flagged for QA (yocto-3.0.1.rc3) was completed on the autobuilder and >is >available at: > > >https://autobuilder.yocto.io/pub/releases/yocto-3.0.1.rc3 > > >Build hash information: > >bitbake: 8569ccb5e9fbdeaaf96b78bd02a263b26de54059 >meta-gplv2: 0f4eecc000f66d114ad258fa31aed66afa292166 >meta-intel: dc1fcaa858e85273676f4363a645661b5f1fb6e5 >meta-mingw: 756963cc28ebc163df7d7f4b4ee004c18d3d3260 >oecore: 75a4cabf55e13e6714c0fdb229cd51b5184ddbef >poky: 12a4c177bb541b3187c7a54d5804f30c35f22d8c > > > >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 (#47441): https://lists.yoctoproject.org/g/yocto/message/47441 Mute This Topic: https://lists.yoctoproject.org/mt/63871809/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] Review request [CD][BSP]marvell_cn96xx - upgrade to kernel v5.4
Hi Bruce, These commits will update marvell_cn96xx to kernel v5.4 on linux-yocto-dev. Target branch: standard/cn96xx. Patches based on:standard/base. Thanks~ Br. The following changes since commit 7169ab2c05a45377ad22ba50f0b1a7a02e0c88ef: arm64: dts: ti: k3-am65-main: Enable support for sdhci1 (2019-11-25 16:29:06 -0500) are available in the Git repository at: https://github.com/yinxts/linux-yocto-develop.git for you to fetch changes up to 58952fd7644103f761e648773b03d2e5f35a9696: octeontx2-pf: Allow setting VF mac and vlan only when PF is UP (2019-11-27 19:38:46 +0800) Aleksey Makarov (6): octeontx2-pf: Set irq affinity hints for CQ interrupts octeontx2-pf: Implement ndo_tx_timeout callback octeontx2-pf: Support queue interrupts octeontx2-pf: Add reset count to stats octeontx2-af: Add low level support for Marvell PTP coprocessor octeontx2-pf: Add support for PTP clock Alex Belits (2): arm64: Add support for ASID locking kernel/exit.c: Add task cleanup callbacks Andrew Pinski (3): arm64: Add MIDR encoding for some Marvell OcteonTX 2. arm64: Add workaround for Cavium erratum 36890 arm64: Add workaround for Marvell erratum 37119 Angela Czubak (2): octeontx2-af: fix rvu_sso_ggrp_taq_flush octeontx2-af: fix cgx_lmac_rx_tx_enable Bharat Bhushan (2): dt-bindings: perf: arm-smmuv3-pmu: Add documentation for arm-smmuv3 pmu perf/smmuv3: Add device tree support Chandrakala Chavva (1): mmc: cavium_thunderx: Use proper register to clear interrupts Christina Jacob (26): octeontx2-pf: BQL support. octeontx2-pf: IRQ coalescing config and tuning via ethtool octeontx2-af: Dump current resource provisioning status octeontx2-pf: Adding ethtool support for link status information. octeontx2-af: Patch to prevent redundant message from pf to af. octeontx2-pf: Fix redundant message from AF to PF octeontx2-af: Support to get link info like current speed, fec etc octeontx2-pf: Ethtool support for fec configuration octeontx2-pf: Fix smmuv3 messages while deferring pf driver probe. octeontx2-af: Move to rvu_fwdata version 1. octeontx2-pf: Add ethtool -m option support. octeontx2-af: Extend fwdata structure with additional information. octeontx2-af: Update fwadata structure with few more reserved fields. octeontx2-af: Fetch FEC stats of the physical link octeontx2-pf: Support to display fec counters also in ethtool stats. octeontx2-af: sync ATF and Kernel firmware data structure. octeontx2-pf: Support to display current settings of a vf network interface via ethtool net:thunderx: fix memory leak in nicvf driver. soc: octeontx2: Add mdio command interface using debugfs octeontx2-af: Introduce SET_LINK_MODE command to change various configurations of a network interface. octeontx2-pf: support to change link speed and autoneg octeontx2-pf: Disply the link detected status in ethtool command net: thunderx: Do a PCS reset upon SGMII link toggle octeontx2-pf: remove redundant changes from speed change suppcrt. octeontx-af: Interface mode change feature via ethtool octeontx2-pf: Interface Mode change using ethtool. Felix Manlunas (5): octeontx2-af: Add new CGX_CMDs to set and get PHY modulation type octeontx2-pf: Add ethtool priv flag to control PAM4 on/off octeontx2-pf: Fix wrong info in ethtool's list of supported link modes octeontx2-af: Increase mbox response timeout to 2 seconds octeontx2-pf: Add LIO3 link modes to ethtool's list of supported modes Geetha sowjanya (34): iommu/arm-smmu-v3: Force 32 byte command queue memory reads on SMMU for 96xx and 95xx silicons octeontx2-af: Sync hw mbox with bounce buffer. octeontx2-pf: Add mailbox bounce buffer octeontx2-pf: Add interface stats to ndo_get_stats64 octeontx2-af: Config receive and transmission of pause frames octeontx2-af: Add mbox message to enable/disable pause frames. octeontx2-af: Add mbox messages to configure backpressure for an interface. octeontx2-pf: Add ethtool support to enable/disable pause frames octeontx2-pf: Configure RED drop levels for packet reception. octeontx2-pf: Configure backpressure level for packet reception octeontx2-pf: Skip CQ_STATUS read if pending CQEs greater than budget octeontx2-pf: Set RVU PF/VF watchdog timeout octeontx2-af: Check SQ counters to detect the deadlock octeontx2-af: Enable pci bus mastering octeontx2-af: Fix rvu probe on cgx disable octeontx2-pf: Add VF function level reset (FLR) support octeontx2-vf: Configure backpressure level for packet reception octeontx2-af: Support configurable NDC cache way_mask octeontx2: Fix mbox driver compilation dependency.
[linux-yocto][yocto-kernel-cache master/yocto-5.2][PATCH] features: avoid enabling edac feature in mips
From: Yanfei Xu When some layer include this edac feature and bitbake kernel ARCH =mips, that will cause some warning masseges. CONFIG_EDAC and CONFIG_EDAC_DEBUG depend on CONFIG_EDAC_SUPPORT, but CONFIG_EDAC_SUPPORT isn't enabled in most of mips bsps(except CAVIUM_OCTEON_SOC, however CAVIUM_OCTEON_SOC is not defined in bsps) Signed-off-by: Yanfei Xu --- features/edac/edac-enable.scc | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/features/edac/edac-enable.scc b/features/edac/edac-enable.scc index c60d2790..f9a56af0 100644 --- a/features/edac/edac-enable.scc +++ b/features/edac/edac-enable.scc @@ -1,5 +1,7 @@ # SPDX-License-Identifier: MIT -define KFEATURE_DESCRIPTION "Enable core EDAC functionality" -define KFEATURE_COMPATIBILITY board +if [ "$KARCH" != "mips" ]; then +define KFEATURE_DESCRIPTION "Enable core EDAC functionality" +define KFEATURE_COMPATIBILITY board -kconf hardware edac.cfg +kconf hardware edac.cfg +fi -- 2.23.0 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8118): https://lists.yoctoproject.org/g/linux-yocto/message/8118 Mute This Topic: https://lists.yoctoproject.org/mt/63635414/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OpenEmbedded Workshop at FOSDEM20 CFP
On Thu, Nov 21, 2019 at 4:12 PM Jon Mason wrote: > > We are proud to announce the inaugural OpenEmbedded Workshop. It is > being held on 03 February 2020 in Brussels, Belgium. The day after > FOSDEM. > > The Call for Participation is open now. For more information, go to > https://pretalx.com/oe-workshop-2020/cfp > > Early-bird tickets coming soon! > > Thank you, > The OpenEmbedded Board We forgot to mention that the deadline for the CFP is December 15th. Please get your topic in before the deadline. Also, look for early-bird tickets next week! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47440): https://lists.yoctoproject.org/g/yocto/message/47440 Mute This Topic: https://lists.yoctoproject.org/mt/61340554/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto v5.2] Another patch series for the Marvell cn96xx support
On Tue, Nov 26, 2019 at 5:51 AM Kevin Hao wrote: > > Hi Bruce, > > Here is another patch series for the Marvell cn96xx SoC support. The main > changes are two CPU erratas and misc Ethernet bug fix. Please help me merge > these to the following two branches: > v5.2/standard/cn96xx > v5.2/standard/preempt-rt/cn96xx > > The following changes since commit d09d842d90ee891def1e0599bd287f9079b714a6: > > Merge branch 'v5.2/standard/base' into v5.2/standard/cn96xx (2019-11-17 > 22:12:02 -0500) > > are available in the Git repository at: > > git://github.com/haokexin/linux v5.2/standard/cn96xx for some reason this email didn't get the normal tags applied to it .. so I almost missed it during my merge activities today. But I did find it in time :D Thanks for the changes, they look good to me and are now merged. Bruce > > for you to fetch changes up to 2dbea6690bb772b7896071d61c965f81ffbe1445: > > net: octeontx2-pf: Don't set the parse mode for LBKs (2019-11-26 18:04:24 > +0800) > > > Andrew Pinski (3): > arm64: Add MIDR encoding for some Marvell OcteonTX 2. > arm64: Add workaround for Cavium erratum 36890 > arm64: Add workaround for Marvell erratum 37119 > > Bharat Bhushan (3): > dt-bindings: perf: arm-smmuv3-pmu: Add documentation for arm-smmuv3 pmu > perf/smmuv3: Add device tree support > perf/smmuv3: Fix programming event type with global > > Felix Manlunas (3): > octeontx2-pf: Fix wrong info in ethtool's list of supported link modes > octeontx2-af: Increase mbox response timeout to 2 seconds > octeontx2-pf: Add LIO3 link modes to ethtool's list of supported modes > > Geetha sowjanya (4): > octeontx: Reduce mbox wait response time. > octeontx2-af: Reduce mbox wait response time. > octeontx2-pf: Fix clearing SQ/CQ queue interrupt > octeontx2-pf: Drop packets size more than configured FRS > > Hao Zheng (1): > octeontx2-af: kpu profile add support for HIGIG2 protocol > > Harman Kalra (1): > octeontx2-pf: notify VF about ptp event > > Kevin Hao (1): > net: octeontx2-pf: Don't set the parse mode for LBKs > > Kiran Kumar K (1): > octeontx2-af: add default ldata ext for higig2 > > Rakesh Babu (1): > octeontx2-af: Get MSIXTR_BASE from fw_data > > Subbaraya Sundeep (1): > octeontx2-pf: Use BLKTYPE in register macros > > Subrahmanyam Nilla (1): > octeontx2-af: Add SDP interface support. > > Sunil Goutham (11): > octeontx2-pf: NAPI handler cleanup > octeontx2-pf: Fix CQE cleanup done while teardown > octeontx2-pf: Use napi_get_frags instead of build_skb > octeontx2-pf: Use napi_complete_done instead of napi_complete > octeontx2-pf: Alloc only used MSIX vectors > octeontx2-pf: Aggregate multiple boolean fields into common flags > octeontx2-pf: Cleanup otx2_nic and hw structs > octeontx2-pf: Optimize populating SQE_HDR > octeontx2-pf: Advertise lockless transmit capability > octeontx2-pf: Use 2048 byte receive buffers > octeontx2-pf: Allow setting VF mac and vlan only when PF is UP > > hariprasad (5): > octeontx2-af : handle rvu pfvf mac address > octeontx2-pf: Simplify ndo vf mac and vlan > octeontx2-af: dont force enable default unicast entry > octeontx2-af: Support for parsing pkts with switch headers > octeontx2-pf: Support to enable EDSA/Higig2 pkts parsing > > Documentation/devicetree/bindings/perf/arm_smmuv3_pmu.txt | 34 + > arch/arm64/Kconfig | 25 > arch/arm64/include/asm/cpucaps.h | 4 +- > arch/arm64/include/asm/cputype.h | 5 + > arch/arm64/kernel/cpu_errata.c | 58 + > arch/arm64/kernel/entry.S | 3 + > drivers/net/ethernet/cavium/thunder/nicvf_main.c | 9 +- > drivers/net/ethernet/marvell/octeontx2/af/Makefile | 2 +- > drivers/net/ethernet/marvell/octeontx2/af/common.h | 3 + > drivers/net/ethernet/marvell/octeontx2/af/mbox.c | 18 ++- > drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 19 ++- > drivers/net/ethernet/marvell/octeontx2/af/npc.h| 9 ++ > drivers/net/ethernet/marvell/octeontx2/af/npc_profile.h| 630 > ++- > drivers/net/ethernet/marvell/octeontx2/af/rvu.c| 23 +++- > drivers/net/ethernet/marvell/octeontx2/af/rvu.h| 15 ++- > drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c| 2 +- > drivers/net/ethernet/marvell/octeontx2/af/rvu_nix.c| 29 - > drivers/net/ethernet/marvell/octeontx2/af/rvu_npc.c| 91 > -- > drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c | 36 -- >
[yocto] Which layer is best for tpm2 stack
Hello, I need to use a TPM2 software stack for my project (tpm2-tools, tpm2-abrmd, tpm2-tss, etc.), where I am already using Yocto, meta-intel, meta-oe, meta-networking, etc. I see there are at least the following three layers that carry the necessary TPM2 bits, with varying recipe versions. * meta-tpm in meta-security repo (https://git.yoctoproject.org/cgit/cgit.cgi/meta-security/) * meta-tpm2 in meta-secure-core repo (https://github.com/jiazhang0/meta-secure-core) * meta-measured (https://github.com/flihp/meta-measured) My current objective is to use the TPM2 as a security chip from our software (in the future we may extend its use to root fs encryption keys and the like). Are there any recommendations as to which of these layers would be more appropriate, is better maintained, etc.? BTW, the meta-tpm layer in meta-security repo is not listed in the OpenEmbedded Layer index, although meta-security itself and some of the other layers in that repo are listed. Is that because of a name clash with the ones under the meta-secure-core repo, which also carries layers named meta-tpm and meta-integrity? Thanks, Diego -- Diego Santa Cruz, PhD Technology Architect spinetix.com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47439): https://lists.yoctoproject.org/g/yocto/message/47439 Mute This Topic: https://lists.yoctoproject.org/mt/63206848/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v5.2] Revert "platform/x86: wmi: Destroy on cleanup rather than unregister"
On Wed, Nov 27, 2019 at 3:55 AM Yongxin Liu wrote: > > Hi Bruce, > > This patch was sent to mainline kernel for review. > But it costs much more time than I thought. > Could help to review whether it can be merged to linux-yocto v5.2? Thanks for the link to the discussion! We can fix the issue you've seen (and fixed), while the broader upstream fix is considered. I've gone ahead and merged the patch. Bruce > > For more details, please refer to https://patchwork.kernel.org/patch/11244821/ > > Yongxin Liu (1): > Revert "platform/x86: wmi: Destroy on cleanup rather than unregister" > > drivers/platform/x86/wmi.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > -- > 2.14.4 > > > Thanks, > Yongxin -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8116): https://lists.yoctoproject.org/g/linux-yocto/message/8116 Mute This Topic: https://lists.yoctoproject.org/mt/62461543/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto-5.2]: [kernel v5.2/standard/base]: ti-am65x: add SD support
On Tue, Nov 26, 2019 at 7:53 AM Jun Miao wrote: > > Hi Bruce, > > About BSP ti-am65x platform, there are conflict in k3-am65-main.dtsi between > v5.4. > Below 2 patches are used to SD card. > > Could you please help to merge the 2 patches into branch v5.2/standard/base, > linux-ycoto kernel. merged! Bruce > > > Faiz Abbas (2): > arm64: dts: ti: k3-am654-base-board: Add Support for SD card > arm64: dts: ti: k3-am65-main: Enable support for sdhci1 > > arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 13 + > .../arm64/boot/dts/ti/k3-am654-base-board.dts | 19 +++ > 2 files changed, 32 insertions(+) > > -- > 2.17.1 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8115): https://lists.yoctoproject.org/g/linux-yocto/message/8115 Mute This Topic: https://lists.yoctoproject.org/mt/61958287/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [yocto-kernel-cache]: marvell-cn96xx: Add JUMP_LABEL config for ethernet
On Tue, Nov 26, 2019 at 3:28 AM Xiaotao Yin wrote: > > Hi Bruce, > > This is Xiaotao, is working on marvell-cn96xx platform, and I want to enable > CONFIG_JUMP_LABEL for marvell-cn96xx ethernet. > > Could you please help to merge this patch into yocto-kernel-cache, branche: > master. merged to master. Bruce > > > Thanks. > Br. > > diffstat info ad below: > > marvell-cn96xx.cfg |1 + > 1 file changed, 1 insertion(+) > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8113): https://lists.yoctoproject.org/g/linux-yocto/message/8113 Mute This Topic: https://lists.yoctoproject.org/mt/63182245/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [yocto-kernel-cache]: bcm-2xxx-rpi: enable CONFIG_FB_SIMPLE for bcm-2xxx-rpi BSP in kernel-cache
Looks good to me. This is merged Bruce On Mon, Nov 25, 2019 at 11:52 PM wrote: > From: Limeng > > Hi Bruce, > > Jason Wessel is working on Raspbeerypi 4 platform, and he wants to enable > CONFIG_FB_SIMPLE for display feature. > > Could you please help to merge this patch into yocto-kernel-cache, > branches are master and yocto-5.2? > > diffstat info ad below: > > bcm-2xxx-rpi.cfg |1 + > 1 file changed, 1 insertion(+) > > > thanks, > Limeng > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8112): https://lists.yoctoproject.org/g/linux-yocto/message/8112 Mute This Topic: https://lists.yoctoproject.org/mt/61954606/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] How to reduce rootfs image size?
Hi JH, The image root file system size is based on the actual content of the root file system. Besides ROOTFS_SIZE there are other variables that control how the root file system is sized: IMAGE_ROOTFS_SIZE: Defines the size in kilobytes of the created root filesystem image. The build system uses this value as a request or recommendation. The final root filesystem image size may be larger depending on the actual space required. The default value is 65536. IMAGE_ROOTFS_ALIGNMENT: Defines the alignment of the root filesystem image in kilobytes. If the final size of the root filesystem image is not a multiple of this value, it is rounded up to the nearest multiple of it. The default value is 1. IMAGE_ROOTFS_EXTRA_SPACE: Adds extra free space to the root filesystem image. The variable specifies the value in kilobytes. For example, to add an additional 4 GB of space, set the variable to IMAGE_ROOTFS_EXTRA_SPACE = "4194304". The default value is 0. IMAGE_OVERHEAD_FACTOR: This variable specifies a multiplicator for the root filesystem image. The factor is applied after the actual space required by the root filesystem has been determined. The default value is 1.3. Here is some pseudo code on how these variables are used to determine the final root file system size: _get_rootfs_size(): ROOTFS_SIZE =`du -ks IMAGE_ROOTFS` BASE_SIZE = ROOTFS_SIZE * IMAGE_OVERHEAD_FACTOR if (BASE_SIZE < IMAGE_ROOTFS_SIZE): IMG_SIZE = IMAGE_ROOTFS_SIZE + IMAGE_ROOTFS_EXTRA_SPACE else: IMG_SIZE = BASE_SIZE + IMAGE_ROOTFS_EXTRA_SPACE IMG_SIZE = IMG_SIZE + IMAGE_ROOTFS_ALIGNMENT – 1 IMG_SIZE = IMG_SIZE % IMAGE_ROOTFS_ALIGNMENT return IMG_SIZE :rjs On 11/27/19 3:12 AM, JH wrote: > Hi, > > Does the Yocto rootfs image size is based on real contents included in > the image-rootfs.tar.gz? > > When I build the image with very large size of applications and > libraries such as boost, I have my image-rootfs.tr.gz about 44 MB, > then I removed all large size of applications and libraries, I changed > IMAGE_ROOTFS_SIZE to a small size IMAGE_ROOTFS_SIZE = 2, I thought > the image-rootfs.tar.gz should be reduced to a small size, but it is > still 43 MB I don't believe it is that big, which variable I should > use to reduce the image size? > > Thank you. > > Kind regards, > > - jh > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#47433): > https://lists.yoctoproject.org/g/yocto/message/47433 > Mute This Topic: https://lists.yoctoproject.org/mt/62495609/3617932 > Group Owner: yocto+ow...@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub > [rudolf.str...@ibeeto.com] > -=-=-=-=-=-=-=-=-=-=-=- -- - Rudolf J Streif CEO/CTO ibeeto +1.855.442.3386 x700 signature.asc Description: OpenPGP digital signature -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47438): https://lists.yoctoproject.org/g/yocto/message/47438 Mute This Topic: https://lists.yoctoproject.org/mt/62495609/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Yocto build to add root password
Mauro wrote...
Actually I'm using:
EXTRA_USERS_PARAMS = " usermod -p '$(openssl passwd -6 myrootpassword)' root;"
...
But at this point I'm not sure if ${ROOT_PASSWORD} works (I'm using the
password wrote on the command, not passed by variable).
Switching to the ‘$(openssl …)’ form has worked, even using the
${ROOT_PASSWORD} variable.
Thanks for your help!
-Andy.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#47437): https://lists.yoctoproject.org/g/yocto/message/47437
Mute This Topic: https://lists.yoctoproject.org/mt/61917008/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] How to reduce rootfs image size?
Hi If you want to reduce the size of your root filesystem, you have to remove software you don't need. IMAGE_ROOTFS_SIZE has no effect on the size of your image-rootfs.tar.gz. Putting a smaller size will just lead to a rootfs that don't fit in the expected IMAGE_ROOTFS_SIZE. Fabien Le mercredi 27 novembre 2019 à 22:12 +1100, JH a écrit : > Hi, > > Does the Yocto rootfs image size is based on real contents included > in > the image-rootfs.tar.gz? > > When I build the image with very large size of applications and > libraries such as boost, I have my image-rootfs.tr.gz about 44 MB, > then I removed all large size of applications and libraries, I > changed > IMAGE_ROOTFS_SIZE to a small size IMAGE_ROOTFS_SIZE = 2, I > thought > the image-rootfs.tar.gz should be reduced to a small size, but it is > still 43 MB I don't believe it is that big, which variable I should > use to reduce the image size? > > Thank you. > > Kind regards, > > - jh > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#47433): > https://lists.yoctoproject.org/g/yocto/message/47433 > Mute This Topic: https://lists.yoctoproject.org/mt/62495609/3618224 > Group Owner: yocto+ow...@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [fabien.la > houd...@collabora.co.uk] > -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47436): https://lists.yoctoproject.org/g/yocto/message/47436 Mute This Topic: https://lists.yoctoproject.org/mt/62495609/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Yocto build to add root password
On 27/11/19 12:06, Andy Pont wrote:
I tried this out on a build that I am working on for which I needed to
add a root password and to create a non-root user with a password.
If I use:
EXTRA_USERS_PARAMS += "usermod -p `openssl passwd -6 ${ROOT_PASSWORD}`
root;”
When I try to login to the device it rejects the password that was
defined as ROOT_PASSWORD. If I remove the “-6” from the openssl command
and rebuild/deploy the image then I can login to the target as expected.
Is there something else that needs to be defined/included in the Yocto
configuration in order for the “-6” option to work?
-Andy.
Actually I'm using:
EXTRA_USERS_PARAMS = " usermod -p '$(openssl passwd -6 myrootpassword)'
root;"
with success on warrior.
Sorry, I forgot to mention that with password algorithms like the -6 we
need the two ' ' around the openssl command, because the generated hash
contains the "$" character, that is resolved as a bash variable
somewhere in the process.
But at this point I'm not sure if ${ROOT_PASSWORD} works (I'm using the
password wrote on the command, not passed by variable).
Regards
--
Mauro
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#47435): https://lists.yoctoproject.org/g/yocto/message/47435
Mute This Topic: https://lists.yoctoproject.org/mt/61917008/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] How to reduce rootfs image size?
On Wed, Nov 27, 2019 at 10:12:13PM +1100, JH wrote: > Hi, > > Does the Yocto rootfs image size is based on real contents included in > the image-rootfs.tar.gz? > > When I build the image with very large size of applications and > libraries such as boost, I have my image-rootfs.tr.gz about 44 MB, > then I removed all large size of applications and libraries, I changed > IMAGE_ROOTFS_SIZE to a small size IMAGE_ROOTFS_SIZE = 2, I thought > the image-rootfs.tar.gz should be reduced to a small size, but it is > still 43 MB I don't believe it is that big, which variable I should > use to reduce the image size? tar.gz ist a content-based format, not a filesystem based one. So if the tarball is that big, then you certainly have all those things in your rootfs. Look at the manifest files to find out that goes in there, and use buildhistory to find out the sizes of the things. Greetz -- ——— Josef Holzmayr Software Developer Embedded Systems Tel: +49 8444 9204-48 Fax: +49 8444 9204-50 R-S-I Elektrotechnik GmbH & Co. KG Woelkestrasse 11 D-85301 Schweitenkirchen www.rsi-elektrotechnik.de ——— Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393 Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg Ust-IdNr: DE 128592548 _ Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363 Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg USt-IdNr.: DE 128592548 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47434): https://lists.yoctoproject.org/g/yocto/message/47434 Mute This Topic: https://lists.yoctoproject.org/mt/62495609/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] How to reduce rootfs image size?
Hi, Does the Yocto rootfs image size is based on real contents included in the image-rootfs.tar.gz? When I build the image with very large size of applications and libraries such as boost, I have my image-rootfs.tr.gz about 44 MB, then I removed all large size of applications and libraries, I changed IMAGE_ROOTFS_SIZE to a small size IMAGE_ROOTFS_SIZE = 2, I thought the image-rootfs.tar.gz should be reduced to a small size, but it is still 43 MB I don't believe it is that big, which variable I should use to reduce the image size? Thank you. Kind regards, - jh -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47433): https://lists.yoctoproject.org/g/yocto/message/47433 Mute This Topic: https://lists.yoctoproject.org/mt/62495609/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Yocto build to add root password
Mauro wrote...
pay attention that "openssl passwd ${ROOT_PASSWORD}" command handles only
passwords up to 8 characters (the extra characters will be truncated and the generated
hash is for the first eight).
If you want to use more than 8 characters in the password, use another password algorithm
instead of the default one. You can see other supported algorithms typing "openssl
help passwd".
For example, command could become
openssl passwd -6 ${ROOT_PASSWORD}
I tried this out on a build that I am working on for which I needed to
add a root password and to create a non-root user with a password.
If I use:
EXTRA_USERS_PARAMS += "usermod -p `openssl passwd -6 ${ROOT_PASSWORD}`
root;”
When I try to login to the device it rejects the password that was
defined as ROOT_PASSWORD. If I remove the “-6” from the openssl command
and rebuild/deploy the image then I can login to the target as expected.
Is there something else that needs to be defined/included in the Yocto
configuration in order for the “-6” option to work?
-Andy.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#47432): https://lists.yoctoproject.org/g/yocto/message/47432
Mute This Topic: https://lists.yoctoproject.org/mt/61917008/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.2][PATCH 1/1] Revert "platform/x86: wmi: Destroy on cleanup rather than unregister"
This reverts commit 7b11e8989618581bc0226ad313264cdc05d48d86. Consider the following hardware setting. |-PNP0C14:00 | |-- device #1 |-PNP0C14:01 | |-- device #2 When unloading wmi driver module, device #2 will be first unregistered. But device_destroy() using MKDEV(0, 0) will locate PNP0C14:00 first and unregister it. This is incorrect. Should use device_unregister() to unregister the real parent device. Signed-off-by: Yongxin Liu --- drivers/platform/x86/wmi.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/platform/x86/wmi.c b/drivers/platform/x86/wmi.c index 22f4b92c5da4..a719acac6031 100644 --- a/drivers/platform/x86/wmi.c +++ b/drivers/platform/x86/wmi.c @@ -1307,7 +1307,7 @@ static int acpi_wmi_remove(struct platform_device *device) acpi_remove_address_space_handler(acpi_device->handle, ACPI_ADR_SPACE_EC, _wmi_ec_space_handler); wmi_free_devices(acpi_device); - device_destroy(_bus_class, MKDEV(0, 0)); + device_unregister((struct device *)dev_get_drvdata(>dev)); return 0; } @@ -1361,7 +1361,7 @@ static int acpi_wmi_probe(struct platform_device *device) return 0; err_remove_busdev: - device_destroy(_bus_class, MKDEV(0, 0)); + device_unregister(wmi_bus_dev); err_remove_notify_handler: acpi_remove_notify_handler(acpi_device->handle, ACPI_DEVICE_NOTIFY, -- 2.14.4 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8111): https://lists.yoctoproject.org/g/linux-yocto/message/8111 Mute This Topic: https://lists.yoctoproject.org/mt/62461548/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto v5.2] Revert "platform/x86: wmi: Destroy on cleanup rather than unregister"
Hi Bruce, This patch was sent to mainline kernel for review. But it costs much more time than I thought. Could help to review whether it can be merged to linux-yocto v5.2? For more details, please refer to https://patchwork.kernel.org/patch/11244821/ Yongxin Liu (1): Revert "platform/x86: wmi: Destroy on cleanup rather than unregister" drivers/platform/x86/wmi.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- 2.14.4 Thanks, Yongxin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8110): https://lists.yoctoproject.org/g/linux-yocto/message/8110 Mute This Topic: https://lists.yoctoproject.org/mt/62461543/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
