Post Reply

[DEV][Info] BoardConfig.mk for kernel developer and AOSP (platform) developer

2nd May 2012, 03:09 PM   |  #11  
F3niX's Avatar
Senior Member
Flag Hyderabad
Thanks Meter: 297
 
688 posts
Join Date:Joined: Jul 2010
More
Where have you been Mate?? Awesome Work!! Continue!!
2nd May 2012, 04:17 PM   |  #12  
OP Senior Member
Thanks Meter: 388
 
224 posts
Join Date:Joined: Oct 2011
So I have figured out our right BoardConfig.mk. Do not change the TARGET_ARCH_VARIANT_FPU, otherwise the boot.img won't boot @ all.

LOCAL_PATH := $(call my-dir)
#USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/samsung/I9103/BoardConfigVendor.mk

TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a
TARGET_ARCH_VARIANT_CPU := cortex-a9
# DO NOT change the following line to vfpv3 as it is not supported on our device!
TARGET_ARCH_VARIANT_FPU := vfpv3-d16
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_HAVE_TEGRA_ERRATA_657451 := true
TARGET_BOARD_PLATFORM := tegra
TARGET_BOARD_PLATFORM_GPU := tegra # Useless for CM7 build
TARGET_BOOTLOADER_BOARD_NAME := n1
TARGET_USERIMAGES_USE_EXT4 := true

BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048

# fix this up by examining /proc/mtd on a running device
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000
BOARD_FLASH_BLOCK_SIZE := 2048

TARGET_PREBUILT_KERNEL := device/samsung/I9103/kernel

TARGET_NO_KERNEL := false
TARGET_NO_RECOVERY := false
TARGET_NO_BOOTLOADER := true
TARGET_NO_RADIOIMAGE := true

BOARD_HAS_NO_SELECT_BUTTON := true
# Use this flag if the board has a ext4 partition larger than 2gb
BOARD_HAS_LARGE_FILESYSTEM := true
Last edited by UnknownzD; 2nd May 2012 at 04:21 PM.
The Following 6 Users Say Thank You to UnknownzD For This Useful Post: [ View ]
2nd May 2012, 04:24 PM   |  #13  
OP Senior Member
Thanks Meter: 388
 
224 posts
Join Date:Joined: Oct 2011
btw the errata fix is for our cpu and is only needed on userland (non-kernel side binary), do not remove that errata fix otherwise the SMP part doesn't work. It requires the errata patch to make it working.
The Following 4 Users Say Thank You to UnknownzD For This Useful Post: [ View ]
2nd May 2012, 04:31 PM   |  #14  
Senior Member
Thanks Meter: 201
 
119 posts
Join Date:Joined: May 2010
Quote:
Originally Posted by UnknownzD

So I have figured out our right BoardConfig.mk. Do not change the TARGET_ARCH_VARIANT_FPU, otherwise the boot.img won't boot @ all.

LOCAL_PATH := $(call my-dir)
#USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/samsung/I9103/BoardConfigVendor.mk

TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a
TARGET_ARCH_VARIANT_CPU := cortex-a9
# DO NOT change the following line to vfpv3 as it is not supported on our device!
TARGET_ARCH_VARIANT_FPU := vfpv3-d16
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_HAVE_TEGRA_ERRATA_657451 := true
TARGET_BOARD_PLATFORM := tegra
TARGET_BOARD_PLATFORM_GPU := tegra # Useless for CM7 build
TARGET_BOOTLOADER_BOARD_NAME := n1
TARGET_USERIMAGES_USE_EXT4 := true

BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048

# fix this up by examining /proc/mtd on a running device
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000
BOARD_FLASH_BLOCK_SIZE := 2048

TARGET_PREBUILT_KERNEL := device/samsung/I9103/kernel

TARGET_NO_KERNEL := false
TARGET_NO_RECOVERY := false
TARGET_NO_BOOTLOADER := true
TARGET_NO_RADIOIMAGE := true

BOARD_HAS_NO_SELECT_BUTTON := true
# Use this flag if the board has a ext4 partition larger than 2gb
BOARD_HAS_LARGE_FILESYSTEM := true

Compiling a CM7 build right now!!!
Will be back soon...
Thank you soo much!!
The Following 3 Users Say Thank You to FranzJesus For This Useful Post: [ View ]
2nd May 2012, 05:24 PM   |  #15  
OP Senior Member
Thanks Meter: 388
 
224 posts
Join Date:Joined: Oct 2011
Quote:
Originally Posted by FranzJesus

Compiling a CM7 build right now!!!
Will be back soon...
Thank you soo much!!

If you guys want to see the difference between the old armv7-a.mk and my version, look it here : http://review.cyanogenmod.com/#/c/15...arm/armv7-a.mk

Now I need some time to finish my CWM, by working on the ramdisk.
The Following 4 Users Say Thank You to UnknownzD For This Useful Post: [ View ]
3rd May 2012, 09:43 AM   |  #16  
OP Senior Member
Thanks Meter: 388
 
224 posts
Join Date:Joined: Oct 2011
I have a minor update on the first post as changing the line
TARGET_ARCH_VARIANT_FPU := vfpv3
to
TARGET_ARCH_VARIANT_FPU := vfpv3-d16

That is because our device won't boot with the code compiled with -mfpu=vfpv3. Please refer to the first post for more info.
The Following User Says Thank You to UnknownzD For This Useful Post: [ View ]
3rd May 2012, 03:22 PM   |  #17  
CallMeVentus's Avatar
Recognized Contributor
Flag Singapore
Thanks Meter: 2,867
 
9,969 posts
Join Date:Joined: Jul 2011
Donate to Me
More
Wow you're good . My hat's off to you sire

This was sent from a Galaxy Ace. Problem?
4th May 2012, 06:38 AM   |  #18  
CallMeVentus's Avatar
Recognized Contributor
Flag Singapore
Thanks Meter: 2,867
 
9,969 posts
Join Date:Joined: Jul 2011
Donate to Me
More
Will the errata patch update the ARMv7 revision ?

This was sent from a Galaxy Ace. Problem?
4th May 2012, 06:45 AM   |  #19  
OP Senior Member
Thanks Meter: 388
 
224 posts
Join Date:Joined: Oct 2011
Quote:
Originally Posted by EmoBoiix3

Will the errata patch update the ARMv7 revision ?

This was sent from a Galaxy Ace. Problem?

The errata patch does not update the ARM revision (if you are talking the one captured from cpuinfo). That is because basically all the erratas cannot be patched as it is a hardware problem or bug. However, we can avoid such thing happens (such as errata in race condition) by applying the so called 'patch'. Therefore those patches are NOT fixing the problem at all, instead they just try to avoid it.
The Following User Says Thank You to UnknownzD For This Useful Post: [ View ]
4th May 2012, 10:32 AM   |  #20  
CallMeVentus's Avatar
Recognized Contributor
Flag Singapore
Thanks Meter: 2,867
 
9,969 posts
Join Date:Joined: Jul 2011
Donate to Me
More
Quote:
Originally Posted by UnknownzD

The errata patch does not update the ARM revision (if you are talking the one captured from cpuinfo). That is because basically all the erratas cannot be patched as it is a hardware problem or bug. However, we can avoid such thing happens (such as errata in race condition) by applying the so called 'patch'. Therefore those patches are NOT fixing the problem at all, instead they just try to avoid it.

Ohh , you meant by workarounds !

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools
Display Modes


Top Threads in Galaxy R i9103 Android Development by ThreadRank