[U-Boot] ksz9021 phy support

Hi Troy, is here any specific reason for the "disable_giga" switch in the ksz9021 phy driver? We're just having some issues here, most of the times we don't get the link up with a gigabit connection. Anything else that caused trouble on your side, apart from the PHY ID mess? :) Kolja Kolja Sc

Re: [U-Boot] ksz9021 phy support

On 13.07.2012 10:20, Schneider, Kolja wrote: Hi Troy, is here any specific reason for the "disable_giga" switch in the ksz9021 phy driver? We're just having some issues here, most of the times we don't get the link up with a gigabit connection. Anything else that caused trouble on your side, a

Re: [U-Boot] problem on BL1.bin

Hi Balaji, On 13 July 2012 11:04, VISWANADHULA BALAJI wrote: > Hi All, > > Iam using smdkv310 board of SAMSUNG EXYNOS SOC. How bl1.bin file copy the > uboot.bin file from SD/MMC card to DDR2 RAM. > > by using the following device copy functions > > #define SDMMC_ReadBlocks_eMMC_ByCPU(uNumOfBlks,

Re: [U-Boot] [PATCH 2/2 v3] FSL/eSDHC: enable the clock to detect the SD card

Dear Huang Changming-R66093, > Hi, Andy > There is not any feedback for very long time, > Could it be applied to u-boot? Could it be we have a maintainer problem and unhappy contributor problem in here? > Best Regards > Jerry Huang > > > -Original Message- > > From: u-boot-boun...@list

Re: [U-Boot] [PATCH v2 4/7] dfu: MMC specific routines for DFU operation

Dear Tom Rini, > On Thu, Jul 12, 2012 at 02:39:27PM +0200, Lukasz Majewski wrote: > > On Wed, 11 Jul 2012 04:54:31 -0700 > > > > Tom Rini wrote: > > > On Tue, Jul 10, 2012 at 12:38:54PM +0200, Lukasz Majewski wrote: > > > > Hi Tom, > > > > > > > > > On Wed, Jul 04, 2012 at 05:48:39PM +0200, Luk

Re: [U-Boot] FDT driver initialization function declaration

Dear Michal Simek, > On 07/10/2012 05:11 PM, Marek Vasut wrote: > > Dear Michal Simek, > > > >> Dear Wolfgang, > >> > >> On 07/10/2012 03:03 PM, Wolfgang Denk wrote: > >>> Dear Michal Simek, > >>> > >>> In message<4ffc1ef8.9060...@monstr.eu> you wrote: > The hardest part I have identify

Re: [U-Boot] [PATCH V2] i.MX: fsl_esdhc: allow use with cache enabled.

Dear Dirk Behme, [...] > >> I'm not likely to have any time until after FTF next week. > >> > >> Any chance that a PPC maintainer can chime in here? > > > > I think WD applied the cache stub patch already. Can you try now please? > > Ping ;) > > Thanks Adding our human interactions expert in

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

Dear Joe Hershberger, > Hi Marek, > > On Fri, Dec 16, 2011 at 2:36 PM, Marek Vasut wrote: > >> On Friday 16 December 2011 13:13:33 Marek Vasut wrote: > >> > On Friday 16 December 2011 12:33:53 Mike Frysinger wrote: > >> > > rename ISA_OFFSET to CONFIG_NE2000_IO_OFFSET, then move the "2" to > >>

Re: [U-Boot] [PATCH 3/3] mxc_i2c: remove setting speed at each start

Dear Dirk Behme, [...] > > Ok, everything was already clear, and I can also add my: > > > > Acked-by: Stefano Babic > > Same for this one: Is this applied anywhere? It doesn't seem to be part > of v2012.07-rc1? > > Best regards Stefano, once you're out of mont blanc, can you apply this pleas

Re: [U-Boot] [U-Boot-DM] FDT driver initialization function declaration

Dear Tomas Hlavacek, > On Thu, Jul 12, 2012 at 10:22 AM, Michal Simek wrote: > >> thats what platform_data is for, if i understand what you mean > > > > That's my understanding too. But the point is how it is passed to the > > driver itself > > because I didn't see any pointer to it there. > >

Re: [U-Boot] [PATCH 3/3] mxc_i2c: remove setting speed at each start

Dear Marek Vasut, In message <201207131238.11964.ma...@denx.de> you wrote: > > > > Ok, everything was already clear, and I can also add my: > > > > > > Acked-by: Stefano Babic > > > > Same for this one: Is this applied anywhere? It doesn't seem to be part > > of v2012.07-rc1? > > > > Best reg

[U-Boot] [PATCH] Add support for DS1388.

Support for DS1388 is added by extending the DS1337 driver. DS1388 is similar to DS1337. The time registers are offset by 1 (due to support for hundreds of seconds), and there is no century bit. The configuration and trickle charge registers are also different. Tested on hardware with Freescale

Re: [U-Boot] [U-Boot-DM] FDT driver initialization function declaration

On Thu, Jul 12, 2012 at 10:22 AM, Michal Simek wrote: > > >> thats what platform_data is for, if i understand what you mean >> > > That's my understanding too. But the point is how it is passed to the > driver itself > because I didn't see any pointer to it there. > > I had an impression that plat

Re: [U-Boot] [PATCH 3/3] mxc_i2c: remove setting speed at each start

Dear Wolfgang Denk, > Dear Marek Vasut, > > In message <201207131238.11964.ma...@denx.de> you wrote: > > > > Ok, everything was already clear, and I can also add my: > > > > > > > > Acked-by: Stefano Babic > > > > > > Same for this one: Is this applied anywhere? It doesn't seem to be part > >

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Wolfgang Denk wrote: > This is a totally broken design then, when you have a growing data > structure where vital information fields get shifted. In such case, > the CRC should have been at the beginning, so it never changes > location. Or even better, you should not have used a binary data > stru

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Wolfgang Denk wrote: >> >My patch provides transparent updates to handle it. It will read broken >> >EEPROMs and verify the CRC in the old location, and if you have re-save >> >the EEPROM, it will put the CRC in the right place. > It will work by chance, accessing random data. This is crap. It

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

sun york-R58495 wrote: > I agree it was a broken design. Now we are using all available space > and put CRC to the very end. It is not perfect but should work. *sigh* The design was never broken, the code was just wrong. The CRC has always supposed to have been at the end. -- Timur Tabi Linu

[U-Boot] [PATCH] dts/Makefile: Turn off system-/gcc-specific predefined macros

Add '-undef' to DTS_CPPFLAGS to avoid unwanted expansion of dts content that matches system-specific or gcc-specific predefined macros. Example: A number of PowerPC related *.dts files in the kernel define a property named 'linux,network-index' which (w/o '-undef') is expanded to '1,network-index'

[U-Boot] Doubt on uboot code

Hi, Thank you for your reply. I have the U-boot source code of SAMSUNG EXYNOS SMDKV310 board. When i compiled the U-boot source code I got uboot.bin file and bl1.bin file. Actually bl1.bin file is extracted from the uboot.bin file by using the mkbl2 tool(tool's source code is prese

Re: [U-Boot] [PATCH] cfb_console: Add support for some ANSI terminal escape codes

On Sunday 01 July 2012 12:34:49 Pali Rohár wrote: > Hello, > > I'm sending new patch which add support for ANSI terminal in > cfb_console driver. This patch comes from RX-51 patch series, > but more cfb patches were commited to u-boot git. This is last > patch for cfb driver, so I'm sending it sepa

[U-Boot] V2 S3c64xx: Switch all I/O to use readl/writel functio and Clear variable

V2: 1. Modify the type of return for s3c64xx_get_base_nand 2. Add patch 0014 to support s3c6410 board 3. Adjust patch for mix content. V1: This serial patch intent to: 1. Switch all I/O to use readl/writel function 2. Change nand_spl to use SPL framework 3. S3C64XX serial includes s3c6400 and s3c6

[U-Boot] [V2 01/15] SMDK6400: Move smdk6400 board from Makefile to boards.cfg

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - None --- Makefile | 20 board/samsung/smdk6400/config.mk |4 +--- boards.cfg |2 ++ include/configs/smdk6400.h |2 +- 4 files change

[U-Boot] [V2 02/15] S3C64XX: Switch to use readl/writel to operate nand flash

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - Change the type of the return value from unsinged int to unsinged long for s3c64xx_get_base_nand function. - Delete const for the local variable. --- arch/arm/include/asm/arch-s3c64xx/nand.h| 69

[U-Boot] [V2 03/15] S3C64XX: Use readl/writel to operate uart

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - Change the type of the return value from unsinged int to unsinged long for s3c64xx_get_base_uart function. - Delete const for the local variable. --- arch/arm/include/asm/arch-s3c64xx/s3c6400.h | 65

[U-Boot] [V2 04/15] S3C64XX: add pwm for s3c64xx support

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - Change the type of the return value from unsinged int to unsinged long for s3c64xx_get_base_nand function. --- arch/arm/cpu/arm1176/s3c64xx/Makefile |1 + arch/arm/cpu/arm1176/s3c64xx/pwm.c

[U-Boot] [V2 05/15] S3C64XX: reference s5p cpu time system for s3c64xx timer

From: Zhong Hongbo The old s3c64xx timer is not work normal, Adopt s5p time design, It work perfect. Signed-off-by: Zhong Hongbo --- Change for V2: - Delete const key word for the variable of struct s3c_timer. --- arch/arm/cpu/arm1176/s3c64xx/timer.c | 193

[U-Boot] [V2 06/15] S3C64xx: mov cpu_init.S to the board directory

From: Zhong Hongbo It just only do the memory init. The memory depend on the design of board. Signed-off-by: Zhong Hongbo --- Change for V2: - None. --- arch/arm/cpu/arm1176/s3c64xx/Makefile |2 +- arch/arm/cpu/arm1176/s3c64xx/cpu_init.S | 135 --- bo

[U-Boot] [V2 07/15] S3C6400: Delete nand_spl for S3C6400

From: Zhong Hongbo The old spl use nand_spl directory file to support nand flash boot. We will adopt the new SPL framework to implement it. Signed-off-by: Zhong Hongbo --- Change for V2: - None. --- board/samsung/smdk6400/config.mk | 28 --- boards.cfg

[U-Boot] [V2 08/15] S3C6400: Adopt SPL framwork to support spl for nand flash

From: Zhong Hongbo Adopt the new SPL framework to implement the SPL booting of the nand flash for S3C6400. Signed-off-by: Zhong Hongbo --- Change for V2: - seprate some code. --- arch/arm/cpu/arm1176/start.S| 16 +--- board/samsung/smdk6400/Makefile

[U-Boot] [V2 09/15] arm1176: Fixed No relocation.

From: Zhong Hongbo When It do not need to relocat for u-boot, the offset(r9) of relocation should be set zero. Signed-off-by: Zhong Hongbo --- Change for V2: - This fix is seprated from nand_spl patch. --- arch/arm/cpu/arm1176/start.S |1 + 1 files changed, 1 insertions(+), 0 delet

[U-Boot] [V2 10/15] S3C64XX: Change SROM init to use read/write operation

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - Change the type of return for s3c64xx_get_base_sromc function. --- arch/arm/cpu/arm1176/s3c64xx/Makefile |2 +- arch/arm/cpu/arm1176/s3c64xx/srom.c | 51 +++ arch/arm/include/

[U-Boot] [V2 11/15] S3C64XX: Switch to use read/writel to operation clock system

From: Zhong Hongbo Switch to use read/writel function and clear the relevant variable. Signed-off-by: Zhong Hongbo --- Change for V2: - merge clock patch. - Change the type of return for s3c64xx_get_base_clock function. --- arch/arm/cpu/arm1176/s3c64xx/reset.S|4 +-

[U-Boot] [V2 12/15] S3c64xx: clear GPIO, Interrupt, Watchdog variable.

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - None. --- arch/arm/include/asm/arch-s3c64xx/s3c6400.h | 260 --- board/samsung/smdk6400/lowlevel_init.S | 23 ++-- 2 files changed, 11 insertions(+), 272 deletions(-) diff --git a/arch/a

[U-Boot] [V2 13/15] S3C6400: clear memory init variable

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - None. --- arch/arm/include/asm/arch-s3c64xx/s3c6400.h | 173 +-- board/samsung/smdk6400/lowlevel_init.S | 13 +-- board/samsung/smdk6400/mem_init.S | 114 +- 3

[U-Boot] [V2 14/15] S3C64XX: Move s3c6400.h to cpu.h to support s3c6410 board

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - New. --- arch/arm/cpu/arm1176/s3c64xx/pwm.c |2 +- arch/arm/cpu/arm1176/s3c64xx/reset.S|2 +- arch/arm/cpu/arm1176/s3c64xx/speed.c|2 +- arch/arm/cpu/arm1176/s3c64xx/srom.c |

[U-Boot] [V2 15/15] S3C6400: Remove the unused variable for S3C6400

From: Zhong Hongbo Signed-off-by: Zhong Hongbo --- Change for V2: - None. --- include/configs/smdk6400.h | 15 --- 1 files changed, 0 insertions(+), 15 deletions(-) diff --git a/include/configs/smdk6400.h b/include/configs/smdk6400.h index 46241e2..b8b9d1a 100644 --- a/in

Re: [U-Boot] [V2 04/15] S3C64XX: add pwm for s3c64xx support

resend again, I receive Message undeliverable On 07/14/2012 12:11 AM, Zhong Hongbo wrote: > From: Zhong Hongbo > > Signed-off-by: Zhong Hongbo > --- > Change for V2: > - Change the type of the return value from unsinged int > to unsinged long for s3c64xx_get_base_nand function. >

[U-Boot] __led_set usage is inconsistent

Hi, I hope that this is not a common question. I have read doc/README.LED, compiled in the GPIO LED driver, provided my GPIO number, enabled the LED command and then noticed that "led 0 on" didn't do what I wanted. It appears that the semantic of "state" in __led_set(mask, state) is used in two d

[U-Boot] [PATCH 1/2] sf: stmicro: support JEDEC standard two-byte signature

There are more than the M25Pxx serial flashs that can be used with the stmicro driver, for example: the M25PXxx or N25Qxx serie. All these chips have burned in the original stmicro manufacture id 0x20 together with a standard two-byte signature. In preperation to support all these chips the stmicr

[U-Boot] [PATCH 2/2] sf: stmicro: add support N25Q128 parts

Adds support for Numonyx's N25Q128 SPI flash. These devices are used on (among others) Avnet Spartan-6 LX9 micro-evaluation boards. Tested with "sf" commands and CONFIG_ENV_IS_IN_SPI_FLASH. Signed-off-by: Stephan Linz --- drivers/mtd/spi/stmicro.c |7 +++ 1 files changed, 7 insertions(+)

[U-Boot] uboot for zyxel nsa320

I have a new Zyxel NSA320. It is unmodified. At the uboot prompt I printenv and save all environment variables. Next I pulled code from https://github.com/psch2/uboot-nsa320, compiled and used kwboot to load new uboot. No problems so far. Now if I reload all environment variables I saved and bo

[U-Boot] [PATCH u-boot-arm/next 1/2] OMAP3: igep00x0: Add config option to choose flash storage memory

IGEP-based boards can have two different flash memories, a OneNAND or a NAND device. Add a configuration option for to choose which memory to use. Signed-off-by: Javier Martinez Canillas --- board/isee/igep0020/igep0020.h |4 board/isee/igep0030/igep0030.h |4 boards.cfg

[U-Boot] [PATCH u-boot-arm/next 2/2] OMAP3: igep00x0: add SPL support for IGEP-based boards

This patch adds SPL support for IGEP-based boards. Tested on an IGEPv2 Rev.C board with Micron NAND Flash memory. Signed-off-by: Javier Martinez Canillas --- board/isee/igep0020/config.mk | 33 board/isee/igep0020/igep0020.c | 34 - board/isee/igep0

[U-Boot] [PATCH] part_mac: dcache: allocate cacheline-aligned buffers

This patch forces the correct alignment for DMA operations of buffers used by part_mac.c. Signed-off-by: Benoît Thébaudeau Cc: Wolfgang Denk --- {u-boot.orig => u-boot}/disk/part_mac.c | 68 +++ 1 file changed, 34 insertions(+), 34 deletions(-) diff --git u-boot.o

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

On Fri, 2012-07-13 at 05:12 -0700, Tabi Timur-B04825 wrote: > sun york-R58495 wrote: > > > I agree it was a broken design. Now we are using all available space > > and put CRC to the very end. It is not perfect but should work. > > *sigh* > > The design was never broken, the code was just wrong.

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Dear Tabi Timur-B04825, In message <50001038.50...@freescale.com> you wrote: > > > York is mistaken. The CRC was always at location 0xFC, but for some > reason, when I wrote the code, I put it at 0xCC. Now I'm fixing it, and > providing some backwards compatibility to avoid causing problems fo

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Dear Tabi Timur-B04825, In message <5000106b.5090...@freescale.com> you wrote: > > > It will work by chance, accessing random data. This is crap. > > It is not crap, and it will not work by chance. It is not accessing > random data, it is accessing the CRC in the old location, just like the >

Re: [U-Boot] [PATCH v2 4/7] dfu: MMC specific routines for DFU operation

>> > Generally it is in my opinion a good way to go. >> > >> > However, why we aren't first writing sanity checks for passed arguments? >> >> Simply because I didn't want to ask you to do a lot more unrelated work >> >> :) If you want to split and check the mmc (and fatwrite) argueuments >> >> and

