Linux kernel, Android, Golang & Recsys

Android基于ClockworkMod Recovery(CWM)的系统升级

April 18th, 2012 BianJiang 15 comments

Android 系统自带了升级的接库RecoverySystem.installPackage，但是通过installPackage进入ClockworkMod Recovery(CWM)后，包的签名验证是打开的，导致升级错误。但是在实践中发现，如果通过自己手动按键进入CWM Recovery模式后，签名验证默认是关闭的，而自己通过APK升级进入后验证是打开的，这个就说明签名验证是可以通过外部参数调整的。由于CWM本身是不开源的，无法看到具体的实现细节，只能通过反编译，RomManager的日志和猜。

CWM提供了一个配套的RomManager.apk进行升级，那我们就从RomManager.apk下手。

通过分析RomManager.apk的日志，发现RomManager.apk在运行的时候会通过一个 rommanager.sh 的脚本，来进行相关的reboot 并进入recovery模式。

border@kvbian:~ s$ cat rommanager.sh 
mkdir -p /cache/recovery ; cat /data/data/com.koushikdutta.rommanager/files/extendedcommand > /cache/recovery/extendedcommand ;  rm /cache/recovery/command ; mkdir -p /sdcard/clockworkmod ; echo 1 > /sdcard/clockworkmod/.recoverycheckpoint ;  reboot recovery ;
border@kvbian:~ s$ cat extendedcommand 
ui_print("ROM Manager Version 5.0.0.5");
ui_print("2012年4月18日");
ui_print("Preparing to install ROM...");
assert(install_zip("/sdcard/update/kvbian-rom-signed-20120417-2112.zip"));

从上面的rommanager.sh 脚本可以看出:
CWM如果要取消签名验证进行升级，不能使用Android默认的
/cache/recovery/command 文件进行相关的命令。
而是使用 /cache/recovery/extendedcommand 执行相关的升级命令。

同时要在 /sdcard/clockworkmod/.recoverycheckpoint 文件做相关的标记。

相关的升级代码:
权限:

1 2	<uses-permission android:name="android.permission.ACCESS_CACHE_FILESYSTEM" /> <uses-permission android:name="android.permission.REBOOT" />

Java 代码(完成的程序参考: 升级程序RomUpdate下载):

package com.kvbian.romupdate;
 
import java.io.File;
import java.io.FileOutputStream;
import java.io.FileWriter;
import java.io.IOException;
import java.io.InputStream;
import java.net.HttpURLConnection;
import java.net.MalformedURLException;
import java.net.URL;
 
import android.app.Activity;
import android.content.Context;
import android.os.Bundle;
import android.os.PowerManager;
import android.os.StrictMode;
import android.util.Log;
import android.widget.TextView;
 
/**
 * @author Jiang Bian
 * mail: borderj@gmail.com
 * blog: http://wifihack.net
 *
 */
public class RomUpdateActivity extends Activity {
    /** Called when the activity is first created. */
 
    /*
     * Android 3.0
     * 测试机器: GT-P7300/GT-P7310
     *  本程序之在 ClockworkMod_Recovery_v5.5.0.4 版本测试过，其他版本没有测试。
     *  ClockworkMod Recovery(CWM) 如果要取消签名验证进行升级，不能使用Android默认的
     *  /cache/recovery/command 文件进行相关的命令。
     *  而是使用 /cache/recovery/extendedcommand 执行相关的升级命令。
     *  
     *  同时要在 /sdcard/clockworkmod/.recoverycheckpoint 文件做相关的标记。
     * 
     * 本文参考: 
     *  1. frameworks/base/core/java/android/os/RecoverySystem.java
     *  2. bootable/recovery/recovery.c
     *  3. RomManager.apk
     */
 
    private static final String TAG = "RomUpdateActivity";
 
    private static final String ROM_DOWNLOAD_URL = "http://192.168.1.66/update.zip";
 
    private static final String ROMPATH = "/sdcard/update.zip";
 
    private static int buffer_size = 1024 * 10;
 
    /** Used to communicate with recovery.  See bootable/recovery/recovery.c. */
    private static File RECOVERY_DIR = new File("/cache/recovery");
    private static File CLOCK_WORK_MOD_DIR = new File("/sdcard/clockworkmod");
 
