env: Rename eth_getenv_enetaddr() to eth_env_get_enetaddr()Rename this function for consistency with env_get().Signed-off-by: Simon Glass <sjg@chromium.org>
env: Rename eth_setenv_enetaddr() to eth_env_set_enetaddr()Rename this function for consistency with env_set().Signed-off-by: Simon Glass <sjg@chromium.org>
pepper: Implement Board Detection mechanismAM335x-based 'Gumstix Pepper' SBCs and variants use different types ofRAM (DDR2 vs DDR3 with DDR3 being the default). Detect the board typeby reading t
pepper: Implement Board Detection mechanismAM335x-based 'Gumstix Pepper' SBCs and variants use different types ofRAM (DDR2 vs DDR3 with DDR3 being the default). Detect the board typeby reading the factory-programmed EEPROM [1] and use this to select anyruntime boot options such as RAM type.[1] http://elinux.org/BeagleBoardPinMux#List_of_Vendor_and_Device_IDsSigned-off-by: Adam YH Lee <adam.yh.lee@gmail.com>Signed-off-by: Ash Charles <ashcharles@gmail.com>
show more ...
net: cosmetic: Name ethaddr variables consistentlyUse "_ethaddr" at the end of variables and drop CamelCase.Make constant values actually 'const'.Signed-off-by: Joe Hershberger <joe.hershberger@
net: cosmetic: Name ethaddr variables consistentlyUse "_ethaddr" at the end of variables and drop CamelCase.Make constant values actually 'const'.Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>Acked-by: Simon Glass <sjg@chromium.org>
dm: select CONFIG_DM* optionsAs mentioned in the previous commit, adding default values in eachKconfig causes problems because it does not co-exist with the"depends on" syntax. (Please note this
dm: select CONFIG_DM* optionsAs mentioned in the previous commit, adding default values in eachKconfig 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 weconvert a driver into Driver Model, the board only works with DriverModel, i.e. CONFIG_DM must be always enabled for that board.So, using "select DM" is more suitable rather than allowing users tomodify it. Another good thing is, Kconfig warns unmet dependenciesfor "select" syntax, so we easily notice bugs.Actually, CONFIG_DM and other related options have been addedwithout consistency: some into arch/*/Kconfig, some intoboard/*/Kconfig, and some into configs/*_defconfig.This commit prefers "select" and cleans up the following issues.[1] Never use "CONFIG_DM=n" in defconfig filesIt 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, wedo 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 isweird. Instead, add "select DM" only to appropriate boards, whicheventually eliminates "CONFIG_DM=n", etc.[2] Delete redundant CONFIGsSandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it againin configs/sandbox_defconfig.Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig anddefines it also in omap3_beagle_defconfig and devkit8000_defconfig.Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
kconfig: remove unneeded dependency on !SPL_BUILDNow CONFIG_SPL_BUILD is not defined in Kconfig, so"!depends on SPL_BUILD" and "if !SPL_BUILD" are redundant.Signed-off-by: Masahiro Yamada <yamad
kconfig: remove unneeded dependency on !SPL_BUILDNow CONFIG_SPL_BUILD is not defined in Kconfig, so"!depends on SPL_BUILD" and "if !SPL_BUILD" are redundant.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
dm: omap3: Move driver model CONFIGs to KconfigRemove driver model CONFIGs from the board config headers and use Kconfiginstead.Signed-off-by: Simon Glass <sjg@chromium.org>
kconfig: arm: introduce symbol for ARM CPUsThis commit introduces a Kconfig symbol for each ARM CPU:CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,CPU_ARM1176, CPU_V7, CPU_PXA
kconfig: arm: introduce symbol for ARM CPUsThis commit introduces a Kconfig symbol for each ARM CPU:CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selectedfor CPU_ARM1176 and CPU_V7.For each target, the corresponding CPU is selected and the definition ofSYS_CPU in the corresponding Kconfig file is removed.Also, it removes redundant "string" type in some Kconfig files.Signed-off-by: Georges Savoundararadj <savoundg@gmail.com>Acked-by: Albert ARIBAUD <albert.u.boot@aribaud.net>Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
kconfig: remove redundant "string" type in arch and board KconfigsNow the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}are specified in arch/Kconfig.We can delete the ones in
kconfig: remove redundant "string" type in arch and board KconfigsNow the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}are specified in arch/Kconfig.We can delete the ones in arch and board Kconfig files.This commit can be easily reproduced by the following command:find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '/config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ { N s/\n[[:space:]]*string//}'Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Add board MAINTAINERS filesWe have switched to Kconfig and the boards.cfg file is going tobe removed. We have to retrieve the board status and maintainersinformation from it.The MAINTAINERS for
Add board MAINTAINERS filesWe have switched to Kconfig and the boards.cfg file is going tobe removed. We have to retrieve the board status and maintainersinformation from it.The MAINTAINERS format as in Linux Kernel would be nicebecause we can crib the scripts/get_maintainer.pl script.After some discussion, we chose to put a MAINTAINERS file under eachboard directory, not the top-level one because we want to collectrelevant information for a board into a single place.TODO:Modify get_maintainer.pl to scan multiple MAINTAINERS files.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Suggested-by: Tom Rini <trini@ti.com>Acked-by: Simon Glass <sjg@chromium.org>
kconfig: add board Kconfig and defconfig filesThis commit adds: - arch/${ARCH}/Kconfig provide a menu to select target boards - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
kconfig: add board Kconfig and defconfig filesThis commit adds: - arch/${ARCH}/Kconfig provide a menu to select target boards - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig set CONFIG macros to the appropriate values for each board - configs/${TARGET_BOARD}_defconfig default setting of each board(This commit was automatically generated by a conversion scriptbased on boards.cfg)In Linux Kernel, defconfig files are located underarch/${ARCH}/configs/ directory.It works in Linux Kernel since ARCH is always given from thecommand line for cross compile.But in U-Boot, ARCH is not given from the command line.Which means we cannot know ARCH until the board configuration is done.That is why all the "*_defconfig" files should be gathered into asingle directory ./configs/.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Acked-by: Simon Glass <sjg@chromium.org>
am335x_evm / gumstix pepper: Correct DDR settingsAs noted by clang, we have been shifting certain values out of 32bitrange when setting some DDR registers. Upon further inspection thesehad been
am335x_evm / gumstix pepper: Correct DDR settingsAs noted by clang, we have been shifting certain values out of 32bitrange when setting some DDR registers. Upon further inspection thesehad been touching reserved fields (and having no impact). These came infrom historical bring-up code and can be discarded. Similarly, we hadbeen declaring some fields as 0 when they will be initialized that way.Tested on Beaglebone White.Reported-by: Jeroen Hofstee <jeroen@myspectrum.nl>Cc: Ash Charles <ash@gumstix.com>Signed-off-by: Tom Rini <trini@ti.com>Tested-By: Ash Charles <ashcharles@gmail.com>
am335x: pepper: Add Gumstix Pepper AM335x-based machineThis adds the Gumstix Pepper[1] single-board computer based on theTI AM335x processor. Schematics are available [2].[1] https://store.gumst
am335x: pepper: Add Gumstix Pepper AM335x-based machineThis adds the Gumstix Pepper[1] single-board computer based on theTI AM335x processor. Schematics are available [2].[1] https://store.gumstix.com/index.php/products/344/[2] https://pubs.gumstix.com/boards/PEPPER/Signed-off-by: Ash Charles <ash@gumstix.com>[trini: Move 'cdev' in board.c down to under #ifdef's where it's used]Signed-off-by: Tom Rini <trini@ti.com>