変更点いろいろ
From git://git.android-x86.org/device/amd 63e8d94..586ba1e ics-x86 -> x86/ics-x86 From git://git.android-x86.org/device/asus 73e0bbf..8f1492e ics-x86 -> x86/ics-x86 From git://git.android-x86.org/device/tegatech/tegav2 9fc1167..26e7230 ics-x86 -> x86/ics-x86 From git://git.android-x86.org/platform/system/vold 3ad9072..3fef6f5 ics-x86 -> x86/ics-x86
kinneko@BuildSV:~/ICSx86/device/amd$ git log 63e8d94..586ba1e
commit 586ba1ee9f2ff7ea5dd52b760f4426405df9a58e
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Wed Dec 7 10:12:07 2011 +0800
brazos_defconfig: add support for rt2800pci
This enables wifi for HP Pavilion DM1 Netbook series.
kinneko@BuildSV:~/ICSx86/device/asus$ git log 73e0bbf..8f1492e
commit 8f1492ee052625103f9b7cc013ea49807a31ccfe
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Thu Dec 8 11:36:05 2011 +0800
eeepc_defconfig: correct Atheros wifi support
kinneko@BuildSV:~/ICSx86/device/tegatech/tegav2$ git log 9fc1167..26e7230
commit 26e7230815a31f0ea7254305a782104a8a7df4d8
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Thu Dec 8 13:38:37 2011 +0800
update for ics-x86
kinneko@BuildSV:~/ICSx86/system/vold$ git log 3ad9072..3fef6f5
commit 3fef6f53251274745beb6e07f4c5087f4ad8cbf2
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Thu Dec 9 11:23:24 2010 +0800
vold: extend the syntax of vold.fstab
Now vold.fstab can accept the following:
dev_mount sdcard /mnt/sdcard auto <devpath> // use normal DirectVolume
dev_mount sdcard /mnt/sdcard auto SDCARD=dev_node // use AutoVolume for spec
dev_mount sdcard /mnt/sdcard auto // use AutoVolume to mount
commit 376a3b7ce95a35da7f00c730dbc36066b78fe298
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Thu Nov 18 11:54:00 2010 +0800
vold: add class AutoVolume to support auto-mount and fake sdcard
commit c827dae19b3347304a3ad79e6f0cd8a4c3af6d20
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Fri Aug 6 17:20:54 2010 +0800
void: avoid duplicate code
commit 31b42c286168b8c7cdb18561f4f3e064d078f319
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Thu Jan 27 11:30:28 2011 +0800
vold: do not consider a fatal error on initializeMbr failed
Instead, format the entire device and try to mount it.
In this way we are able to support more generic block devices
like loopback device or ramdisk. It's not possible to initialize
mbr on such devices. But they can still be formatted and
mounted correctly.
Change-Id: I14b3cd1b2986c84efba1f9ce5dba99634b6b462f
commit e6fea9e0a6afea91cf154f66d71027f2e31b776b
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Thu Jan 27 11:18:03 2011 +0800
vold: derived the partition to be formatted according to the disk
The minor number of a block device is not always 0. For example,
for a usb stick /dev/block/sdc, it's (8,32).
Change-Id: Ic155296a1cead2293b8ffbbbbdbbdd61acac9021
commit c81b89612a3388352111d30d87b3eb81d6c7978b
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Tue Dec 14 15:47:00 2010 +0800
vold: fix a race condition between vold and MountService
The details of the race condition is described in the post:
http://groups.google.com/group/android-platform/browse_thread/thread/724b3a2
Change-Id: I1a1d9840fd3d25164e60b6c94ea36c6c1d2e9095
commit 31304f008bec033098733f83050fedd388f6d76f
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Tue Dec 14 13:41:40 2010 +0800
vold: fix always pending issue if partition table is not continuous
The partition table may not be continuous, say
Device Boot Start End Blocks Id System
/dev/block/sdd1 20480 4214783 2097152 c W95 FAT32 (LBA
/dev/block/sdd3 5955584 7744511 894464 83 Linux
In this case the volume will always be pending.
So instead of relying on mPendingPartMap, just count how many
partitions we expected.
Besides, if block uevent missing 'NPARTS', set mDiskNumParts = 0.
Change-Id: I90d84781f3f9d0ea507841b29d4ae1bade368a98
commit a2677dab9b582e83d5d586c932202a89fe222dd5
Author: Chih-Wei Huang <cwhuang@linux.org.tw>
Date: Thu Nov 18 17:33:58 2010 +0800
vold: avoid mismatch wrong device with same prefix
Suppose we have two devices whose devpath are
/devices/...../mmcblk1
/devices/...../mmcblk11
and the first is the target device. The current implementation will
mismatch the later device.
Since we hope to match the target device and its partitions
whose devpath are
/devices/...../mmcblk1/...
so the correct devpath should have the expected prefix,
followed by '\0' or '/'.
Change-Id: I398b55712b884a8499f73a52bc863b4d8294ee5e
tegav2では、
AndroidBoard.mkで、LOCAL_FIRMWARESがath3k-2.fwから ath3k-1.fwに変更。
tegav2.mkで、PRODUCT_COPY_FILESで、Vendor_20b3_Product_0a18.idc, Vendor_03eb_Product_201c.idcのパス変更。
tegav2_defconfigに、ネットフィルタまわり、IPv6、トンネル、NAT、CRYPTOでいくつかマストにくらい。
+CONFIG_INET_ESP=y -CONFIG_INET_TUNNEL=m +CONFIG_INET_TUNNEL=y -CONFIG_IPV6_SIT=m +CONFIG_IPV6_SIT=y +CONFIG_NETFILTER=y +CONFIG_NETFILTER_ADVANCED=y +CONFIG_NETFILTER_NETLINK=y +CONFIG_NETFILTER_NETLINK_QUEUE=y +CONFIG_NETFILTER_NETLINK_LOG=y +CONFIG_NF_CONNTRACK=y +CONFIG_NF_CONNTRACK_MARK=y +CONFIG_NF_CONNTRACK_EVENTS=y +CONFIG_NETFILTER_TPROXY=y +CONFIG_NETFILTER_XTABLES=y +CONFIG_NETFILTER_XT_TARGET_TPROXY=y +CONFIG_NETFILTER_XT_MATCH_HL=y +CONFIG_NETFILTER_XT_MATCH_QTAGUID=y +CONFIG_NETFILTER_XT_MATCH_SOCKET=y +CONFIG_NF_DEFRAG_IPV4=y +CONFIG_NF_CONNTRACK_IPV4=y +CONFIG_NF_CONNTRACK_PROC_COMPAT=y +CONFIG_IP_NF_IPTABLES=y +CONFIG_IP_NF_MATCH_AH=y +CONFIG_IP_NF_MATCH_ECN=y +CONFIG_IP_NF_MATCH_TTL=y +CONFIG_IP_NF_FILTER=y +CONFIG_IP_NF_TARGET_REJECT=y +CONFIG_IP_NF_TARGET_LOG=y +CONFIG_NF_NAT=y +CONFIG_NF_NAT_NEEDED=y +CONFIG_IP_NF_TARGET_MASQUERADE=y +CONFIG_IP_NF_TARGET_NETMAP=y +CONFIG_IP_NF_TARGET_REDIRECT=y +CONFIG_IP_NF_MANGLE=y +CONFIG_NF_DEFRAG_IPV6=y +CONFIG_IP6_NF_IPTABLES=y +CONFIG_CRYPTO_AEAD=y +CONFIG_CRYPTO_AUTHENC=y -CONFIG_CRYPTO_MD5=m +CONFIG_CRYPTO_MD5=y -CONFIG_CRYPTO_DES=m +CONFIG_CRYPTO_DES=y
