as it is, if someone new to yocto checks out the git tree and sees the documentation/ directory, they'll immediately hop in there, see the possible manuals and perhaps run "make" to try to build them,

Thanks for noting this. What happens when we release software is that the manuals are released as well. The released manuals become the "current" version of the manuals. Any bugs or errors with the

It uses syslinux which only works on IA32? Cheers, Richard

Hi Tom, I saw in initramfs-live-install_1.0.bb recipe, there is a line to set the COMPATIBLE_HOST: COMPATIBLE_HOST = "(i.86|x86_64).*-linux" But actually initramfs-live-install is set as dependency

On Wed, 29 Feb 2012 03:02:35 +0000, "Nicholson, Andrew" <andrew.nicholson@...> wrote: I'm working through the experience for someone new to embedded Linux development to use the Yocto Project,

I'm working through the experience for someone new to embedded Linux development to use the Yocto Project, and I believe I found a problem with the current quick start manual. I followed the

Done. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

Looks good. I have the same fix that I didn't get around to pushing today. I assume you'll push this into the layer ? Bruce

i understand that reasonably well, and i'll make one more observation, then i'll shut up. i cloned the meta-ti layer into my yocto clone, and here's the majority of the meta-ti README: =====

Several unquoted variables assignments are now resulting parse errors. Correct them throughout meta-kernel-dev. Signed-off-by: Darren Hart <dvhart@...> CC: Tom Zanussi

I'm not 100% up on the progress on the TI layers, but as far as I know, your description above is a goal. meta-ti works on top of oe-core and with other layers (i.e. angstrom) to produce what

No, the amount of testing is not the difference, the amount of support for the board is. Meta-ti supports the camera interfaces, 3d engine, dsp, crypto engines, expansion boards, etc. Meta-yocto lacks

ok, that's perfectly reasonable -- meta-yocto provides a generic, well-tested product, while the meta-ti layer provides more leading-edge content, correct? which is a perfectly

It is true that the beagleboard is a hardware reference board in the yocto consolidated kernel tree and meta-yocto layers. That means that it gets the yocto standard QA builds and boot testing. That

i asked this on the beagle list, and koen pointed out that it was probably more appropriate elsewhere (probably here). what's the proper algorithm for building the leading-edge images for a beagle

Attendees: Scott R, Jeremy, Michael H, Matthew, Tom, Jeff, Darren, Sean, Beth, Richard, Jessica, Paul, Belen, Dave, Josh, Bruce. Message to the team: - Please take a look at the task board, move

On 27/02/2012 17:07, Khem Raj wrote: Hi Raj Thank you for your reply - this seems to have resolved my issue. Can you let me know if there is a correct way to build gdbserver

Hmm, previously we use the taskdata is to reduce the time for building up the dependency tree. It seems that we will have to use runqueue to determine the dependency. Thanks, Dongxiao

Thanks - the issue is restricted to Edison so far as I can tell so the bug has been marked thus. This is definitely a bug but not preventing you from installing the ADT. I've created a patch for this

Ok. I sent a new pull request after removing the merge line. Thanks Kishore.