The AudioHardwareInterface abstraction layer allows for user space drivers. You need an implementation that matches your driver. Some want ALSA, some want OSS, still others want some proprietary interface with user space code that isn't required to be open sourced under GPL. By abstracting the audio interface, we aren't tied to a particular implementation.
On Dec 4, 6:49 am, Pivotian <[EMAIL PROTECTED]> wrote: > I am porting Android on S3c6410 and it contains wolfson wm8580 sound > chip and the ALSA driver for this is already written inside kernel, Do > i need to make any modification in the user space of android to > support sound or android will automatically detect the sound? I read > somewhere that Porting Android to other audio stacks (OSS, ALSA, > proprietary user-space audio libraries, etc.) requires inheriting from > and modifying AudioHardwareInterface to support the driver-specific > implementation. I am not able to understand what they were trying to > say, Can anybody put some light on this? --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
