-
Notifications
You must be signed in to change notification settings - Fork 71
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
5188e36
commit a67d474
Showing
14 changed files
with
82 additions
and
55 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -437,6 +437,25 @@ config MACH_MSM8X60_FFA | |
|
||
endmenu | ||
|
||
choice | ||
prompt "Kernel Offset" | ||
default ZTE_GEN2 | ||
|
||
config ZTE_GEN1 | ||
bool "ZTE Generation 1" | ||
help | ||
This option is used to indicate if the kernel is to be compiled | ||
for a ZTE Blade Generation 1 (phone that is sold with Android 2.1 | ||
and loads the kernel to 0x02A00000.) | ||
|
||
config ZTE_GEN2 | ||
bool "ZTE Generation 2" | ||
help | ||
This option is used to indicate if the kernel is to be compiled | ||
for a ZTE Blade Generation 1 (phone that is sold with Android 2.1 | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
TomGiordano
via email
Author
Owner
|
||
and loads the kernel to 0x02600000.) | ||
endchoice | ||
|
||
config MSM_STACKED_MEMORY | ||
bool "Stacked Memory" | ||
default y | ||
|
@@ -448,7 +467,8 @@ config MSM_STACKED_MEMORY | |
#ZTE_BOOT_HUANGYANJUN_20100903_01 0x2A00000 ->0x02600000 | ||
config PHYS_OFFSET | ||
hex | ||
default "0x02600000" if !MSM_STACKED_MEMORY | ||
default "0x02A00000" if !MSM_STACKED_MEMORY && ZTE_GEN1 | ||
default "0x02600000" if !MSM_STACKED_MEMORY && ZTE_GEN2 | ||
default "0x00000000" if ARCH_QSD8X50 && MSM_SOC_REV_A | ||
default "0x20000000" if ARCH_QSD8X50 | ||
default "0x40200000" if ARCH_MSM8X60 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
shouldn't this say "Generation 2" ?
could we clarify the usage case for gen1 phones that have been TPT'd to gen2, such as mine that seems to work fine at 0x02A