DeprecatedPortingGuideS5PC110 » History » Version 8
Paul Kocialkowski, 12/23/2012 10:32 AM
1 | 1 | Paul Kocialkowski | h1. PortingGuideS5PC110 |
---|---|---|---|
2 | |||
3 | *This guide assumes your phone has a S5PC110/Exynos 3110 SoC* |
||
4 | |||
5 | 3 | Paul Kocialkowski | h2. Prerequisites |
6 | 1 | Paul Kocialkowski | |
7 | 3 | Paul Kocialkowski | Before porting your device to Replicant, you must make sure it complies with the following: |
8 | * Already supported by CyanogenMod (or, worst-case scenario, by a non-official CyanogenMod port) |
||
9 | * CyanogenMod support for this device is available for one of Replicant versions (pick the latest) |
||
10 | * The phone is GSM: Replicant doesn't support CDMA phones yet |
||
11 | * It is likely to be usable without blobs nor firmwares and with Replicant replacements |
||
12 | 1 | Paul Kocialkowski | |
13 | 3 | Paul Kocialkowski | h2. Investigating the phone hardware |
14 | 1 | Paul Kocialkowski | |
15 | 3 | Paul Kocialkowski | Before doing anything, you will need to know the codename of the device. You can find it out on "CyanogenMod Wiki":http://wiki.cyanogenmod.org/ or on "CyanogenMod download page":http://get.cm/. |
16 | For instance, the "Nexus S":http://wiki.cyanogenmod.org/wiki/Nexus_S codename is: @crespo@. |
||
17 | 1 | Paul Kocialkowski | |
18 | 3 | Paul Kocialkowski | First thing to consider before starting a port, when all of the above is assumed, is to see how many non-free components are required by CyanogenMod. |
19 | The easiest way to do this is to spot the device repository in "CyanogenMod repos":https://github.com/CyanogenMod/ and look for the @extract-files.sh@ or @proprietary-blobs.txt@ file. |
||
20 | For instance, the list of non-free components for the "Nexus S":https://github.com/CyanogenMod/android_device_samsung_crespo is "extract-files.sh":https://github.com/CyanogenMod/android_device_samsung_crespo/blob/ics/extract-files.sh |
||
21 | |||
22 | From that list, spot what is related to what hardware component (audio, camera, sensors, gps, modem, etc): that gives an idea of the amount of work required to add support for the phone. |
||
23 | |||
24 | During the port, you might need to find precise infos about the hardware that is in the phone. A good to do this is by looking at the kernel defconfig for the device, another way is to download the Service Manual for the device. |
||
25 | |||
26 | h2. Getting everything ready |
||
27 | |||
28 | In order to prepare everything for the Replicant port: |
||
29 | * Install CyanogenMod on the phone |
||
30 | * Install the [[BuildDependencies]] |
||
31 | * Get the sources: [[GettingReplicantSources]] |
||
32 | * Read Replicant developer guide: [[DeveloperGuide]] |
||
33 | * Learn how to do debug: [[GettingLogs]] [[GDBDebugging]] |
||
34 | |||
35 | 8 | Paul Kocialkowski | h2. Cloning the device files |
36 | |||
37 | Once your Replicant tree is ready, you can start by adding the necessary repos for your device. |
||
38 | That means cloning the necessary repos in the right place. These repos are: |
||
39 | * A device-specific repo. On CyanogenMod, it is usually called: @android_device_vendor_device@. |
||
40 | * Sometimes one or more common repo(s), usually called: @android_device_vendor_devices-common@. |
||
41 | Some devices don't need any common repo, but some do. |
||
42 | * A kernel repo. On CyanogenMod, it is usually called: @android_kernel_samsung_devices@. |
||
43 | The kernel repo can be shared across a family of devices (for instance, on kernel repo for Samsung Exynos, one for Samsung OMAP, etc). |
||
44 | |||
45 | h3. Creating the kernel repo |
||
46 | |||
47 | If the kernel repo is nowhere to be found, you'll need to get the kernel source directly from the vendor, especially if your device is supported by a 3rd party CyanogenMod fork. |
||
48 | Keep in mind that the Linux kernel is GPLv2, so vendors have the legal obligation to release the modified kernel sources as soon as they sell you the device. |
||
49 | That means the kernel sources will be available online. Here are some websites where such releases are done: |
||
50 | * "Samsung Open Source Release Center":http://opensource.samsung.com/ |
||
51 | For Samsung kernels. Search the device codename (e.g. I9000) and download the package called "Opensource Update" (e.g. GT-I9000_Opensource_GB_Update2.zip). |
||
52 | This will hold a kernel archive with all the sources and instructions on how to build it and which defconfig to use. |
||
53 | |||
54 | Once you have the kernel sources, read the instructions to find out which defconfig to use. |
||
55 | |||
56 | Since manufacturers usually don't release the git history along with the files, you'll need to recreate a git repo: |
||
57 | * Clone the mainline kernel in the same version as the Makefile from the sources you just obtained |
||
58 | * Remove the cloned files *except the .git directory* |
||
59 | * Move the manufacturer kernel tree at the place of the files you just removed |
||
60 | * Add all the files in git (@git add -A@) and commit (@git commit@) with a message explaining what you just imported (e.g. "GT-I9000 GB Opensource Update 2") |
||
61 | |||
62 | Now that you have a git repo, you can move it to the Replicant code tree, under the name: @kernel/vendor/devices@ (e.g. @kernel/samsung/aries@). |
||
63 | Make sure to make the @devices@ name match the @devices@ in @android_device_vendor_devices-common@ if the kernel is shared across these devices or to match the @device@ in @android_device_vendor_device@. |
||
64 | |||
65 | h2. Building the kernel |
||
66 | |||
67 | The first step when porting a new device to Replicant is to build a kernel image and ensure it works. |
||
68 | Start by looking if |
||
69 | |||
70 | For doing that, you need to sport where the kernel source is held. CyanogenMod |
||
71 | |||
72 | 1 | Paul Kocialkowski | h2. Get the source and build a kernel image |
73 | |||
74 | * adding the 3rd party repos if any |
||
75 | * add kernel: where the find the kernels? |
||
76 | - official feeds |
||
77 | - the ones on GIT (teamhacksung, better ask CM people) |
||
78 | - 3rd party projects |
||
79 | * add kernel to product files on vendor/replicant |
||
80 | 2 | Paul Kocialkowski | |
81 | * change ro.modversion on product vendor file |
||
82 | 4 | Paul Kocialkowski | |
83 | 6 | Denis 'GNUtoo' Carikli | h2. Various hardware and software fixes to get things working. |
84 | 1 | Paul Kocialkowski | |
85 | 6 | Denis 'GNUtoo' Carikli | h3. To get software video decoding (OMX stuff): |
86 | 7 | Denis 'GNUtoo' Carikli | |
87 | 4 | Paul Kocialkowski | * remove OMX libs for hardware video decoding |
88 | 1 | Paul Kocialkowski | * remove libstagefrighthw.so |
89 | 5 | Denis 'GNUtoo' Carikli | like that: http://gitorious.org/replicant/device_samsung_crespo/commit/c8edb6539977c8820d665691d53c33892cfa4fdd |