Fixes [BUGID #488 #734]
Enable audio for qemux86/qemux86-64 via the following kernel
configuration options.
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_
Richard/Saul,
This Fixes [BUGID #488 #734]
As discussed, this enables the configuration options for qemu
audio for x86/x86-64 (limited to this for now). I did build and
boot testing (but couldn't directly test audio) for the impacted
qemu boards.
The commit message from the patch tells the rest
>
> > Path 2: ADT installer (Not ready yet). Most code should be reused for
> > the above two path. I think.
> The symlinks are created.
>
> One gotcha for ADT installer testing is, please completely delete the
> toolchain that installed from the toolchain tar ball under /opt/poky.
> Since
> the
Is there a simple way to set a root password in the images that are
created?
I'm currently using sed in a .bbappend to edit the root entry in the
password file, but this doesn't 'feel' right !
Chris Tapp
opensou...@keylevel.com
www.keylevel.com
__
a. Which architecture you chose in step 3.
I used poky-image-sato.
b. How easily you were able to build an image and boot an image.
I did it quite easily.
- I installed the environment on an Ubuntu Desktop. I just copy/paste the
command given by the Yocto Quick Start in a Termina
> Path 2: ADT installer (Not ready yet). Most code should be reused for
> the above two path. I think.
The symlinks are created.
One gotcha for ADT installer testing is, please completely delete the
toolchain that installed from the toolchain tar ball under /opt/poky. Since
the toolchain tar
How do I get v86d in to my rootfs image?
I'm building using my own machine.conf (LX800) and I've got a
v86d_0.1.9.bbappend file so I can add compatibility for it:
COMPATIBLE_MACHINE_LX800 = "LX800"
The LX800.conf machine file has:
MACHINE_ESSENTIAL_EXTRA_RDEPENDS = "v86d"
v86d builds ok an
Hiļ¼Jessica
Thanks!
And I am now writing a script for automating our toolchain test.
Currently: Test input
1) Test_image (meta-toolchain tarball, target rootfs tarball, adt_installer
tarball)
2) Test_project (cvs, Sudoku, iptables for libtools)
Test area
Path 1: old meta-toolchain testing
1) un