History log of /openbmc/u-boot/arch/arm/mach-aspeed/ast2500/Kconfig (Results 1 – 5 of 5)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v00.04.15, v00.04.14, v00.04.13, v00.04.12, v00.04.11, v00.04.10, v00.04.09, v00.04.08, v00.04.07, v00.04.06, v00.04.05, v00.04.04, v00.04.03, v00.04.02, v00.04.01, v00.04.00, v2021.04, v00.03.03, v2021.01, v2020.10, v2020.07, v00.02.13, v2020.04, v2020.01, v2019.10, v00.02.05, v00.02.04, v00.02.03, v00.02.02, v00.02.01
# baa29d5e 18-Jul-2019 Johnny Huang <johnny_huang@aspeedtech.com>

Merge remote-tracking branch 'origin/aspeed-dev-v2019.04' into aspeed-master-v2019.04


# 827cd61a 11-Jul-2019 Chia-Wei, Wang <chiawei_wang@aspeedtech.com>

Merge branch 'feature/aspeed-build' into aspeed-dev-v2019.04


# 3ceef17c 10-Jul-2019 Chia-Wei, Wang <chiawei_wang@aspeedtech.com>

configs: aspeed: refactor Kconfig and sync defconfig

1. make Aspeed target selection mutually exclusive
2. sync defconfig to fit new Kconfig options


Revision tags: v2019.07, v00.02.00, v2019.04, v2018.07, v2018.03, v2018.01, v2017.11
# d9b88d25 18-Jan-2017 maxims@google.com <maxims@google.com>

aspeed: Support for ast2500 Eval Board

ast2500 Eval Board device tree and board specific configuration.
Reviewed-by: Simon Glass <sjg@chromium.org>


# 14e4b149 18-Jan-2017 maxims@google.com <maxims@google.com>

aspeed: Add basic ast2500-specific drivers and configuration

Clock Driver

This driver is ast2500-specific and is not compatible with earlier
versions of this chip. The differences are not that big,

aspeed: Add basic ast2500-specific drivers and configuration

Clock Driver

This driver is ast2500-specific and is not compatible with earlier
versions of this chip. The differences are not that big, but they are
in somewhat random places, so making it compatible with ast2400 is not
worth the effort at the moment.

SDRAM MC driver

The driver is very ast2500-specific and is completely incompatible
with previous versions of the chip.

The memory controller is very poorly documented by Aspeed in the
datasheet, with any mention of the whole range of registers missing. The
initialization procedure has been basically taken from Aspeed SDK, where
it is implemented in assembly. Here it is rewritten in C, with very limited
understanding of what exactly it is doing.
Reviewed-by: Simon Glass <sjg@chromium.org>

show more ...