This is a very bad idea (tm) for a number of reasons:
- As described, it makes the Amazon system image read/write during play.
- Program is just dump'd into the root of USB storage, ignoring our policies for placement of additions. Policies learned the hard way here.
- The application is built to use VFPv2 instructions and the K3 processor supports only the VFP instruction set.
Code:
core2quad adom $ readelf -A adom
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "6"
Tag_CPU_arch: v6
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-1
Tag_FP_arch: VFPv2
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_align_preserved: 8-byte, except leaf SP
Tag_ABI_enum_size: int
Tag_ABI_HardFP_use: SP and DP
Tag_ABI_VFP_args: VFP registers
Tag_CPU_unaligned_access: v6
Tag_DIV_use: Not allowed
This project goes against basic principles we (the developers) at Mobilread support.
- No sources to be made available (see: readme1st.txt, section III.E).
- The above, in violation of license terms of some of the software components (see: text of the various licenses in the archive's "license" directory.
- It is a commercial project (crowd funded, but commercial none the less).
Personal Opinion:
Not Recommended!