From: "Thomas Gleixner" <tglx@linutronix.de>
To: linux-mtd@lists.infradead.org
Subject: Re: FW: DOC Mil Plus 32 question erase size erase shift????
Date: Tue, 22 Jun 2004 15:01:29 +0200 [thread overview]
Message-ID: <200406221501.30299.tglx@linutronix.de> (raw)
In-Reply-To: <EFF9A3506F74924AB5CC77BDC66E79351812CB@atcml01.atc.army.mil>
On Tuesday 22 June 2004 14:49, Carlos, John J USAATC wrote:
> What should the buffer size be for an erase block in memory. How is that
> value tied to the chip geometry???
Would you please be so kind and answer the questions, if we should be able to
help you.
1. Is the device running in x16 mode?
If yes, then we have to fix this first, as it is not supported by nand_base.c
at the moment. nand_scan() has to be made aware of this.
2. What's the output of the chip detection routine including nand_scan() ?
3. What did you change in nand_bbt.c ?
4. What's the bbt structure you pass to nand_scan_bbt ?
5. Can you send me your driver code including he modifications to nand_base.c
and nand_bbt.c, so I can have a look ?
--
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-22 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 12:49 FW: DOC Mil Plus 32 question erase size erase shift???? Carlos, John J USAATC
2004-06-22 13:01 ` 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=200406221501.30299.tglx@linutronix.de \
--to=tglx@linutronix.de \
--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