June 2011 - U-Boot

Re: [U-Boot] about at91 board in uboot
by Reinhard Meyer 17 Jun '11

17 Jun '11

Dear Lin, > The following is the status XU Hong is reporting to me on u-boot-atmel/master. > I saw it has been silent for 2 days. I don’t know if we could do something to help maintain all the boards. > I will try to help allocate some of my people to handling missing parts for our EK. I send a message about 2 days ago, asking that the SoC relevant parts are changed in a manner consistent with the changes for the 9260, like in at91sam9260_devices.c, at91sam9260.h, at91sam9260_matrix.h. Once that is done, and added to u-boot-atmel/master, the board specific patches should be rebased on that and submitted. Since nobody did volunteer so far, I was going to edit the SoC specific parts and submit them, but unfortunately that could take some time (until next week maybe, I was going to start today with that, but have paid work to finish as well :) ) I am not fond of quick and dirty solutions here, the boards are not going to be removed with this u-boot release, but will be after if no progress is seen - but we do have progress here - so no need to panic. So lets do it in two distinct steps: 1. fix SoCs 2. fix boards > 9261 soc & ek have been merged to atmel branch. > 9rl – v3 patches have been pushed out just now and shall be ok. > 9263 – soc part has been merged into atmel branch. I’m asking the ek part. > 9g45 - patches were sent by 3rd party. The SoC specific changes will/should be based before those patches, and will replace the current ones. --- Original Message: Dear Friends, I have received several different patches reworking "at91sam*_devices.c" and "at91sam9*.h". Lokking at them, none of them is completely done the way the files for at91sam9260 are done. Examples: 9260, 9263: ATMEL_ID_USART0 9261: ATMEL_ID_US0 9260 uses the CONFIG_AT91_GPIO_PULLUP define, the others do not. 9261 still uses the CONFIG_USARTx defines. Please have a look at at91sam9260 as a reference. We do need a properly fixed SoC port for 9261, 9263 and the others before individual board ports can be fixed. Just because there is a sudden rush to get things fixed for the next release should NOT tempt us to get in interim versions. With Best Regards, Reinhard

2 1

[U-Boot] праздник стоит у дверей
by Alexander 17 Jun '11

17 Jun '11

Добрый день, Стремитесь ли Вы приумножать свои доходы или просто хотите преодолеть финансовые проблемы? Можете ли Вы исполнять свои желания, не ограничивая себя в финансах или это сложно для Вас? Не упустите шанс реализовать свои мечты! - Абсолютно бесплатно и гарантированно - Для каждого подходит - Не выходя из дома Если Вы искали возможность зарабатывать побочно хорошие деньги, тогда Вы должны посетить мой сайт. Если Вы начнете сейчас, Вы заработаете деньги еще сегодня. - Никакого риска - Никаких данных не нужно (только Ваше имя) Нажмите просто здесь: Если хотите узнать, как это работает нажмите здесь Я рад Вашему посещению. Александр Воропаев

1 0

[U-Boot] About the CRC of u-boot.bin
by Peter Pan 17 Jun '11

17 Jun '11

I found out that even with the same source code, the final u-boot.bin has a different MD5sum each time I build. Is that possible to get an identical u-boot.bin for the same source code, no matter when I build?

5 8

[U-Boot] (no subject)
by FROM JORDAN GLOBAL LOANCORPORATION 17 Jun '11

17 Jun '11

This is to inform you that Jordan Global Loan Corporation here in Jordan have began a loan program to any one who might be in need of a loan for any financial concern.Should you be interested in applying for a business or personal loan, you are required to send an inquiry to us for further proceedings via (). Interested applicants are advice to fill this application form and get back to us 1)Full Names:___________________ 2)Country:_____________________ 3)address:____________________ 4)State :______________________ 5)Sex:________________________ 6)Age:_______________________ 7)Marital Status:________________ 8)Occupation:__________________ 9)Phone Number:_______________ 10)Currently position in place of work:__________________ 11)Amount Needed As Loan____________________ 12)Loan Duration_________________ 13) Current salary received:_________________ 14) Purpose of loan Consolation's_____ Yours Faithfully, Khaled Fatima Online advert coordinator Tel: (+962) 795 475 716

1 0

[U-Boot] [PATCH V4 0/2] GPIO: Tegra2: add GPIO driver for Tegra2
by Tom Warren 17 Jun '11

17 Jun '11

This patchset adds a GPIO driver for Tegra2 SoC, and enables it for all boards Changes in V2: - use 'gpio_pin' enum in gpio.h (Simon Glass review request) - change 'GPIO_PORT8' to 'GPIO_FULLPORT' (Simon Glass request) - change 'offset' to 'pin' globally - enable GPIO for all boards (tegra2-common.h) Changes in V3: - use common cmd_gpio; remove redundant cmd processing code - add gpio_request, gpio_free and gpio_toggle - alias 'gpio_status' to 'gpio_info' for use in cmd_gpio Changes in V4: - update code as per Mike Frysinger's review comments - rewrite gpio_info, aka gpio_status Tom Warren (2): GPIO: Tegra2: add GPIO driver for Tegra2 arm: Tegra2: GPIO: enable GPIO for Tegra2 boards arch/arm/include/asm/arch-tegra2/gpio.h | 250 +++++++++++++++++++++++++++++-- arch/arm/include/asm/gpio.h | 38 +++++ drivers/gpio/Makefile | 1 + drivers/gpio/tegra2_gpio.c | 254 +++++++++++++++++++++++++++++++ include/configs/tegra2-common.h | 2 + 5 files changed, 535 insertions(+), 10 deletions(-) create mode 100644 arch/arm/include/asm/gpio.h create mode 100644 drivers/gpio/tegra2_gpio.c -- 1.7.5.4

2 4

[U-Boot] misc patches and cleanup
by Christopher Harvey 17 Jun '11

17 Jun '11

I recently dabbled in u-boot and kept track of a few points I found confusing. I fixed them up to the best of my ability and created some patches for consideration.

2 1

[U-Boot] [RFC][Timer API] Revised Specification - Implementation details
by Graeme Russ 16 Jun '11

16 Jun '11

