May 2014 - U-Boot

[U-Boot] [PATCH] net/designware: call phy_connect_dev() to properly setup phylib device
by Ian Campbell 21 May '14

21 May '14

This sets up the linkage from the phydev back to the ethernet device. This symptom of not doing this which I noticed was: <NULL> Waiting for PHY auto negotiation to complete.... rather than: dwmac.1c50000 Waiting for PHY auto negotiation to complete.... Signed-off-by: Ian Campbell <ijc(a)hellion.org.uk> Cc: Alexey Brodkin <Alexey.Brodkin(a)synopsys.com> --- drivers/net/designware.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/designware.c b/drivers/net/designware.c index c9afe16..b8a7631 100644 --- a/drivers/net/designware.c +++ b/drivers/net/designware.c @@ -390,6 +390,8 @@ static int dw_phy_init(struct eth_device *dev) if (!phydev) return -1; + phy_connect_dev(phydev, dev); + phydev->supported &= PHY_GBIT_FEATURES; phydev->advertising = phydev->supported; -- 1.9.0

2 7

[U-Boot] Export Uboot command line functions to a standalone app.
by mazen.e 21 May '14

21 May '14

Hello, is it possible to export some Uboot command line functions (e.g. bootm) to a standalone app, in such shall my app be GPLed. Many thanks. -- View this message in context: http://u-boot.10912.n7.nabble.com/Export-Uboot-command-line-functions-to-a-… Sent from the U-Boot mailing list archive at Nabble.com.

1 0

[U-Boot] [PATCH] tb100 - add Abilis TB100 board
by Alexey Brodkin 21 May '14

21 May '14

