2007/11/13 Kalle Vahlman <[EMAIL PROTECTED]>:
> 2007/9/30, Kalle Vahlman <[EMAIL PROTECTED]>:
>> (grabbing this moldy thread up since the full answer is still open)
>>
>> 2007/5/7, Stefan Kost <[EMAIL PROTECTED]>:
>> > hi,
>> >
>> > the sources are there:
>> >
>> > <http://repository.maemo.org/pool/bora/free/source/gst-plugins-dsp0.10_0.65-1.tar.gz>
>> >
>> > Stefan
>>
>> Yes, for the plugins. But unfortunately I see nowhere the
>> osso-dsp-headers-rx-34 package which would be pretty essential if you
>> wanted to compile the plugins and not just ogle at the code.
>
> Just to note, this situation seems to be changed in Chinook.
>
> Now the missing package is osso-dsp-headers-rx-44 instead of -34.
>
> You can apparently build the plugins without the headers now too, but
> the result is a dummy version that talks to /dev/zero instead of the
> dsp tasks.
>
> So not a lot of improvement there, which is a bit sad.

*blows dust from the thread*

Some other people managed to be more persuasive elsewhere[1] and now
the headers are there and you actually can build a working set of the
dsp plugins yourself.

Nice to see progress happening!

Since the osso-dsp-loader and the GStreamer DSP plugins are now
buildable and usable, all you need to do is copy the DSP kernel, the
DSP tasks and the configs (ie. /lib/dsp) from ITOS and voilĂ , you have
working DSP decoders/encoders and pcm output for
$YOUR_FAVOURITE_NON-ITOS_ROOTFS.

It would be only too cool to have the kernel and DSP tasks in a
distributable form instead of binaries copied from existing system.
Technically you'd only need the pcm tasks for audio output, decoding
can always happen on the ARM side. But well, this is already a vast
improvement over the previous situation.


[1] https://bugs.maemo.org/show_bug.cgi?id=2271

-- 
Kalle Vahlman, [EMAIL PROTECTED]
Powered by http://movial.fi
Interesting stuff at http://syslog.movial.fi
_______________________________________________
maemo-developers mailing list
[email protected]
https://lists.maemo.org/mailman/listinfo/maemo-developers

Reply via email to