search for: oxfw911

...not sure what ARM CPU my first-gen iPhone has but I think it uses the arm6 instruction set. Finally I have three Oxford Semiconductor FireWire / USB / Parallel IDE storage bridge chip target boards. They all have ARM7TDMI cores with 64 kb to 128 kb of Flash and some microscopic amount of RAM: my OXFW911 chip has 64 kb of 16-bit Flash but only 1800 BYTES - not Megabytes, not Kilobytes, but just BYTES - of RAM. There wouldn't be enough memory in these things to run a shell, but any of the tests that could be packaged as a subroutine with a single entry point could be compiled into the firmware....

...not sure what ARM CPU my first-gen iPhone has but I think it uses the arm6 instruction set. Finally I have three Oxford Semiconductor FireWire / USB / Parallel IDE storage bridge chip target boards. They all have ARM7TDMI cores with 64 kb to 128 kb of Flash and some microscopic amount of RAM: my OXFW911 chip has 64 kb of 16-bit Flash but only 1800 BYTES - not Megabytes, not Kilobytes, but just BYTES - of RAM. There wouldn't be enough memory in these things to run a shell, but any of the tests that could be packaged as a subroutine with a single entry point could be compiled into the firmware....

Thanks for the info, Dave. Speed is a very important feature, but there might be some risk choosing the FFmpeg decoder. They've had trouble with their encoder in the past, which tells me it's possible your users might one day run into a valid FLAC that the FFmpeg decoder won't handle correctly. A better suggestion might be to start with libFLAC, optimize as needed, and

...not sure what ARM CPU my first-gen iPhone has but I think it uses the arm6 instruction set. Finally I have three Oxford Semiconductor FireWire / USB / Parallel IDE storage bridge chip target boards. They all have ARM7TDMI cores with 64 kb to 128 kb of Flash and some microscopic amount of RAM: my OXFW911 chip has 64 kb of 16-bit Flash but only 1800 BYTES - not Megabytes, not Kilobytes, but just BYTES - of RAM. There wouldn't be enough memory in these things to run a shell, but any of the tests that could be packaged as a subroutine with a single entry point could be compiled into the firmware....

Admittedly we're very interested in becoming ARM backend maintainers as our product heavily relies on LLVM. However, we don't have testing resources to test both our product and LLVM on a host of target boards. We have some chumbys, beagleboards, iPhones, iPod Touches, tables, Android Phones, etc. And most of those are already booked solid with our own regression tests (most of which