<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>2868</bug_id>
          
          <creation_ts>2012-07-31 13:53:30 +0000</creation_ts>
          <short_desc>amixer missing from e-Menlow sato image</short_desc>
          <delta_ts>2012-08-08 07:01:45 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>BSPs</product>
          <component>bsps-meta-intel</component>
          <version>1.3</version>
          <rep_platform>E-Menlow</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>INVALID</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Undecided</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Alexandru Georgescu">alexandru.c.georgescu</reporter>
          <assigned_to name="Nitin Kamble">nitin.a.kamble</assigned_to>
          <cc>jiajun.xu</cc>
    
    <cc>tom.zanussi</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>23654</commentid>
    <comment_count>0</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-07-31 13:53:30 +0000</bug_when>
    <thetext>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#</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23672</commentid>
    <comment_count>1</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-07-31 16:51:12 +0000</bug_when>
    <thetext>Is amixer supposed to be installed on all sato images?

Emenlow doesn&apos;t have an alsa-state recipe - it should probably be added (see n450 for an example).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23699</commentid>
    <comment_count>2</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-08-01 08:56:05 +0000</bug_when>
    <thetext>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 &apos;Master&apos;,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 &apos;Mic&apos;,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 &apos;Mic Boost&apos;,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 &apos;Capture&apos;,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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23708</commentid>
    <comment_count>3</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-08-01 11:33:01 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23709</commentid>
    <comment_count>4</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-08-01 11:47:25 +0000</bug_when>
    <thetext>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 += &quot;tools-testapps&quot;


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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23710</commentid>
    <comment_count>5</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-08-01 11:49:57 +0000</bug_when>
    <thetext>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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23727</commentid>
    <comment_count>6</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2012-08-02 04:04:09 +0000</bug_when>
    <thetext>(In reply to comment #5)
&gt; Jiajun, Tom,
  Do you know how this kind of testing is done? Do QA build
&gt; their own images? or they only test core-image-sato-sdk images?

 Alex, you
&gt; 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 &quot;image profile&quot; for each test case in testlink, by indicating which image profile we should use.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23729</commentid>
    <comment_count>7</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-08-02 04:06:58 +0000</bug_when>
    <thetext>Alex,
 then you should not be testing core-image-sato for these BSPs.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23879</commentid>
    <comment_count>8</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-08-08 07:01:45 +0000</bug_when>
    <thetext>I have set it to verified - invalid</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>