On 5月10日, 上午4時08分, Yi Sun <[email protected]> wrote: > There are a few things planed in my mind for next: > 1. a mail list for Eeepc/X86 issues only
I think android-porting list is just good for it. Unless the topics are too hot, then we can fork a new list. > 2. a git server for Eeepc/x86 platforms. Yes. Since the eee_701 project is almost dead, I do think to re-invent a new one is better. Actually I'm planning to do that. But there are something I need to figure out first. Instead of eee_701, I plan to use a more generic name like eeepc (more generic? please suggest). And I hope to add some scripts to automatically detect the hardware and load appropriate drivers or configurations. The problem is, now it is not possible to use shell scripts in android ramdisk(boot.img). Current I'm considering two approaches: 1. Add /system/bin/sh (+linker, all necessary libraries) to ramdisk. I also have to add toolbox that provides utilities for scripts. However, android toolbox lacks some important utilities like sed and cut. Without them it's hard to write useful scripts. So I may have to add the necessary utilities to toolbox first. 2. Add a prebuilt, static linked busybox with all utilities I need to ramdisk. The approach may be much easier, but I don't know if it is acceptable by google. I may need your comments to move on. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