Re: [U-Boot] Doubt on uboot code

Dear VISWANADHULA BALAJI, In message you wrote: > > I have the U-boot source code of SAMSUNG EXYNOS SMDKV310 board. When i Where did you get this code from? >"bl1.bin responsibility is to load the second stage bootloader from > the sd card to SD RAM".*I have the doubt in the bl1.b

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Wolfgang Denk wrote: > In case you have an EEPROM with correct layout (CRC at 0xFC) but > incorrect CRC, you will access random data and interpret this as CRC. > This is provoking undefined behaviour. True, but it doesn't matter. The EEPROM is not that important, and the odds of screwing this up

Re: [U-Boot] [PATCH 1/2 v2] SDHC/MMC: fix the wrong infomation after change SD card

On Wed, Jul 11, 2012 at 4:29 AM, Huang Changming-R66093 wrote: > Hi, Andy, > There is not any feedback for very long time, > Could it be applied to the u-boot? I'm afraid I have to reject this patch. We need to find a better solution to the two problems: 1) We want to change cards and still hav

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Dear Timur Tabi, In message <50009349.9000...@freescale.com> you wrote: > > > In case you have an EEPROM with correct layout (CRC at 0xFC) but > > incorrect CRC, you will access random data and interpret this as CRC. > > This is provoking undefined behaviour. > > True, but it doesn't matter. Th

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Wolfgang Denk wrote: > Well, if it's really so unimportant and used in only a small number > of boards, then just omit this broken code that provokes the > undefined behaviour. As I said before, we need to support situations where people upgrade their U-Boot. When the EEPROM is read, the CRC is c

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