Development board for headless gateway platform from Abilis Systems. Initial commit with working UART and DW GMAC. For now with generic Ethernet PHY due to problems in Realtek PHY driver. Signed-off-by: Alexey Brodkin <abrodkin(a)synopsys.com> Cc: Vineet Gupta <vgupta(a)synopsys.com> Cc: Christian Ruppert <christian.ruppert(a)abilis.com> Cc: Pierrick Hascoet <pierrick.hascoet(a)abilis.com> --- board/abilis/tb100/Makefile | 7 +++ board/abilis/tb100/tb100.c | 23 +++++++++ boards.cfg | 1 + include/configs/tb100.h | 123 ++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 154 insertions(+) create mode 100644 board/abilis/tb100/Makefile create mode 100644 board/abilis/tb100/tb100.c create mode 100644 include/configs/tb100.h diff --git a/board/abilis/tb100/Makefile b/board/abilis/tb100/Makefile new file mode 100644 index 0000000..4f273b3 --- /dev/null +++ b/board/abilis/tb100/Makefile @@ -0,0 +1,7 @@ +# +# (C) Copyright 2014 Pierrick Hascoet, Abilis Systems +# +# SPDX-License-Identifier: GPL-2.0+ +# + +obj-y += tb100.o diff --git a/board/abilis/tb100/tb100.c b/board/abilis/tb100/tb100.c new file mode 100644 index 0000000..ff3632f --- /dev/null +++ b/board/abilis/tb100/tb100.c @@ -0,0 +1,23 @@ +/* + * (C) Copyright 2014 Pierrick Hascoet, Abilis Systems + * + * SPDX-License-Identifier: GPL-2.0+ + */ + +#include <common.h> +#include <netdev.h> +#include <asm/io.h> + +void reset_cpu(ulong addr) +{ +#define CRM_SWRESET 0xff101044 + writel(0x1, (void *)CRM_SWRESET); +} + +int board_eth_init(bd_t *bis) +{ + if (designware_initialize(ETH0_BASE_ADDRESS, 0) >= 0) + return 1; + + return 0; +} diff --git a/boards.cfg b/boards.cfg index 0497a91..64f3dca 100644 --- a/boards.cfg +++ b/boards.cfg @@ -47,6 +47,7 @@ Active aarch64 armv8 - armltd vexpress64 Active arc arc700 - synopsys - axs101 - Alexey Brodkin <abrodkin(a)synopsys.com> Active arc arc700 - synopsys <none> arcangel4 - Alexey Brodkin <abrodkin(a)synopsys.com> Active arc arc700 - synopsys <none> arcangel4-be - Alexey Brodkin <abrodkin(a)synopsys.com> +Active arc arc700 - abilis - tb100 - Alexey Brodkin <abrodkin(a)synopsys.com> Active arm arm1136 - armltd integrator integratorcp_cm1136 integratorcp:CM1136 Linus Walleij <linus.walleij(a)linaro.org> Active arm arm1136 mx31 - - imx31_phycore - - Active arm arm1136 mx31 davedenx - qong - Wolfgang Denk <wd(a)denx.de> diff --git a/include/configs/tb100.h b/include/configs/tb100.h new file mode 100644 index 0000000..8a861a8 --- /dev/null +++ b/include/configs/tb100.h @@ -0,0 +1,123 @@ +/* + * Copyright (C) 2011-2014 Pierrick Hascoet, Abilis Systems + * + * SPDX-License-Identifier: GPL-2.0+ + */ + +#ifndef _CONFIG_TB100_H_ +#define _CONFIG_TB100_H_ + +#include <linux/sizes.h> + +/* + * CPU configuration + */ +#define CONFIG_ARC700 +#define CONFIG_ARC_MMU_VER 3 +#define CONFIG_SYS_CACHELINE_SIZE 32 +#define CONFIG_SYS_CLK_FREQ 500000000 +#define CONFIG_SYS_TIMER_RATE CONFIG_SYS_CLK_FREQ + +/* + * Board configuration + */ +#define CONFIG_SYS_GENERIC_BOARD +#define CONFIG_ARCH_EARLY_INIT_R + +/* + * Memory configuration + */ +#define CONFIG_SYS_TEXT_BASE 0x84000000 +#define CONFIG_SYS_MONITOR_BASE CONFIG_SYS_TEXT_BASE + +#define CONFIG_SYS_DDR_SDRAM_BASE 0x80000000 +#define CONFIG_SYS_SDRAM_BASE CONFIG_SYS_DDR_SDRAM_BASE +#define CONFIG_SYS_SDRAM_SIZE SZ_128M + +#define CONFIG_SYS_INIT_SP_ADDR \ + (CONFIG_SYS_SDRAM_BASE + 0x1000 - GENERATED_GBL_DATA_SIZE) + +#define CONFIG_SYS_MALLOC_LEN SZ_128K +#define CONFIG_SYS_BOOTM_LEN SZ_32M +#define CONFIG_SYS_LOAD_ADDR 0x82000000 + +#define CONFIG_SYS_NO_FLASH + +/* + * UART configuration + */ +#define CONFIG_CONS_INDEX 1 +#define CONFIG_SYS_NS16550 +#define CONFIG_SYS_NS16550_SERIAL +#define CONFIG_SYS_NS16550_REG_SIZE -4 +#define CONFIG_SYS_NS16550_CLK 166666666 +#define CONFIG_SYS_NS16550_COM1 0xFF100000 +#define CONFIG_SYS_NS16550_MEM32 + +#define CONFIG_BAUDRATE 115200 + +/* + * Ethernet PHY configuration + */ +#define CONFIG_PHYLIB +#define CONFIG_PHY_GIGE + +/* + * Even though the board houses Realtek RTL8211E PHY + * corresponding PHY driver (drivers/net/phy/realtek.c) behaves unexpectedly. + * In particular "parse_status" reports link is down. + * + * Until Realtek PHY driver is fixed fall back to generic PHY driver + * which implements all required functionality and behaves much more stable. + * + * #define CONFIG_PHY_REALTEK + * + */ + +/* + * Ethernet configuration + */ +#define CONFIG_DESIGNWARE_ETH +#define ETH0_BASE_ADDRESS 0xFE100000 +#define ETH1_BASE_ADDRESS 0xFE110000 + +/* + * Command line configuration + */ +#include <config_cmd_default.h> + +#define CONFIG_CMD_DHCP +#define CONFIG_CMD_ELF +#define CONFIG_CMD_PING + +#define CONFIG_OF_LIBFDT + +#define CONFIG_AUTO_COMPLETE +#define CONFIG_SYS_MAXARGS 16 + +/* + * Environment settings + */ +#define CONFIG_ENV_IS_NOWHERE +#define CONFIG_ENV_SIZE SZ_2K +#define CONFIG_ENV_OFFSET 0 + +/* + * Environment configuration + */ +#define CONFIG_BOOTDELAY 3 +#define CONFIG_BOOTFILE "uImage" +#define CONFIG_BOOTARGS "console=ttyS0,115200n8" +#define CONFIG_LOADADDR CONFIG_SYS_LOAD_ADDR + +/* + * Console configuration + */ +#define CONFIG_SYS_LONGHELP +#define CONFIG_SYS_PROMPT "[tb100]:~# " +#define CONFIG_SYS_CBSIZE 256 +#define CONFIG_SYS_BARGSIZE CONFIG_SYS_CBSIZE +#define CONFIG_SYS_PBSIZE (CONFIG_SYS_CBSIZE + \ + sizeof(CONFIG_SYS_PROMPT) + 16) + +#endif /* _CONFIG_TB100_H_ */ -- 1.9.0

