From: "Thomas Gleixner" <tglx@linutronix.de>
To: "Carlos, John J USAATC" <john.carlos@atc.army.mil>,
linux-mtd@lists.infradead.org
Subject: Re: Generic nand and DOC
Date: Wed, 9 Jun 2004 12:00:50 +0200 [thread overview]
Message-ID: <200406091200.50583.tglx@linutronix.de> (raw)
In-Reply-To: <EFF9A3506F74924AB5CC77BDC66E79351812B3@atcml01.atc.army.mil>
On Tuesday 08 June 2004 16:22, Carlos, John J USAATC wrote:
> Hi All,
>
> I have been trying to get my DOC Mil plus to work properly. The code in
> the devices dir that is M-sys specific seems to works for the chip but I
> can't use nandwrite on the chip. Am I to assume from the lists that the
> goal is to stop using the code in the devices directory and use the generic
> nand/inftl stuff to work for all devices?
The plan is to have a doc driver in drivers/mtd/nand which uses the generic
nand code and overrides the doc specific functions. On top of this (I)NFTL
can be used or JFFS2/YAFFS without the (I)NFTL layer.
Dan Brown is actually working on it.
> The code for DoC_IdentChip is
> very specific, is it the plan that nand_scan will replace the later?
No, this will be part of the doc driver in drivers/mtd/nand
--
Thomas
_____________________________________________________________________
From slash dot org
"When customers are visiting, engineers are not allowed to wear ties.
That way the customer can tell who is the engineer and who is the
salesman (and therefore whom to believe.). Ties cut off blood flow
to the brain, making it easier for the salesmen to do their jobs."
_____________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2004-06-09 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 14:22 Generic nand and DOC Carlos, John J USAATC
2004-06-09 10:00 ` Thomas Gleixner [this message]
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=200406091200.50583.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=john.carlos@atc.army.mil \
--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