* DOCBoot: "diskonchip" driver depreciated?
@ 2005-09-28 0:36 Joseph M Dupre (AVAB Inc.)
2005-09-28 14:18 ` Dan Brown
0 siblings, 1 reply; 3+ messages in thread
From: Joseph M Dupre (AVAB Inc.) @ 2005-09-28 0:36 UTC (permalink / raw)
To: linux-mtd
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: DOCBoot: "diskonchip" driver depreciated?
2005-09-28 0:36 DOCBoot: "diskonchip" driver depreciated? Joseph M Dupre (AVAB Inc.)
@ 2005-09-28 14:18 ` Dan Brown
2005-09-28 19:19 ` Joseph M Dupre (AVAB Inc.)
0 siblings, 1 reply; 3+ messages in thread
From: Dan Brown @ 2005-09-28 14:18 UTC (permalink / raw)
To: Joseph M Dupre (AVAB Inc.); +Cc: linux-mtd
Joseph M Dupre (AVAB Inc.) wrote:
> 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).
> 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.
> Should this generic NAND driver work in conjunction with the DOCboot
> code and a "newer" DOC 2000 device?
Yes.
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: DOCBoot: "diskonchip" driver depreciated?
2005-09-28 14:18 ` Dan Brown
@ 2005-09-28 19:19 ` Joseph M Dupre (AVAB Inc.)
0 siblings, 0 replies; 3+ messages in thread
From: Joseph M Dupre (AVAB Inc.) @ 2005-09-28 19:19 UTC (permalink / raw)
To: linux-mtd
On 28 Sep 2005 at 10:18, Dan Brown wrote:
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-09-28 19:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-28 0:36 DOCBoot: "diskonchip" driver depreciated? Joseph M Dupre (AVAB Inc.)
2005-09-28 14:18 ` Dan Brown
2005-09-28 19:19 ` Joseph M Dupre (AVAB Inc.)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox