Thanks for the write-up RP. Do we plan to integrate this with the reference manual? Perhaps something on the wiki until this is all a bit more final and then move it into the ref

From: Paul Eggleton <paul.eggleton@...> iPXE is a network bootloader primarily for Intel-based systems (the successor to gPXE). Signed-off-by: Paul Eggleton

From: Paul Eggleton <paul.eggleton@...> Add iPXE to help with NFS root setup on Intel-based machines [1]. Note that this pulls from an arbitrary (but tested) git SRCREV due to there not

We had an earlier discussion with RP and per his suggestion, we're looking into the option of having a UI cache file that only contains the extra fields the UI is needed... Right now we only have one

Shall I start an OE wiki page to collect this information then? (I wasn't present at said discussion, so I'm not sure what was decided.) Cheers, Paul -- Paul Eggleton Intel Open Source Technology

Thanks to all who attended the Yocto Technical Team meeting today. Here are the notes from the meeting. Thanks. - Julie Attendees: Julie, Paul, Saul, Beth, Tom, Jefro, Mark, Jessica, Joshua,

We certainly should be doing this. I have some automation of release process tasks coming up, and will make sure that that is part of it. I want to think about how this is going to be done, process

Op 19 apr 2011, om 14:58 heeft Gary Thomas het volgende geschreven: At ELC we talked about having a single webpage listing all the layers out there, with descriptions to address that problem. FWIW,

Can someone let me in on the secret? On the Yocto WiKi, I can only find directions for checking out oe-core (and bitbake). The WiKi page for meta-yocto is empty :-( Also, I've seen references to

Dear Elizabeth Flanagan, In message <4DAC90D3.3050905@...> you wrote: I know that such things happen, but then it would have been at least a good idea to post some information about this - as

Yocto Technical Team, We are resuming our Yocto Technical Team meetings in order to track Yocto Project 1.1 deliverables. If you are interested in attending, our next meeting will be Tuesday, April

Wolfgang, Yes, there was a problem with what I assumed would be our bernard-5.0 release and the tag needed to be moved, which, while a messy practice, was the only available option at the time. The

I'm cc'ing Beth on this thread, since I was not involved in the tag move. Scott -- Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center

Oh, that surprises me as well. What is the justification here? Generally speaking, I'd expect the tags to be static. -- Darren -- Darren Hart Intel Open Source Technology Center Yocto Project -

Hi all, This is the weekly test report for Yocto 20110412 build. There are 2 new BLOCK issues for BSP testing, that all meta-intel BSP build failed on autobuilder, reported as bug 976 and 978.

Hi all, This is latest Yocto bug trend chart for WW16. There are 2 BLOCK bugs for BSP build on autobuilder. The open bug number is 182, which is the highest during last 3 months. Best

;-) Done OK Done Great. So now, whenever someone says "someday I'm going to..." we need to point them to the wiki. We really need yoctobot on #yocto :-) Oh! Hah... guess I should add that to

I think my descriptions are more confusing than my intent. Evidently I have not had enough coffee yet today. I'll try to summarize more betterly: - the text that starts "When adding tasks..." and

Cleaned-up, improved, etc. The page currently contains 3 tasks/projects: 1) Document undocumented variables according to bbvars.py 2) Rewrite bbvars.py to use bitbake to find variables 3) Modify

Maybe I'm the one who is confused. Looking at the contents of the Janitors page - I expected to see a list of existing things that need to be cleaned up. The most visible thing on the page is the