    private static File CLOCK_WORK_MOD_CHECKPOINT_FILE = new File(CLOCK_WORK_MOD_DIR, ".recoverycheckpoint");
    private static File COMMAND_FILE = new File(RECOVERY_DIR, "command");
    //     // /cache/recovery/extendedcommand
    private static File EXTENDED_FILE = new File(RECOVERY_DIR, "extendedcommand");
    private static File LOG_FILE = new File(RECOVERY_DIR, "log");
 
    /**
     * Reboot into the recovery system with the supplied argument.
     * @throws IOException if something goes wrong.
     *  From: frameworks/base/core/java/android/os/RecoverySystem.java
 
border@kvbian:~ s$ cat rommanager.sh 
mkdir -p /cache/recovery ; cat /data/data/com.koushikdutta.rommanager/files/extendedcommand > /cache/recovery/extendedcommand ;  rm /cache/recovery/command ; mkdir -p /sdcard/clockworkmod ; echo 1 > /sdcard/clockworkmod/.recoverycheckpoint ;  reboot recovery ;
border@kvbian:~ s$ cat extendedcommand 
ui_print("ROM Manager Version 5.0.0.5");
ui_print("2012年4月18日");
ui_print("Preparing to install ROM...");
assert(install_zip("/sdcard/update/kvbian-rom-signed-20120417-2112.zip"));
     */
    private  void bootCommand(Context context) throws IOException {
        RECOVERY_DIR.mkdirs();  // In case we need it
        CLOCK_WORK_MOD_DIR.mkdirs();
 
        EXTENDED_FILE.delete();
        COMMAND_FILE.delete();  // In case it's not writable
        CLOCK_WORK_MOD_CHECKPOINT_FILE.delete();
        LOG_FILE.delete();
 
        Log.v(TAG, "write ClockWorkMod Checkpoint File: " + CLOCK_WORK_MOD_CHECKPOINT_FILE.getAbsolutePath());
        FileWriter checkpoint = new FileWriter(CLOCK_WORK_MOD_CHECKPOINT_FILE);
 
        try {
            checkpoint.write("1");
            checkpoint.write("\n");
        } finally {
            checkpoint.close();
        }
 
        Log.v(TAG, "write Extended Command File: " + EXTENDED_FILE.getAbsolutePath());
        Log.v(TAG, "write Extended Command File args: " + ROMPATH);
        FileWriter command = new FileWriter(EXTENDED_FILE);
 
        try {
            command.write("ui_print(\"ZPad ROM Manager Version:\"); ");
            command.write("\n");
            command.write("ui_print(\"2012.4.18\");");
            command.write("\n");
            command.write("ui_print(\"Preparing to install ROM...\");");
            command.write("\n");
            //assert(install_zip("/sdcard/update/kvbian-rom-signed-20120417-2112.zip"));
            command.write("assert(install_zip(\"" + ROMPATH  + "\"));");
            command.write("\n");
        } finally {
            command.close();
        }
 
        /**
         * boot-recovery
         * recovery
         */
        // Having written the command file, go ahead and reboot
        PowerManager pm = (PowerManager) context.getSystemService(Context.POWER_SERVICE);
        //pm.reboot("recovery");
        pm.reboot("recovery");
    }
 
 
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
 
