Difference between revisions of "BeagleBoard/DSP Clarification"

From eLinux.org
Jump to: navigation, search
(dsp-bridge: Some reverts and more explanations)
(Improve references)
Line 19: Line 19:
 
It is probably not production ready, and it still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.
 
It is probably not production ready, and it still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.
  
Unfortunately there's a disagreement between TI and the community as how power management must be handled, so there are two forks: linux-omap, and omapzoom.<ref name="mcgill.ca">{{cite web|url=http://marc.info/?l=linux-omap&m=123626584228670&w=2|title=Different power management thread}}</ref>. TI is also working with the community on the linux-omap-pm branch maintained by Kevin Hillman.
+
Unfortunately there's a disagreement<ref name="mcgill.ca">[http://marc.info/?l=linux-omap&m=123626584228670&w=2 Different power management thread]</ref> between TI and the community as how power management must be handled, so there are two forks: linux-omap, and omapzoom. TI is also working with the community on the linux-omap-pm branch maintained by Kevin Hillman.
  
 
It's under heavy development, the linux-omap tree was originally maintained by Hiroshi DOYU, but now Ameya Palande took over.
 
It's under heavy development, the linux-omap tree was originally maintained by Hiroshi DOYU, but now Ameya Palande took over.
Line 39: Line 39:
 
See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.
 
See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.
  
= Interesting threads =
+
== References ==
 +
<references/>
 +
 
 +
== Interesting threads ==
  
 
* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
 
* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
 
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]
 
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

Revision as of 00:10, 8 May 2009

This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on BeagleBoard), how they are similar and different.

dsp-gateway

DSP Gateway was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

dsp-bridge

tidspbridge originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It is probably not production ready, and it still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

Unfortunately there's a disagreement[1] between TI and the community as how power management must be handled, so there are two forks: linux-omap, and omapzoom. TI is also working with the community on the linux-omap-pm branch maintained by Kevin Hillman.

It's under heavy development, the linux-omap tree was originally maintained by Hiroshi DOYU, but now Ameya Palande took over.

There are plans to share the mailbox and iommu that the dsp-gateway uses (which are part of the omap platform) as well as to move parts of it to user-space. However, TI argues the platform code is missing features from tidspbridge.

There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.

For documentation and project overview, visit: TI DSP/Bridge project

dsp-link

A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.

It is the one farther from meeting Linux standards. The code hasn't even been submitted for reviewing nor is planned to to be merged at any time.

It's tightly tied to CodecEngine and DMAI, and there are GStreamer plug-ins provided by TI to use the algorithms.

See DSPLink articles in Texas Instruments Embedded Processors Wiki, too.

References

  1. Different power management thread

Interesting threads