Hi Daniel, Could you paste or send me your asound.conf file? I am having the same WM9713 codec and I have no idea how to get the correct values such as type and card name for the AndroidPlayback device. Could you tell me how you found that?
Thanks. Reed On Dec 16 2008, 6:56 pm, "Daniel Youn" <youn.dan...@gmail.com> wrote: > Hi, Gougou > > I've checked /dev and /dev/snd directory. > There is PCMC0D0 and other device files in /dev not in /dev/snd. > > It is curious, because a few days ago, I've patched > system/core/init/devices.c file with this command: > > >> repo download platform/system/core 4432/2 > > But system/core/init/devices.c file actually didn't modified at all. ( I > don't know why ) > > So, I manually modified system/core/init/devices.c file. > > And this time, PCMC0D0 and other device files located in /dev/snd. > > As a result, now I can here sound on my android. :) > > Thanks for advice. > > Regards. > Daniel Yun. > > On Tue, Dec 16, 2008 at 11:44 AM, gougou <zqy2000...@gmail.com> wrote: > > > Can you check your audio device files (like PCMC0D0 )in /dev/snd > > or /dev > > > If sb get the error: no such device, please check the alsa-lib > > ---------- alsa-lib-1.0.13/include/config.h > > > #define ALSA_DEVICE_DIRECTORY "/dev/" > > > The old device path is /dev > > if Andriod has below update, this value need to be /dev/snd > > > On 12月15日, 下午1时16分, "Daniel Youn" <youn.dan...@gmail.com> wrote: > > > Hi, gougou > > > I am also using WM9713 codec but I can't get sound driver working. > > > > After reading this mailling list, I've check the following: > > > > 1) get source for /platform/external/alas-lib > > > 2) get source for /platform/hardware/alsasound > > > 3) modified BoardConfig.mk like this > > > > #HAVE_HTC_AUDIO_DRIVER := true > > > #BOARD_USES_GENERIC_AUDIO := true > > > BOARD_USES_ALSA_AUDIO := true > > > > 4) add sample asound.conf file to /platform/system/core/rootdir/etc/ > > > > But, when the system starts up, there's some infinite loop like this log > > > > >> I/ServiceManager( 42): Waiting for sevice media.audio_flinger... > > > > and the cause is this log > > > > >> E/AudioHardwareALSA( 123): Unable to attach mixer to device > > > > AndroidPlayback: No such file or directory>> E/AudioHardwareALSA( 123): > > Unable to attach mixer to device default: No > > > > such file or directory>> E/AudioHardwareALSA( 123): Unable to attach > > mixer to device > > > > AndroidRecord: No such file or directory>> E/AudioHardwareALSA( 123): > > Unable to attach mixer to device default: No > > > > such file or directory > > > > Do you guys have any idea, what's wrong? > > > Thanks for help in advance. > > > > On Fri, Dec 12, 2008 at 3:45 PM, gougou <zqy2000...@gmail.com> wrote: > > > > > Hi Yang > > > > > I am using WM97xx codec and has it's ALSA driver worked. > > > > And I also integrated the alsa-lib into my source. Now the audio > > > > working fine. > > > > > But the only thing I wanna know is : > > > > How the asound.conf work and How to write this file. Now I skip this > > > > config file and wite the configurations directly into my hardware. > > > > Thanks > > > > > PS: > > > > If sb get the error: no such device, please check the alsa-lib > > > > ---------- alsa-lib-1.0.13/include/config.h > > > > > #define ALSA_DEVICE_DIRECTORY "/dev/" > > > > > The old device path is /dev > > > > if Andriod has below update, this value need to be /dev/snd > > > >http://review.source.android.com/r/e2ff04fb6804 > > > > > On 11月26日, 下午5时09分, "Yang, Xiaopeng" <xiaopeng.y...@windriver.com> > > > > wrote: > > > > > Hi Maxime, > > > > > > The ALSA contribution from Wind River includes alsa-lib and > > > > > libaudio-alsa libraries, along with other patches for bionic and > > > > system/core. > > > > > > Because alsa-lib and libaudio-alsa are new projects, they have been > > sent > > > > to > > > > > Google for integration, and may be available in the repositories > > soon. > > > > > > The other modifications on bionic and system/core have been submitted > > to > > > > > Gerrit for review: > > > > > > -------------------------------------------- > > > > > [OK ] bionic/ defaulthttp:// > > > > review.source.android.com/r/fad1668b10d5 > > > > > (as xiaopeng.y...@windriver.com) > > > > > > [OK ] system/core/ defaulthttp:// > > > > review.source.android.com/r/e2ff04fb6804 > > > > > (as xiaopeng.y...@windriver.com) > > > > > > After above projects and patches have been integrated into andorid, > > you > > > > can > > > > > build android images with ALSA support. To that end, there are > > still > > > > two > > > > > things need to do: > > > > > > 1. A /etc/asound.conf is required for ALSA to work. Attached patch > > adds a > > > > > sample asound.conf for zoom board, copy this sample file to > > > > > system/core/rootdir/etc/asound.conf and make necessary changes to it > > > > > according to your hardware. > > > > > > 2. Add the following line into the BoardConfig.mk of your board: > > > > > > BOARD_USES_ALSA_AUDIO := true > > > > > > then rebuild android to see whether ALSA audio work. > > > > > > Regards, > > > > > Xiaopeng > > > > > > Maxime Petazzoni 写道: > > > > > > > Hi Sean, > > > > > > > Do you have more information to give us about when and how this > > code > > > > > > is going to be available? The implementation proposed down here by > > > > > > Misael looks nice too, but I'd like to have a peek about the code > > you > > > > > > used for the Freerunner, and more importantly how you used it. > > > > > > > Thanks in advance, > > > > > > - Maxime > > > > > > > On 12 nov, 05:42, Sean McNeil <seanmcne...@gmail.com> wrote: > > > > > >> Hi Maxime, > > > > > > >> Wind River is in the process of submitting an ALSA audio > > > > implementation. > > > > > >> That is what I use on the Openmoko Freerunner and what has been > > > > > >> successfully used on the TI OMAP Zoom reference platform. > > > > > > >> Maxime Petazzoni wrote: > > > > > >>> Hi, > > > > > >>> I believe most of the porting efforts on the various hardware > > > > platform > > > > > >>> will soon get to the point (if not already) of a running system ; > > the > > > > > >>> next step being making sure all the basic functionality is there. > > > > > >>> Audio being one of the most important one, since telephony also > > > > > >>> depends on it. > > > > > >>> Without anything done on that front, we're facing the "using > > stubbed > > > > > >>> audio hardware, no sound will be produced" warning message when > > > > Dalvik > > > > > >>> starts. > > > > > >>> From what I've read, Android relies on an hardware glue library > > > > > >>> libaudio, providing AudioFlinger with the appropriate > > AudioInterface > > > > > >>> implementation to output sound to whatever sound driver the > > hardware > > > > > >>> uses. For example, on the HTC G1/MSM72xx hardware platform, > > Google > > > > > >>> useshttp:// > > > > android.git.kernel.org/?p=platform/hardware/msm7k.git;a=summary > > > > > >>> But I think most of the Androids ports are made on hardware that > > have > > > > > >>> ALSA device drivers (OMAP for example). And before 20 different > > > > people > > > > > >>> start implementing their own libaudio bridging to ALSA, maybe we > > > > > >>> should coordinate this community effort. Starting by knowing if > > > > > >>> anything has already been started by someone, somewhere :) > > > > > >>> If not, I will most likely start working on one, and I foresee > > that > > > > > >>> it's going to be tough, as the only real documentation is the > > msm7k > > > > > >>> libaudio source code itself. > > > > > >>> Ideas, comments, suggestions ... and help are most welcome! > > > > > >>> - Maxime > > > > > >>> PS: of course, if you got audio working without going through > > this > > > > > >>> libaudio stuff, please share your discoveries ! > > > > > > sample_asound_conf.patch > > > > > 3K查看下载- 隐藏被引用文字 - > > > > > > - 显示引用的文字 -- 隐藏被引用文字 - > > > > - 显示引用的文字 - > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
