From: Dan Brown <dan_brown@ieee.org>
To: "Joseph M Dupre (AVAB Inc.)" <dupre@avab.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: DOCBoot: "diskonchip" driver depreciated?
Date: Wed, 28 Sep 2005 10:18:19 -0400 [thread overview]
Message-ID: <433AA62B.20102@ieee.org> (raw)
In-Reply-To: <4339830F.14600.1D083FD@localhost>
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
next prev parent reply other threads:[~2005-09-28 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 0:36 DOCBoot: "diskonchip" driver depreciated? Joseph M Dupre (AVAB Inc.)
2005-09-28 14:18 ` Dan Brown [this message]
2005-09-28 19:19 ` Joseph M Dupre (AVAB Inc.)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=433AA62B.20102@ieee.org \
--to=dan_brown@ieee.org \
--cc=dupre@avab.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox