Am 28. Mai 2013 04:54:52 schrieb Arun Raghavan
<[email protected]>:
> - For setting up the mixer, I'll try to talk to the Android HAL layer.
> Mixer controls vary a lot between hardware, so making a bridge to >
Android here would likely save us work in the long run. (This is the > most
uncertain part.)
IMO, this is good for short-term porting effort, but not that great in
the longer term. The Android HAL is an abstraction on top of another
abstraction (UCM/XML config). To my mind, it makes more sense to use UCM
here. Or if the UCM folks prefer the newer XML format, we could look at
that as well.
I think the android Hal isn't stable at all so possibly you end up with
code for each major android version or even each vendor / custom ROM
(phone specific).
Another question, is the Hal API defined somewhere or does it require
reverse engineering?
However, since part of your goal is to have PA usable on devices without
a large porting effort, maybe having this option isn't bad. My main
worry is code clutter.
Just as a thought, do you know if we're clear, license-wise, to load
binary blob HALs? Particularly the ones that aren't
tinyalsa/tinyhal-based.
_______________________________________________
pulseaudio-discuss mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
