Port Bionic to a new CPU

735 views
Skip to first unread message

Jallen

unread,
Jul 18, 2009, 11:34:24 AM7/18/09
to android-porting
Hi, everybody!

I'm a newbee of android development~ Recently, I'm involved in a
project of porting android to a new CPU which uses RISC. And my task
is the bionic part.

Now I'm still puzzled by which files are involved in the arch-related
part. I'm planning to follow the arm way to accomplish the task.
Tranlate all .S and .h files in the Arch-arm or Arm directories. I
don't know whether it will works...

So, would someone who has similar experiences provide me some guide,
like useful links or key words.

Thank you!
Jallen.o.y

Neo

unread,
Jul 22, 2009, 3:05:13 AM7/22/09
to android-porting
The best though fraught with dangers is to compile both the kernel and
android with the tool chain which supports your cpu.

Ouyang Jiannan

unread,
Jul 22, 2009, 5:09:40 AM7/22/09
to android...@googlegroups.com
Thanks for your reply
Now, our team has port linux kernel, gcc, glibc, binutils to our cpu, these are tools I'm using

ghalib khan

unread,
Dec 21, 2020, 12:41:57 PM12/21/20
to android-porting
Hello Ouyang Jiannan,
 
                 This is ghalib khan a senior software engineer,  started working on android porting to RISC-V, can you help in porting android to new platform RISC-V, i think you are working with RISC but still wan't to know porting thinks, am new in porting line.

Thanks in advance.
Ghalib khan c. 

Chen Wang

unread,
Dec 28, 2020, 1:34:30 PM12/28/20
to android-porting
hello, Jallen
I find this old email from out of this group, how about your progress? I wonder what's the risc chip you were working with? Because I'm studying how to port android to RISC-v.

Notur Business

unread,
Mar 20, 2021, 1:11:37 PM3/20/21
to android-porting
I can't give you a list of commands.  But clang can compile to a target without use of multiple computers.  However:  news I heard is that compiling Linux Kernel for an unsupported architecture is NOT SIMPLE.  If one of the known good architectures covers "many but not more" for your target CPU your luck.  If not, it is "not supposed to be easy".

You should know you compile linux with target processor.  Then the whole tool chain the same.  Then assemble a (likely bootable usb), and boot the device with that USB.  Then also, if your serious, you would configure the kernel for remote debugging if you have that need (say, serial?)

that's all very simple stuff.  i hope i'm not repeating things people didn't need to hear.
Reply all
Reply to author
Forward
0 new messages