From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Schweigstill Date: Sat, 27 Jan 2007 18:04:17 +0100 Subject: [U-Boot-Users] Atmel DataFlash hooks. In-Reply-To: <20070127163626.3935F352B87@atlas.denx.de> References: <20070127163626.3935F352B87@atlas.denx.de> Message-ID: <45BB8611.5070900@schweigstill.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello! Wolfgang Denk schrieb: > ... and to me this sounds is if it would fit better in the set of > flash related commands (protect etc.) than any other existing > interface. The flash related commands could work on an extension of the block device layer. IDE/ATA drives also seem to have a means for provision of drive geometry data to the file system driver or application (e.g. fdisk under DOS/Windows/Linux). (Yes, I am just joking... :-) ) There is something what I really don't like about U-Boot's current Dataflash implementation: after copying data to Dataflash using the "cp.b" command the source data has been corrupted; it has been swapped with the old contents of the Dataflash. The reason for this behaviour can be found in the AT91F_SpiWrite() function (at45.c) which programs the PDC to use the SPI transmit buffer address also as receive address. Has anybody found out if it is possible to ignore the read data? With best regards Andreas Scheigstill -- Dipl.-Phys. Andreas Schweigstill Schweigstill IT | Embedded Systems Schauenburgerstra?e 116, D-24118 Kiel, Germany Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436 Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/