public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Changwoo Ryu <cwryu@debian.org>
To: linux-mtd@lists.infradead.org
Subject: Re: Am29LV065D woes -- ZFMicro MachZ help?
Date: 14 Aug 2001 12:10:38 +0900	[thread overview]
Message-ID: <87u1zbgwup.fsf@hades.idis.co.kr> (raw)
In-Reply-To: Luke's message of "Mon, 13 Aug 2001 17:35:49 -0700 (PDT)"

Luke <luke_epsilon@yahoo.com> writes:

> I appreciate the help so far - I have been trying to read what I can about
> my system.
> 
> --- Vipin Malik <vipin@embeddedlinuxworks.com> wrote:
> > 
> > That's entirely dependent on your hardware- as to which address range it
> > decodes the chip select (CS) line going to the flash chip.
> ...
> > If it is going to your (embedded PC on a chip) processor (if that's the 
> > case- like in an AMD SC520 or Intel 386EX) then either look in the bios 
> > settings where the PAR (programmable address range) chip select
> > registers are being set or you may have to program them yourself- say in
> > the physmap.c file before you do the probe for the flash chip.
> 
> The flash is going directly to the processor.  In this case it is a
> ZFMicro MachZ chip (Cyrix 486 dx4) - the documentation on the physical
> address space is very confusing to me.  Has anyone tried using MTD for
> this chip?
> 
> In the bios, one can configure mem_cs_0 (0-3 actually) memory page size,
> memory base, and memory offset.  I have 2 Am29LV065D 8M flash chips - one
> linked to mem_cs_0 and the other to mem_cs_1.  The confusing part comes
> with the Rom Extension Linux Loader that comes with the platform.  Looking
> at the assemby for this loader it seems as though it uses the default
> settings set in bios for mem_cs_0 and then the loader changes these values
> to address an initrd, and kernel address space.  

You don't need the register values (set by the linux loader) after
linux/initrd loading.  Then the regsiter values should be changed
before probing the flash.

You can read the H/W manual "ZF-Logic" section about setting the
values.

-- 
Changwoo Ryu

      parent reply	other threads:[~2001-08-14  3:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-11  4:34 Am29LV065D woes??? Luke
2001-08-12 14:06 ` Vipin Malik
2001-08-14  0:35   ` Am29LV065D woes -- ZFMicro MachZ help? Luke
2001-08-14  2:30     ` Vipin Malik
2001-08-14  4:08       ` Luke
2001-08-23  6:08         ` ZFMicro MachZ success with the Am29LV065D Luke
2001-08-23 10:33           ` Vipin Malik
2001-08-23 14:54             ` Luke
2001-08-23 15:00               ` Vipin Malik
2001-08-23 19:41                 ` ZFMicro MachZ modification of physmap.c Luke
2001-08-23 21:36                   ` Vipin Malik
2001-08-14  3:10     ` Changwoo Ryu [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=87u1zbgwup.fsf@hades.idis.co.kr \
    --to=cwryu@debian.org \
    --cc=linux-mtd@lists.infradead.org \
    /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