-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Keef Aragon wrote:
> Maybe I'll get more response having looked more closely at the code. At
> this point, I can get the alsa driver to set the pcap registers
> appropriately except for TX_AUD_AMPS AKA PCAP_INPUT_AMP. The necessary
> mask for making calls is defined as PCAP2_INPUT_AMP_V2EN2, but I don't
> see it being used anywhere. That is to say, I don't see a
> pcap2_codec_write where this could be specified. Is that correct?
Are you using the Baseband loopback pcm interface? I left code for
setting PCAP to talk to the baseband by opening the alsa pcm (3?) and
not writing to it. The code is still untested, so very likely you will
need to fix it on ezx-asoc.patch.
> I checked out the archive and found
>
> https://lists.openezx.org/pipermail/openezx-devel/2007-August/001408.html
>
> <https://lists.openezx.org/pipermail/openezx-devel/2007-August/001408.html>
> . I was looking at the driver in svn and can't figure out for
> the life of me how that worked. (Looks like there isn't even a
> write proc for /proc/pcap).
> Was ezx-pcap altered to remove this or is there another way to
> set pcap registers from userspace now?
I decided not to commit the proc interface for writing the PCAP
registers, because it is a huge security flaw, and I would encourage
developer laziness to not fix the asoc driver. ;)
It was just a proof of concept, and it worked at the time. I encourage
you to do it the right way, open the BP pcm, dont try to read/write
from/to it (you cant anyway), setup the speaker/mic audio path and
volume (with amixer), and send the ATD to make a call. In case it doesnt
work, cat /proc/pcap and compare the values with my email and send us a
fix for ezx-asoc.patch. ;)
- --
Daniel Ribeiro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHdk2kw3OYl0G0liQRApOdAJ9kPgqSRADKqCj5x0IP+7vpFp8oUACeJNvC
mQ0ITLMpZLyAIIoPy0nCwHA=
=0bIK
-----END PGP SIGNATURE-----
