Correct. I'm hesitant to say this, but I'm hoping to have the bug fixed and patch submitted by the end of this week. Hopefully I haven't just jinxed myself. :) Scott -- Scott Garman Embedded Linux

If you want to put the image on a hard drive use the .ext3 image and follow the "how do I" on the wiki at: https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_put_Yocto_on_a_hard_drive.3F Jim

On Tue, May 22, 2012 at 1:04 PM, Scott Garman <scott.a.garman@...> wrote: So if I read this right, I don't need any route or bridge commands to make this work. If the bug gets fixed runqemu qemux86

There is some sort of routing or IP forwarding bug in the sato images that is due to be fixed soon. One thing I've found is you can actually get out to the internet for about 30 seconds or so

Yep, third time was the charm - applied cleanly and booted into sato without problem... Pulled into meta-intel/master. Thanks! Tom

On Tue, May 22, 2012 at 10:45 AM, Autif Khan <autif.mlist@...> wrote: I can see the tap0 interface on my host at 192.168.7.1 by using ifconfig. I can also see the eth0 on the qemu machine at

Yes, I am able to get networking to work out of the box (bitbake core-image-sato, etc.) Internetworking does not work out of the box. This is accomplished over tun/tap devices - I do not know much

when testing an image using runqemu qemux86, can you get networking to work?? mine comes up disabled. I want to test an application that requires Internet access. Jim A

You should *not* do this in your machine configuration. Machine configuration should only contain items that are machine-specific. This belongs in distro configuration, or in local.conf if you want

Hi Chris, You can either set it in local.conf as you have mentioned or you can define the variable in your machine conf. You can do something like this, require

I haven't sync'd lately. I'm using poky: f39ba520d6f2477c99839a92049b1bb279f092cf meta-intel: bde31fd7e66faea865d24ff0858a9006b89e4e54 Third time should be a charm. With kergoth's help, I think I

Agenda * Opens collection - 5 min (Song) * 1.2.1 update - 10 min (ScottG) * 1.1.2 update - 10 min (Josh) * Yocto 1.3 status - 10 min (Song/team) - 1.3 feature list:

When libraries are installed in ${libdir}/${BPN} we need to ensure that those libraries without version number end up in the -dev package. If not the error "ERROR: QA Issue: non -dev/-dbg/-nativesdk

Hello, I am trying to install an image of Yocto to my CRB (cedartrail). After creating the bootable usb with the new image on it as a usb-zip (because it is too large for the hdd method of install),

Yes it is. Forget that. We decided to use a single layer for both distros.

After seeing: I thought this was now 'the' meta-layer for the RPi. Is that not the case? It really would make sense for everyone to pull in the same direction. Chris

It is indeed. I'll work up a patch for this (doesn't look like a work-around causes any undue complications) -- ------------------------------------------------------------ Gary Thomas

If your distro is using make-3.82 than you need something like this http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=9c45467120d525a406fe8ec012c6231180c99767 to fix this race. (I

Strange. I just built the kernel and worked ok for me. I will give it a try tonight. On May 21, 2012 9:56 PM, "Gary Thomas" <gary@...> wrote:

That's about all there is - you can see the layer versions, it's breaking during the kernel install. Looks like there may be some package dependency that's missing - where does the