While optimizing rendering of the preorder graph the other day, I now create an intermediate datafile with deduplicated entries, it might be easier to look through?
http://p.rdw.se/preorder_stats_dedup.txt
ARMv7A is an instruction set, not an implementation. In the same sense that an Intel Celeron may implement the exact same instruction set as an Intel Xeon.
The effects go further than just cache/bus configuration, even if it helps.
dbp-run will send a bunch of commands to dbpd over dbus, which will set up the aufs and mount the image. After that, it'll chdir into the aufs root and execute a given binary using a runscript in /etc. Any kind of jailing would likely have to happen in the run script.
While I can see the appeal of running such software in a jail, I'm not yet convinced that integration will work competently. If anyone have an idea of how to implementing it in practice rather than just listing technologies, I'd consider adding it as a configuration option for those who wants...
The USB3 port is the only port that can act as a client port. With an OTG adapter, it should be usable as a host port. USB A or C can't dynamically decide if it's a host or a client.
The drivers we get for the pyra has no full OpenGL support at all, it only has OpenGL|ES 1 and 2, with some extensions.
Full OpenGL 1.x support is provided using glshim. A version supporting full OpenGL 2.x is something _aegis_ wants to work on, but it's a massive undertaking.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.