        StrictMode.setThreadPolicy(new StrictMode.ThreadPolicy.Builder()
                .detectDiskReads().detectDiskWrites().detectNetwork() // or
                                                                      // .detectAll()
                                                                      // for
                                                                      // all
                                                                      // detectable
                                                                      // problems
                .penaltyLog().build());
        StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder()
                .detectLeakedSqlLiteObjects().detectLeakedClosableObjects()
                .penaltyLog().penaltyDeath().build());
 
        // getRomFromNet(ROM_DOWNLOAD_URL);
        romUpdate(this);
 
        TextView tv = new TextView(this);
        tv.setText("RomUpdate Version: 1.1 - 2012.4.18");
        setContentView(tv);
    }
 
    public void romUpdate(Context context) {
 
        try {
            bootCommand(context);
 
        } catch (IOException e) {
            Log.v(TAG, e.getMessage());
            e.printStackTrace();
        }
    }
 
    public void getRomFromNet(String romURL) {
 
        try {
            // set the download URL, a url that points to a file on the internet
            // this is the file to be downloaded
            Log.v(TAG, "   -------------  url: " + romURL + " -------------  ");
 
            URL url = new URL(romURL);
 
            // create the new connection
            HttpURLConnection urlConnection = (HttpURLConnection) url
                    .openConnection();
 
            File file = new File(ROMPATH);
 
            // this will be used in reading the data from the internet
            InputStream inputStream = urlConnection.getInputStream();
 
            // this is the total size of the file
            int totalSize = urlConnection.getContentLength();
 
            // variable to store total downloaded bytes
            int downloadedSize = 0;
 
            // create a buffer...
            byte[] buffer = new byte[1024];
            int bufferLength = 0; // used to store a temporary size of the
 
            Log.v(TAG, "Download From [" + romURL + "], Save File To: "
                    + ROMPATH + "]");
 
            FileOutputStream fileOutput = new FileOutputStream(file);
 
            while ((bufferLength = inputStream.read(buffer)) > 0) {
 
                fileOutput.write(buffer, 0, bufferLength);
 
                downloadedSize += bufferLength;
            }
            // close the output stream when done
            fileOutput.close();
            Log.v(TAG, " Save File To: [" + ROMPATH + "]");
        } catch (MalformedURLException e) {
            e.printStackTrace();
        } catch (IOException e) {
            e.printStackTrace();
        }
 
    }
 
}

测试机器: GT-P7300/GT-P7310
测试环境: Android 3.0
在 ClockworkMod_Recovery_v5.5.0.4 版本测试过，其他版本没有测试。

本文参考:
1. frameworks/base/core/java/android/os/RecoverySystem.java
2. bootable/recovery/recovery.c
3. RomManager.apk
4. 升级程序RomUpdate下载

Categories: Android, Tech.Notes Tags: android, ClockworkMod, CWM, Recovery, rom, RomManager, update, 定制ROM

在现存的Git里面增加一个远程的仓库

April 18th, 2012 BianJiang No comments

1. 在你当前的目录执行:

1
2
3

cd existing_git_repo
git remote add origin git@github.com:caius/foo.git
git push origin master

2. 在 .git/config 文件中增加:

1
2
3

[branch "master"]
    remote = origin
    merge = refs/heads/master

详细信息:

border@kvbian:~/workspace/RomUpdate$ git remote add origin git://127.0.0.1/RomUpdate.git
border@kvbian:~/workspace/RomUpdate$ git push origin master
Everything up-to-date
border@kvbian:~/workspace/RomUpdate$ git pull
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details
 
    git pull <remote> <branch>
 
If you wish to set tracking information for this branch you can do so with:
 
    git branch --set-upstream master origin/<branch>
 
border@kvbian:~/workspace/RomUpdate$ git branch 
* master
border@kvbian:~/workspace/RomUpdate$ git push
Everything up-to-date
border@kvbian:~/workspace/RomUpdate$ gitk --all
border@kvbian:~/workspace/RomUpdate$ vi .git/config 
[branch "master"]
    remote = origin
    merge = refs/heads/master
border@kvbian:~/workspace/RomUpdate$ git push
Everything up-to-date
border@kvbian:~/workspace/RomUpdate$ git pull
Already up-to-date.
border@kvbian:~/workspace/RomUpdate$

参考: http://caiustheory.com/adding-a-remote-to-existing-git-repo

Categories: Tech.Notes Tags: Git, Notes, remote

Android定制启动画面

April 14th, 2012 BianJiang No comments

今天在做Android启动画面的时候，被打包bootanimation.zip给折腾个半死，自己打包的启动画面死活不能用，后来查了些资料发现，打包zip的时候要选择“存储”模式，而不是压缩模式。
Linux:
zip -0 -r ../bootanimation.zip .

Windows:
打包的时候选择”存储”。

打包后把bootanimation.zip方到板子的 /system/media/ 目录就可以。

bootanimation.zip 的格式:

border@kvbian:~/work/bootanimation$ tree
.
├── desc.txt
└── part0
    ├── 00000.png
    ├── 00001.png
    ├── 00002.png
    └── 00003.png

desc.txt:
分辨率帧数
part 循环次数间隔时间目录
例如:

border@kvbian:~/work/bootanimation$ cat desc.txt 
1280 752 1
 
p 0 0 part0
 
border@kvbian:~/work/bootanimation$

当然这里可以设置多个部分，多方几个不同类型的动画，需要建多个动画的目录.

border@kvbian:~/work/bootanimation$ cat desc.txt 
1280 752 1
 
p 0 0 part0
 
p 0 0 part1
 
p 0 0 part2
 
border@kvbian:~/work/bootanimation$

完整的例子:

border@kvbian:~/work$ cd bootanimation/
border@kvbian:~/work/bootanimation$ ls
desc.txt  part0
border@kvbian:~/work/bootanimation$ tree
.
├── desc.txt
└── part0
    ├── 00000.png
    ├── 00001.png
    ├── 00002.png
    └── 00003.png
 
1 directory, 5 files
border@kvbian:~/work/bootanimation$ cat desc.txt 
1280 752 1
 
p 0 0 part0
 
border@kvbian:~/work/bootanimation$ ls
desc.txt  part0
border@kvbian:~/work/bootanimation$ zip -0 -r ../bootanimation.zip .
  adding: part0/ (stored 0%)
  adding: part0/00003.png (stored 0%)
  adding: part0/00001.png (stored 0%)
  adding: part0/00002.png (stored 0%)
  adding: part0/00000.png (stored 0%)
  adding: desc.txt (stored 0%)
border@kvbian:~/work/bootanimation$ ls -l ../bootanimation.zip 
-rw-rw-r-- 1 border border 408259 2012-04-14 23:08 ../bootanimation.zip
border@kvbian:~/work/bootanimation$ adb push ../bootanimation.zip /system/media
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Categories: Android Tags: android, bootanimation, rom, zip, 定制, 开机画面

[GUIDE] Android How To Modifying Custom ROM

April 10th, 2012 BianJiang No comments

看到一份比较全的如何制作Android ROM的文章，先贴过来。
From: http://www.android-indonesia.com/home/145-samsung-galaxy-y/135116-guide-modifying-custom-rom

>>>ADVANCED USER ONLY<<<<
kopas dari forum sebelah. jauh lebih simpel dari membuat ROM sendiri. maaf belum bisa translate (agak disengaja biar gak dibaca sembarangan). feel free to read and try.

I made this guide because I've found that a lot of us doesn't satisfied with our current custom ROM. Please don't bully the dev to make a rom with our personal preference. You may follow this guide instead to modify the custom rom to suit with your personal taset. I hope I could make it as simple as possible so all of us so even a new android user could understand. Please make sure you've read this guide throughly before make any modification.

Please note that this is just a simple guide. You won't find any guide about theming a rom here. Please refer to another guide about uot kitchen or apk modification.

tools:
Warning: Spoiler!
1. a custom rom (to be customized) or stock rom.
2. 7zip or another similar program
3. apk files
4. dsixda kitchen (mandatory)
5. apktools (mandatory)
6. titanium backup (mandatory)
7. CWM.

First of all, extract your custom rom. You'll see that the custom rom's zip file contain several files and folders. Some of them are common and could be find in almost all custom rom. The files and folders are:
Warning: Spoiler!
1. meta-inf : contain the script needed to install the rom (don't touch it if you don't understand about scripting nor dsixdia kitchen).
2. system : contain the system files and folder of the custom rom
3. boot.img : the kernel used in the custom rom
4. additional file : (eg:install-busybox, check-data and bmlunlock) additional file contain scripts needed to install additional feature (eg: busybox, additional app in data/app, and install custom kernel) in the custom rom.

NOTE:
Warning: Spoiler!
you can start from either stock or custom rom. If you start from stock rom, use CWM to make nandroid backup, then extract the system.rfs.tar. That's the system folder that we need later. You'll need installer script from other custom rom to make your rom installable to other device. In my past experience, the script form hybrid 2.1 or myss 3.4 is easy to use. I'd like suggest use them if you only want a light customization (without custom kernel, init.d script, or a2sd support.)

If you don't know much about them, don't touch anything but system folder
Warning: Spoiler!
now, open the the system folder. You'll see a lot of folders and some common files. Leave CSC files and SWconfiguration intact if you don't know about them. You can edit build.prop to insert more build.prop setting or modify the content if you understand how to do it. To change the rom's name, edit the value for 'ro.build.display.id'. You may also change the value for 'ro.build.version.release' to any number like 9.9.9 if you want to show off your modified custom rom

I'll give a quick explanation about the folders in /system.
Warning: Spoiler!
1. app : contain all the system's app
2. bin : contain the command and bin files for the rom (don't touch it)
3. cameradata : camera files
4. csc : csc files. contain dictionary for the keyboard
5. etc : additional setting and files for the rom
6. font : the fonts
7. framework : system's framework
8. lib : drivers, modules, for the rom
9. media : media files-ringtones, notification
10. sd : folder created by a2sd darktremor. (don't touch it)
11. usr : files needed for keyboard, bluetooth, etc.
12. xbin : additional command and bin files (busybox is normally installed here)(don't touch it)

NOTE: if you start from stock rom, copy all the files under /system folder (the one from system.rfs.tar) except /system/bin and system/xbin. don't touch them.

now, you're ready to customize the rom. I'll divide the guide into several section. pass the section if you don't want to modify it.

>>> SYSTEM APP-CUSTOMIZATION <<<
Warning: Spoiler!
DEODEX VS ODEXED ROM. Most of custom rom available is deodexed rom while our stock rom is half deodexed rom. I'll try to explain it in most simple way. First of all, we should understand that mostly every app in android consist of three part, *apk files, *dex/odex files, and lib files.

ODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in same folder with the apk files (/system/app). the positive side, it consume less internal memory. the negative side, it makes the app uncostumizable (cannot apply custom themes) and need more space in system partition.

DEODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in /data/dalvik-cache. the positive side, the app can be themed (full customizable) and consume less system partition. we could put more app in /system/app in deodexed rom. the negative side, it consume a lot of internal memory. please be cautious with the internal memory space if you use deodexed rom. (NOTE: if you start from stock rom, you may use dsixdia to convert odexed to deodexed rom).

system app customization is easy. you can add or remove any app in /system/app folder as long as it fit with the space in sistem partition (220MB). if you start from stock rom, please be cautious to not remove essential app from the folder. you may see the app in hybrid rom v.2.1 to see which app is safe to remove or not (the spreadsheet document in this forum is gone. sorry). having ~20mb free space in system partition is a good thing if you want to make the rom more customizable.

NOTE:
1. not all apk could be placed in /system/app (especially keyboard app)
2. tw launcher file is named tw'xxxxx'launcher.apk. you may remove it if you have another launcher.
3. not all custom launcerh could be placed in /system/app. you may put the launcher from other custom rom to minimalize the risk.

>>> THEME-CUSTOMIZATION <<<
Warning: Spoiler!
Basicly, theme is easily changed by replacing systemUI.apk in /system/app and framework-res.apk in /system/framework. You may put theme from another custom rom or make for yourself from uot kitchen or make it by yourself with apktool. A high modified theme like dysmenorrhea is also modify some part in setting.apk and jobmanager.apk. and another app. Don't forget to delete the *odex file (for all changed app only)from /system/app if you start from stock rom.

NOTE: please be aware with the base firmware of the rom. make sure that systemUI.apk and framework-res.apk files are from exact firmware version. I've found that theme for DXLA, DXLB, DXLC are exchangeable but you can't put theme from DXKL2 to DXLA or the reverse. to minimize any risk, please use themes only from exact same firmware.

>>> PERFORMANCE-TUNING <<<
Warning: Spoiler!

Performance tuning could be done in several ways. the easiest (proven works but risky) method is by edit build.prop file. I won't give you all the script. Feel free to search and apply the script with your personal preference. you can found in this forum or just copy from another rom. these script below is used to increase gprs/hsxdpa speed. this script is a common script and proven to be works in a lot of device. (I forgot the original source. sorry)

ro.ril.enable.dtm=1
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.enable.a53=1

======

the second way, (little bit harder, but its still proven works) by create or modify some file in /system/etc. I'll give you some of them.

1. sysctl script-to increase internet speed.
make a new file in system/etc, name it 'sysctl.conf' (or edit if it already exist). put this script inside.

net.ipv4.tcp_wmem = 4096 39000 187000
net.ipv4.tcp_rmem = 4096 39000 187000
net.ipv4.tcp_mem = 187000 187000 187000
net.ipv4.tcp_rfc1337 = 1
net.ipv4.tcp_sack = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_ecn = 0
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.route.flush = 1
net.ipv4.ip_no_pmtu_disc = 0
net.core.rmem_default = 524288
net.core.rmem_max = 524288
net.core.wmem_default = 524288
net.core.wmem_max = 524288

its a common sysctl mod for linux based OS (I found it in another mod for another device but I forgot the source). you'll need busybox, and terminal emulator. to run it, type:
'su
'sysctl -p
in your terminal emulator (without ' symbol).

2. GPS mod-to make the GPS lock faster
this mod is based on zeusseuz's guide. please see this page for further information (the script is quite long) forum.xda-developers.com/showthread.php?t=1552076

======

the last way...by init.d script. it only works in custom kernel. I won't put any script here. you should find by yourself.

======

>>> ADDITIONAL CUSTOMIZATION <<<
Warning: Spoiler!
I’ll only put the one I’ve tested and proven to be works.
1. beats audio
this is the old version but doesn’t have FC issue. get the file from here forum.xda-developers.com/showthread.php?t=1526643
unzip. copy all the files into their respective folder

2. bravia engine
put be_photo and be_movie in system/etc folder then edit the build.prop file doesn’t seems work. The real bravia engine mod is consist of
- be_photo, be_movie in /system/etc
- com.sonyericsson.android.SwIqiBmp.xml in /system/etc/permission
- com.sonyericsson.android.SwIqiBmp.jar in /system/framework
sorry, I can’t find the link. chobits rom have all the files needed. you may copy from the rom then put in your rom.

3. boot animation
download or get custom boot animation file from another custom rom or another source. rename it to bootanimation.zip, put it on /system/media.
you may check this out forum.xda-developers.com/showthread.php?t=1548479

please note that DXLB rom doesn’t support bootanimation. you need to put bootanimation and samsungani files from another rom (like hybrid) in /system/bin

4. boot sound
make or download boot sound. please make sure the format is *ogg. rename it to poweron.ogg then put it in /system/etc.

5. custom ringtones, notification,
make or download the sound file (in ogg format). put it in /system/media/audio/(respective folder)

6. disable boot animation (for quick boot)
put ‘debug.sf.nobootanimation=1′ in build.prop.

If you’ve done with the customization, enter the custom rom folder. select all the files then create zip file. to install the rom, copy to your sdcard, flash it either by stock recovery or CWM after wipe /data. PLEASE MAKE SURE THAT ALL THE FILES DOESN’T EXCEED THE LIMIT 220MB BEFORE ZIPPED.

DISCLAIMER:
1. do it with your own risk
2. please note that NOT ALL YOUR MODIFICATION WILL WORK. ROM modification is seriously hard thing. its not easy. thats why we should give the dev proper respect to them. you’ll need a lot of research to make it work.
3. this guide is made for personal use only. don’t publish the customized rom without permission from the original dev.

All credits for the dev who make the rom, the one I’ve used the guide here, and all XDA member. no need to say thanks or press it for me. give that to the real dev. I’m just a noob here. Feel free to correct me if I’m wrong.

Categories: Android Tags: android, apk, apktools, CWM, rom, 定制, 定制ROM

5PC2XX: Rename S5pc2XX to exynos

March 16th, 2012 BianJiang No comments

最新的Samsung的 Cortex-A9 和Cortex-A15的目录分别改为Exynos4和Exynos5，简单记录一下，以免忘记。

As per new naming convention for Samsung SoC’s, all Cortex-A9 and Cortex-A15
based SoC’s will be classified under the name Exynos. Cortex-A9 and Cortex-A15
based SoC’s will be sub-classified as Exynos4 and Exynos5 respectively.

In order to better adapt and reuse code across various upcoming Samsung Exynos
based boards, all uses of s5pc210 prefix/suffix/directory-names are renamed in
this patch. s5pc210 is renamed as exynos4210 and S5PC210/s5pc210 suffix/prefix
are renamed as exynos4/EXYNOS4.

Signed-off-by: Chander Kashyap <chander.kashyap@linaro.org>
---
Changes for v2:
       - Removed renaming of s5p-common to exynos4-common
       - Renamed s5pc210 prefixes to exynos4210
Changes for v3:
       - Dropped number 4 in exenos4.
 
Rebased on following commit.
19cdfd3e84bff108febb127b598ac3f1634c768c
"Ethernut 5 board support"
 
 MAINTAINERS                                        |    6 +-
 Makefile                                           |    2 +-
 arch/arm/cpu/armv7/{s5pc2xx => exynos}/Makefile    |    0
 arch/arm/cpu/armv7/{s5pc2xx => exynos}/clock.c     |   50 ++++++++--------
 arch/arm/cpu/armv7/{s5pc2xx => exynos}/soc.c       |    0
 .../asm/{arch-s5pc2xx => arch-exynos}/adc.h        |    0
 .../asm/{arch-s5pc2xx => arch-exynos}/clk.h        |    0
 .../asm/{arch-s5pc2xx => arch-exynos}/clock.h      |    2 +-
 .../asm/{arch-s5pc2xx => arch-exynos}/cpu.h        |   64 ++++++++++----------
 .../asm/{arch-s5pc2xx => arch-exynos}/gpio.h       |   28 ++++----
 .../asm/{arch-s5pc2xx => arch-exynos}/mmc.h        |    0
 .../asm/{arch-s5pc2xx => arch-exynos}/pwm.h        |    0
 .../asm/{arch-s5pc2xx => arch-exynos}/sromc.h      |    0
 .../asm/{arch-s5pc2xx => arch-exynos}/sys_proto.h  |    0
 .../asm/{arch-s5pc2xx => arch-exynos}/uart.h       |    0
 board/samsung/origen/lowlevel_init.S               |   26 ++++----
 board/samsung/origen/mem_setup.S                   |   12 ++--
 board/samsung/origen/origen.c                      |    8 +-
 board/samsung/origen/origen_setup.h                |    8 +-
 board/samsung/smdkv310/lowlevel_init.S             |   22 ++++----
 board/samsung/smdkv310/mem_setup.S                 |    8 +-
 board/samsung/smdkv310/smdkv310.c                  |    8 +-
 board/samsung/universal_c210/lowlevel_init.S       |   24 ++++----
 board/samsung/universal_c210/universal.c           |    8 +-
 boards.cfg                                         |    6 +-
 include/configs/origen.h                           |    6 +-
 include/configs/s5pc210_universal.h                |   10 ++--
 include/configs/smdkv310.h                         |    6 +-
 28 files changed, 152 insertions(+), 152 deletions(-)
 rename arch/arm/cpu/armv7/{s5pc2xx => exynos}/Makefile (100%)
 rename arch/arm/cpu/armv7/{s5pc2xx => exynos}/clock.c (81%)
 rename arch/arm/cpu/armv7/{s5pc2xx => exynos}/soc.c (100%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/adc.h (100%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/clk.h (100%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/clock.h (99%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/cpu.h (64%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/gpio.h (84%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/mmc.h (100%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/pwm.h (100%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/sromc.h (100%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/sys_proto.h (100%)
 rename arch/arm/include/asm/{arch-s5pc2xx => arch-exynos}/uart.h (100%)
 
diff --git a/MAINTAINERS b/MAINTAINERS
index 37bbb34..d493e4e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -691,12 +691,12 @@ Minkyu Kang <mk7.kang@samsung.com>
 
       SMDKC100                ARM ARMV7 (S5PC100 SoC)
       s5p_goni                ARM ARMV7 (S5PC110 SoC)
-       s5pc210_universal       ARM ARMV7 (S5PC210 SoC)
+       s5pc210_universal       ARM ARMV7 (EXYNOS4210 SoC)
 
 Chander Kashyap <k.chander@samsung.com>
 
-       origen                  ARM ARMV7 (S5PC210 SoC)
-       SMDKV310                ARM ARMV7 (S5PC210 SoC)
+       origen                  ARM ARMV7 (EXYNOS4210 SoC)
+       SMDKV310                ARM ARMV7 (EXYNOS4210 SoC)
.
.
.

From: linaro-dev@lists.linaro.org
Source: http://lists.linaro.org/pipermail/linaro-dev/2011-December/009015.html

–EOF–

Categories: Kernel Tags: Cortex-A15, Cortex-A9, Exynos, Exynos4, Exynos5, linaro, S5PC210, samsung

Older Entries

Linux kernel, Android, Golang & Recsys

Android基于ClockworkMod Recovery(CWM)的系统升级

在现存的Git里面增加一个远程的仓库

Android定制启动画面

[GUIDE] Android How To Modifying Custom ROM

5PC2XX: Rename S5pc2XX to exynos

站内搜索

Go语言中文讨论组

Sponsored Links

Categories

Recent Posts

Meta

Pages

Recent Comments

Categories

Blogroll

Archives