1 0

[U-Boot] VMM as a standalone app.
by mazen.e 21 May '14

21 May '14

Dear all, I am thinking of getting the Uboot to load a VMM (in hyp mode) rather than a standard kernel, is it a good (and feasible) idea to set the VMM as a standalone application which runs in hyp mode, and then the VMM uncompress and load a kernel image to be executed in SVC mode, is there a better way to do it? please share your experience. Also, is it possible to allocate a large pool of contiguous physical memory from within Uboot, please suggest s tutorial on how to it. Many thanks. -- View this message in context: http://u-boot.10912.n7.nabble.com/VMM-as-a-standalone-app-tp180376.html Sent from the U-Boot mailing list archive at Nabble.com.

1 0

[U-Boot] [PATCH] board/t2080qds: enable sst and eon spi flash for nor boot
by Shengzhou Liu 21 May '14

21 May '14

Remove unnecessary condition CONFIG_RAMBOOT_PBL to have SST and EON SPI flash work in case of NOR boot. Signed-off-by: Shengzhou Liu <Shengzhou.Liu(a)freescale.com> --- include/configs/T208xQDS.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/configs/T208xQDS.h b/include/configs/T208xQDS.h index 0332648..200ca4f 100644 --- a/include/configs/T208xQDS.h +++ b/include/configs/T208xQDS.h @@ -540,7 +540,7 @@ unsigned long get_board_ddr_clk(void); #ifdef CONFIG_SPI_FLASH #define CONFIG_FSL_ESPI #define CONFIG_SPI_FLASH_STMICRO -#if !defined(CONFIG_SPL_BUILD) && defined(CONFIG_RAMBOOT_PBL) +#ifndef CONFIG_SPL_BUILD #define CONFIG_SPI_FLASH_SST #define CONFIG_SPI_FLASH_EON #endif -- 1.8.0

1 0

[U-Boot] [PATCH 1/2] ARM: at91sam9m10g45ek: enable mci0 support
by Josh Wu 21 May '14

21 May '14

