However, the Pi has hardware support for these via its GPU and AFAIK directly exposes it through OpenMax, we only have a generic DSP which needs a kernel module on its own to be of any use, using codecs this way requires a little bit more than just supporting a generic interface.What *should* work out for us is that the DM3730 in the 1Ghz Pandora has TI codecs available for many many codecs.
However, the Pi has hardware support for these via its GPU and AFAIK directly exposes it through OpenMax, we only have a generic DSP which needs a kernel module on its own to be of any use, using codecs this way requires a little bit more than just supporting a generic interface.What *should* work out for us is that the DM3730 in the 1Ghz Pandora has TI codecs available for many many codecs.
There is, however, some kind of GStreamer module that is supposed to work with TI's DSP codecs.
Same SOC? What are you talking about? The Raspberry Pi is using an ARMv6 Processor while we have an ARMv7. The only likeness to a Pi is that both are using an ARM Processor. Also the DSP chips are totally different chips.However, the Pi has hardware support for these via its GPU and AFAIK directly exposes it through OpenMax, we only have a generic DSP which needs a kernel module on its own to be of any use, using codecs this way requires a little bit more than just supporting a generic interface.What *should* work out for us is that the DM3730 in the 1Ghz Pandora has TI codecs available for many many codecs.
There is, however, some kind of GStreamer module that is supposed to work with TI's DSP codecs.
So the Pandora's DSP is wired differently than the Pi's? How can that be when it's the same SoC? I would have thought we could just about drop a Pi image on an SD card and make it work (granted all the 'outside' stuff probably would need work).
And ya, GStreamer has been heavily supported by TI. As far as XBMC goes though, the Pi XBMC should work with accel if we can provide an equivalent OS/modules environment for it to run in shouldn't it? I remember way back there was an issue with using the DSP because RAM needed to be set aside for it and there wasn't enough. But then that was back with the OMAP, so perhaps not relevant for the 1Ghz ones?
Same SOC? What are you talking about? The Raspberry Pi is using an ARMv6 Processor while we have an ARMv7. The only likeness to a Pi is that both are using an ARM Processor. Also the DSP chips are totally different chips.However, the Pi has hardware support for these via its GPU and AFAIK directly exposes it through OpenMax, we only have a generic DSP which needs a kernel module on its own to be of any use, using codecs this way requires a little bit more than just supporting a generic interface.What *should* work out for us is that the DM3730 in the 1Ghz Pandora has TI codecs available for many many codecs.
There is, however, some kind of GStreamer module that is supposed to work with TI's DSP codecs.
So the Pandora's DSP is wired differently than the Pi's? How can that be when it's the same SoC? I would have thought we could just about drop a Pi image on an SD card and make it work (granted all the 'outside' stuff probably would need work).
And ya, GStreamer has been heavily supported by TI. As far as XBMC goes though, the Pi XBMC should work with accel if we can provide an equivalent OS/modules environment for it to run in shouldn't it? I remember way back there was an issue with using the DSP because RAM needed to be set aside for it and there wasn't enough. But then that was back with the OMAP, so perhaps not relevant for the 1Ghz ones?
EDIT: Oh I think I know. You most propably mixed up the Raspberry Pi with the Beagleboard.