public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jan Rovins <Jan.Rovins@radisys.com>
Cc: linux-mtd@lists.infradead.org, Steve Ferri <steve.ferri@radisys.com>
Subject: Re: MTD on a Motorola MPCN765 ? (32 bit linux and 64 bit flash)
Date: Tue, 22 May 2001 02:16:20 +0100	[thread overview]
Message-ID: <31007.990494180@redhat.com> (raw)
In-Reply-To: <F1BD619B2A58D41197990050DA2C08E40258E3@SLINK12>

Jan.Rovins@radisys.com said:
> But the recommendations I was given assume I am running Linux in 64
> bit mode,  which I am not. My longs are still 32 bit,
>  and I can now read the flash through MTD, but can't yet form commands
> to write and erase the upper two 16 bit flash devices. (To access
> those upper two devices I would have to add 0x04 to the unlock1,&2
> addresses) When using interleaved chips, are the commands always given
> to the whole bank simultaneously? Could I fake a 64 bit write by doing
> two 32 bit writes? Basically I will be reading & writing flash as a 32
> bit machine would, but faking up 64 bit commands.  Would this work?

That should work.

But if you're doing that, why not just pretend that you have two entirely 
separate chip mappings, with two entirely independent pairs of 16-bit chips 
in them? Then you don't need to muck about with the 64-bit flash command 
stuff. You just need to be aware that your bootloader will probably then be 
split between the first erase block of each device. But that's easy enough 
to deal with.



--
dwmw2

  reply	other threads:[~2001-05-22  1:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22  0:57 MTD on a Motorola MPCN765 ? (32 bit linux and 64 bit flash) Jan Rovins
2001-05-22  1:16 ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-22 19:59 Jan Rovins
2001-05-23 10:18 ` 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=31007.990494180@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=Jan.Rovins@radisys.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=steve.ferri@radisys.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