Re: [yocto] linux-libc-headers - how to handle for older kernels?

On 2019-12-03 16:28, Bruce Ashfield wrote: I'm assuming that you mean those headers are in a separate package and are installed into the dependent packages sysroot (or the SDK in your descriptin) via other means that linux-libc-headers .. if so, yes, that is the right thing to do. Thanks Bruce!

Re: [yocto] Are both TFTPd and TFTPd-HPA handled in one YP version ?

I've got 1 YP image with tftpd and another one with tftp-hpa daemon I'd like to merge these 2 YP images embedding the both tftp deamons in a single YP image, Is it possible ? I suggest having a look at the relevant recipes at the openembedded layer index. You can filter per yocto version.

[yocto][meta-rockchip][PATCH] Fix rk3288 bootloader

Recent versions of u-boot use a combined SPL/TPL (called idbloader.img) in the loader1 partition, which then loads the full u-boot from the loader2 partition. Update the GPT partition class to reflect this change. Additionally, remove the u-boot bbappend since it is no longer needed.

[yocto] [meta-security][PATCH 2/5] tpm2-abrmd": update to 2.3.0

Signed-off-by: Armin Kuster --- .../tpm2-abrmd/{tpm2-abrmd_2.2.0.bb => tpm2-abrmd_2.3.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta-tpm/recipes-tpm2/tpm2-abrmd/{tpm2-abrmd_2.2.0.bb => tpm2-abrmd_2.3.0.bb} (97%) diff --git

[yocto] [meta-security][PATCH 3/5] tpm2-tools: update to 4.0.1

LIC_FILES_CHKSUM added new copyrights Migrate to https d/l from git clone Signed-off-by: Armin Kuster --- .../recipes-tpm2/tpm2-tools/tpm2-tools_3.2.0.bb | 15 --- .../recipes-tpm2/tpm2-tools/tpm2-tools_4.0.1.bb | 14 ++ 2 files changed, 14 insertions(+), 15

[yocto] [meta-security][PATCH 1/5] tpm2-pkcs11: update to tip

Signed-off-by: Armin Kuster --- meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_0.9.9.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_0.9.9.bb b/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_0.9.9.bb index 2185749..351e03e

[yocto] [meta-security][PATCH 4/5] tpm2-tss-engine: update to tip to us tss-tools 4.0.x

LIC_FILES_CHKSUM update to be true BSD-3-clause text Signed-off-by: Armin Kuster --- .../recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.0.1.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.0.1.bb

[yocto] [meta-security][PATCH 4/6] tpm2-tss-engine: update to tip to us tss-tools 4.0.x

LIC_FILES_CHKSUM update to be true BSD-3-clause text Signed-off-by: Armin Kuster --- .../recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.0.1.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.0.1.bb

[yocto] [meta-security][PATCH 2/6] tpm2-abrmd": update to 2.3.0

Signed-off-by: Armin Kuster --- .../tpm2-abrmd/{tpm2-abrmd_2.2.0.bb => tpm2-abrmd_2.3.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta-tpm/recipes-tpm2/tpm2-abrmd/{tpm2-abrmd_2.2.0.bb => tpm2-abrmd_2.3.0.bb} (97%) diff --git

[yocto] [meta-security][PATCH 6/6] README: update mailing list to new groups.io

Signed-off-by: Armin Kuster --- README | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README b/README index 5abb0e2..c419d50 100644 --- a/README +++ b/README @@ -52,14 +52,14 @@ other layers needed. e.g.: Maintenance --- -Send pull requests, patches,

[yocto] [meta-security][PATCH 3/6] tpm2-tools: update to 4.0.1

LIC_FILES_CHKSUM added new copyrights Migrate to https d/l from git clone Signed-off-by: Armin Kuster --- .../recipes-tpm2/tpm2-tools/tpm2-tools_3.2.0.bb | 15 --- .../recipes-tpm2/tpm2-tools/tpm2-tools_4.0.1.bb | 14 ++ 2 files changed, 14 insertions(+), 15

Re: [linux-yocto] [linux-yocto-5.2/dev]: [kernel]: xilinx-zynqmp: add canfd feature

> -Original Message- > From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com] > Sent: Tuesday, December 03, 2019 11:09 PM > To: Li, Meng > Cc: Michal Simek; michal.si...@xilinx.com; linux-yo...@yoctoproject.org > Subject: Re: [linux-yocto] [linux-yocto-5.2/dev]: [kernel]: xilinx-zynqmp:

[yocto] raspberry pi Rpi3 does not boot to login prompt.

Hello all,I am testing a zeus rpi3.  Any and all help is appreciated. I created a rpi2 core-image-minimal and built a micro sd card.which booted okay.I then modified the build/conf/local.conf file for a raspberrypi3. The rpi3 core-image-minimal does not boot to login prompt.This is the output as

[yocto-announce] [ANNOUNCEMENT] Yocto Project 3.0.1 (zeus 22.0.1) Released

Hello, We are pleased to announce the Yocto Project 3.0.1 (zeus-22.0.1) Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.1/poky-zeus-22.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.0.1/poky-zeus-22.0.1.tar.bz2 A gpg signed version

[yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 3.0.1 (zeus 22.0.1) Released

Hello, We are pleased to announce the Yocto Project 3.0.1 (zeus-22.0.1) Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.1/poky-zeus-22.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.0.1/poky-zeus-22.0.1.tar.bz2 A gpg signed version

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On Tue, Dec 3, 2019 at 3:54 PM Steve Pavao wrote: > > > > On Thu, Nov 7, 2019 at 2:03 PM Khem Raj wrote: >> >> >> >> On Thu, Nov 7, 2019 at 10:42 AM Steve Pavao wrote: >>> >>> > On Nov 4, 2019, at 4:26 PM, Steve Pavao wrote: >>> > >>> >> On Nov 4, 2019, at 11:32 AM, Steve Pavao wrote: >>> >>>

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On Thu, Nov 7, 2019 at 2:03 PM Khem Raj wrote: > > > On Thu, Nov 7, 2019 at 10:42 AM Steve Pavao wrote: > >> > On Nov 4, 2019, at 4:26 PM, Steve Pavao wrote: >> > >> >> On Nov 4, 2019, at 11:32 AM, Steve Pavao wrote: >> >>> >> >>> On Nov 4, 2019, at 11:16 AM, Steve Pavao wrote: >> >>

Re: [yocto] zeus issues with fetching linux-yocto for beaglebone

On Tue, Dec 3, 2019 at 2:54 PM Marek Belisko wrote: > > Hi, > > I'm building yocto-beagle machine on poky zeus branch and linux-yocto > cannot be fetched. It still retry and start from beginning with > warning like; > > linux-yocto-5.2.17+gitAUTOINC+bd0762cd13_25b14cdf96-r0 do_fetch: > Failed to

[yocto] error trying to add repo file to image

Hello, I am trying to make an image (this is for an i.MX8, although I don't think it matters for this question) that contains a dnf repo in it. I created a dnf_%.bbappend file in my layer with the following contents: LICENSE = "CLOSED" FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI +=

[yocto] zeus issues with fetching linux-yocto for beaglebone

Hi, I'm building yocto-beagle machine on poky zeus branch and linux-yocto cannot be fetched. It still retry and start from beginning with warning like; linux-yocto-5.2.17+gitAUTOINC+bd0762cd13_25b14cdf96-r0 do_fetch: Failed to fetch URL

Re: [yocto] QA cycle report for yocto-3.0.1.rc3

On 03/12/2019 15:15, Richard Purdie wrote: On Tue, 2019-12-03 at 07:15 +, Jain, Sangeeta wrote: This is the full report for 3.0.1 RC3: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No

Re: [yocto] Yocto Image Build for NXP i.MX8M

On 12/3/19 1:51 AM, Aj Cit wrote: Dear Randy, Could you please tell me the steps for running a "Hello world" app on x86 QEMU? I've been following the guidelines as per https://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html tnx Aj Aj, Please CC the yocto email

[yocto] Yocto Project Status WW49'19

Current Dev Position: YP 3.1 M1 Next Deadline: YP 3.1 M1 build Dec. 2, 2019 Next Team Meetings: * Bug Triage meeting Thursday Dec. 5th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Dec. 3rd at 8am PDT (

Re: [yocto] linux-libc-headers - how to handle for older kernels?

On Tue, Dec 3, 2019 at 2:59 AM Peter Bergin wrote: > > On 2019-12-02 14:44, Bruce Ashfield wrote: > > On Mon, Dec 2, 2019 at 4:14 AM Mike Looijmans > > wrote: > >> On 01-12-19 22:57, Peter Bergin via Lists.Yoctoproject.Org wrote: > >>> Hi, > >>> > >>> I'm currently working in a project using

[yocto] Getting linux kernel version

Hi all, is there a standard way to get the Linux kernel version (output of `uname -r`)? I'm using a custom kernel recipe that inherit from kernel class. I need to get that version in a task executed after do_rootfs. Any help would be appreciated, best regards, Gabriele -=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] QA cycle report for yocto-3.0.1.rc3

On Tue, 2019-12-03 at 07:15 +, Jain, Sangeeta wrote: > This is the full report for 3.0.1 RC3: > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults > > === Summary > No high milestone defects. > No new defects are found in this

Re: [linux-yocto][yocto-kernel-cache master/yocto-5.2][PATCH] features: avoid enabling edac feature in mips

On Tue, Dec 3, 2019 at 4:38 AM Xu, Yanfei wrote: > > > On 12/2/19 12:28 PM, Bruce Ashfield wrote: > > In message: [linux-yocto][yocto-kernel-cache master/yocto-5.2][PATCH] > features: avoid enabling edac feature in mips > on 27/11/2019 yanfei...@windriver.com wrote: > > From: Yanfei Xu > > When

Re: [linux-yocto] [linux-yocto-5.2/dev]: [kernel]: xilinx-zynqmp: add canfd feature

In message: RE: [linux-yocto] [linux-yocto-5.2/dev]: [kernel]: xilinx-zynqmp: add canfd feature on 03/12/2019 Li, Meng wrote: > > > > -Original Message- > > From: linux-yocto@lists.yoctoproject.org [mailto:linux- > > yo...@lists.yoctoproject.org] On Behalf Of Michal Simek > > Sent:

Re: [linux-yocto] [yocto-kernel-cache]: [branch master/yocto-5.2]: xilinx-zynqmp: enable clock-wizard driver on xilinx-zcu102 platform

In message: [yocto-kernel-cache]: [branch master/yocto-5.2]: xilinx-zynqmp: enable clock-wizard driver on xilinx-zcu102 platform on 03/12/2019 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce & Michal, > > I am working on xilinx-zcu102 platform to impelment canfd feature. > > Could

Re: [V2][linux-yocto][linux-yocto v5.2/standard/base][linux-yocto-dev standard/base][PATCH 0/1] yaffs: add strict check when call yaffs_internal_read_super

In message: [V2][linux-yocto][linux-yocto v5.2/standard/base][linux-yocto-dev standard/base][PATCH 0/1] yaffs: add strict check when call yaffs_internal_read_super on 03/12/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > V1 ---> V2: > 1. split into 2 patches

Re: [yocto] Adding libstdc++-dev path?

Sorry. I sleep over the keyboard. The solution is adding manually the location of /usr/include/c++/5.3.0 /usr/include/c++/5.3.0/arm-poky-linux-gnueabi where library foldes. Your recipe is usefull to test my problem Thans. M Il 03/12/19 13:59, Gabriele Zampieri ha scritto: Forget about

Re: [yocto] Adding libstdc++-dev path?

Forget about the DEPENDS, I used that in another scenario. I tried the following recipe: FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI = "file://main.cpp" do_compile() { # For example purpose use only ${CXX} ${CXXFLAGS} ${WORKDIR}/main.cpp -o ${B}/${PN} } With a simple main:

Re: [yocto] Are both TFTPd and TFTPd-HPA handled in one YP version ?

Sure, I've got 1 YP image with tftpd and another one with tftp-hpa daemon I'd like to merge these 2 YP images embedding the both tftp deamons in a single YP image, Is it possible ? BR / J-Fr+ -Message d'origine- De : yocto@lists.yoctoproject.org De la part de Morne via

Re: [yocto] Adding libstdc++-dev path?

I try, But libstdc++-dev is procudes by gcc-runtime recipe. I try to put gcc-runtime in DEPENDS e RDEPENDS_${PN} but this doesn't. Finally I put manually the -I${STAGING_INCDIR}/c++/5.3.0 -I${STAGING_INCDIR}/c++/5.3.0/${CC_PREFIX} in the Makefile. CC_PREFIX=arm-poky-linux-gnueabi Il

[yocto] Adding libstdc++-dev path?

Hi all I'm trying to compile a library which need cstdio. The file is in ${STAGING_INCDIR}/c++/5.3.0 and in ${STAGING_INCDIR}/c++/5.3.0/tr1 I think I need to "include" in my recipe all libstdc++dev package Looking on ${CXX} -v I get --with-gxx-include-dir=/not/exist/usr/include/c++/5.3.0

[linux-yocto][PATCH 3/3] spi: spi-mem: zynq-qspi: add is-dual support for zc706 board

From: Quanyang Wang There are 2 SPI flash memories in zc706 board and it use the configuration "Dual SS, 8-bit Parallel" which means separate Slave-Select lines and separate 4 data lines. So add the is-dual support for zc706 board according to the spi driver in SDK. Refer to bd2c1810ae87 ("spi:

[linux-yocto][PATCH 2/3] xilinx-zynqmp: add xlnx_drm_framebuffer_init to replace drm_gem_fbdev_fb_create

From: Quanyang Wang Since the function drm_gem_fbdev_fb_create has been removed in commit 73415b4ea5b5 ("drm/fb: remove unused function: drm_gem_fbdev_fb_create()"), add a new function xlnx_drm_framebuffer_init to create a drm_framebuffer structure. Signed-off-by: Quanyang Wang ---

[linux-yocto] [linux-yocto-dev standard/xlnx-soc]][PATCH 0/3] New patches for v5.4

From: Quanyang Wang Hi Bruce & Michal, There are 3 patches in this pull-request. 1) The patch "0001-spi-zynq-qspi-use-wait_for_completion_timeout-instea.patch" fixes a bug which occurs in zc706 and zc702 boards using mainline and linux-yocto kernel. Using the command as below can reproduce

[linux-yocto][PATCH 1/3] spi: zynq-qspi: use wait_for_completion_timeout instead of wait_for_completion_interruptible_timeout

From: Quanyang Wang When umount jffs2 filesystem on mtdblock device, the process "jffs2_gcd_mtdX" which calls zynq_qspi_exec_mem_op to read/write flash will receive signal "SIGKILL" from thread "jffs2_stop_garbage_collect_thread". This means that at this moment the function

Re: [linux-yocto] [linux-yocto-dev standard/xlnx-soc][PATCH 0/9] Patches from linux-yocto v5.2 branch

On 03. 12. 19 10:21, quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce & Michal, > > There are 9 patches in this pull request. > The patch "0001-ARM-dts-zynq-enablement-of-coresight-topology.patch" is > picked from > the upstream commit from Michal and delete ITM compatible

Re: [linux-yocto][yocto-kernel-cache master/yocto-5.2][PATCH] features: avoid enabling edac feature in mips

On 12/2/19 12:28 PM, Bruce Ashfield wrote: In message: [linux-yocto][yocto-kernel-cache master/yocto-5.2][PATCH] features: avoid enabling edac feature in mips on 27/11/2019 yanfei...@windriver.com wrote: From: Yanfei Xu When some layer include this edac feature and bitbake kernel ARCH

[linux-yocto][PATCH 8/9] sound: soc: xilinx: give a name to stream_name in xilinx_dp_dai_links

From: Quanyang Wang If .stream_name is NULL, when calling "aplay -l", it will show: card 0: monitor [DisplayPort monitor], device 0: (null) xilinx-dp-snd-codec-dai-0 [(null) xilinx-dp-snd-codec-dai-0] Adding .stream_name can eliminate the "(null)" in the output. Signed-off-by: Quanyang Wang

[linux-yocto][PATCH 7/9] i2c: cadence: keep bus_hold_flag unless I2C_M_NOSTART is set

From: Quanyang Wang When using i2c_smbus_read_byte_data to read one byte from a slave device, because of the commit d358def70688 ("i2c: cadence: Fix the hold bit setting"), the transaction becomes: S Addr Wr [A] Comm [A] P S Addr Rd [A] [Data] NA P ^

[linux-yocto] [linux-yocto-dev standard/xlnx-soc][PATCH 0/9] Patches from linux-yocto v5.2 branch

From: Quanyang Wang Hi Bruce & Michal, There are 9 patches in this pull request. The patch "0001-ARM-dts-zynq-enablement-of-coresight-topology.patch" is picked from the upstream commit from Michal and delete ITM compatible string from it. The patch

[linux-yocto][PATCH 4/9] clk: zynqmp: fix memory leak in zynqmp_register_clocks

From: Quanyang Wang This is detected by kmemleak running on zcu102 board: unreferenced object 0xffc877e48180 (size 128): comm "swapper/0", pid 1, jiffies 4294892909 (age 315.436s) hex dump (first 32 bytes): 64 70 5f 76 69 64 65 6f 5f 72 65 66 5f 64 69 76 dp_video_ref_div 31 00 00 00 00 00

[linux-yocto][PATCH 3/9] ARM: zynq: use physical cpuid in zynq_slcr_cpu_stop/start

From: Quanyang Wang When kernel booting, it will create a cpuid map between the logical cpus and physical cpus. In a normal boot, the cpuid map is as below: Physical Logical 0==> 0 1==> 1 But in kdump, there is a condition that the crash happens at the

[linux-yocto][PATCH 9/9] xilinx-zynq: Revert "zynq: SMP crashkernel support"

From: Quanyang Wang This reverts commit 5d1a5900882ceb86cddf36c258bd5bda498c8da8. Since the commit ("ARM: zynq: use physical cpuid in zynq_slcr_cpu_stop/start") has fixed the hang issue in kdump, this patch can be reverted. Signed-off-by: Quanyang Wang Acked-by: Michal Simek Signed-off-by:

[linux-yocto][PATCH 2/9] arm: zynq: delete AFLAGS_suspend.o to fix compile warning

From: Quanyang Wang When using arm-linux-gnueabihf-gcc v9.2.0 to compile kernel, there will be warning info as below: cc1: warning: switch '-mcpu=cortex-a9' conflicts with '-march=armv7-a' switch This is because that if "-march" and "-mcpu" options are passed to gcc together, gcc will check if

[linux-yocto][PATCH 6/9] drivers: soc: xilinx: fix compile warning by defining payload array length to 32

From: Quanyang Wang In zynqmp-ipi-mailbox.c and zynqmp_r5_remoteproc.c, the variables of zynqmp_ipi_message structures are all using 32 as the maximum size of data length. So move IPI_BUF_LEN_MAX to zynqmp-ipi-message.h to share with zynqmp_power.c. Signed-off-by: Quanyang Wang Acked-by:

[linux-yocto][PATCH 1/9] ARM: dts: zynq: enablement of coresight topology

From: Zumeng Chen This patch is to build the coresight topology structure of zynq-7000 series according to the docs of coresight and userguide of zynq-7000. Signed-off-by: Zumeng Chen Link: https://patchwork.kernel.org/patch/11181257/ [Quanyang: delete compatible string for itm node]

[linux-yocto][PATCH 5/9] dma: xilinx: dpdma: alloc xilinx_dpdma_tx_desc using GFP_ATOMIC

From: Quanyang Wang The function xilinx_dpdma_chan_alloc_tx_desc can be called from atomic context, hence use GFP_ATOMIC instead of GFP_KERNEL, or else it will cause the calltrace as below: BUG: sleeping function called from invalid context at mm/slab.h:418 in_atomic(): 1, irqs_disabled(): 128,

[linux-yocto][PATCH 2/2] yaffs: add strict check when call yaffs_internal_read_super

From: Quanyang Wang When kernel booting, mount_block_root will be called to judge the filesystem type of root device. Then .mount function in file_system_type structure will do the check operation. But yaffs filesystem has a relaxed examination because as a filesystem for NAND Flash, it doesn't

[V2][linux-yocto][linux-yocto v5.2/standard/base][linux-yocto-dev standard/base][PATCH 0/1] yaffs: add strict check when call yaffs_internal_read_super

From: Quanyang Wang Hi Bruce, V1 ---> V2: 1. split into 2 patches to make the fix more reasonable. 2. add crash info to the patch. Would you please help merge this patch to the branches for: linux-yocto v5.2/standard/base linux-yocto-dev standard/base Quanyang Wang (2): yaffs: repair

[linux-yocto][PATCH 1/2] yaffs: repair yaffs_get_mtd_device

From: Quanyang Wang The function yaffs_get_mtd_device use wrong function to retrieve mtd_info structure (using yaffs_get_mtd_device itself will cause dead loop). Use get_mtd_device to do this. Signed-off-by: Quanyang Wang --- fs/yaffs2/yaffs_mtdif.c | 12 ++-- 1 file changed, 10

Re: [yocto] Are both TFTPd and TFTPd-HPA handled in one YP version ?

I'm looking for a trigger to handle both tftp deamons (tftpd and tftp-hpa) but could we have an YP image embedding these 2 tftp servers ? You said Yes. If it's handling could be done through a simple U-Boot configuration then itanswers to my question, but what could this trigger be at the

Re: [linux-yocto][PATCH 1/1] yaffs: add strict check when call yaffs_internal_read_super

On 12/3/19 4:38 PM, Kevin Hao wrote: On Tue, Dec 03, 2019 at 04:27:15PM +0800, quanyang.wang wrote: From: Quanyang Wang When kernel booting, mount_block_root will be called to judge the filesystem type of root device. Then .mount function in file_system_type structure will do the check

Re: [linux-yocto][PATCH 1/1] yaffs: add strict check when call yaffs_internal_read_super

On Tue, Dec 03, 2019 at 04:27:15PM +0800, quanyang.wang wrote: > From: Quanyang Wang > > When kernel booting, mount_block_root will be called to judge > the filesystem type of root device. Then .mount function in file_system_type > structure will do the check operation. But yaffs filesystem has

[linux-yocto][linux-yocto v5.2/standard/base][linux-yocto-dev standard/base][PATCH 0/1] yaffs: add strict check when call yaffs_internal_read_super

From: Quanyang Wang Hi Bruce, Would you please help merge this patch to the branches for: linux-yocto v5.2/standard/base linux-yocto-dev standard/base This patch fixes a bug: when using MMC card with btrfs filesystem to be root device, kernel will crash and the log as below: mmc0: new high

[linux-yocto][PATCH 1/1] yaffs: add strict check when call yaffs_internal_read_super

From: Quanyang Wang When kernel booting, mount_block_root will be called to judge the filesystem type of root device. Then .mount function in file_system_type structure will do the check operation. But yaffs filesystem has a relaxed examination because as a filesystem for NAND Flash, it doesn't

Re: [yocto] linux-libc-headers - how to handle for older kernels?

On 2019-12-02 14:44, Bruce Ashfield wrote: On Mon, Dec 2, 2019 at 4:14 AM Mike Looijmans wrote: On 01-12-19 22:57, Peter Bergin via Lists.Yoctoproject.Org wrote: Hi, I'm currently working in a project using Yocto 2.6 (thud) release. It has default kernel v4.18 and also linux-libc-headers