Adding dspbridge module using openembedded

Hello all. I'm very new to embedded Linux (actually Linux in general)
so you will have to bear with me! I'm working on a project for school
- we're trying to use the beagle to develop a portable touchscreen
guitar effects processor. My first step is getting the DSP up and
running within an X-11 environment. I'm hoping someone can point me
towards a how-to for adding the dspbridge (or any module) to the
kernel using openembedded. I've successfully used Felipe's how-to wiki
and kernel to ping the DSP. I've also implemented the basic X-11
openembedded kernel for the beagle. Now I'm hoping to put together my
own kernel with the DSP bridge and hopefully get some guitar effects
going soon! Any help would be greatly appreciated. Thanks.

Matt H

If you're using openembedded you are better of using DSPlink. Link is already integrated into openembedded and the integration is done and supported by TI. Bridge is neither.

regards,

Koen

Koen Kooi said the following on 04/20/2009 03:28 AM:

If you're using openembedded you are better of using DSPlink. Link is
already integrated into openembedded and the integration is done and
supported by TI. Bridge is neither.

well.. part true -> on "supported by TI" for dsp bridge: (no flames
please ;)).. dsp bridge is supported in linux-omap mailing list ;).. it
is becoming more of a community thing now and TI engineers are active
directly on linux-omap mailing list.. anyone is welcome to add
additional support/fix/playaround with dspbridge :D..

Regards,
Nishanth Menon

"support" was meant for the openembedded integration, not TI support in general. There is *no* support for dspbridge in OE whatsoever. Personally, I need a solution that works on dm6446, dm355 and omap3, which means link.

regards,

Koen

Hello!

[...]

"support" was meant for the openembedded integration, not TI support in
general. There is *no* support for dspbridge in OE whatsoever. Personally, I
need a solution that works on dm6446, dm355 and omap3, which means link.
regards,
Koen

We have an overlay with recipes for DSP Bridge here:
  http://github.com/mturquette/meta-texasinstruments/tree/ddiaz/gitomapzoom
(It's tidspbridge-lib and tidspbridge-module in packages/tidspbridge/,
git versions.)

I'll submit the recipes to OE soon (once I eliminate the
'virtual/dspbridge-module' dependency).

Greetings!

Daniel Díaz
ddiaz@ti.com

Ugh, this demonstrates exactly why developing stuff 'in secret' without commucation is bad. "Redo from scratch" comes to my mind after a quick look :frowning:
The codec-engine recipes aren't a picture of beauty either[1], but at least they were made *together* with OE developers so both sides know why hacks were made.

regards,

Koen

[1] They were even uglier, but thanks to TI and especially Roger fixes for the buildsystem and kernel integration got (and are getting!) upstream into codec-engine and friends

Hey, Koen!

Ugh, this demonstrates exactly why developing stuff 'in secret' without
commucation is bad. "Redo from scratch" comes to my mind after a quick look
:frowning:

[...]

I couldn't agree more. This must have been hinted on some emails this
month referring to DSP Bridge and Poky using the Beagle
(http://elinux.org/BeagleBoard/Poky), but we never made a formal
announcement of it.

The meta-ti overlay is fairly new, some months old. We switched to
OE/Poky and gradually converted the whole build system to recipes that
we could use. Internally at TI (Wireless Division) it's being used for
a Linux program. Switching officially to it meant that we had to get
everything working, however difficult it would be.

It hadn't occurred to me to submit the recipes to oe-devel since they
were leading a happy life in meta-ti, as its own overlay. I see the
benefit now, since Angstrom and other distros could take use it
directly. We'll try to submit as much as possible in the coming weeks
via oe-devel.

Greetings!

Daniel Díaz
ddiaz@ti.com