So I would say if any of our documentation is out-of-date or unclear, it should be fixed, no deliberation needed :) However, in Poky master, README.hardware has now been updated to remove

A few things you will need.. a tune file for the CPU, and a tune file for the machine/bsp... and you'll have to make sure that eglibc/Linux can still run on that machine. I know a while back some

Excellent question, Jack - we are working on that this week. No promises, but highly likely!

Yup, I wrote then off the cuff, I am glad that a typo is the only error and no major missing steps :-) I am also glad that these steps worked for you. I have not. I am not sure I should. I am not

This worked fine for me. one typo in step (5) ext3 and not text3, but these are good instructions. How do we get them put into the README.hardware instead of the directdisk section that doesn't work

I have been using core-image-sato and core-image-sato-sdk on the hard disk on Intel Atom (crownbay in my case). I perform the following broad steps: 1) have a suitable partition on the disk - say

Hi, In oe-classic there used to be a machine configuration for an i486sx based machine called vortex86sx. In the past I was successful in building a running image for such a target. Since I'd like to

If you make FOSDEM (www.fosdem.org), Paul Eggleton is talking in the Embedded room about Yocto and

On 19/01/12 19:41, Jeff Osier-Mixon wrote: Hi Jeff, Would there be any chance of having these talks recorded? They sound fantastic but unfortunately I work for a small

The README.hardware file in the poky directory talks about creating images on 2 types of disk for the Atom based PCs like the n450. The one I've successfully tested is the core-image-sato on a USB

Great planning session, kernel team! Thanks for prioritizing and cleaning up the schedule. At the same time, if anyone gets time to work on any items moved to post 1.2, it's always a great thing to

Bruce, please apply to linux-yocto-3.0/yocto/standard/base Upstream-Status: Accepted (Linux 3.3) If the MAC is invalid or not implemented, do not abort the probe. Issue a warning and prevent

I'll test this out and see. I'm plan on keeping this system on a UPS anyway. Jim S

Keep Tuesday, February 14, open. That is the day before the Embedded Linux Conference in Redwood Shores, CA, and it is also the day of the first Yocto Project Developer Day, a full-day opportunity to

You may be able to improve upon that with the following in /etc/fstab: /dev/md0 /build ext4 noauto,noatime,nodiratime,commit=6000 0 2 This reduces the number of writes due to updated access

This looks pretty important to me. Can you create a bug report for this Jim? It may be decided that it is a dup of the one Darren already pointed to but I would like to see someone prove that. It

Hi all This is the fullpass test report for Yocto 1.2 M2 RC1 build. There are 9 new bugs found for this build. A new crownbay image has been built out with Tom’s fixing patches. QA has finished

After reading the comments in the local.conf file about the download directory (DL_DIR), I experimented with creating it outside of the normal <build dir> directory used by "source oe-init-build-env

On 01/18/2012 04:34 PM, Darren Hart wrote: Learned a few things in this process. I appreciate all the help and advice. So we know that at least with Edison, btrfs does not work

When: Occurs every Tuesday from 8:00 AM to 9:00 AM effective 1/10/2012 until 6/19/2012. There are 22 more occurrences. (UTC-08:00) Baja California Where: Bridge Info