IMAGE USED: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120730-2/machines/emenlow/core-image-sato-emenlow-20120730042252.hddimg root@emenlow:~/abat# amixer -sh: amixer: command not found root@emenlow:~/abat#
Is amixer supposed to be installed on all sato images? Emenlow doesn't have an alsa-state recipe - it should probably be added (see n450 for an example).
With the image built from the code of the denzil branches, I am seeing root@emenlow:~# find / | grep amixer /var/lib/opkg/info/alsa-utils-alsamixer.list /var/lib/opkg/info/alsa-utils-alsamixer.control /var/lib/opkg/info/alsa-utils-amixer.control /var/lib/opkg/info/alsa-utils-amixer.list /usr/bin/amixer /usr/bin/alsamixer root@emenlow:~# amixer Simple mixer control 'Master',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 17 [55%] [-21.00dB] [on] Front Right: Playback 17 [55%] [-21.00dB] [on] Simple mixer control 'Mic',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 0 [0%] [-34.50dB] [off] Front Right: Playback 0 [0%] [-34.50dB] [off] Simple mixer control 'Mic Boost',0 Capabilities: volume penum Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 3 Front Left: 0 [0%] [0.00dB] Front Right: 0 [0%] [0.00dB] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch penum Capture channels: Front Left - Front Right Limits: Capture 0 - 31 Front Left: Capture 16 [52%] [12.00dB] [on] Front Right: Capture 16 [52%] [12.00dB] [on] I will try same with the master branch also. Nitin
Is amixer supposed to be installed ONLY on the SATO SDK images? I tried also on the crownbay (NON SDK) image and amixer is not present there either. Thanks, Alex.
As learnt from Tom I always add this line to local.conf before building for the core-image-sato images to be tested. and it gets all the test tools including amixer. EXTRA_IMAGE_FEATURES += "tools-testapps" this is with the latest master: root@emenlow:~# uname -a Linux emenlow 3.4.4-yocto-standard #1 SMP PREEMPT Tue Jul 31 02:37:01 PDT 2012 i686 GNU/Linux root@emenlow:~# which amixer /usr/bin/amixer
Jiajun, Tom, Do you know how this kind of testing is done? Do QA build their own images? or they only test core-image-sato-sdk images? Alex, you should have a knowledge transfer session with Jiajun. Nitin
(In reply to comment #5) > Jiajun, Tom, Do you know how this kind of testing is done? Do QA build > their own images? or they only test core-image-sato-sdk images? Alex, you > should have a knowledge transfer session with Jiajun. Nitin Hi all, We used to only test sato-sdk images for most real hardware. In the test plan, we define which image profile will be validated for each hardware. Please have a check at https://wiki.yoctoproject.org/wiki/Yocto_1.3_Overall_Test_Plan. And you could also find a field named "image profile" for each test case in testlink, by indicating which image profile we should use.
Alex, then you should not be testing core-image-sato for these BSPs.
I have set it to verified - invalid