On Monday 18 May 2009, Nicolas Pitre wrote: > > The following are some notes I put together about the "nand" > > commands based on reading the source code. > > > > I plan to turn them into documentation sometime later, maybe by this > > time next week. I've seen no documentation on the NAND commands; that > > seems like a significant omission. > > > > Meanwhile I thought I'd send them around for comments and corrections. > > Looks all fine to me. This matches my own understanding of the code.
Thanks for the feedback. > > The "==>" comments are things which seem like they deserve some action > > other than documenting the current status. One example is removing (or > > at least disabling) the "nand copy" command until it gets implemented. > > Implementing it in a generic way would be quite slow if the data has to > make the round trip to the host and back to the target over the JTAG > link. Ideally each controller driver would need to implement its own > copy method which would involve uploading some code on the target in > order to perform the copy directly. > > Still I don't see this as being really useful, otherwise someone would > have implemented it by now. So disabling it is probably the best option > for the moment. OK, I'll send a patch doing that, soonish. I also noticed that two commands (erase, check_bad) are unusual in that they require *block* numbers as parameters, rather than the offsets used everywhere else in OpenOCD (and in U-Boot, and the Linux-MTD utilities). Comments on changing that to become more consistent, and holding off on documenting/committing-to the current interface until this issue is resolved? - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
