February 2013 - U-Boot

[U-Boot] [PATCH] configs:Remove unused macro CONFIG_DISCOVER_PHY
by Ashok Kumar Reddy 04 Feb '13

04 Feb '13

Remove unused macro CONFIG_DISCOVER_PHY from configs. Signed-off-by: Ashok Kumar Reddy <ashokkourla2000(a)gmail.com> --- include/configs/apx4devkit.h | 1 - include/configs/sc_sps_1.h | 1 - 2 files changed, 2 deletions(-) diff --git a/include/configs/apx4devkit.h b/include/configs/apx4devkit.h index 6764b47..73c66af 100644 --- a/include/configs/apx4devkit.h +++ b/include/configs/apx4devkit.h @@ -175,7 +175,6 @@ #define CONFIG_FEC_MXC_PHYADDR 0 #define IMX_FEC_BASE MXS_ENET0_BASE #define CONFIG_MII -#define CONFIG_DISCOVER_PHY #define CONFIG_FEC_XCV_TYPE RMII #endif diff --git a/include/configs/sc_sps_1.h b/include/configs/sc_sps_1.h index f5dc393..6140d5b 100644 --- a/include/configs/sc_sps_1.h +++ b/include/configs/sc_sps_1.h @@ -160,7 +160,6 @@ #define CONFIG_FEC_MXC #define CONFIG_FEC_MXC_MULTI #define CONFIG_MII -#define CONFIG_DISCOVER_PHY #define CONFIG_FEC_XCV_TYPE RMII #define CONFIG_PHYLIB #define CONFIG_PHY_SMSC -- 1.7.9.5

3 3

[U-Boot] [PATCH] drivers/block/systemace - fixed data type in "systemace_read" to match prototype in "block_dev_desc_t"
by Alexey Brodkin 04 Feb '13

04 Feb '13

Currently we have "unsigned long blkcnt" which is fine with CONFIG_SYS_64BIT_LBA undefined because "lbaint_t" is basically the same "unsigned long". If CONFIG_SYS_64BIT_LBA gets defined "lbaint_t" is defined as "unsigned long long". Even though not many embedded systems have CONFIG_SYS_64BIT_LBA defined it's good to have types in function implementation that match exactly with prototypes. Signed-off-by: Alexey Brodkin <alexey.brodkin(a)gmail.com> --- drivers/block/systemace.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/block/systemace.c b/drivers/block/systemace.c index 247cf06..80076b4 100644 --- a/drivers/block/systemace.c +++ b/drivers/block/systemace.c @@ -83,7 +83,7 @@ static u16 ace_readw(unsigned off) } static unsigned long systemace_read(int dev, unsigned long start, - unsigned long blkcnt, void *buffer); + lbaint_t blkcnt, void *buffer); static block_dev_desc_t systemace_dev = { 0 }; @@ -149,7 +149,7 @@ block_dev_desc_t *systemace_get_dev(int dev) * number of blocks read. A zero return indicates an error. */ static unsigned long systemace_read(int dev, unsigned long start, - unsigned long blkcnt, void *buffer) + lbaint_t blkcnt, void *buffer) { int retry; unsigned blk_countdown; -- 1.7.10.4

2 1

[U-Boot] [PATCH 2/2] beagle: expansion boards: add LSR COM6L adapter
by Robert Nelson 04 Feb '13

04 Feb '13

http://www.lsr.com/wireless-products/com6l The eeprom on this expansion board requires 16bit addressing. Signed-off-by: Robert Nelson <robertcnelson(a)gmail.com> --- board/ti/beagle/beagle.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/board/ti/beagle/beagle.c b/board/ti/beagle/beagle.c index 9493c6b..58bd556 100644 --- a/board/ti/beagle/beagle.c +++ b/board/ti/beagle/beagle.c @@ -72,6 +72,7 @@ #define BBTOYS_LCD 0x03000B00 #define BCT_BRETTL3 0x01000F00 #define BCT_BRETTL4 0x02000F00 +#define LSR_COM6L_ADPT 0x01001300 #define BEAGLE_NO_EEPROM 0xffffffff DECLARE_GLOBAL_DATA_PTR; @@ -462,6 +463,11 @@ int misc_init_r(void) case BCT_BRETTL4: printf("Recognized bct electronic GmbH brettl4 board\n"); break; + case LSR_COM6L_ADPT: + printf("Recognized LSR COM6L Adapter Board\n"); + MUX_BBTOYS_WIFI() + setenv("buddy", "lsr-com6l-adpt"); + break; case BEAGLE_NO_EEPROM: printf("No EEPROM on expansion board\n"); setenv("buddy", "none"); -- 1.7.10.4

1 0

[U-Boot] common/cmd_disk.c doesn't actually define any "commands"
by Robert P. J. Day 04 Feb '13

04 Feb '13

another observation from my weekend perusal of all of the common/cmd_*.c files is that, despite its "cmd_" filename prefix, the source file cmd_disk.c doesn't define any actual u-boot commands. according to what i see as u-boot filename naming conventions, it shouldn't be named "cmd_*", should it? rday

3 8

[U-Boot] the weirdness with cmd_df.c
by Robert P. J. Day 04 Feb '13

04 Feb '13

i mentioned this this weekend as well, can someone clarify this? the source file cmd_df.c looks weird: U_BOOT_CMD( sf, 2, 1, do_serial_flash, "Serial flash sub-system", "probe [bus:]cs - init flash device on given SPI bus and CS") so the source file "cmd_df.c" allegedly defines a command called "sf", which invokes "do_serial_flash", which isn't even defined in that source file -- what's defined in that file is "do_df". i don't see "do_serial_flash" defined anywhere in the u-boot source tree. am i just being blind? i see no reference to that source file in Makefile, so i'm guessing it's historical cruft that could be deleted? rday

