The TI page lists the blaze as having a wilink module on it which lists having a two way FM module. Your plughw:0,1 looks like the emitor for the board.
On 18 August 2011 12:49, sarika baby <sarikababy...@gmail.com> wrote: > Hello, > Thanks for youre reply, but on my board there are many audio devices like > FM, bluetooth, headset, speaker etc... > actually in one of the header files for my BLAZE board it was mentioned > > #define MM_DEFAULT_DEVICE "plughw:0,0" > #define BLUETOOTH_SCO_DEVICE "plughw:0,0" > #define FM_TRANSMIT_DEVICE "plughw:0,0" > #define FM_CAPTURE_DEVICE "plughw:0,1" > #define MM_LP_DEVICE "hw:0,6" > #define HDMI_DEVICE "plughw:0,7" > > so here can i change #define FM_CAPTURE_DEVICE "plughw:0,1" to #define > FM_CAPTURE_DEVICE "plughw:0,4" and still get the things working well. > > I am not able to understand that does "plughw:0,1" decide the audio path? > > > Thanks in advance for your reply. > Regards > Sarika > > > On Thu, Aug 18, 2011 at 12:34 PM, Radu Iscu <linke...@gmail.com> wrote: > >> A summary search yielded this: >> http://www.suse.de/~mana/alsa090_howto.html >> >> (do an in page search for plughw) >> >> the following bits seemed relevant: >> >> /* Name of the PCM device, like plughw:0,0 */ >> /* The first number is the number of the soundcard, */ >> /* the second number is the number of the device. */ >> char *pcm_name; >> >> /* Init pcm_name. Of course, later you */ >> /* will make this configurable ;-) */ >> pcm_name = strdup("plughw:0,0"); >> >> Given the fact that you are working with an embedded system I think that >> it's safe to assume that this is the only available sound device. >> >> Good luck, Iscu. >> >> On 17 August 2011 08:55, sarika baby <sarikababy...@gmail.com> wrote: >> >>> Hello, >>> I am not sure if this would be the rite place to post my doubt, >>> Actually i am working on ALSA (Blaze board), i am not able to >>> understand how the set the various audio paths using ALSA. >>> In the alsa files in mydroid folder, >>> "mydroid/hardware/ti/omap3/modules/alsa/ " there are files dealing with ALSA >>> where they are using "plughw:0,0" kind of terminology for few of the devices >>> like FM, Bluetooth etc...Can anyone explaind what actually "plughw:0,0" term >>> means.... >>> >>> Thanks in advance for ur help >>> >>> Sarika >>> >>> On Tue, Aug 9, 2011 at 1:06 AM, Chris Stratton <cs07...@gmail.com>wrote: >>> >>>> On Monday, August 8, 2011 2:10:16 PM UTC-4, Anil wrote: >>>>> >>>>> I work for an OEM and am trying to implement an idea - to log all >>>>> inputs (keystrokes, >>>>> text field input, browser tests including Javascript, plugging/ >>>>> unplugging SD card etc.) by the testers to have a set of trails that >>>>> would be useful. I want to do a custom build. >>>>> So I am trying to figure out the minimal set of points in the >>>>> framework code at which I can log "this text was input", "this key was >>>>> pressed". Does such a tool to log trails already exist? >>>>> >>>> >>>> Two "choke points" I can think of would be that it likely comes from two >>>> kernel drivers (physical buttons and touches) and most likely at some point >>>> all goes through Binder (though in a very implementation-private manner). >>>> It may be better to really understand and instrument each mechanism in the >>>> framework code though. >>>> >>>> Converting touch coordinates to drawn controls is going to be tricky - >>>> for those drawn using framework widgets it's possible, but there's nothing >>>> to keep an app from doing its own coordinate-to-button conversion. For >>>> games based on physics engines I'd expect a lot of that. >>>> >>>> -- >>>> unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> website: http://groups.google.com/group/android-porting >>>> >>> >>> >>> >>> -- >>> SarikA >>> >>> -- >>> unsubscribe: android-porting+unsubscr...@googlegroups.com >>> website: http://groups.google.com/group/android-porting >>> >> >> >> >> -- >> Radu Iscu >> Tel: 0742082607 >> >> > > > -- > SarikA > > -- Radu Iscu Tel: 0742082607 -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
