BeagleBoard/DSP Clarification - Revision history

Felipec: Add syslink

2010-09-08T11:37:57Z

Add syslink

Felipec: /* dsp-link */ add key differences

2010-09-08T11:30:34Z

‎dsp-link: add key differences

Felipec: No more to reference

2010-07-21T22:34:22Z

No more to reference

Felipec: Update mainly for tidspbridge

2010-07-21T22:33:59Z

Update mainly for tidspbridge

DavidSchleef: /* dsp-bridge */

2010-04-14T18:36:10Z

‎dsp-bridge

Hyc: update doc url

2009-10-12T21:05:45Z

update doc url

ChrisRing: Clarified a few DSP Link details, wordsmithing, added links

2009-07-01T02:48:08Z

Clarified a few DSP Link details, wordsmithing, added links

Felipec: /* dsp-bridge */ no valid reference for TI willing to use linux-omap pm

2009-05-14T23:30:45Z

‎dsp-bridge: no valid reference for TI willing to use linux-omap pm

Felipec: /* dsp-bridge */ Remove comments about stability.

2009-05-14T23:16:54Z

‎dsp-bridge: Remove comments about stability.

Felipec: /* dsp-gateway */ reword

2009-05-14T23:13:29Z

‎dsp-gateway: reword

← Older revision		Revision as of 11:37, 8 September 2010
Line 42:		Line 42:

	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.
		+
		+	== syslink ==
		+
		+	For OMAP4 a new consolidated bridge is being developed [http://omappedia.org/wiki/Syslink_Project syslink]. It's an evolution of previous IPC mechanisms, reusing elements such as iommu and mailbox, and incorporating ideas such as moving the module loading to user-space from dsp-gateway.
		+
		+	Unlike it's predecessors it's supposed to be upstreamed since the get-go, and in fact some patches are already integrated (in iommu and mailbox).

	== Interesting threads ==		== Interesting threads ==

← Older revision		Revision as of 11:30, 8 September 2010
Line 34:		Line 34:

	The kernel driver doesn't meet the Linux kernel coding conventions. The sources haven't been submitted for review, and it is not currently planned to be merged into upstream kernels.		The kernel driver doesn't meet the Linux kernel coding conventions. The sources haven't been submitted for review, and it is not currently planned to be merged into upstream kernels.
		+
		+	Some of the key differences with respect to dsp-bridge is the lack of advanced power management features (like DVFS and [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12032&contentId=4609 SmartReflex]), and lack of dynamic MMU support.

	[http://tiexpressdsp.com/index.php/Codec_Engine_Overview Codec Engine] and [http://tiexpressdsp.com/index.php/DMAI DMAI] have been built upon it, and there are GStreamer plug-ins provided by TI to use the algorithms.		[http://tiexpressdsp.com/index.php/Codec_Engine_Overview Codec Engine] and [http://tiexpressdsp.com/index.php/DMAI DMAI] have been built upon it, and there are GStreamer plug-ins provided by TI to use the algorithms.

← Older revision		Revision as of 22:34, 21 July 2010
Line 40:		Line 40:

	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.
−
−	~~== References ==~~
−
−	~~<references/>~~

	== Interesting threads ==		== Interesting threads ==

@@ Line 1: / Line 1: @@
 [[Category: Linux]]
 [[Category: OMAP]]
-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.
+This article tries to explain all the different Linux DSP systems for OMAP3 chips (e.g. used on [[BeagleBoard]]), how they are similar and different.
 == dsp-gateway ==
@@ Line 12: / Line 12: @@
 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 ==
@@ Line 19: / Line 21: @@
 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.
-There is a disagreement<ref>[http://marc.info/?l=linux-omap&m=120820462123556&w=2 Omapzoom predecessor: "new development happens where there are gaps"]</ref> between TI and the community as how power management must be handled, which created two forks: linux-omap, and omapzoom. However, TI is also working with the community on the linux-omap-pm branch maintained by Kevin Hillman.
+There has been a lot of work spent into cleaning up the code to live up to linux standards, and currently it's on the staging tree with a strong push to merge it on mainline.
-It's under heavy code cleanup<ref>[http://marc.info/?l=linux-omap&m=124148814309478&w=2 Dspbridge: Staging TODO List]</ref>; the first dspbridge appearance was in form of tarballs <ref>[http://marc.info/?l=linux-omap&m=120761100810527&w=2 Dspbridge: First appearance]</ref>, some time later it was merged into TI's omapzoom tree<ref>[http://marc.info/?l=linux-omap&m=121340174005072&w=2 Dspbridge: First set of patches]</ref>. Then, Hiroshi DOYU split the driver into a logical set of patches<ref>[http://marc.info/?l=linux-omap&m=121878286205991&w=2 Port TI DSP BRIDGE for a new dedicated branch in linux-omap]</ref> but its inclusion into linux-omap was rejected and it was maintained in www.muru.com<ref>[http://marc.info/?l=linux-omap&m=121879938429430&w=2 muru.com tidspbridge/]</ref> (Tony Lindgren's personal site), from there it jumped into Hiroshi's personal web space <ref>[http://marc.info/?l=linux-omap&m=122188661716962&w=2 Latest dspbridge rebased on l-o and sync'ed with o-z]</ref> and it finally ended in gitorious <ref>[http://marc.info/?l=linux-omap&m=122692901013682&w=2 Dspbridge gitorious repository]</ref>, now Ameya Palande took over.
+It shares the mailbox code with dsp-gateway, and soon iommu too.
-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 more user-space applications using it, including gst-dsp directly, gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.  [http://code.entropywave.com/leonora Leonora] is a project implementing the Theora codec on the DSP, and is a good example of non-trivial code running on the DSP and communicating with a process running on the ARM core.
-−
-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.  [http://code.entropywave.com/leonora Leonora] is a project implementing the Theora codec on the DSP, and is a good example of non-trivial code running on the DSP and communicating with a process running on the ARM core.
 For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]
@@ Line 42: / Line 42: @@
 == References ==
 <references/>

@@ Line 25: / Line 25: @@
 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.
+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.  [http://code.entropywave.com/leonora Leonora] is a project implementing the Theora codec on the DSP, and is a good example of non-trivial code running on the DSP and communicating with a process running on the ARM core.
 For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

@@ Line 15: / Line 15: @@
 == dsp-bridge ==
-[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.
+[http://omappedia.org/wiki/DSPBridge_Project tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.
 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.

@@ Line 31: / Line 31: @@
 == 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.
+A slimmer version of the dsp-bridge, also developed by TI.  It supports a wide variety of devices (e.g. DaVinci, OMAP2, OMAP3, and discreet GPP+DSP devices).
-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.
+The kernel driver doesn't meet the Linux kernel coding conventions.  The sources haven't been submitted for review, and it is not currently planned to be merged into upstream kernels.
-It's tightly tied to CodecEngine and DMAI, and there are GStreamer plug-ins provided by TI to use the algorithms.
+[http://tiexpressdsp.com/index.php/Codec_Engine_Overview Codec Engine] and [http://tiexpressdsp.com/index.php/DMAI DMAI] have been built upon it, and there are GStreamer plug-ins provided by TI to use the algorithms.
 Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

@@ Line 5: / Line 5: @@
 == dsp-gateway ==
-[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ 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.
+[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the first open implementation and currently the more open. 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.