On Fri, May 30, 2008 at 08:00:32PM +0200, Wolfgang Grandegger wrote: [...] > Fix that, but I can still not access the device properly. I'm a bit > puzzled because it uses a different algorithm to access the device. > While my and the Linux fsl_upm driver uses NAND_ALE, NAND_CLE and > friends to manage the access via hwcontrol callback, the fsl_upm driver > of U-Boot uses the cmdfunc callback doing different things.
I wonder if your NAND chip is a large page one? Because currently fsl_upm_nand hardcodes OOB stuff (bad thing, but with old mtd subsystem I didn't find better way ;-). As for u-boot and linux doing different things... with this patch u-boot and linux are identical: http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-nand-flash.git;a=commitdiff;h=dffa9a8b31b2c21fd3a72ba1f58dd04911b95b6f This is in U-Boot's mtd-2.6.22.1 branch though. :-/ Your approach with hwctl seem to be more universal (for old mtd subsystem), since it doesn't duplicate MTD cmdfunc, thus should work for all NAND chips... Could you prepare a patch that replacing fsl_upm_nand.c's current logic with yours (that should work for your NAND chip), and I'll test it on MPC8360E-RDK? -- Anton Vorontsov email: [EMAIL PROTECTED] irc://irc.freenode.net/bd2 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
