public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: Shawn Jin <shawnxtech@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: 64 bit bus access on a customed MPC8245 board
Date: 28 Jan 2004 08:48:18 -0700	[thread overview]
Message-ID: <m3u12g8471.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <20040128034734.77883.qmail@web20725.mail.yahoo.com>

Shawn Jin <shawnxtech@yahoo.com> writes:

> Hi,
> 
> I'm working on a customed MPC8245 board with flash
> chip Am29LV320 and trying to enable MTD driver
> support.

The MPC8245 is an embedded ppc processor.
?? 

I looked and I can't find documentation for that chip.
Is it an atmel one?

Chips with similar part numbers are 8 bit flash.  Atmel
does make a few 16bit flash parts.  And I don't know
if Atmel does cfi?  You may need jedec_probe.
 
> The configuration is 32 bit bus width in each chip
> with 2 chips interleaved. So CONFIG_MTD_CFI_B8 and
> CONFIG_MTD_CFI_I2 are defined.

Ok so you have configured it for 2 8bit chips that are
interleaved to form a 16bit path.

> MPC8245 requires the following memory mapping:
> bank 0: 0xFF800000 - 0xFFFFFFFF
> bank 1: 0xFF000000 - 0xFF7FFFFF
> 
> I noticed that FPU must be enabled for 64-bit
> read/write from/to flash.

But that is not even interesting if you are only 16bits wide.

> I use read64() and write64() functions in the
> attachment, which are copied from sbc8240.c. However
> no chip can be found. Any suggestions? Thank you very
> much.

I suggest you focus on read16()/write16().

Eric

  reply	other threads:[~2004-01-28 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28  3:47 64 bit bus access on a customed MPC8245 board Shawn Jin
2004-01-28 15:48 ` Eric W. Biederman [this message]
2004-01-28 15:59   ` David Woodhouse
2004-01-28 17:58     ` Shawn Jin
2004-01-28 18:39     ` Shawn Jin

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=m3u12g8471.fsf@maxwell.lnxi.com \
    --to=ebiederman@lnxi.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shawnxtech@yahoo.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