1) cross compiling v.s. building kernel
someone tells me that I have to build a kernel with dvsdk if I want to use it. is it right? I am think if we can write the code with dvsdk lib and then cross-compile it.

You should not use the kernel provided by the DVSDK. You should use your own kernel.

git clone git://www.sakoman.com/git/linux-omap-2.6
cd linux-omap-2.6
checkout v2.6.38

You will have to make a few changes depending on which kernel version you use.
Example: https://github.com/fastr/ti-dvsdk-3-overlay/commit/07f6a609e29cd29fe1c9b36ca4429456b3feef9c

Aside from the Kernel and DVSDK, any other software you create will be easiest to native compile with Linaro.
2) Linaro vs Openembeded
I have build a SD card with Linaro. it has better GUI than OpenEmbedded. But it seems that Linaro consumes more RAM than Open-embedded. I may have to to use Open-embedded. do you know how to improve Linaro performance?

There are different prebuilt images. It will be easiest if you develop your software with the "developer" image. Then use the "headless" image for production.

Also, you could do your compiling with one of your devices with the "developer" image and use a second device for testing with "headless".

Aside from the image itself, you can look in `/etc/init` and rename the files for any services you aren't using from
3) Installing with OpenEmbedded Tool Chain

I follow the instruction @ https://bitbucket.org/thayne/ti-omap-tools/src to install dvsdk on host computer.

$> ./ti-setup-dvsdk -d /some/path/ti-cs -o /some/path/to/openembedded

after that , I use the commands below to "make" new kernels (http://fastr.github.com/articles/omap-dvsdk-on-openembedded.html)

make linux_clean
make linux

make clobber
make everything

make install

Assuming that all of that worked, you should be able to begin your DVSDK development.
The example applications built with "make everything" are a good place to base your work off of.

I haven't had good experiences with OpenEmbedded, but apparently other people have.

However, no matter which you choose you'll also have to fix some small errors in the kernel source, unless you manage to get a very old kernel to work with your OS and applications.

AJ ONeal
On Wed, May 4, 2011 at 11:35 AM, AJ ONeal <coolaj86@gmail.com> wrote:

I'm including this on the gumstix mailing list so we can continue our discussion there.
(Just be sure to CC me when you want the message to come directly into my inbox.)

Go ahead and look here:

And perhaps here:

Once you have the Linaro toolchain and pre-built image you can run the script here:

After that there are a few tweaks you may need to make before the DVSDK will compile successfully.

AJ ONeal

On Wed, May 4, 2011 at 12:18 PM, Yang Chenhui <yang.ch@asu.edu> wrote:
thanks for your timely reply.
I use gumstix Overo™ Fire COM. 
do you know if we can build kernel with gui?

which mail list you refer ? please let me know. I will post it.

On Wed, May 4, 2011 at 10:32 AM, AJ ONeal <coolaj86@gmail.com> wrote:
Yes, first you should git clone the kernel you need from sakoman

The next step depends on which toolchain you wish to use.
To get a quick test up and running I would suggest using Linaro. Their setup is much faster than OpenEmbedded's.

Can you tell me more about your setup?

Also, can we continue our discussion on the mailing list so that everyone can benefit from it?

AJ ONeal

On Wed, May 4, 2011 at 10:55 AM, Bitbucket <notifications-noreply@bitbucket.org> wrote:
You have received a notification from chenh.

AJ ONeal-3

My name is chenhui, working on gumstix. I find your post about dvsdk @http://old.nabble.com/-OT--ti-omap-tools---script-for-setting-up-DVSDK-3-with-various-toolchains-p31444010.html
I am not sure how to build kernel for gumstix with the dvsdk support. have you done this ?.

my email is:  chen.h.yang@gmail.com
thanks for your help


Change your notification settings at https://bitbucket.org/account/notifications/