Re: MTD map drivers (FSL UPM NAND)

[Scott Wood <scottwood@freescale.com>]

Alemao wrote:
> Here is an output from someone using it:
> 
> -----
> 
> 070500 U-Boot 1.1.2 (May 30 2007 - 20:20:09)
> 
> Motorola PowerPC
> Board: GDA Technologies CSC-PP MPC8560 [PowerQUICC III]
> CPU: 660 MHz
> CCB: 330 MHz
> DDR: 165 MHz
> 
> Creating 7 MTD partitions on "CSC flash":
> 0x00f80000-0x01000000 : "uboot"
> 0x00d00000-0x00e00000 : "kernel0"
> 0x00e00000-0x00f00000 : "kernel1"
> 0x00700000-0x00d00000 : "app"
> 0x00000000-0x00380000 : "root0"
> 0x00380000-0x00700000 : "root1"
> 0x00f00000-0x00f80000 : "env"
> 
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca
> Scanning device for bad blocks
> Bad eraseblock 1780 at 0x0de80000
> Creating 1 MTD partitions on "NAND 256MiB 3,3V 16-bit":
> 0x00000000-0x10000000 : "NAND Partition"
> 
> -----
> 
> Thats exactly what I want to do. If you say not to use physmap with
> NAND, how he is doing this? Through the device tree source?

I see nothing in that output to suggest that physmap is being used for NAND.

NAND is not directly mapped like NOR is; you cannot just give an address 
range with no knowledge of the controller and expect it to work.

Note that if you look in drivers/mtd/maps/physmap.c, the supported probe 
types are CFI, JEDEC, and ROM.

-Scott