View Single Post
Old 07-12-2012, 09:24 AM   #131
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Okay, instead of using the latest source code, I suppose I should use the PATCHED 1.0.13 version from the 2.5.8 and 3.3 GPL sourcecode.

Do I ALSO need another version for 5.x? The one in the 5.x GPL source code is 1.0.22, and appears to be UNPATCHED.

And 4.x does not even HAVE alsa code, so if I wanted to PWM sound out the power LEDs (green and yellow, for stereo), I do not know what alsa version to use.

Is there an alsa lib that I can static build which will work on all the kindles (except 4.x)?

---

With my current knowledge base, it would be easier (for me) to just pipe raw audio to the aplay app (not much different from calling eips to do eink updates), like I already did when piping from ffmpeg.

If we really DO need multiple app versions to work with different installed alsa lib version, piping to aplay would be a lot more "cross platform". Futzing with libraries hurts my brain, and a kindle OTA update could potentially break my sound apps.

Last edited by geekmaster; 07-12-2012 at 09:28 AM.
geekmaster is offline   Reply With Quote