That's alright. Although if it's all open, I'm not sure why it wouldn't work.you may want to get all of your conniptions ready for a fit. Just voice of experience with dealing with Ti things.
Edit: Ah didn't read the "not" in your sentence on the first read through.
As far as I can see the code for everything is available under a custom (but quite open) license. It looks like they are using the M4s to manage IVA-HD, which of course requires some firmware (both available as source code and binaries)
It is not, and never has been, "all open". The actual codecs are binary, only the loader/management code on the M3/M4 subsystem is available, although the package with binary blobs necessary to compile it has apparently been unavailable since 2012 or so. It may be possible to extract them from the firmware image though, especially since the one I linked to above helpfully includes a linker map.That's alright. Although if it's all open, I'm not sure why it wouldn't work.
Score!I just browsed https://git.ti.com/ivimm/ipumm and it looks like the codec blobs are actually present in that git repo, the extrel folder contains several .lib files related to codecs that are apparently being linked into the M4s' firmware.
No, at least we currently don't, not sure what features these blobs add over the current opensource drivers.One needs blobs for audio?
I tried to connect a bluetooth keyboard but this always fails, first with bluetoothctl, then with graphical manager on desktop. The device was visible, trusted, pair code was requested, and in bluetoothctl accepted, connected, but device couldn't added. I used two different bluetooth sticks and two different keyboards, changed my active usb hub, but nothing helps.
There is nothing that needs to be done, the base of PyraOS is still going to be Jessie or perhaps Stretch the further we wait... I just picked up these changes that fix this the other day on my OMAP5 devboard with a simple apt update.Might be intresting since it is Debian based: