Re: [U-Boot] [PATCH] MIPS: Add onenand_init() to board.c and move nand_init()

Stefan Roese wrote: > This patch adds a call to onenand_init() for OneNAND support and moves > the nand_init() call to an earlier place, so that the environment can > be used from NAND and OneNAND. Fair enough. Thanks for your work. Then, I've checked qemu-mips build with GCC 4.2.3, and got no w

Re: [U-Boot] [PATCH] MIPS: Add board_early_init_f() to init_sequence

Stefan Roese wrote: > This patch adds the board_early_init_f() call to the MIPS init > sequence. A weak dummy implementation is also added which can be > overridden by a board specific version. > > This will be used by the upcoming VCTH board support. > > Signed-off-by: Stefan Roese <[EMAIL PROTE

Re: [U-Boot] [PATCH] MIPS: Add CONFIG_SKIP_LOWLEVEL_INIT and flush dcache upon relocation

Hi Stefan, Stefan Roese wrote: > This patch adds the CONFIG_SKIP_LOWLEVEL_INIT option to start.S. This > enables support for boards where the lowlevel initialization is > already done when U-Boot runs (e.g. via OnChip ROM). > > Also the data cache will be flushed upon relocation. This is missing

[U-Boot] [PATCH-OMAP3] OMAP3: Clean up EVM board file

- Use readx/writex instead of direct pointer access - Replace hardcoded values by macros - Minor space to tab conversion Notes: - Instead of read/modify/write GPIO_DATAOUT register use SET/CLEARDATAOUT register for GPIO64 - GPIO 1-6 CM_FCLKEN_PER and CM_ICLKEN_PER are already configured in pe

[U-Boot] add usb_system_autoupdate command.

Hi, I have add the possibility to automatic update entire flash using a USB pendrive. To make it, need the following steps: 1) insert usb pendrive. In pendrive must be present these files: install.dat and the files we want to copy. 2) from uboot console: => usb_system_autoupdate 3) the syste

[U-Boot] CFG_ENV_SECT_SIZE doubt

Hi all, I'm using a flash with the top sectors smaller then the others. The flash has got four 32kb sector and 255 sectors of 128kb. I'd like to use the small sectors to deploy there the environment. I've got a doubt about the configuration, is it possible to have CFG_ENV_SIZE bigger then CFG_ENV_

[U-Boot] [PATCH-OMAP3] OMAP3: Clean up board files

- Use readx/writex instead of direct pointer access - Replace hardcoded values by macros - Minor space to tab conversion No functional change. Signed-off-by: Dirk Behme <[EMAIL PROTECTED]> --- board/omap3/beagle/beagle.c| 78 +++- board/omap3/overo/overo.c