TargetsEvaluation » History » Version 1
Brian Kemp, 02/08/2012 04:15 PM
| 1 | 1 | Brian Kemp | h1. Good Potential Targets |
|---|---|---|---|
| 2 | |||
| 3 | h2. Good Targets |
||
| 4 | A good potential target for Replicant will have: |
||
| 5 | |||
| 6 | * Unlocked / Engineering bootloader capable of booting unsigned operating system files |
||
| 7 | * Works with standard tools (adb, fastboot) |
||
| 8 | * GSM / UMTS network capability (CDMA2000 devices require proprietary libraries signed with a particular key in order to use the network.) |
||
| 9 | * Components (e.g., Wifi, Bluetooth, Camera, Video, Touchscreen) with freely available documentation |
||
| 10 | * Ability to flash via fastboot. (Currently Replicant does not publish update.zip files.) |
||
| 11 | * Support in CyanogenMod or other AOSP-based Android build |
||
| 12 | * As few binary-only drivers as possible |
||
| 13 | |||
| 14 | h2. Ideal Targets |
||
| 15 | |||
| 16 | An ideal potential target for Replicant will have: |
||
| 17 | |||
| 18 | * All of the good potential target characteristics |
||
| 19 | * Processor Isolation - Modem cannot spy on the memory of the Application processor |
||
| 20 | * Components that do not require loadable firmware |
||
| 21 | * Commonality with devices already supported in Replicant or other Free Software phone project |
||
| 22 | * Zero binary-only drivers |
||
| 23 | * Free-able bootloader |