public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Thomas W. Nelson" <twn@dot4.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD support on Motorola Hawk ASIC-based boards
Date: Wed, 07 Jul 2004 20:36:52 +0100	[thread overview]
Message-ID: <1089229011.4840.2.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <40EC43ED.6090401@dot4.com>

On Wed, 2004-07-07 at 14:41 -0400, Thomas W. Nelson wrote:
> Just as a sanity check (since I have so little left :-), will these 
> modifications also correctly deal with the 32-bit only write limitation 
> during probes?  Getting the chips into query mode appears to be the real 
> challenge here; I haven't been able to perform the correct incantation 
> to get them to respond in any way, CFI or JEDEC. 

You ought to be able to fake 64-bit buswidth for the case you described.
Play with it in GDB for a while, poking commands at various addresses
and looking for the idents.

> I'd also like to inject some personal observations about the more 
> complex flash geometries that are appearing.  On higher-end boards, such 
> as those from Dy4, Pentek, etc., these multibank interleaved 
> configurations are becoming very common as their customers want high 
> performance flash access for their XIP or flash filesystem-based 
> application environments. 

Whereas others just use Intel chips configured for burst reads... 

I suspect that the best way forward might be to turn the cfi_word
typedef into a structure with an array of unsigned longs. In the common
case there'll be only one of them, but for pathological cases there can
be many.

-- 
dwmw2

  reply	other threads:[~2004-07-07 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 20:35 MTD support on Motorola Hawk ASIC-based boards Thomas W. Nelson
2004-07-07 10:32 ` David Woodhouse
2004-07-07 18:41   ` Thomas W. Nelson
2004-07-07 19:36     ` David Woodhouse [this message]
2004-07-10 21:22 ` Call for testing: Wide flash bank support David Woodhouse

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=1089229011.4840.2.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=twn@dot4.com \
    /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