Enable mci0 support. And enable the mmc command in configuration file. As both CONFIG_CMD_MMC and CONFIG_CMD_USB use the CONFIG_DOS_PARTITION, so remove the redundant CONFIG_DOS_PARTITION definition. Signed-off-by: Josh Wu <josh.wu(a)atmel.com> --- board/atmel/at91sam9m10g45ek/at91sam9m10g45ek.c | 28 +++++++++++++++++++++++ include/configs/at91sam9m10g45ek.h | 15 +++++++++++- 2 files changed, 42 insertions(+), 1 deletion(-) diff --git a/board/atmel/at91sam9m10g45ek/at91sam9m10g45ek.c b/board/atmel/at91sam9m10g45ek/at91sam9m10g45ek.c index b7e2efd..fd6860b 100644 --- a/board/atmel/at91sam9m10g45ek/at91sam9m10g45ek.c +++ b/board/atmel/at91sam9m10g45ek/at91sam9m10g45ek.c @@ -15,7 +15,9 @@ #include <asm/arch/gpio.h> #include <asm/arch/clk.h> #include <lcd.h> +#include <mmc.h> #include <atmel_lcdc.h> +#include <atmel_mci.h> #if defined(CONFIG_RESET_PHY_R) && defined(CONFIG_MACB) #include <net.h> #endif @@ -217,6 +219,29 @@ void lcd_show_board_info(void) #endif /* CONFIG_LCD_INFO */ #endif +#ifdef CONFIG_GENERIC_ATMEL_MCI +void at91sam9m10g45ek_mci_hw_init(void) +{ + struct at91_pmc *pmc = (struct at91_pmc *)ATMEL_BASE_PMC; + + at91_set_a_periph(AT91_PIO_PORTA, 0, 0); /* MCI0 CLK */ + at91_set_a_periph(AT91_PIO_PORTA, 1, 0); /* MCI0 CDA */ + at91_set_a_periph(AT91_PIO_PORTA, 2, 0); /* MCI0 DB0 */ + at91_set_a_periph(AT91_PIO_PORTA, 3, 0); /* MCI0 DB1 */ + at91_set_a_periph(AT91_PIO_PORTA, 4, 0); /* MCI0 DB2 */ + at91_set_a_periph(AT91_PIO_PORTA, 5, 0); /* MCI0 DB3 */ + + /* Enable clock */ + writel(1 << ATMEL_ID_MCI0, &pmc->pcer); +} + +int board_mmc_init(bd_t *bis) +{ + at91_set_pio_input(AT91_PIO_PORTD, 10, 0); /* MCI0 CD */ + return atmel_mci_init((void *)ATMEL_BASE_MCI0); +} +#endif + int board_early_init_f(void) { at91_seriald_hw_init(); @@ -247,6 +272,9 @@ int board_init(void) #ifdef CONFIG_ATMEL_SPI at91_spi0_hw_init(1 << 4); #endif +#ifdef CONFIG_GENERIC_ATMEL_MCI + at91sam9m10g45ek_mci_hw_init(); +#endif #ifdef CONFIG_MACB at91sam9m10g45ek_macb_hw_init(); #endif diff --git a/include/configs/at91sam9m10g45ek.h b/include/configs/at91sam9m10g45ek.h index ccfda71..df277e7 100644 --- a/include/configs/at91sam9m10g45ek.h +++ b/include/configs/at91sam9m10g45ek.h @@ -115,6 +115,20 @@ #endif +/* MMC */ +#define CONFIG_CMD_MMC + +#ifdef CONFIG_CMD_MMC +#define CONFIG_MMC +#define CONFIG_GENERIC_MMC +#define CONFIG_GENERIC_ATMEL_MCI +#endif + +#if defined(CONFIG_CMD_USB) || defined(CONFIG_CMD_MMC) +#define CONFIG_CMD_FAT +#define CONFIG_DOS_PARTITION +#endif + /* Ethernet */ #define CONFIG_MACB #define CONFIG_RMII @@ -126,7 +140,6 @@ #define CONFIG_USB_EHCI #define CONFIG_USB_EHCI_ATMEL #define CONFIG_SYS_USB_EHCI_MAX_ROOT_PORTS 2 -#define CONFIG_DOS_PARTITION #define CONFIG_USB_STORAGE #define CONFIG_SYS_LOAD_ADDR 0x22000000 /* load address */ -- 1.7.9.5

2 5

[U-Boot] [U-boot] Does u-boot support being compiled by clang compiler?
by TigerLiu＠via-alliance.com 20 May '14

20 May '14

Hi, experts: Does u-boot support being compiled by clang compiler? Clang compiler is provied by LLVM. Best wishes,

2 1

[U-Boot] [PATCH] cmd_mmc.c: check mmc_init() during mmc dev
by Bryan Wu 20 May '14

20 May '14

