On 19/10/2011 13:43, Rainer Koenig wrote:
Hi all,
I'm using yoctoproject since one week now and got the latest
yocto-1.1/edison-6.0 git tree. I have been able to build core-image-sato
for the Beagleboard xM rev. A and the image works fine.
Now my next goal is to build an image for the TI 8148
On 19/10/2011 14:01, Jack Mitchell wrote:
On 19/10/2011 13:43, Rainer Koenig wrote:
Hi all,
I'm using yoctoproject since one week now and got the latest
yocto-1.1/edison-6.0 git tree. I have been able to build core-image-sato
for the Beagleboard xM rev. A and the image works fine.
Now my next
On 10/19/2011 5:43 AM, Rainer Koenig wrote:
Hi all,
I'm using yoctoproject since one week now and got the latest
yocto-1.1/edison-6.0 git tree. I have been able to build core-image-sato
for the Beagleboard xM rev. A and the image works fine.
Now my next goal is to build an image for the TI
I'm booting using the rootfs produced by bitbake as in initrd. This
works nicely and gives a read-only boot device and a system that runs
from RAM.
What I want to do now is allow changes to be made to some files (e.g.
network configuration) and have these saved on the boot device so that
On Wed, Oct 19, 2011 at 2:50 PM, Chris Tapp opensou...@keylevel.com wrote:
I'm booting using the rootfs produced by bitbake as in initrd. This works
nicely and gives a read-only boot device and a system that runs from RAM.
What I want to do now is allow changes to be made to some files (e.g.
