bcm63xx/u-boot/configs/maxbcm_defconfig, branch masterBroadcom-s U-Boothttps://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master2019-04-30T01:41:40Zconfigs: move CONFIG_SPL_TEXT_BASE to Kconfig2019-04-30T01:41:40ZSimon Goldschmidt2018-09-30T12:31:53Zurn:sha1:f89d6133eef2e068f9c33853b6584d7fcbfa9d2e
Moved CONFIG_SPL_TEXT_BASE to common/spl/Kconfig and migrate existing
values.
Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
[trini: Re-run migration]
Signed-off-by: Tom Rini <trini@konsulko.com>
configs: Resync with savedefconfig2019-04-30T01:41:40ZTom Rini2019-04-29T19:54:04Zurn:sha1:d168bcb6fe39108042c0c771f0823a95346a8e7e
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini <trini@konsulko.com>
Convert CONFIG_ENV_SPI_* to Kconfig2019-03-25T21:36:59ZPatrick Delaunay2019-02-27T14:20:38Zurn:sha1:abe66b1b5decf9cc2fb5daad42c9e870e5b99b67
This converts the following to Kconfig:
CONFIG_ENV_SPI_BUS
CONFIG_ENV_SPI_CS
CONFIG_ENV_SPI_MAX_HZ
CONFIG_ENV_SPI_MODE
Most of time these value are not needed, CONFIG_SF_DEFAULT
with same value is used, so I introduced CONFIG_USE_ENV_SPI_*
to force the associated value for the environment.
Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
configs: Don't use SPI_FLASH_BAR as default2019-02-07T10:03:22ZVignesh R2019-02-05T05:59:28Zurn:sha1:6d82517836418f984b7b4c05cf1427d7b49b1169
Now that new SPI NOR layer uses stateless 4 byte opcodes by default,
don't enable SPI_FLASH_BAR. For SPI controllers that cannot support
4-byte addressing, (stm32_qspi.c, fsl_qspi.c, mtk_qspi.c, ich.c,
renesas_rpc_spi.c) add an imply clause to enable SPI_FLASH_BAR so as to
not break functionality.
Signed-off-by: Vignesh R <vigneshr@ti.com>
Tested-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
Tested-by: Stefan Roese <sr@denx.de>
Tested-by: Horatiu Vultur <horatiu.vultur@microchip.com>
Reviewed-by: Jagan Teki <jagan@openedev.com>
Tested-by: Jagan Teki <jagan@amarulasolutions.com> #zynq-microzed
configs: Resync with savedefconfig2018-09-03T19:26:12ZTom Rini2018-09-03T19:26:12Zurn:sha1:8c5cad05c97122b33ef8de981b56f701d6bfb6ea
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini <trini@konsulko.com>
Convert CONFIG_MII et al to Kconfig2018-08-17T17:03:54ZAdam Ford2018-07-21T04:03:57Zurn:sha1:d7869b2183d2b786e5410b97a5a6b2e630e7825e
This converts the following to Kconfig:
CONFIG_MII
CONFIG_DRIVER_TI_EMAC
Signed-off-by: Adam Ford <aford173@gmail.com>
Acked-by: Jagan Teki <jagan@amarulasolutions.com>
Acked-by: Joe Hershberger <joe.hershberger@ni.com>
configs: Migrate CONFIG_NR_DRAM_BANKS2018-08-16T20:45:02ZTom Rini2018-08-16T12:16:24Zurn:sha1:86cf1c82850f7c226f23684e19616e526ffaf10f
We have the following cases:
- CONFIG_NR_DRAM_BANKS was defined, migrate normally
- CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
- CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
2), set this to 8.
Signed-off-by: Tom Rini <trini@konsulko.com>
configs: Resync with savedefconfig2018-06-04T15:57:37ZTom Rini2018-06-04T15:57:37Zurn:sha1:358b6a20e4428f1834dc96aff14077d43e9cd190
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini <trini@konsulko.com>
treewide: Move CONFIG_PHY_MARVELL to Kconfig2018-05-15T01:28:38ZMario Six2018-04-27T12:52:21Zurn:sha1:a8ca5c8adb3efe892982389aae8b2a234939a588
The CONFIG_PHY_MARVELL has already been migrated to Kconfig (some boards
already had it in their Kconfig), but had not been moved for older
boards.
Move it to the defconfigs for all boards.
Signed-off-by: Mario Six <mario.six@gdsys.cc>
Acked-by: Joe Hershberger <joe.hershberger@ni.com>
configs: Resync with savedefconfig2018-04-17T14:10:47ZTom Rini2018-04-17T13:22:31Zurn:sha1:34b3722e381c0146b4aa7fea3a5243c588b8ed2f
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini <trini@konsulko.com>