And what U R getting exactly? ls -al /dev | grep ttyS And, also, could you do it for: ls -al /dev | grep ttyUSB (with serial/USB cable plugged-in)? Zee _______

Dear Team, I'm building linux-raspberry, in this I'm not getting getting /dev/ttyS0 even after giving enable_uart=1 in config.txt file. I'm building two different kernels i.e. 4.14 and 5.4 using

Try adding the following line to the match section of the 80-wired.network file. KernelCommandLine=!ip Regards, Chen Qi On 03/12/2021 02:12 AM, jchludzinski

merged. thanks.

On Thu, Mar 11, 2021 at 3:45 AM darshak.raval via lists.yoctoproject.org <darshak.raval=volansys.com@...> wrote: you could backport nodejs 12.x from master as your own risk but

On 3/11/21 10:12 AM, jchludzinski wrote: Not that I know of. Why anyway? -- Rudolf J StreifCEO/CTO ibeeto+1.855.442.3386 x700

Hi, I've bumped from poky dunfell: dunfell-23.0.6 to actual dunfell branch and I have an problem that all linux-firmware packages are installed in my rootfs (even I have in IMAGE_INSTALL

Can this be done using boot parameters? Something like(?): LABEL Arria10 SOCDK SDMMC KERNEL ../zImage FDT ../socfpga_arria10_phead.dtb APPEND root=/dev/mmcblk0p2 rw rootwait earlyprintk

Ignore this. I reused an old git-send-email and sent it to the wrong list. I've re-send to oe-core :D Bruce On Thu, Mar 11, 2021 at 8:56 AM Bruce Ashfield

From: Bruce Ashfield <bruce.ashfield@...> perf generates pmu-events.c as part of the build process. The code that generates the events is doing tree walks and potentially other non-determinstic

Hi, I am currently using yocto warrior bsp as my build system. In warrior, nodejs version 10 is running at sources/meta-openembedded/meta-oe/recipes-devtools I want to use nodejs 14. I couldn't find

Hello! I am using u-boot on a pocketbeagle which, according to "Default Device Tree for DT control" in `bitbake -c menuconfig u-boot`, uses am335x-evm, which I understand is the file in

Hi Robert, For that particular example, I'm not entirely sure what the actual value for VAR would be. Also not sure what: VAR = "snafu" VAR_append = " more" VAR_qemux86 = "qemu" would mean for VAR.

From: Kai Kang <kai.kang@...> It fails to comile samhain for powerpc(qemuppc): | x_sh_dbIO.c: In function 'swap_short': | x_sh_dbIO.c:229:36: error: initializer element is not constant |

On Wed, 10 Mar 2021, Quentin Schulz wrote: ... snip ... > https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux/linux-yocto_5.10.bb#n12 > for example. > > This is an example

BBB example: https://www.yoctoproject.org/pipermail/yocto/2018-July/041696.html The line: DISTRO_FEATURES_append = " ram" Should be: DISTRO_FEATURES_append = " nfs" BSP Traces for BBB (YOCTO

From: Kai Kang <kai.kang@...> It fails to comile samhain for powerpc(qemuppc): | x_sh_dbIO.c: In function 'swap_short': | x_sh_dbIO.c:229:36: error: initializer element is not constant |

On 3/10/21 1:32 PM, jchludzinski wrote: Preferred method for local configuration is using /etc/systemd/network. However, the probable reason why it did not work is that the file

Hello everyone, I am currently using this Yocto-based build setup provided by NXP to create a custom Linux distribution for one of the i.MX boards. My custom image is based on the core-image-minimal

That didn't work BUT editing /lib/systemd/network/80-wired.network [Match]Name=en*