mmc dev ${devnum} will return 0 as success even if there is no card inserted. Booting script like tegra-common-post.h will call mmc dev ${devnum} to check the mmc device status, it always return 0 even if mmc_init() fails. Check mmc_init() return value let mmc dev command return failure when mmc_init() fails. Signed-off-by: Bryan Wu <pengw(a)nvidia.com> --- common/cmd_mmc.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/common/cmd_mmc.c b/common/cmd_mmc.c index c1916c9..56dcf48 100644 --- a/common/cmd_mmc.c +++ b/common/cmd_mmc.c @@ -195,6 +195,7 @@ static int do_mmcops(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) } else if (strcmp(argv[1], "dev") == 0) { int dev, part = -1; struct mmc *mmc; + int ret; if (argc == 2) dev = curr_device; @@ -217,7 +218,10 @@ static int do_mmcops(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) return 1; } - mmc_init(mmc); + ret = mmc_init(mmc); + if (ret) + return ret; + if (part != -1) { int ret; if (mmc->part_config == MMCPART_NOAVAILABLE) { -- 1.7.11.4

2 2

Re: [U-Boot] [RFC] POWER framework v3 - wish list
by Przemyslaw Marczak 20 May '14

20 May '14

Hello, Some time ago I had a pleasure to work on some kind of a simple charger manager for u-boot. For checking battery charge level, cable state, and some more info I made a common calls which were implemented in board files, so actually it didn't base directly on PMIC framework. This allowed making charger abstraction but it was a second power related framework next to the PMIC. From my side I would like to introduce its next version according to the doc/README.power-framework documents "TO DO" list and some more... In this RFC any comments about next version of power management framework are welcome. What new PMIC framework should provide? How to extend it? What can be fixed? So, what should be done (in my opinion): 1. Framework architecture: I think that current PMIC hierarchy is not so clean as it could be. It is just based on Trats board architecture. I would like to add there some more abstraction to make it common and simply to use. The main problem is that current PMIC framework is based on names of devices. So to check some specific device options I need to know the name of such device. Examples of useful options: - battery state, - battery level - charger state, - charger type, - battery charge, and some else... On Trats2 which I mostly use, not every option refers to a single PMIC device. Now this problem refers only to few Samsung boards - no more supports battery charger at present - but this maybe change... Looking at pmic header we can find some specific ops: [struct structure_name: fields (ops)] - struct power_fg: fg_battery_check; fg_battery_update; - struct power_chrg: chrg_type; chrg_bat_present; chrg_state; - struct power_battery: struct bat; battery_init; battery_charge; To simplify this - in my opinion those all operations could be stored in a single structure, because actually it refers to one abstract device - CHARGER. Battery should not be treated as a device because it is only passive element and actually in a simple version it has no logical interface besides power contacts - so actually charger is responsible for maintaining battery condition and checking its state. Next architectural change which I'm thinking of about is to add some abstraction of real IC features. Nowadays boards come with highly integrated power management ICs which provide various subsystems like: - ldo / buck - battery charger - micro USB interface controller - gpio / keys - rtc - led flash driver - motor driver - system temperature control - and more, and more...(e.g. device power off feature) And this all is often controlled by more then one device/interface. Example in trats2: there are two power ICs registered as many devices, some of them share the same interface and bus. This is shown on diagram below: (taken from: doc/README.power-framework) ----------------- --------| BAT |------------ | | | | | ----------------- | | | | \|/ \|/ \|/ ----------- ----------------- --------- |FG | |MUIC | |CHRG | | | | | | | ----------- ----------------- --------- MAX77693 MAX77693 MAX77693 addr: 0x6C addr: 0x4A addr: 0xCC There is also another ic: MAX77686 - which acts as: - LDO/BUCK regulator, pwr key event (i2c addr: 0x12) - rtc (i2c addr: 0x0C) So this is the main POWER device - but framework doesn't provide any common ops for it besides standard register's read/write. I think that this architecture could look as shown on the diagram below. ------------------------- | COMMON POWER FRAMEWORK | | with supported ops: | | - A | | - B | | - C | | - and N - others | ------------------------- | | | | | | (N-number of registered power devices) | | . . . | | | | ------------- ------------- ---- | POWER DEV | | POWER DEV | | | name "AAA" | | name "BBB" | | | dev id 0 | | dev id 1 | . . . | |-------------| |-------------| | . . . | ops type A | | ops type B | | | iface I2C1 | | iface SPI1 | | |-------------| ------------- | | ops type B | | | iface I2C2 | . |-------------| . | ops type C | . | iface XXXX | ------------- So the main change is to add multiple ops on a multiple interfaces. And those changes actually resolve PMIC IC instances problem. Please look at some piece of code below. (some part of include/power/pmic.h): enum { PMIC_I2C, PMIC_SPI, PMIC_NONE}; enum { I2C_PMIC, I2C_NUM, }; enum { PMIC_READ, PMIC_WRITE, }; enum { PMIC_SENSOR_BYTE_ORDER_LITTLE, PMIC_SENSOR_BYTE_ORDER_BIG, }; struct p_i2c { no changes }; struct p_spi { no changes }; (new framework): enum { POWER_OPS_REGISTER_RW, POWER_OPS_REGULATOR, POWER_OPS_CHARGER, POWER_OPS_MUIC, POWER_OPS_KEY_POWER, POWER_OPS_RTC, POWER_OPS_MOTOR, POWER_OPS_LED_FLASH, POWER_OPS_TEMP_CONTROL, }; struct power_ops_register_rw { int (*register_read) (int reg, int *val); int (*register_write) (int reg, int *val); }; struct power_ops_regulator { int (*ldo_set_value) (int regulator, int val, int mode, ...); int (*ldo_get_value) (int regulator, int *val, int mode, ...); int (*buck_set_value) (int buck, int val, int mode, ...); int (*buck_get_value) (int buck, int *val, int mode, ...); }; struct power_ops_charger { int (*chrg_present) (void); int (*chrg_type) (void); int (*bat_present) (void); int (*battery_state) (struct battery *bat); int (*battery_charge) (struct battery *bat); }; struct power_ops_muic { int (*cable_attached) (void); int (*cable_accesory_type) (void); }; struct power_ops_key_power { int (*key_state) (int *state); }; struct power_ops_rtc { int (*sec) (int set_get, int *val); int (*min) (int set_get, int *val); int (*hour) (int set_get, int *val); int (*day) (int set_get, int *val); int (*month) (int set_get, int *val); int (*year) (int set_get, int *val); }; struct power_ops_motor { int (*configure) (void); int (*enable) (int time, int gain); }; struct power_ops_led_flash { int (*configure) (void); int (*enable) (void); int (*disable) (void); }; struct power_ops_temp_control { int (*configure) (void); int (*get_temp) (int *val); }; struct power_dev_interface { int id; /* One device can use few interfaces */ int type; /* enum { PMIC_I2C, PMIC_SPI, ...}; */ int bus; int sensor_byte_order; int number_of_regs; union hw { struct p_i2c i2c; struct p_spi spi; } hw; }; struct power_dev_ops { /* type: enum { POWER_DEV_REGULATOR, ... } */ int type; /* id: for multiple ops of one type */ int id; /* corresponding interface */ struct power_dev_interface *io; /* Pointer to proper type ops structure */ void *ops; /* Recognized by sequential OPS */ struct list_head list; }; struct power_dev { int id; const char *name; /* device operations list */ struct power_dev_ops *ops; /* device instances list */ struct list_head list; }; Such organization of structures allows to: - initialize few instances of one driver, - initialize only supported operations, - provide driver's operations on a few interfaces, - initialize driver with the same ops on a different interfaces, Specified ops types allow implementation of optional framework command line tool especially we can search devices by: name, ops type, interface - every with optional multiple instance. e.g. command use # power list ops # power list devices # power list interfaces the rest of commands could be used as in current pmic framework. Of course this is just a proposition - It's not implemented yet. The next change is the integration with device tree which is obligatory here and device model could be added in the future. Drivers ops and interfaces could be initialized into linker lists. Device parameters like an interface, bus and instances could be parsed from dtb at runtime. So this gives some abstraction to power related devices. On a top of those changes I will add a simple charger manager. Before I start writing code I would like to receive some feedback, about this idea. Thank you, -- Przemyslaw Marczak Samsung R&D Institute Poland Samsung Electronics p.marczak(a)samsung.com

2 3

[U-Boot] [PATCH] powerpc/srio-pcie-boot: Adjust addresses for SRIO/PCIE boot
by Liu Gang 20 May '14

20 May '14

The new 768KB u-boot image size requires changes for SRIO/PCIE boot. These addresses need to be updated to appropriate locations. The updated addresses are used to configure the SRIO/PCIE inbound windows for the boot, and they must be aligned with the window size based on the SRIO/PCIE modules requirement. So for the 768KB u-boot image, the inbound window cannot be set with 0xfff40000 base address and 0xc0000 size, it should be extended to 1MB size and the base address can be aligned with the size. Signed-off-by: Liu Gang <Gang.Liu(a)freescale.com> --- include/configs/B4860QDS.h | 10 +++++----- include/configs/P2041RDB.h | 10 +++++----- include/configs/T208xQDS.h | 10 +++++----- include/configs/T208xRDB.h | 10 +++++----- include/configs/T4240QDS.h | 10 +++++----- include/configs/corenet_ds.h | 10 +++++----- 6 files changed, 30 insertions(+), 30 deletions(-) diff --git a/include/configs/B4860QDS.h b/include/configs/B4860QDS.h index eecff98..fc90c53 100644 --- a/include/configs/B4860QDS.h +++ b/include/configs/B4860QDS.h @@ -559,15 +559,15 @@ unsigned long get_board_ddr_clk(void); * for slave u-boot IMAGE instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef080000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff80000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x80000 /* 512K */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff80000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef200000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff00000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x100000 /* 1M */ +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff00000ull /* * for slave UCODE and ENV instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef040000ull +#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef100000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_BUS 0x3ffe00000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_SIZE 0x40000 /* 256K */ diff --git a/include/configs/P2041RDB.h b/include/configs/P2041RDB.h index 113bbb2..0616b20 100644 --- a/include/configs/P2041RDB.h +++ b/include/configs/P2041RDB.h @@ -383,15 +383,15 @@ unsigned long get_board_sys_clk(unsigned long dummy); * for slave u-boot IMAGE instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef080000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff80000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x80000 /* 512K */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff80000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef200000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff00000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x100000 /* 1M */ +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff00000ull /* * for slave UCODE and ENV instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef040000ull +#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef100000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_BUS 0x3ffe00000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_SIZE 0x40000 /* 256K */ diff --git a/include/configs/T208xQDS.h b/include/configs/T208xQDS.h index 0332648..cf5406b 100644 --- a/include/configs/T208xQDS.h +++ b/include/configs/T208xQDS.h @@ -509,15 +509,15 @@ unsigned long get_board_ddr_clk(void); * for slave u-boot IMAGE instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef080000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff80000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x80000 /* 512K */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff80000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef200000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff00000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x100000 /* 1M */ +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff00000ull /* * for slave UCODE and ENV instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef040000ull +#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef100000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_BUS 0x3ffe00000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_SIZE 0x40000 /* 256K */ diff --git a/include/configs/T208xRDB.h b/include/configs/T208xRDB.h index 2c12eab..12c24d0 100644 --- a/include/configs/T208xRDB.h +++ b/include/configs/T208xRDB.h @@ -462,15 +462,15 @@ unsigned long get_board_ddr_clk(void); * for slave u-boot IMAGE instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef080000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff80000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x80000 /* 512K */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff80000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef200000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff00000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x100000 /* 1M */ +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff00000ull /* * for slave UCODE and ENV instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef040000ull +#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef100000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_BUS 0x3ffe00000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_SIZE 0x40000 /* 256K */ diff --git a/include/configs/T4240QDS.h b/include/configs/T4240QDS.h index 9779825..491a866 100644 --- a/include/configs/T4240QDS.h +++ b/include/configs/T4240QDS.h @@ -379,15 +379,15 @@ unsigned long get_board_ddr_clk(void); * for slave u-boot IMAGE instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef080000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff80000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x80000 /* 512K */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff80000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef200000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff00000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x100000 /* 1M */ +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff00000ull /* * for slave UCODE and ENV instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef040000ull +#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef100000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_BUS 0x3ffe00000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_SIZE 0x40000 /* 256K */ diff --git a/include/configs/corenet_ds.h b/include/configs/corenet_ds.h index beb87bb..ca4ae51 100644 --- a/include/configs/corenet_ds.h +++ b/include/configs/corenet_ds.h @@ -381,15 +381,15 @@ * for slave u-boot IMAGE instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef080000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff80000ull -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x80000 /* 512K */ -#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff80000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_PHYS 0xfef200000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS1 0xfff00000ull +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_SIZE 0x100000 /* 1M */ +#define CONFIG_SRIO_PCIE_BOOT_IMAGE_MEM_BUS2 0x3fff00000ull /* * for slave UCODE and ENV instored in master memory space, * PHYS must be aligned based on the SIZE */ -#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef040000ull +#define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_PHYS 0xfef100000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_MEM_BUS 0x3ffe00000ull #define CONFIG_SRIO_PCIE_BOOT_UCODE_ENV_SIZE 0x40000 /* 256K */ -- 1.8.5

2 1