Re: [yocto] QA notification for completed autobuilder build (yocto-3.3_M3.rc1)

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.3_M3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC

Re: [yocto] Building test code?

On 3/15/21 4:11 PM, jchludzinski via lists.yoctoproject.org wrote: > I got a piece of code from github: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c > > I'd like to add it somewhere under /*tools/testing*/ and build it there. > > Not sure if

[yocto] GPT instead of MBR in my WKS file

Hello :-), Learning Yocto with my Pocketbeagle, I have been looking at the WKS file recently. Starting with the default beaglebone-yocto.wks, it is working fine for an MBR partition table: ``` part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 4

[yocto] Building test code?

I got a piece of code from github: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/spi/spidev_test.c I'd like to add it somewhere under _tools/testing_ and build it there. Not sure if this is appropriate? If so, how do I go about this? If not, what's the best

[yocto] QA notification for completed autobuilder build (yocto-3.3_M3.rc1)

A build flagged for QA (yocto-3.3_M3.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.3_M3.rc1 Build hash information: bitbake: 53c30efec4099035d19e6717059dfceff8ff88fd meta-arm: a949ebfd06dcae26ca3c625195e1a3ed703b2c6e

Re: [yocto] How can I create a truly minimal distribution that runs entirely from RAM?

On 3/14/21 6:16 PM, p32 via lists.yoctoproject.org wrote: Thank you very much. I figured out that you can have Yocto create a suitable U-Boot wrapper as follows (from the image recipe): IMAGE_FSTYPES = "cpio.xz.u-boot" Now there is only one last issue that I wasn't able to solve yet: I would

Re: [yocto] How can I create a truly minimal distribution that runs entirely from RAM?

On Mon, 2021-03-15 at 17:01 +0100, Zoran wrote: > > How can I instruct Yocto to execute do_image_cpio first? > > YOCTO people are entitled to answer that question. Aren't ya, INTEL folks??? > > Actually, iNTEL (IOTG) is responsible for that (since YOCTO support is > 90% from INTEL), and I assume

[yocto] M+ & H bugs with Milestone Movements WW11

All, YP M+ or high bugs which moved to a new milestone in WW11 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 5322 Global DNS fallback mechanism not present in poky distro

[yocto] Enhancements/Bugs closed WW11!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 4 alexandre.bell...@bootlin.com 3 richard.pur...@linuxfoundation.org 3 r...@burtonini.com 1 kory.mainc...@bootlin.com 1 bruce.ashfi...@gmail.com 1 Grand

[yocto] Current high bug count owners for Yocto Project 3.3

All, Below is the list as of top 48 bug owners as of the end of WW11 of who have open medium or higher bugs and enhancements against YP 3.3. There are 33 possible work days left until the final release candidates for YP 3.3 needs to be released. Who Count richard.pur...@linuxfoundation.org

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

Re: [yocto] How can I create a truly minimal distribution that runs entirely from RAM?

> Please be aware that this is a community mailing list for the Yocto > Project, and we expect everyone to be as pleasant as possible > I don't think the tone of your last email is appropriate for our > mailing lists. Unfortunately, Nicolas, you are barking under the wrong tree. Please, go to

Re: [yocto] How can I create a truly minimal distribution that runs entirely from RAM?

I can tell you... Ross! Please, focus on The Problem. Could you, please??? Since, I, an independent entity, am trying to help the people! OK? Since I do not care about political IOTG development, rather than on overall (NOT INTEL) resolution of the problem?! Do you understand the core of the

Re: [yocto] How can I create a truly minimal distribution that runs entirely from RAM?

hey Zoran, On Mon, Mar 15, 2021 at 5:01 PM Zoran wrote: > > > How can I instruct Yocto to execute do_image_cpio first? > > YOCTO people are entitled to answer that question. Aren't ya, INTEL folks??? > > Actually, iNTEL (IOTG) is responsible for that (since YOCTO support is > 90% from INTEL),

Re: [yocto] How can I create a truly minimal distribution that runs entirely from RAM?

> How can I instruct Yocto to execute do_image_cpio first? YOCTO people are entitled to answer that question. Aren't ya, INTEL folks??? Actually, iNTEL (IOTG) is responsible for that (since YOCTO support is 90% from INTEL), and I assume INTEL YOCTO people are entitled answering that/// Thank

Re: [yocto] [error-report-web][PATCH] report-error.bbclass: Add layer and bitbake version info to error report

Hi, Review reminder for [YOCTO #9700]. https://lists.yoctoproject.org/g/yocto/message/51891 Thanks & Regards, Milan Shah *Milan Shah* * | Software Engineer* *a: * MontaVista Software, LLC | Bangalore, India *e:* i...@mvista.com | *w:* www.mvista.com/ *p:*

[linux-yocto][yocto-kernel-cache][yocto-5.4][PATCH] bsp/intel-x86: change thunderbolt to usb4

for intel-x86 bsp CONFIG_THUNDERBOLT has changed to CONFIG_USB4, adjust it in kernel-cache only for intel-x86 bsp, together enable USB4_DEBUGFS_WRITE=m, and remove old thunderbolt.scc from intel-x86.scc Signed-off-by: Liwei Song --- bsp/intel-x86/intel-x86.cfg | 6 ++

Re: [linux-yocto][yocto-kernel-cache][yocto-5.4][PATCH] features/thunderbolt: change thunderbolt to usb4

Hi Bruce, Please ignore this patch, this patch does not work with other bsp, CONFIG_USB4 is only applicable for intel-x86 bsp now. Thanks, Liwei. On 3/15/21 10:46, LiweiSong wrote: > CONFIG_THUNDERBOLT has changed to CONFIG_USB4, adjust it > in kernel-cache. And enable USB4_DEBUGFS_WRITE=m > >