1 |
On Fri, Oct 30, 2009 at 8:34 PM, wireless <wireless@×××××××××××.com> wrote: |
2 |
> Can the gentoo embedded, openmoko, or any other |
3 |
> embedded linux stack run on the (verizon) Android |
4 |
> (verizon droid) phone? |
5 |
|
6 |
yes. |
7 |
|
8 |
my suggestions would be to |
9 |
|
10 |
1) cross-compile busybox statically for armv5tel |
11 |
2) push the busybox binary (and symlinks) to the device using adb |
12 |
3) download a gentoo stage3 filesystem for armv5tel |
13 |
4) extract the filesystem to a suitable memory card |
14 |
5) log in to the device using 'adb shell' |
15 |
6) execute '/bin/ash' (the busybox shell) |
16 |
7) mount proc sys dev -o bind to your memory card, where the gentoo |
17 |
root is installed |
18 |
8) chroot to the gentoo root filesystem |
19 |
|
20 |
If you do that, you'll have android and gentoo 'running' on the device |
21 |
at the same time. I'm not sure how easy it is to do all of that on a |
22 |
Motorola Droid, and you might need to make some software modifications |
23 |
to start the adb (android debug bridge) service on the device. |
24 |
|
25 |
You can of course do the same with an OpenMoko filesystem image |
26 |
instead of a Gentoo filesystem image. Unfortunately, you won't be able |
27 |
to use the framebuffer while Android is using it (AFAIK). |
28 |
|
29 |
> Isn't the Android(2.0) phone just somebody's Linux |
30 |
> stack? If so, is it an open/hackable embedded |
31 |
> linux stack for an Arm? |
32 |
|
33 |
I would suggest that you ask Motorola to release the source code for |
34 |
their Droid Linux kernel. Aside from that, all of the available source |
35 |
and documentation for Android is at http://source.android.com . Note |
36 |
that most of the 'good' Android apps are not open source - they (e.g. |
37 |
Google, Motorola, HTC) can get away with that because the userland is |
38 |
made available under an Apache-2.0 license. |
39 |
|
40 |
If you really want to experiment, then try to modify the Droid boot |
41 |
loader so it will boot into your Gentoo root on /dev/mmcblk0p1 or |
42 |
something instead of /dev/mdtblockX (where Android resides). You'll |
43 |
probably want to check out mtd-utils to do that. Warning: You'll most |
44 |
likely void your warranty by doing so, and you might end up with a |
45 |
bricked device. |
46 |
|
47 |
IMHO - the best (current) device you can use for a hackable handheld |
48 |
is the Nokia N900 - I wish I had one myself. |
49 |
|
50 |
Good luck! |