2 1

[U-Boot] [PATCH V2 0/7] ARM: OMAP4+: Cleanup clocks, control and emif code
by R Sricharan 04 Feb '13

04 Feb '13

This series is intended to cleanup code which is duplicated across soc specific files. This is accomplished by moving soc specifc data to one place and having the code common. This helps in avoiding un necessary cpu checks and minimal code addition for future socs. Tested this on OMAP5 ES1.0, OMAP4460 Panda boards and verified MAKEALL for all armv7 boards. Lokesh Vutla (4): ARM: OMAP4+: emif: Detect SDRAM from SDRAM config register ARM: OMAP4+: Cleanup emif specific files ARM: OMAP4+: Make control module register structure generic ARM: OMAP5: Clean up iosettings code R Sricharan (3): ARM: OMAP4+: Change the PRCM structure prototype common for all Socs ARM: OMAP4+: Cleanup the clocks layer ARM: OMAP4+: Clean up the pmic code arch/arm/cpu/armv7/omap-common/clocks-common.c | 283 ++++++++---- arch/arm/cpu/armv7/omap-common/emif-common.c | 71 ++- arch/arm/cpu/armv7/omap-common/hwinit-common.c | 8 +- arch/arm/cpu/armv7/omap-common/vc.c | 11 +- arch/arm/cpu/armv7/omap4/Makefile | 3 +- arch/arm/cpu/armv7/omap4/clocks.c | 517 ---------------------- arch/arm/cpu/armv7/omap4/hw_data.c | 502 +++++++++++++++++++++ arch/arm/cpu/armv7/omap4/hwinit.c | 36 +- arch/arm/cpu/armv7/omap4/prcm-regs.c | 315 +++++++++++++ arch/arm/cpu/armv7/omap4/sdram_elpida.c | 16 +- arch/arm/cpu/armv7/omap5/Makefile | 3 +- arch/arm/cpu/armv7/omap5/clocks.c | 494 --------------------- arch/arm/cpu/armv7/omap5/hw_data.c | 494 +++++++++++++++++++++ arch/arm/cpu/armv7/omap5/hwinit.c | 131 +++--- arch/arm/cpu/armv7/omap5/prcm-regs.c | 380 ++++++++++++++++ arch/arm/cpu/armv7/omap5/sdram.c | 119 +++-- arch/arm/include/asm/arch-omap4/clocks.h | 562 ++---------------------- arch/arm/include/asm/arch-omap4/omap.h | 33 +- arch/arm/include/asm/arch-omap4/sys_proto.h | 3 +- arch/arm/include/asm/arch-omap5/clocks.h | 506 +-------------------- arch/arm/include/asm/arch-omap5/omap.h | 96 +--- arch/arm/include/asm/arch-omap5/sys_proto.h | 4 +- arch/arm/include/asm/emif.h | 18 +- arch/arm/include/asm/omap_common.h | 482 ++++++++++++++++++++ drivers/mmc/omap_hsmmc.c | 25 +- include/configs/omap5_evm.h | 1 + 26 files changed, 2659 insertions(+), 2454 deletions(-) delete mode 100644 arch/arm/cpu/armv7/omap4/clocks.c create mode 100644 arch/arm/cpu/armv7/omap4/hw_data.c create mode 100644 arch/arm/cpu/armv7/omap4/prcm-regs.c delete mode 100644 arch/arm/cpu/armv7/omap5/clocks.c create mode 100644 arch/arm/cpu/armv7/omap5/hw_data.c create mode 100644 arch/arm/cpu/armv7/omap5/prcm-regs.c -- 1.7.9.5

2 15

[U-Boot] Need Support to Flash Uboot on Intel platform
by rajesh n 04 Feb '13

04 Feb '13

Hi All, I am trying to boot U-boot on Intel platform.. I want to clarify following Questions, Please help to me.. 1) If U-boot supports for Intel, then How can we create and flash U-boot image on Intel host machine. and also what configuration file i can use? 2) i go through the U-boot source code, it contains Bios-emulator code. is there any use to boot U-boot with Bios emulator. Please give me your valuable suggestions ASAP. Regards, Rajesh.

2 1

[U-Boot] Watchdog Handlers
by Gurucharan Ch 04 Feb '13

04 Feb '13

Hi Everyone, I know how to initialise watchdog registers & and how to change delay using WLDR reg, but I'm not getting how to use pre-scalar(i.e. WCLR reg), and one more thing is I want to stop the counter register of watchdog after it has reached certain point I want to know what is the procedure to stop watchdog counter after initialisation. Please guide me in this issue. Thanks & Regards, Guru Charan

2 1

[U-Boot] [U-boot] mkimage -F parameter
by TigerLiu＠viatech.com.cn 04 Feb '13

04 Feb '13

Hi, experts: It seems mkimage has supported signing a image. So, I have a question about signed linux kernel image: 1. if kernel image is signed by mkimage tool. Could uboot verify this signed linux kernel image bf jumping to its entry point function? 2. if uboot could verify the signed linux kernel image how to management these different vendors' public keys in uboot code? Using env variable? Best wishes,

3 5

[U-Boot] u-boot command list, grouped by source file
by Robert P. J. Day 03 Feb '13

03 Feb '13

while i was scouring the source code in the common/ directory, i put together this lengthy list of all of the possible commands, grouped by their source file and annotated by whatever *additional* CONFIG settings they require: http://www.crashcourse.ca/wiki/index.php/U-Boot_command/file_reference not perfect, but it gives me a quick way to know what source files provide which commands, and under what circumstances. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================

1 0