Skip to contentSkip to conversation

DOCBoot: "diskonchip" driver depreciated?

DISCUSSION Joseph M Dupre (AVAB Inc.) 2 participants 3 messages Sep 28, 2005 Memory technology devices (MTD)

lore
Share & tools
lore
#0 lore raw

The DOCboot README refers to the kernel's diskonchip driver.

I am currently working with an un-patched 2.6.11.12 kernel. It it there are drivers for Disk-On-Chip 2000 and various Millennium devices. These are all marked depreciated. Menuconfig help suggests to use the generic NAND device driver instead on the Disk-On-Chip driver.

Should this generic NAND driver work in conjunction with the DOCboot code and a "newer" DOC 2000 device?

I'm not tied to this kernel by any means, it is just what was current when I started. But I _do_ need to get booting from the DOC 2000 device and have not yet figured out how to do this. I am using the DOC MD2202 series DIP on an i486 platform.

Thanks,

- Joe

#1 lore raw
Quoted 1 line · Joseph M Dupre (AVAB Inc.)

The DOCboot README refers to the kernel's diskonchip driver.

There are more than one. By referring in the README to the "diskonchip" driver, I mean specifically the driver that is *called* "diskonchip". (The parenthesized hint in step one about doing "modprobe diskonchip" is intended to make this clear).

Quoted 1 line

I am currently working with an un-patched 2.6.11.12 kernel. It it there are drivers for Disk-On-Chip 2000 and various Millennium devices. These are all marked depreciated. Menuconfig help suggests to use the generic NAND device driver instead on the Disk-On-Chip driver.

I'll have to check the menuconfig wording, but what it should say is to use the new DOC driver that works *with* the generic NAND device layer, rather than the old DOC driver(s) that doesn't. If you enable NAND support, you'll find this new driver.

Quoted 1 line

Should this generic NAND driver work in conjunction with the DOCboot code and a "newer" DOC 2000 device?

Yes.

Quoted 1 line

I'm not tied to this kernel by any means, it is just what was current when I started. But I _do_ need to get booting from the DOC 2000 device and have not yet figured out how to do this. I am using the DOC MD2202 series DIP on an i486 platform.

Should work fine; let me know if you need any more help.

-Dan

#2 lore raw
Quoted 4 lines · Dan Brown

I'll have to check the menuconfig wording, but what it should say is to use the new DOC driver that works *with* the generic NAND device layer, rather than the old DOC driver(s) that doesn't. If you enable NAND support, you'll find this new driver.

Ah ha. I had CONFIG_EXPERIMENTAL unset which prevented the new driver from showing up under NAND Flash Device Drivers. I will carry on...

- Joe