Read the license and docs of the sgx stuff, it has all the answers
Well, kind of. The legal stuff (redistribution, etc.) are explained.
The technical answers have been harder to find. Maybe I'm not reading
the right stuff yet.
FWIW, here's what I've found so far.
> 1. Will the binary OpenGL/ES libraries work given that I'm compiling
> everything else with Crosstool-NG?
I couldn't find an answer to this but this is one of those "try it and
see" problems. I'll have to see what issues I come across by using a
different cross compiler. But I have a ways to go before I get to
If I have to switch from Crosstool-NG to CodeSourcery I'll do so, but
I'd like to understand why that's necessary. That's part of the reason
I'm doing this little project.
> 2. Are the libraries redistributable or must they be acquired manually
> by end users by retrieving the entire TI sgx package?
Yeah. Boils down to: be a good person and do the right thing (re:
credits, copyrights, etc.). That's not a problem should I decide that
BeagleBox will provide images instead of just a build system.
> 3. Can I repackage the open source drivers to make it possible for users
> of my system to grab a smaller package for building? This won't be
> necessary if the libraries are not also redistributable since they'd
> have to get the big package anyway. OE appears to require that you
> download the big package.
Yes though the existing build for the drivers may make it less optimal
to break it out rather than leave it in the TI distribution. I hacked a
package build for this in BeagleBox to test it. Basically it's easier
to leave it in the TI package for now, though the build fails with my
current config (see next).
> 4. Are the kernel drivers in the TI sgx package specific to a given
> kernel? I'm using the linux-omap-2.6.32 kernel retrieved from the
> tmlind git tree.
Turns out the latest SGX drivers (re: -07) don't build with
linux-omap-2.6.32 as defined in OE. See
My build failed for the same reason.
The -02 version is said to work. The OE recipe link points to the
latest sgx but a little munging of the -07 link finds the -02 release:
I haven't verified this one yet. Gotta download it first.
Also, a 2.6.34 kernel may work with the new -07 release but there isn't
a recipe for 2.6.34 for OMAP yet so I'm not sure if that is a valid path
for me yet. If it is it may answer the next question.
Is this git tree the appropriate kernel for
> BeagleBoard? Has this tree been pushed upstream? I thought I'd seen on
> this list that the stable 2.6.34 or later had everything from the git
> tree pushed to it. But I'm not clear if that's correct or not.
Haven't found the authoritative answer on this. But I'm still looking.
> haven't checked what the validation builds use yet, but it's on my todo
Still on the todo list.
Just thought I'd follow up my own questions in case anyone else found
them useful. I keep notes on this on the BeagleBox bug db: