This wiki shows me the detail procedure to use git to work with Google code.
The main procedure is:
1. git svn clone --username my-gmail-name -s https://my-project.googlecode.
2. git add FILENAME
3. git commit -a
4. git svn dcommit --username jacky.tw -s https://my-project.googlecode.
2009年11月20日星期五
How to work with Google code
Good article to start Gstreamer plugin
If you want to study Gstreamer plugin writing tip, I would like to share this with you all.
參考來源： furseal's lair: 踏出 gstreamer plugin 的第一步 (在「Google 網頁註解」中檢視)2009年11月8日星期日
Howto run native Linux application on Android
Recently I am working an Embedded Linux Internal project, and use many open source tools to build cross compiler, Linux kernel, small Linux root filesystem on JK2410(Jollen Kit based on Samsung S3C2410 - ARM 920T).
From this project I learned how to build cross compiler, busybox by myself. and use such kind of tools, the static linked code also can run on Android emulator. I would like to share this knowledge from this blog.
First I used OSELAS toolchain, it must be build by ptxdist tool.
Following is the step how to build ptxdist and setup the right gcc, kernel version you want to build the toolchain. Download ptxdist-1.99.12.tgz and ptxdist-1.99.12-patches.tgz from http://www.ptxdist.org/software/ptxdist/download/v1.99/
Run command in the terminal shell:
# tar -zxf ptxdist-1.99.12.tgz
# tar -zxf ptxdist-1.99.12-patches.tgz
# ./configure --prefix=/usr/local
# make
# make install
then, download OSELAS.Toolchain-1.99.3.5.tar.bz2 from http://www.oselas.com/oselas/toolchain/download/
Run following command in the terminal shell:
# tar xf OSELAS.Toolchain-1.99.3.5.tar.bz2
# cd OSELAS.Toolchain-1.99.3.5
# ptxdist select ptxconfigs/arm-v4t-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.31-sanitized.ptxconfig
# ptxdist go
After run "ptxdist go", the tool will get the source code, patch from Internet, and compile the right CPU architecture, gcc, glibc, binutils and kernel version as the select setting you give. You can change the ptxconfig to more match your platform requirement.
The build procedure will take 1 to 2 hours depended on your Building host computing power.
After it finished, you can find the toolchain in /opt/OSELAS.Toolchain-1.99.3/ directory, so make sure your running user have permission to write file into /opt directory.
2nd Step is build up a static linked busybox, now it have some problem to run dynamic shared code on Android, because the linker system program in Android use different technology with toolchain. I haven't let dynamic code run successfully on Android.
Get busybox-1.15.2.tar.bz2 from http://www.busybox.net/downloads/
#tar jxvf busybox-1.15.2.tar.bz2
#cd busybox-1.15.2
#make menuconfig
This step you must change the Busybox setting -> Build options
Choose Build BusyBox as a static binary (no shared libs)
and Set Cross Compiler prefix as "arm-v4t-linux-gnueabi-"
#make
Now you can see the striped busybox present in this folder
3rd Step is to prepare the Android SDK environment, you can get it from here
Please notice the link will not get the whole package, you must following this instruction to get more add-on package.
Assume you place android sdk in /opt/Google/android-sdk-linux, add "/opt/Google/android-sdk-linux/tools" in your PATH variable.
then, run following command:
#android create avd -n my_droid -t 1
#emulator -avd my_droid -shell
From now now, you can see a magic emulator Google phone is launched, and the previous terminal become a single # as prompt.
In this prompt, you are in the Android root shell, you can type "ls -l" "cd" "pwd" as normal command.
Now you also need use following command(in Host Terminal) to put busybox binary into Android emulator.
#adb push busybox /data/busybox
#adb shell chmod 755 /data/busybox
Final, switch to Android shell, and type
#/data/busybox ls -al /system
You can see the file list from the busybox binary output.
This purpose of article is just to share the toolchian buildup experience, and the native C code compatibility on Android platform. You must not to use this way to run your original application. You shall learn how to use Android NDK to build your native C/C++ library.
I am now studying this as my next step to learn more about Android platform. If you are interested on this, we can discuss this by email or other way.
From this project I learned how to build cross compiler, busybox by myself. and use such kind of tools, the static linked code also can run on Android emulator. I would like to share this knowledge from this blog.
First I used OSELAS toolchain, it must be build by ptxdist tool.
Following is the step how to build ptxdist and setup the right gcc, kernel version you want to build the toolchain. Download ptxdist-1.99.12.tgz and ptxdist-1.99.12-patches.tgz from http://www.ptxdist.org/software/ptxdist/download/v1.99/
Run command in the terminal shell:
# tar -zxf ptxdist-1.99.12.tgz
# tar -zxf ptxdist-1.99.12-patches.tgz
# ./configure --prefix=/usr/local
# make
# make install
then, download OSELAS.Toolchain-1.99.3.5.tar.bz2 from http://www.oselas.com/oselas/toolchain/download/
Run following command in the terminal shell:
# tar xf OSELAS.Toolchain-1.99.3.5.tar.bz2
# cd OSELAS.Toolchain-1.99.3.5
# ptxdist select ptxconfigs/arm-v4t-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.31-sanitized.ptxconfig
# ptxdist go
After run "ptxdist go", the tool will get the source code, patch from Internet, and compile the right CPU architecture, gcc, glibc, binutils and kernel version as the select setting you give. You can change the ptxconfig to more match your platform requirement.
The build procedure will take 1 to 2 hours depended on your Building host computing power.
After it finished, you can find the toolchain in /opt/OSELAS.Toolchain-1.99.3/ directory, so make sure your running user have permission to write file into /opt directory.
2nd Step is build up a static linked busybox, now it have some problem to run dynamic shared code on Android, because the linker system program in Android use different technology with toolchain. I haven't let dynamic code run successfully on Android.
Get busybox-1.15.2.tar.bz2 from http://www.busybox.net/downloads/
#tar jxvf busybox-1.15.2.tar.bz2
#cd busybox-1.15.2
#make menuconfig
This step you must change the Busybox setting -> Build options
Choose Build BusyBox as a static binary (no shared libs)
and Set Cross Compiler prefix as "arm-v4t-linux-gnueabi-"
#make
Now you can see the striped busybox present in this folder
3rd Step is to prepare the Android SDK environment, you can get it from here
Please notice the link will not get the whole package, you must following this instruction to get more add-on package.
Assume you place android sdk in /opt/Google/android-sdk-linux, add "/opt/Google/android-sdk-linux/tools" in your PATH variable.
then, run following command:
#android create avd -n my_droid -t 1
#emulator -avd my_droid -shell
From now now, you can see a magic emulator Google phone is launched, and the previous terminal become a single # as prompt.
In this prompt, you are in the Android root shell, you can type "ls -l" "cd" "pwd" as normal command.
Now you also need use following command(in Host Terminal) to put busybox binary into Android emulator.
#adb push busybox /data/busybox
#adb shell chmod 755 /data/busybox
Final, switch to Android shell, and type
#/data/busybox ls -al /system
You can see the file list from the busybox binary output.
This purpose of article is just to share the toolchian buildup experience, and the native C code compatibility on Android platform. You must not to use this way to run your original application. You shall learn how to use Android NDK to build your native C/C++ library.
I am now studying this as my next step to learn more about Android platform. If you are interested on this, we can discuss this by email or other way.
2009年9月29日星期二
17 FreeCall - 網頁電話服務宣稱可以免費撥打台灣市話及手機
Source from: http://www.ithome.com.tw/
博祥網通繼Web Talk雲端運算在市場造成轟動後，
所謂17Freecall，即一起打免費電話。
博祥網通廣告託播服務還不止於此，
Soga, Now RTLinux is belonged to WindRiver
It now separate two types of license, one is free used version, another is commercial version
參考來源："Wind River Systems acquired FSMLabs technology in February 2007 and now makes a version available as Wind River Real-Time Core for Wind River Linux."
- RTLinux - Wikipedia, the free encyclopedia (在「Google 網頁註解」中檢視)
2009年7月27日星期一
How to subscribe Google voice service
看到Google要推voice服務的新聞，已經有一陣時間了，記得很早就到這里申請邀請函了。而在前一個禮拜終於收到邀請函，二話不說，馬上就來試用一下，結果啟始網頁竟然說目前僅提供美國地區，哇，這是擺我一道嗎？我想Google的事就問Google吧，搜尋的結果，說是可以透過Proxy或者Open VPN來讓Google認為你是從美國當地網路過來的，後來透過asterisk-tw@googlegroups.com熱心網友提供一個不錯的網站 - http://hotspotshield.com/ ，下載一個VPN工具後，很簡單的就連上美國的SSLVPN，完全不需要做任何的設定，若不放心此網路程式，建議在虛擬機器上跑（我就是這樣做的）
網路環境準備好後，當然最重要的是要有邀請函了。沒有的可以到這里申請，要等多久我就不知道了。前二個禮拜，我又去申請了3個，結果今天就全部都收到了。
透過邀請函連接可以使用原先Gmail帳號登入，或者申請一個新的帳號。接下來的動作就是他會自動配發一個美國的電話號碼給你，像這樣的格式 （408）512-3803，你可以先查一下你比較想在那個區域，我會選在矽谷地區，是因為公司有些代理的原廠總部是在那里。
號碼選定後，就剩下最后一個步驟了，一定要設定一個可轉接的美國號碼（手機或市話，不可使用網路電話）才能完成整個啟用程序喔。
為了解決這個問題，我找到了ipkall及virtualphoneline都可取得美國市話號碼，申請步驟請各位自行看Signup頁面。ipkall大約要等3天，而Virtualphoneline透過facebook馬上申請，馬上開通帳號。不過Virtualphoneline不是提供完全免費的DID，你還需要按下Try Free ，按下後馬上可以免費使用25天的市話轉VoIP設定，它提供的轉接設定，還蠻多的，例如MSN，Skype, Gtalk。我是設定讓他撥到此Virtual PSTN時轉到Skype。
當這個DID轉接設定好後，就可以將此DID填入Google Voice的轉接號碼內，然后按下Call me now。這時Skype就響了，你只要在Skype的撥號盤上輸入Google voice上看到的認證碼就可以完成啟用程序了。
完成整個啟用程序後，就不需要再使用VPN連線了，我想他只有擋一開始的啟用程式吧。此外Google Voice啟用後，就可以在Setting里面的Phone加Gizmo號碼，然後就可以將此Virtual PSTN停用掉，因為25天後，我不會付費繼續使用這個Virtualphoneline的DID阿。
各位若不是很了解Google voice的，可以看這里。
2009年6月13日星期六
FreedomHEC 2009 at Taipei(6/10,11)
今年是第一次參加FreedomHEC，首先說明什麼是FreedomHEC。
FreedomHEC Taipei是場有關Open Source系統的硬體研討會。透過本研討會，台灣的工程師可與國際資深Linux開發者交流。台灣的廠商可以得到國內外Linux專家的協助，以非常低的成本開發出Linux驅動程式，並整合至上游Linux系統中，讓產品能有即時的Linux支援。
詳細活動網站在這裡
今年主辦單位邀請到數位著名的Linux國外專家，例如Greg,Jonathan,Harald
Greg和Jonathan是Linux Device Driver這本書的作者。而Harald則是netfilter/iptables的開發者，同是也是gpl-violations組織的創辦人。而台灣本土專家則有Jserv,Matt,CIH等。
這裡大概整理一下自己的心得：
Jonathan的內容主要環繞在如何跟Linux Kernel community協同運作，讓自己的driver能上傳至mainline，並且得到Community的協助，增加程式碼品質。
Greg的driver教學則是以實際的USB溫度計來實作Linux驅動程式，內容相當實用。教學過程所使用程式碼，可從這裡下載。
Harald除了是著名的Linux開發者身份外，目前也致力於違背GPL產品查核工作。從他的部落格可以看到最近他盯上了Palm pre這個產品。演講中提到可用那些方法來找出GPL軟體使用證據。例如ROM, Console, JTAG, Reverse Engineering等等。
Jserv及Matt的主體是Qi-Lightweight Bootloader。目前u-boot及Redboot已經非常強大，為何還需要Qi Bootloader，請看Jserv的簡報。
最後是CIH病毒的作者陳盈豪主講的Linux Driver Reverse Engineering。內容真是精彩萬分，技術範圍包含硬體架構,組合語言,程式的除錯技巧等等，真是大開眼界阿。
這二天的收獲真的是滿滿的，但客戶的email還是那麼多，幸好我已經練就隨時可用手機收發的功力，讓我可以在吸收新知之餘又可同時工作，真該感謝現代高科技產品。
FreedomHEC Taipei是場有關Open Source系統的硬體研討會。透過本研討會，台灣的工程師可與國際資深Linux開發者交流。台灣的廠商可以得到國內外Linux專家的協助，以非常低的成本開發出Linux驅動程式，並整合至上游Linux系統中，讓產品能有即時的Linux支援。
詳細活動網站在這裡
今年主辦單位邀請到數位著名的Linux國外專家，例如Greg,Jonathan,Harald
Greg和Jonathan是Linux Device Driver這本書的作者。而Harald則是netfilter/iptables的開發者，同是也是gpl-violations組織的創辦人。而台灣本土專家則有Jserv,Matt,CIH等。
這裡大概整理一下自己的心得：
Jonathan的內容主要環繞在如何跟Linux Kernel community協同運作，讓自己的driver能上傳至mainline，並且得到Community的協助，增加程式碼品質。
Greg的driver教學則是以實際的USB溫度計來實作Linux驅動程式，內容相當實用。教學過程所使用程式碼，可從這裡下載。
Harald除了是著名的Linux開發者身份外，目前也致力於違背GPL產品查核工作。從他的部落格可以看到最近他盯上了Palm pre這個產品。演講中提到可用那些方法來找出GPL軟體使用證據。例如ROM, Console, JTAG, Reverse Engineering等等。
Jserv及Matt的主體是Qi-Lightweight Bootloader。目前u-boot及Redboot已經非常強大，為何還需要Qi Bootloader，請看Jserv的簡報。
最後是CIH病毒的作者陳盈豪主講的Linux Driver Reverse Engineering。內容真是精彩萬分，技術範圍包含硬體架構,組合語言,程式的除錯技巧等等，真是大開眼界阿。
這二天的收獲真的是滿滿的，但客戶的email還是那麼多，幸好我已經練就隨時可用手機收發的功力，讓我可以在吸收新知之餘又可同時工作，真該感謝現代高科技產品。
訂閱：
文章 (Atom)
