Perhaps the host process could handle loading the executable into the 940 and setting up the code to link it. Going a step farther, the host process could handle shutting down the 940 when it is terminated, and doing some locking to avoid multiple use of the 940 or related race conditions.
In...
How difficult would it be to create a call gate on the 920 which can process some system calls for the 940? Obviously things such as mmap would need to be simulated or disallowed because the hardware isn't there to make it effective, and process migration is probably out of the question, but...
And which of those modules is the SD driver? I believe it's built into the kernel (not a module), so you'd have to compare a kernel you built with GPH's using the same settings and compiler.
The important safeguard to take when you reverse engineer something is to have a different person write the alternative implementation (working entirely from specs) than the one who reverse engineered the working sample. This won't get you around patented things though, and therein can lie the...
I bet it wouldn't be terribly hard to reverse engineer the SD driver (I've done hardware reverse engineering via BIOS disassembly on an x86 calculator), but that leaves the project open to potential legal issues.
I think there was a daemon program you could install that would exit out to the main menu (or possibly do other stuff) when you hit a predefined button combo.
Hmm, if that doesn't help, another thought is that maybe only some of the channels getting mixed together are messed up? If there's mixing code specific to that format, you could dump (or checksum) the individual channels and see how they're doing, and narrow down whether it's the mixing...
You could probably alter it to send the samples to stdout, and then run the program over usb networking and capture the output on a computer. I see you've already found the alignment thread (that would have been my first guess as to what the problem might be).
Just place the newer glibc in the same spot as the current one (it should be named with a version number so they don't conflict) - just don't change the versionless symlink away from the current library and I don't think there will be any adverse problems.
Of course the drawback to this is that...
I'm guessing it just uses the framebuffer, but hardware acceleration would be nice if X turns out to be useful. What X on here really needs is a way to store data at >32MB, then it will save some memory on the X server side.
Try setting it up in cygwin?
Edit: Nevermind, I just read the other thread, and this won't work. Maybe the easiest solution would be colinux or another virtualization strategy to run linux.
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.