I think a more effective way to look at the 940 (than as a DSP) is as another processor, with extra limitations. It's got less cache, and no MMU, so it's well suited to tasks that still fit well within its cache, but can be well separated from whatever the main CPU is doing. Sound emulation...
Load an index of the conversations into memory (with offset/length into a conversation file), and load them from that file on demand. One conversation per file would be wasteful on most filesystems. You could include identification info inside the file and make a small utility to generate the...
The way I would suggest starting is by looking at the assembly code gcc produces for those, and then splitting them out into a separate assembly file that you can optimize and compile to object files that get linked with the rest of the code.
I assume you're setting it up so you can run gcc from the command line, etc... in which case, you probably want to add the location(s) to the PATH= environment variable.
In fact, linux preemptively swaps things out (maybe only in more recent kernel versions) to swap before RAM fills, just for that performance reason. It makes more sense to have things in swap and RAM at the same time if memory is getting tight - that way the RAM copy can be dumped right away if...
Even if you assume well optimized code, there's always that extra 30% or so you can squeeze out of overclocking. I agree it shouldn't be depended on (~240MHz is probably reasonable for this device), but it never hurts to consider the option, especially if there are different rendering qualities...
You want to be careful with how you use precalculated tables - if they get too large, they won't fit in the cache anymore. You should try to design the engine so any tables it uses for a given loop fit in the data cache. Don't be afraid to design the engine with different modular parts that...
Consider just shelling out and running tar with gzip or bzip2 decompression. It should just be emulated by busybox, so it won't even cause much extra memory usage if busybox is already loaded for something else.
I'm not sure - if I remember, there may have been a different voltage regulator used in the mkII (or at least it's likely wired differently - the mkII is capable of providing 5V to the EXT port while the mkI wasn't).
I'd try reformatting it first - it's possible the filesystem got messed up and things aren't being written properly. Some card readers can't handle larger sized SD cards, but I'd expect at least one of the readers you tried would have supported it (unless you're really unlucky). As a...
pkostrze, have you tried using a different USB cable? There are lots of reports of people using cables that came with digital cameras, etc, with better results.
There's a lot of reports of bad or marginal USB cables shipped with the units - if you have problems, try to borrow a cable from a digital camera or something like that and see if it works better.
Be careful - the batteries will probably be at a higher voltage when fully charged, and it might be higher than you'd want to connect to the voltage regulator. Kinda like NiMH are rated at 1.2V, but are typically around 1.5V briefly when fully charged. 3.7V is probably OK, but once you start...
Use superglue or similar and make a bump where the button would have been in the write-enabled spot. The switch isn't connected to electronics - it just trips a switch inside the reader. Try not to make it stick out more than the tab would have otherwise, or it might get broken off.
Another approach may be running a customized linux kernel and initrd or similar - that way you can still use filesystems and threading, but you're free to hack whatever you need to in the MMU code in linux. You could also screw with the 32/32 memory split, and make it 48/16 or whatever works...
Ah, a fellow Wisconsinite doing the ol' quad post. For situations like these, I just say "sorry guys, I'm from Merrill". Only it doesn't work on the internet, because like 1/500th of the population would know where that is...
I think the only appreciable advantage is getting full control of the MMU. Everything else would probably have more or less clean solutions. Plus, it leaves open the option for TCP/IP multiplayer.
Another note... there can even be very strange things like switching sample rate or stereo/mono within a file, but I'm not sure it's reasonable to expect that a player handles this correctly.
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.