All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stéphane Laroche" <stephane.laroche@colubris.com>
To: mtd@infradead.org
Subject: CFI problems with 32bit bus and 4 devices
Date: Wed, 10 Jan 2001 14:15:16 -0500	[thread overview]
Message-ID: <3A5CB4C3.41FC20D1@colubris.com> (raw)

Hi,

I've just updated to the latest CVS and my CFI AMD chips are not
accessible anymore.

I lokked briefly into it and saw that the cfi->interleave and
cfi->device_type were removed from offset calculations when accessing
the devices.

So, for my setup, which has 4 x16 devices on a 32 bit bus (AMDs),  the
CFI query structure is located at offsets 0x80, 0x88, 0x90, etc.

cfi_read_query()  uses only the buswidth to calculate the offset, which
is not general enough (it used to be like that before I played with the
code a bit last summer).  It's obviously wrong in my case ( 0x10 << 2 !=
0x80 ).

Rewriting cfi_read_query like this made the CFI query structure
readable:

static inline __u8 cfi_read_query(struct map_info *map, __u32 base,
__u32 addr)
{
    struct cfi_private *cfi = map->fldrv_priv;
    addr *= cfi->interleave * cfi->device_type;  /* instead of addr <<
(buswidth / 2) */
    if (cfi_buswidth_is_1()) {
        return map->read8(map, base + addr);
    } else if (cfi_buswidth_is_2()) {
        return cfi16_to_cpu(map->read16(map, base + addr));
    } else if (cfi_buswidth_is_4()) {
        return cfi32_to_cpu(map->read32(map, base + addr));
    } else {
        return 0;
    }
}

With this change, the chips are now properly recognized.  But I can't
still not use them (reads are wrong), so I think I have to look at
cfi_cmdset_002.c to bring back the use of cfi->interleave in some
calculations...

Any comments?  Is it possible that I'm the only one using that kind of
geometry?

-Stephane



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~2001-01-10 19:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 19:15 Stéphane Laroche [this message]
2001-01-10 20:13 ` CFI problems with 32bit bus and 4 devices Nicolas Pitre
2001-01-10 20:37 ` David Woodhouse
2001-01-10 21:06   ` Stéphane Laroche
2001-01-10 22:35     ` David Woodhouse
2001-01-10 21:37   ` Nicolas Pitre
2001-01-10 22:22     ` David Woodhouse
2001-01-10 22:39       ` Stéphane Laroche
2001-01-10 23:06         ` David Woodhouse
2001-01-11  0:21       ` Nicolas Pitre
2001-01-10 23:34 ` Alice Hennessy
2001-01-10 23:55   ` Alice Hennessy
  -- strict thread matches above, loose matches on Subject: below --
2001-01-10 22:45 Michael Thompson

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=3A5CB4C3.41FC20D1@colubris.com \
    --to=stephane.laroche@colubris.com \
    --cc=mtd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.