2014-08-30 22:11:02 +00:00
|
|
|
if OMAP34XX
|
|
|
|
|
|
2017-05-13 02:33:22 +00:00
|
|
|
# We only enable the clocks for the GPIO banks that a given board requies.
|
|
|
|
|
config OMAP3_GPIO_2
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config OMAP3_GPIO_3
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config OMAP3_GPIO_4
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config OMAP3_GPIO_5
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config OMAP3_GPIO_6
|
|
|
|
|
bool
|
|
|
|
|
|
2014-08-30 22:11:02 +00:00
|
|
|
choice
|
|
|
|
|
prompt "OMAP3 board select"
|
2015-05-12 19:46:23 +00:00
|
|
|
optional
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_AM3517_EVM
|
|
|
|
|
bool "AM3517 EVM"
|
2017-09-20 01:32:11 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
|
|
|
|
select DM_I2C
|
|
|
|
|
select DM_MMC
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_MT_VENTOUX
|
|
|
|
|
bool "TeeJet Mt.Ventoux"
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_4
|
|
|
|
|
select OMAP3_GPIO_5 if USB_EHCI_HCD
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_OMAP3_BEAGLE
|
|
|
|
|
bool "TI OMAP3 BeagleBoard"
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 03:47:53 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_5
|
|
|
|
|
select OMAP3_GPIO_6
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_CM_T35
|
2014-10-21 13:39:45 +00:00
|
|
|
bool "CompuLab CM-T3530 and CM-T3730 boards"
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_2
|
|
|
|
|
select OMAP3_GPIO_5
|
|
|
|
|
select OMAP3_GPIO_6 if LED_STATUS
|
2014-08-30 22:11:02 +00:00
|
|
|
|
omap3: cm-t3517: add basic board support
CompuLab cm-t3517 is Computer on Module (CoM) based on AM3517 SoC.
Features: up to 256MB DDR2, up to 512MB NAND, USB hub, mUSB, WiFi, BT,
Analog audio codec, touch screen controller, LED.
Add basic support including:
LED, Serial console, NAND, MMC, GPIO, I2C, 256MB DRAM.
Signed-off-by: Igor Grinberg <grinberg@compulab.co.il>
2014-11-05 12:25:35 +00:00
|
|
|
config TARGET_CM_T3517
|
|
|
|
|
bool "CompuLab CM-T3517 boards"
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_2
|
|
|
|
|
select OMAP3_GPIO_5
|
|
|
|
|
select OMAP3_GPIO_6 if LED_STATUS
|
omap3: cm-t3517: add basic board support
CompuLab cm-t3517 is Computer on Module (CoM) based on AM3517 SoC.
Features: up to 256MB DDR2, up to 512MB NAND, USB hub, mUSB, WiFi, BT,
Analog audio codec, touch screen controller, LED.
Add basic support including:
LED, Serial console, NAND, MMC, GPIO, I2C, 256MB DRAM.
Signed-off-by: Igor Grinberg <grinberg@compulab.co.il>
2014-11-05 12:25:35 +00:00
|
|
|
|
2014-08-30 22:11:02 +00:00
|
|
|
config TARGET_DEVKIT8000
|
|
|
|
|
bool "TimLL OMAP3 Devkit8000"
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 03:47:53 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_OMAP3_EVM
|
|
|
|
|
bool "TI OMAP3 EVM"
|
2017-12-27 15:40:16 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2017-12-27 15:40:16 +00:00
|
|
|
select OMAP3_GPIO_3
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_OMAP3_IGEP00X0
|
|
|
|
|
bool "IGEP"
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 03:47:53 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_3
|
|
|
|
|
select OMAP3_GPIO_5
|
|
|
|
|
select OMAP3_GPIO_6
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_OMAP3_OVERO
|
|
|
|
|
bool "OMAP35xx Gumstix Overo"
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 03:47:53 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_2
|
|
|
|
|
select OMAP3_GPIO_3
|
|
|
|
|
select OMAP3_GPIO_4
|
|
|
|
|
select OMAP3_GPIO_5
|
|
|
|
|
select OMAP3_GPIO_6
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_OMAP3_ZOOM1
|
|
|
|
|
bool "TI Zoom1"
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 03:47:53 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_AM3517_CRANE
|
|
|
|
|
bool "am3517_crane"
|
|
|
|
|
|
|
|
|
|
config TARGET_OMAP3_PANDORA
|
|
|
|
|
bool "OMAP3 Pandora"
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_4
|
|
|
|
|
select OMAP3_GPIO_6
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_ECO5PK
|
|
|
|
|
bool "ECO5PK"
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_5 if USB_EHCI_HCD
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_TRICORDER
|
|
|
|
|
bool "Tricorder"
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_2
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_MCX
|
|
|
|
|
bool "MCX"
|
2017-01-23 00:43:11 +00:00
|
|
|
select BOARD_LATE_INIT
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_2 if USB_EHCI_HCD
|
|
|
|
|
select OMAP3_GPIO_5 if USB_EHCI_HCD
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_OMAP3_LOGIC
|
|
|
|
|
bool "OMAP3 Logic"
|
2017-01-23 00:43:11 +00:00
|
|
|
select BOARD_LATE_INIT
|
2015-09-02 14:18:20 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2017-08-25 12:33:26 +00:00
|
|
|
select OMAP3_GPIO_3
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_4
|
|
|
|
|
select OMAP3_GPIO_6
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_NOKIA_RX51
|
|
|
|
|
bool "Nokia RX51"
|
|
|
|
|
|
|
|
|
|
config TARGET_TAO3530
|
|
|
|
|
bool "TAO3530"
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_2
|
|
|
|
|
select OMAP3_GPIO_3
|
|
|
|
|
select OMAP3_GPIO_4
|
|
|
|
|
select OMAP3_GPIO_5
|
|
|
|
|
select OMAP3_GPIO_6
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
config TARGET_TWISTER
|
|
|
|
|
bool "Twister"
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_2
|
|
|
|
|
select OMAP3_GPIO_5 if USB_EHCI_HCD
|
2014-08-30 22:11:02 +00:00
|
|
|
|
2015-02-03 17:13:14 +00:00
|
|
|
config TARGET_OMAP3_CAIRO
|
|
|
|
|
bool "QUIPOS CAIRO"
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 03:47:53 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2015-02-03 17:13:14 +00:00
|
|
|
|
2015-07-20 13:17:11 +00:00
|
|
|
config TARGET_SNIPER
|
2016-02-26 12:18:47 +00:00
|
|
|
bool "LG Optimus Black"
|
2015-07-20 13:17:11 +00:00
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
2018-07-23 13:55:13 +00:00
|
|
|
select DM_SERIAL
|
2017-05-13 02:33:22 +00:00
|
|
|
select OMAP3_GPIO_2
|
|
|
|
|
select OMAP3_GPIO_3
|
|
|
|
|
select OMAP3_GPIO_4
|
|
|
|
|
select OMAP3_GPIO_5
|
|
|
|
|
select OMAP3_GPIO_6
|
2018-07-23 13:55:14 +00:00
|
|
|
imply CMD_DM
|
2015-07-20 13:17:11 +00:00
|
|
|
|
2014-08-30 22:11:02 +00:00
|
|
|
endchoice
|
|
|
|
|
|
2017-09-12 20:27:33 +00:00
|
|
|
choice
|
|
|
|
|
prompt "Memory Controller"
|
|
|
|
|
default SDRC
|
|
|
|
|
|
|
|
|
|
config SDRC
|
|
|
|
|
bool "SDRC controller"
|
|
|
|
|
help
|
|
|
|
|
The default memory controller on most OMAP3 boards is SDRC.
|
|
|
|
|
|
|
|
|
|
config EMIF4
|
|
|
|
|
bool "EMIF4 controller"
|
|
|
|
|
help
|
|
|
|
|
Enable this on boards like AM3517 which use EMIF4 controller
|
|
|
|
|
endchoice
|
|
|
|
|
|
2017-08-11 13:51:20 +00:00
|
|
|
config SPL_OMAP3_ID_NAND
|
|
|
|
|
bool "Support OMAP3-specific ID and MFR function"
|
|
|
|
|
help
|
|
|
|
|
Support for an OMAP3-specific set of functions to return the
|
|
|
|
|
ID and MFR of the first attached NAND chip, if present.
|
|
|
|
|
|
2014-08-30 22:11:02 +00:00
|
|
|
config SYS_SOC
|
|
|
|
|
default "omap3"
|
|
|
|
|
|
|
|
|
|
source "board/logicpd/am3517evm/Kconfig"
|
|
|
|
|
source "board/teejet/mt_ventoux/Kconfig"
|
|
|
|
|
source "board/ti/beagle/Kconfig"
|
|
|
|
|
source "board/compulab/cm_t35/Kconfig"
|
omap3: cm-t3517: add basic board support
CompuLab cm-t3517 is Computer on Module (CoM) based on AM3517 SoC.
Features: up to 256MB DDR2, up to 512MB NAND, USB hub, mUSB, WiFi, BT,
Analog audio codec, touch screen controller, LED.
Add basic support including:
LED, Serial console, NAND, MMC, GPIO, I2C, 256MB DRAM.
Signed-off-by: Igor Grinberg <grinberg@compulab.co.il>
2014-11-05 12:25:35 +00:00
|
|
|
source "board/compulab/cm_t3517/Kconfig"
|
2014-08-30 22:11:02 +00:00
|
|
|
source "board/timll/devkit8000/Kconfig"
|
|
|
|
|
source "board/ti/evm/Kconfig"
|
|
|
|
|
source "board/isee/igep00x0/Kconfig"
|
|
|
|
|
source "board/overo/Kconfig"
|
|
|
|
|
source "board/logicpd/zoom1/Kconfig"
|
|
|
|
|
source "board/ti/am3517crane/Kconfig"
|
|
|
|
|
source "board/pandora/Kconfig"
|
|
|
|
|
source "board/8dtech/eco5pk/Kconfig"
|
|
|
|
|
source "board/corscience/tricorder/Kconfig"
|
|
|
|
|
source "board/htkw/mcx/Kconfig"
|
|
|
|
|
source "board/logicpd/omap3som/Kconfig"
|
|
|
|
|
source "board/nokia/rx51/Kconfig"
|
|
|
|
|
source "board/technexion/tao3530/Kconfig"
|
|
|
|
|
source "board/technexion/twister/Kconfig"
|
2015-02-03 17:13:14 +00:00
|
|
|
source "board/quipos/cairo/Kconfig"
|
2016-03-29 12:16:27 +00:00
|
|
|
source "board/lg/sniper/Kconfig"
|
2014-08-30 22:11:02 +00:00
|
|
|
|
|
|
|
|
endif
|
