u-boot.git/drivers/mtd/onenand, branch v1.3.4Unnamed repository; edit this file 'description' to name the repository.http://cgit.235523.xyz/u-boot.git/atom/drivers/mtd/onenand?h=v1.3.42008-08-11T20:07:46ZOneNAND: Remove unused parameters to onenand_verify_page2008-08-11T20:07:46ZSteve Sakomansteve@sakoman.com2008-08-11T18:26:16Zurn:sha1:4d57b0fb2927d4f50d834884b4ec4a7ca01708b0
The block and page parameters of onenand_verify_page() are not used. This causes a compiler error when CONFIG_MTD_ONENAND_VERIFY_WRITE is enabled.
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
NAND: Rename DEBUG to MTDDEBUG to avoid namespace pollution.2008-07-09T22:24:47ZScott Woodscottwood@freescale.com2008-06-20T17:38:57Zurn:sha1:3167c5386ea1c98b638be5d8763ef6d5938ef1bd
This is particularly problematic now that non-NAND-specific code is
including <nand.h>, and thus all debugging code is being compiled
regardless of whether it was requested, as reported by Scott McNutt
<smcnutt@psyent.com>.
Signed-off-by: Scott Wood <scottwood@freescale.com>
onenand: rename 16 bit memory copy into memcpy_16() to avoid conflicts2008-05-01T19:30:16ZWolfgang Denkwd@denx.de2008-05-01T19:30:16Zurn:sha1:d2c6fbec4397c936b18cd42482b6973cd6781bdf
Onenand needs a version of memcpy() which performs 16 bit accesses
only; make sure the name does not conflict with the standard
function.
Signed-off-by: Wolfgang Denk <wd@denx.de>
Fix OneNAND read2008-04-14T06:11:16ZKyungmin Parkkmpark@infradead.org2008-03-31T01:40:36Zurn:sha1:77e475cc0ed1832160017d364be32a0be9ff02a9
It should access with 16-bit instead of 8-bit
Now it uses the generic memcpy with 8-bit access. It means it reads wrong data from OneNAND.
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
Add Flex-OneNAND booting support2008-03-25T23:05:32ZKyungmin Parkkmpark@infradead.org2008-03-16T23:54:06Zurn:sha1:1bb707c39a0833e91d9f797dd862aaaaf4af264d
Flex-OneNAND is a monolithic integrated circuit with a NAND Flash array
using a NOR Flash interface. This on-chip integration enables system designers
to reduce external system logic and use high-density NAND Flash
in applications that would otherwise have to use more NOR components.
Flex-OneNAND enables users to configure to partition it into SLC and MLC areas
in more flexible way. While MLC area of Flex-OneNAND can be used to store data
that require low reliability and high density, SLC area of Flex-OneNAND
to store data that need high reliability and high performance. Flex-OneNAND
can let users take advantage of storing these two different types of data
into one chip, which is making Flex-OneNAND more cost- and space-effective.
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
OneNAND: Separate U-Boot dependent code from OneNAND2008-01-16T13:10:15ZKyungmin Parkkmpark@infradead.org2008-01-14T23:59:44Zurn:sha1:6cb2239ae76faee64434286c4f8fc71374702dd2
OneNAND: Separate U-Boot dependent code from OneNAND
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
drivers/mtd : move mtd drivers to drivers/mtd2007-11-25T22:28:52ZJean-Christophe PLAGNIOL-VILLARDplagnioj@jcrosoft.com2007-11-24T20:26:56Zurn:sha1:59829cc189378c142c13d2aa8d9a897d8bef3961
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>