public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, Nicolas Pouillon <nipo@ssji.net>
Subject: Re: [PATCH]Probing at 0x0
Date: Mon, 11 Oct 2004 15:12:38 +0200	[thread overview]
Message-ID: <1097500358.21607.37.camel@thomas> (raw)
In-Reply-To: <1097497518.318.285.camel@hades.cambridge.redhat.com>

On Mon, 2004-10-11 at 14:25, David Woodhouse wrote:
> > I think you are right. It did handle both of them in 8-bit mode.
> > I believe that if we are going to use 32 MB devices in 8-bit mode, we must 
> > deal with the interleaving crap, right?
> 
> I think so, yes.

You mean 16-bit mode ? Then you need the interleave hack.

http://www.m-systems.com/files/documentation/doc/Mobile_Plus_32_64MB_DS_Rev1.7.pdf

A 13-bit wide address bus enables access to the DiskOnChip 8KB memory
window (as shown in Section 6.2). In 32/64MB capacities, the 16-bit data
bus permits full 16-bit wide access to the flash, due to an internal,
dual-bank, interleaved architecture. With both internal and external
16-bit access, DiskOnChip Millennium Plus 32/64MB provides unrivaled
performance. In 16MB capacities, an 8-bit data bus permits 8-bit wide
internal access to the flash but 16-bit external access to the host.

That means, that the 2 chips are accessed in parallel. So each word you
write is split into two bytes. The even goes into chip 0 and the odd
into chip 1.

This increases pagesize to 1024 byte and the bad block table must be
aware of that too.

The only thing I can not figure out, is whether you must duplicate the
commands, address bytes. 
I assume yes. So we need a seperate command function which does 
writeb16 (command | (command << 8)); 
and shifts the address 1 time right and writes the address bytes the
same way as the command.

The remaining stuff should work unchanged including ecc, but we need a
seperate oobinfo though.

tglx

      reply	other threads:[~2004-10-11 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 19:50 [PATCH]Probing at 0x0 Nicolas Pouillon
2004-10-04 21:53 ` Thomas Gleixner
2004-10-05  8:59 ` Kalev Lember
2004-10-06 19:34   ` Nicolas Pouillon
2004-10-08 18:28     ` Kalev Lember
2004-10-08 19:05       ` Thomas Gleixner
2004-10-11  9:00         ` Kalev Lember
2004-10-11 12:41           ` Nicolas Pouillon
2004-10-08 19:15       ` David Woodhouse
2004-10-11 12:23         ` Kalev Lember
2004-10-11 12:25           ` David Woodhouse
2004-10-11 13:12             ` 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=1097500358.21607.37.camel@thomas \
    --to=tglx@linutronix.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nipo@ssji.net \
    /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