Hi Tom! I don't seem to find proper order using below patch sets. tiistai, 5. marraskuuta 2013 10.35.25 UTC+2 matti kaasinen kirjoitti: > > Hi Tom, > I'm terribly sorry annoying you for once more time with this issue. I have > tried to figure out what patch sets you are suggesting below. > 2013/11/2 <[email protected]> > >> I think that at least part of the answer is that you need to enable >> CONFIG_SYS_NAND_ONFI_**DETECTION. You may also need to apply some of >> Pekon's patches from http://patchwork.ozlabs.org/** >> project/uboot/list/?submitter=**17320&state=*<http://patchwork.ozlabs.org/project/uboot/list/?submitter=17320&state=*>(there >> are 3 series there as of this writing, 2 v2's and a v8, you should >> apply all 3 series, and in the right order, saving each series to an mbox, >> and using git am -3 / git am --abort when they fail should help get the >> right order sorted out quickly). >> > > So, to make it clear as crystal even for me, let's list what I found > matching with your message: > 2013-08-14 > [U-Boot,v2,1/4] mtd: nand: omap: enable BCH ECC scheme using ELM for > generic platform > [U-Boot,v2,2/4] mtd: nand: omap: optimize chip->ecc.hwctl() for H/W ECC > schemes > [U-Boot,v2,3/4] mtd: nand: omap: optimize chip->ecc.calculate() for H/W > ECC schemes > [U-Boot,v2,4/4] mtd: nand: omap: optimized chip->ecc.correct() for H/W ECC > schemes > > 2013-09-06 > 2013-09-10
> [U-Boot,v2,1/3] am33xx: elm: add support for BCH16_ECC - ELM driver updates > [U-Boot,v2,2/3] mtd: nand: omap: add support for BCH16_ECC - NAND driver > updates > [U-Boot,v2,3/3] am335x: update README for BCH16 > > 2013-09-30 > [U-Boot,v2,1/4] mtd: nand: add NAND_BUSWIDTH_AUTO to autodetect bus width > [U-Boot,v2,2/4] am33xx: add CONFIG_SYS_NAND_DEVICE_WIDTH to determine NAND > device bus-width > [U-Boot,v2,3/4] am335x: fix GPMC config for NAND and NOR SPL boot > [U-Boot,v2,4/4] am33xx: add support for beaglebone x16 NAND cape > > 2013-10-10 > [U-Boot,v8,1/5] mtd: nand: omap: enable BCH ECC scheme using ELM for > generic platform > [U-Boot,v8,2/5] mtd: nand: omap: optimize chip->ecc.hwctl() for H/W ECC > schemes > [U-Boot,v8,3/5] mtd: nand: omap: optimize chip->ecc.calculate() for H/W > ECC schemes > [U-Boot,v8,4/5] mtd: nand: omap: optimized chip->ecc.correct() for H/W ECC > schemes > [U-Boot,v8,5/5] board/ti/am335x/README: update for NAND boot > > It seems to me that 2013-08-14 and 2013-10-10 are providing (more or less) > same patch set > => My choice is 2013-10-10 > 2013-09-06 and 2013-09-30 seem different to me > => these are the 2v2's your mentioned above > > My guess for patching order would be: > 1) 2013-10-10 > 2) 2013-09-06 > 2) 2013-09-10 > 3) 2013-09-30 > Patch sets 1) 2013-10-10 and 3) 2013-09-30 work fine if 1) is executed first. However, 2) 2013-09-10 fails in every position. In particular: "[U-Boot,v2,2/3] mtd: nand: omap: add support for BCH16_ECC - NAND driver updates" fails in several places. Firs one takes place when appending arch/arm/include/asm/arch-am33xx/omap_gpmc.h. It tries to make following replacement: - OMAP_ECC_BCH8_CODE_HW+ OMAP_ECC_BCH8_CODE_HW, even though that comma was already provided by: "[U-Boot,v8,1/5] mtd: nand: omap: enable BCH ECC scheme using ELM for generic platform" while creating the stuct including that line. So, somehow it seems that some more patches are required in order to get these patches run. Best regards, Matti -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