Hello Everyone, OK - Starting a new thread to discuss implementation details. This is a heads-up for arch/platform maintainers - Once this is a bit more stable, I will put it on the wiki Assumed Capabilities of the Platform - Has a 'tick counter' that does not rely on software to increment - tick interval may by a fixed constant which cannot be controlled via software, or it could be programmable (PIT) API Functions (/lib/timer.c) - u32 get_timer(u32 start) - Returns the number of elapsed milliseconds since 'start' API Functions (/arch/...) - void udelay(u32 delay) - Used for 'short' delays (generally up to several seconds) - Can use the tick counter if it is fast enough - MUST NOT RESET THE TICK COUNTER 'Helper' Functions (/lib/timer.c) - void sync_timebase(void) - Updates the millisecond timer - Utilises HAL functions to access the platform's tick counter - Must be called more often than the rollover period of the platform's tick counter - Does not need to be called with a regular frequency (immune to interrupt skew) - Is always called by get_timer() - For platforms with short tick counter rollovers it should be called by an ISR - Bill Campbell wrote a good example which proved this can be common and arbitrary (and optionally free of divides and capable of maintaining accuracy even if the tick frequency is not an even division of 1ms) HAL Functions (/arch/... or /board/...) - u64 get_ticks(void) - Returns a tick count as an unsigned 64-bit integer - Abstracts the implementation of the platform tick counter (platform may by 32-bit 3MHz counter, might be a 16-bit 0-999 microsecond plus 16-bit 0-65535 millisecond etc) - u64 ticks_per_millisecond() - Returns the number of ticks (as returned by get_ticks()) per millisecond - void timer_isr() - Optional (particularly if tick counter rollover period is exceptionally log which is usually the case for native 64-bit tick counters) - Simply calls sync_timebase() - For platforms without any tick counter, this can implement one (but accuracy will be harmed due to usage of disable_interrupts() and enable_interrupts() in U-Boot So to get the new API up and running, only two functions are mandatory: get_ticks() which reads the hardware tick counter and deals with any 'funny stuff' including rollovers, short timers (12-bit for example), composite counters (16-bit 0-999 microsecond + 16-bit millisecond) and maintains a 'clean' 64-bit tick counter which rolls over from all 1's to all 0's. The 64-bit tick counter does not need to be reset to zero ever (even on startup - sync_timebase tacks care of all the details) ticks_per_millisecond() simply return the number of ticks in a millisecond - This may as simple as: inline u64 ticks_per_millisecond(void) { return CONFIG_SYS_TICK_PER_MS; } But it may be trickier if you have a programmable tick frequency The optional timer ISR is required if the tick counter has a short roll over duration (short is up to you - 1 second is short, 1 hour might be, 1 century is not) Regards, Graeme

6 86

Re: [U-Boot] Uncompressing kernel ..... OK (Hangs here)
by Smitha 16 Jun '11

16 Jun '11

Wolfgang Denk <wd <at> denx.de> writes: > > In message <001301c3786a$369162b0$321c10ac <at> asradproto50> Tien wrote: > > > > Another thing you can do is go to u-boot/common/cmd_bootm.c in the function > > do_bootm_linux(..), at the end of it : > > > > (*kernel) (kbd, initrd_start, initrd_end, cmd_start, cmd_end); > > > > change it to > > > > (*kernel) (gd->bd, initrd_start, initrd_end, cmd_start, cmd_end); // > > kbd change to gd->bd > > Do NOT do this. > > > It should works. > > No, it is BROKEN. "gd" and "gd->bd" will go out of scope when Linux > is booting. The contents of this memory will be undefined. You create > ndefined behaviour. What do you think why we create a copy of this > date (in "kbd") in the first place? > > Best regards, > > Wolfgang Denk > Hi , I am tryng to bring up the WRlinux kernel on a custom board based on mpc 8247 . When I boot my image using bootm command it hangs at (*kernel) (kbd, initrd_start, initrd_end, cmd_start, cmd_end); in do_bootm_linux ( function.. please can you help Regards, Smitha

1 0

[U-Boot] [PATCH v3 0/5] updates for km ARM boards and board support for portl2
by Holger Brunck 16 Jun '11

16 Jun '11

This is the third version of the patch serie. This patch serie was rebased on top of the two posted patches: http://lists.denx.de/pipermail/u-boot/2011-June/094432.html http://lists.denx.de/pipermail/u-boot/2011-June/094433.html Initial cover letter message: Beside the board support some small cleanup was done and the phy_reset funtion for mgcoge3un was implemented. Additionaly the suen3 and suen8 target are collected in one target km_kirkwood. For new targets which differ only in the usage of the PCI interface on kirkwood a target km_kirkwood_pci was introduced, but they use all the same header file. All keymile boards compile cleanly and checkpatch reports no errors or warnings. Holger Brunck (2): arm/km: remove unneeded define arm/km: replace suenx targets with km_kirkwood Valentin Longchamp (3): arm/km: use board KM_ENV_BUS for CONFIG_I2C_ENV_EEPROM_BUS arm/km: ethernet support for mgcoge3un arm/km: add support for portl2 board MAINTAINERS | 7 ++- MAKEALL | 3 +- board/keymile/km_arm/km_arm.c | 45 ++++++++++++++- boards.cfg | 5 +- include/configs/km/km_arm.h | 4 +- include/configs/{suen3.h => km_kirkwood.h} | 18 +++++-- include/configs/mgcoge3un.h | 5 ++ include/configs/portl2.h | 81 ++++++++++++++++++++++++++++ include/configs/suen8.h | 50 ----------------- 9 files changed, 152 insertions(+), 66 deletions(-) rename include/configs/{suen3.h => km_kirkwood.h} (77%) create mode 100644 include/configs/portl2.h delete mode 100644 include/configs/suen8.h

2 6

[U-Boot] [PATCH v2 1/2] arm/kirkwood: if CONFIG_SOFT_I2C is set don't set CONFIG_I2C_MVTWSI
by Holger Brunck 16 Jun '11

16 Jun '11

Some boards e.g. keymile arm boards have CONFIG_CMD_I2C switched on but they use soft i2c on kirkwood. So don't switch CONFIG_I2C_MVTWSI on in this case. Signed-off-by: Holger Brunck <holger.brunck(a)keymile.com> cc: Valentin Longchamp <valentin.longchamp(a)keymile.com> cc: Prafulla Wadaskar <prafulla(a)marvell.com> cc: Heiko Schocher <hs(a)denx.de> --- changes for v2: - nothing arch/arm/include/asm/arch-kirkwood/config.h | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/arch/arm/include/asm/arch-kirkwood/config.h b/arch/arm/include/asm/arch-kirkwood/config.h index 71ba464..b7dae1e 100644 --- a/arch/arm/include/asm/arch-kirkwood/config.h +++ b/arch/arm/include/asm/arch-kirkwood/config.h @@ -137,7 +137,9 @@ * I2C related stuff */ #ifdef CONFIG_CMD_I2C +#ifndef CONFIG_SOFT_I2C #define CONFIG_I2C_MVTWSI +#endif #define CONFIG_SYS_I2C_SLAVE 0x0 #define CONFIG_SYS_I2C_SPEED 100000 #endif -- 1.7.1

2 3