Add new target
The article describes how to create a target for your own device under Android-x86. Rewritten from the e-mail Chih-wei Huang sent to android-x86 discussion group. You can find the original e-mail in https://mail.google.com/mail/?ui=2&shva=1#search/Chih-wei/125eb28a674c23e9
Create a directory
First, you have to create a directory to hold all stuff specific for your target device.
where xxx is usually the vendor's name and yyy is the product name. Historically, we used the vendor/ directory. However, Google suggested to use device/ since Froyo. We encourage to use the new convention device/ as AOSP does.
At least you have to create four makefiles in the new directory:
This makefile should only contain PRODUCT_MAKEFILES which is a list of product makefiles to expose to the build system. So if your product name is yyy, it is
PRODUCT_MAKEFILES := $(LOCAL_DIR)/yyy.mk
The product makefile: yyy.mk
You have to define PRODUCT_PACKAGES, PRODUCT_NAME, PRODUCT_DEVICE in it, and call inherit-product to inherit from a product makefile.I suggest to to inherit generic_x86.mk to get all common x86 rules.
The board config makefile: BoardConfig.mk
You can override some variables before including $(GENERIC_X86_CONFIG_MK)
set to true if you hope to compile third party apps like ConnectBot, FileManager introduced by Android-x86.
Set to false if you don't want ALSA audio.
If you don't need bluetooth, set it to false.
Set to true if you need tslib to calibrate the touchscreen.
You can customize your cmdline (kernel boot options)
Set to true if you need wifi support
You can override some variables before including
Specify the firmwares to be included in the target. The firmwares are supposed to be already in build/target/board/generic_x86/firmware/.
You may also specify a different directory in LOCAL_FIRMWARES_DIR.
Specify a hook script to be added in the initrd.img. Usually the script should contain a detect_hardware function that will be called by the init script.
Read eeepc_info as an implementation example.