Heavily trimmed down to the remaining points of discussion... Yes, sorry, I intended that, but didn't make that clear. Agreed. Hrm, that's too bad. I really like the explicit coupling of the

Hello all – those of you who read our blog posts know that we are trying to continually improve our developer experience. I have some good news here. I would like to introduce Belen Barros Pena

There are configs that absolutely should be coupled with patches, and configs that don't need to be. We are obviously talking about configs that don't need to be, and we definitely have the

I'm seeing a problem with the coupling of patches and configs. I understand why it made sense to do at the time, but if we want to base all branches off the same sources (and it's clear we do) then

From: Rahul Saxena <rahul.saxena@...> Add cedartrail.cfg, cedartrail.scc, cedartrail-standard.scc, cedartrail-preempt-rt.scc Signed-off-by: Rahul Saxena <rahul.saxena@.intel.com> ---

From: Rahul Saxena <rahul.saxena@...> This is the initial version of a BSP for the Cedar Trail platform. The Cedar Trail platform consists of the Intel Cedarview Atom processor and Tiger Point

Sorry for the slow reply, I got bogged down trying to write some python code yesterday. Sort of. Or what I meant by directly was the "patch <foo>" right in standard.scc. As you well know, for the

Zumeng, The comment from the bug reporter was also that the target doesn't have USB slave hardware to support usbgadget. So mentioning that in the header is probably a good idea as well. And small

There's still a way it will work, merge_config.sh is only ever called from the kern-tools. There shouldn't be any non kern-tools calls to merge_config.sh, the error: mv: cannot stat

1. No mass storage needed to be accessed by usbgadget. 2. This is a router station & switch, so it should not be taken as a USB_NET device too. Signed-off-by: Zumeng.chen@...> ---

Hello, 1- I wish to know how we are supposed to include package name in rootfs *.bb file? Like if I have to include Qt-4.6.3 , which parameter from qt4-embedded_4.6.3.bb file I need to give

Hrm maybe I missed that in the fri2 branches. It does need emgd, so I'll double check that. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

That won't work. He is using the latest kernel which has needs merge_config.sh - as I ran into myself last week. I had Kishore cherry-pick the last two patches to kern-tools-native from master

It's a valid config, and something that works now. So there's no reason to not use it. New branches can be created IF a board really does need to merge conflicting patches. The emgd stuff was a

What does your: meta/conf/distro/include/tcmode-default.inc have as the default ? It should be LINUXLIBCVERSION ?= "3.1". I'm talking about master for that default. In the release branches it was

This is likely the problem. I use and test meta-kernel-dev everyday, but that's always against master. I keep them in lockstep, since meta-kernel-dev never really 'releases'. That being said, we can

Hi All, This is the weekly test report for Yocto 1.2 M1 RC1 build. Test cases for new M1 features are included. HuronRiver is also added into BSP testing. There are 6 new bugs found in this

Only 2 more days left to respond if you haven't, and then I'll quit bugging you. :)

We hit another lock-step SRCREV bug earlier on the FRI2 BSP. This was due mostly to my pushing the efi changes to meta-intel too early - but, it highlights a maintenance step that I believe could be

This was on fri2 yocto/standard/fri2. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel