hi Max

  have you find the answer?
  how "/dev/eac" is connected with host linux's sound system?
  I am trying to add my own device driver to android



On Apr 18, 4:02 pm, max <max.xi...@gmail.com> wrote:
> Hi David,
>
> Thanks for your reply.
>
> When I study the code in frameworks\base\libs\audioflinger
> \AudioHardwareGeneric.cpp, I saw it does open the device node "dev/
> eac" to get a File descriptor. Therefore , the question is how "/dev/
> eac" is connected with the host linux's sound system. I have read the
> code in external/qemu/hw/goldfish_audio.c, but I still can not figure
> out how the device node "/dev/eac" in emulator's linux system is
> connected with host linux's sound system.
>
> Thanks
>
> On Apr 17, 5:48 pm, David Turner <di...@android.com> wrote:
>
>
>
> > On Fri, Apr 17, 2009 at 10:51 AM, max <max.xi...@gmail.com> wrote:
>
> > > Hi Buddies,
>
> > > I wanna get understood that why in emulator "dev/eac" is the device of
> > > audio,
>
> > historical reason, but mostly because that's what the emulator-specific
> > kernel supports
>
> > > as I know, in external/qemu/audio, there is all kinds audio drivers,
> > > such as oss, alsa,
>
> > these are only used to send audio output to the host sound system, this has
> > nothing
> > to do with what is supported in the emulated system. These are not 'drivers'
> > by the way,
> > just usual call to sound libraries / system interfaces
>
> > you can have a look at external/qemu/hw/goldfish_audio.c to see the code
> > used to
> > support sound hardware emulation in Android
>
> > > but I am very curious why in the android linux system, the "dev/eac"
> > > is connected with those drivers.
>
> > > Anybody can give me some light on that?
>
> > > Max- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to