On Tue, Jun 3, 2014 at 1:07 PM, Robert Nelson <[email protected]> wrote: >> 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 >
Is this something that should make its way into meta-beaglebone? >> 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. > Certainly using a binary driver is a tolerable thing if its easily buildable and shippable with the product. >> - 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. > I don't think we know enough here to be able to jump in from zero to help out. Would need a bit more direction or specific tasks to work on in order to be able to be productive. If you or anyone else is up for providing more direction please drop me an email. Chris -- 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.