On 07/13/2012 04:25 PM, Wolfgang Denk wrote: > Dear Tabi Timur-B04825, > > In message <50001038.50...@freescale.com> you wrote: >>> >> York is mistaken. The CRC was always at location 0xFC, but for some >> reason, when I wrote the code, I put it at 0xCC. Now I'm fixing it, and >> providing som

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Scott Wood wrote: > Timur, I know you said you don't control the format, but could you ask > for a version number bump so that going forward there's a way to > unambiguously mark the contents as "good" (the spec wouldn't change, but > there would be no known implementations of v2 with this bug)?

[U-Boot] Please pull u-boot-mmc.git

Merge branch 'master' of git://git.denx.de/u-boot-i2c (2012-07-12 08:17:29 +0200) are available in the git repository at: git://www.denx.de/git/u-boot-mmc.git master Eric Nelson (1): i.MX: fsl_esdhc: allow use with cache enabled. Jaehoon Chung (1): mmc: remove the hard setting

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

On 07/13/2012 04:53 PM, Timur Tabi wrote: > Scott Wood wrote: > >> Timur, I know you said you don't control the format, but could you ask >> for a version number bump so that going forward there's a way to >> unambiguously mark the contents as "good" (the spec wouldn't change, but >> there would b

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Scott Wood wrote: > I know the spec wouldn't change, except the version number. But as I > said above, there would be no known v2 implementations with the bug. > You would only check the bad CRC location if you see v1 data, because > there are known buggy v1 implementations. I already have that:

[U-Boot] [PATCH 2/2] microblaze: Wire up SPI driver

Depending on XILINX_SPI_FLASH_BASEADDR enable SPI flash and environment in SPI flash. Expected values from xparameters.h are: - XILINX_SPI_FLASH_BASEADDR - XILINX_SPI_FLASH_MAX_FREQ - XILINX_SPI_FLASH_CS Signed-off-by: Stephan Linz --- include/configs/microblaze-generic.h | 55 +++

[U-Boot] [PATCH 1/2] spi: microblaze: Adds driver for Xilinx SPI controller

This is an improved version of the driver patch original submitted by Graeme Smecher The changes are: - remove hard coded Xilinx BSP defines (XPAR_SPI_*) and use CONFIG_SYS_SPI_BASE from config.h instead - add extensive register struct definitions - remove offset calculation for

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

On 07/13/2012 05:22 PM, Timur Tabi wrote: > Scott Wood wrote: > >> I know the spec wouldn't change, except the version number. But as I >> said above, there would be no known v2 implementations with the bug. >> You would only check the bad CRC location if you see v1 data, because >> there are kno

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Scott Wood wrote: > But you continue to generate v1 EEPROMs. If we get the people who > define the format to accept v2, then we can generate v2 after the fix is > applied, and the (very small) risk of a real CRC failure combined with a > spurious CRC success in the old location would only apply on

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

On 07/13/2012 05:46 PM, Timur Tabi wrote: > Scott Wood wrote: >> But you continue to generate v1 EEPROMs. If we get the people who >> define the format to accept v2, then we can generate v2 after the fix is >> applied, and the (very small) risk of a real CRC failure combined with a >> spurious CRC

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Dear Scott Wood, In message <500096e0.9010...@freescale.com> you wrote: > > If not, and Wolfgang still refuses to accept this, what about checking > the old location on a CRC fail, and if the old CRC passes, don't > automatically use it but print a message telling the user that they > probably nee

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

Dear Timur Tabi, In message <500098f6.8050...@freescale.com> you wrote: > > I honestly don't see what's wrong with checking the CRC in the old > location, and using it if it's valid. Like I said, we already You are interpreting something which can be random data. > if (e.version == 0) >

Re: [U-Boot] [PATCH] fsl: board EEPROM has the CRC in the wrong location

On 07/13/2012 06:01 PM, Wolfgang Denk wrote: > Dear Timur Tabi, > > In message <500098f6.8050...@freescale.com> you wrote: >> >> I honestly don't see what's wrong with checking the CRC in the old >> location, and using it if it's valid. Like I said, we already > > You are interpreting something

Re: [U-Boot] uboot for zyxel nsa320

Hi, On Fri, Jul 13, 2012 at 12:43:13PM -0500, kqt4a...@gmail.com wrote: > I have a new Zyxel NSA320. It is unmodified. At the uboot prompt I > printenv and save all environment variables. Next I pulled code from > https://github.com/psch2/uboot-nsa320, compiled and used kwboot to > load new uboot.

Re: [U-Boot] [PATCH 1/2 v2] SDHC/MMC: fix the wrong infomation after change SD card

Dear Andy Fleming, > On Wed, Jul 11, 2012 at 4:29 AM, Huang Changming-R66093 > > wrote: > > Hi, Andy, > > There is not any feedback for very long time, > > Could it be applied to the u-boot? > > I'm afraid I have to reject this patch. We need to find a better > solution to the two problems: >

Re: [U-Boot] FDT driver initialization function declaration

Hi Michal, On Tue, Jul 10, 2012 at 3:49 PM, Michal Simek wrote: > On 07/10/2012 03:18 PM, Simon Glass wrote: >> >> Hi Michal, >> >> >> On Tue, Jul 10, 2012 at 12:23 PM, Michal Simek > > wrote: >> >> Hi Simon, Wolfgang and others, >> >> just want to open new topic