Wind River's ALSA code is now available in platform/hardware/ alsa_sound.git and external/alsa-lib.git.
Michael. On Nov 15, 4:09 am, Yann Neveu <[EMAIL PROTECTED]> wrote: > Hi all an particulary Sean, > I'm trying to compile tree with Sean's freerunner patches. > I'm still lacking the libaudio. Is the Wind River's one available > somewhere? > > On Nov 12, 6:55 am, Maxime Petazzoni <[EMAIL PROTECTED]> > wrote: > > > Thanks for your answers. It's nice to know that we'll have an > > available reference ALSA backed libaudio to use with Android. I'm > > looking forward to seeing this submitted. Please keep us posted Sean! > > > On 11 nov, 21:23, "Misael Lopez" <[EMAIL PROTECTED]> wrote: > > > > I have been working in that audio interface for ALSA in OMAP > > > processor, you can find our tree at: > > > >http://git.omapzoom.org/?p=android/hardware/ti/omap3.git;a=summary > > > > We have been successfully played and capture audio using TWL4030 chip > > > in OmapZoom board with that current version of the interface. > > > I'm working on bringing the control part, probably we can have that > > > part ready soon. It will be great if the community collaborates to > > > correct/improve current code. > > > You can find more information atwww.omapzoom.org, particularly about > > > Android if you go to Projects->Android on OMAPZoom. > > > > Misa > > > > 2008/11/11 Sean McNeil <[EMAIL PROTECTED]>: > > > > > 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 ! > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
