linux-mips
[Top] [All Lists]

Re: Common Flash Memory Interface

To: martin.nichols@oxinst.co.uk
Subject: Re: Common Flash Memory Interface
From: Wolfgang Denk <wd@denx.de>
Date: Fri, 22 Apr 2005 17:02:52 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: Your message of "Fri, 22 Apr 2005 13:48:02 BST." <DEF431FFDB15C1488464F0E57D5506642AA6B7@MEDNT02>
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
In message <DEF431FFDB15C1488464F0E57D5506642AA6B7@MEDNT02> you wrote:
> 
> I've arranged for a pair of Spansion S29GL256N 256Mbit flash roms to be
> connected to the
> Au1100 static bus. These devices are each 16bits wide and are connected to
> upper and lower
> halves of the 32 bit static bus at an address such that the boot code can
> reside in them.
> After boot, we want to use the remainder of the devices as flash disk using
> one of the wear
> leveling file systems. Each flash chip implements the Common Flash Memory
> Interface standard,

OK.

> but as they are arranged as 32 bits wide the devices are effectively
> interleaved.

I'd rather say thay are accesses in parallel.

> Can Linux support this arrangement?

Yes, of course. Such a configurationir more or less standard. The MTD
drivers will work just fine.

> Finally, this email is not confidential and is for all Linux-Mips
> addressees.

Then why do you attach such a silly disclaimer?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"...one of the main causes of the fall of the Roman Empire was  that,
lacking  zero,  they had no way to indicate successful termination of
their C programs."                                     - Robert Firth

<Prev in Thread] Current Thread [Next in Thread>