> I appreciate the response, there isn't much good detail on this stuff > on the web. I'd love to see a page on elinux.org or somewhere that > covered the state of the union and the next steps. > > I agree that having sgx support is a pretty critical feature and it > seems like Jason K. is going in the right direction to port things > foward. > > We are using Yocto builds here but I think meta-beaglebone is using a > 3.8 kernel which is too old for the TI graphics support.
https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.8/patches/sgx > From a wishlist perspective it seems like we would want: > > - TI sgx support upstreamed to kernel.org (is this ongoing?) www.imgtec.com will never allow that to happen. The biggest blocker for using the "blob" was the soc reset patchset, which looks like to hit v3.16-rc0, i back ported that from ti's 3.12 to make it work for our self. > - Cape manager support in 3.14+ patches welcome.. It looks like there is a "chance" overlays might get accepted in v3.16-rc0, not holding my breath. > The overall goal is a yocto build for the bbb with wayland 1.5 (recipe > was added last week) and 3d acceleration. > > I mentioned in another post but I'll mention it here because you were > kind enough to respond, the company I work for is using the bbb in a > product. As such it is important for us to have these features. We'd > be willing to help, either in terms of sw engineering time, or > sponsoring some of these efforts. We aren't experts yet but given some > guidance I think we could contribute. If this sounds interesting > please let me know. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
