From: "Stephen Mose Aaskov" <sma@2m.dk>
To: <linux-mips@linux-mips.org>
Subject: MTD drivers and byte/word mode
Date: Mon, 2 Sep 2002 19:17:23 +0200 [thread overview]
Message-ID: <00c301c252a4$9a802a00$016d100a@2m.dk> (raw)
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
I´m working on a 2.4 port to a design with FLASH devices connected through a 16 bit bus.
The FLASH (AMD) is set to word mode.
I have quite a hard time trying to understand the FLASH geometry settings and calculations of the addresses used for CFI query etc.
It looks as if the adresses calculated by cfi_build_cmd_addr() is the double of what my FLASH chips are using.
eg. the CFI query is written to 0xaa where my chip in word mode expects the query command to be written to 0x55
Is there any direct support in the MTD driver for differentiating between word/byte mode ?
The buswidth is set to 16 bits (=2), and interleave to 1 (I have two chips sharing the bus, not in parallel)
Stephen Mose Aaskov
Engineer, R&D
2M ELECTRONIC A/S
Malervej 10, DK-2630 Taastrup
Denmark
Tel: +45 43300555 Fax: +45 43300567
[-- Attachment #2: Type: text/html, Size: 1579 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Stephen Mose Aaskov" <sma@2m.dk>
To: linux-mips@linux-mips.org
Subject: MTD drivers and byte/word mode
Date: Mon, 2 Sep 2002 19:17:23 +0200 [thread overview]
Message-ID: <00c301c252a4$9a802a00$016d100a@2m.dk> (raw)
Message-ID: <20020902171723.DOVPQ2jMGn4C-HpA5EX3lQRFebTtsdOduITtwmVykAA@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
I´m working on a 2.4 port to a design with FLASH devices connected through a 16 bit bus.
The FLASH (AMD) is set to word mode.
I have quite a hard time trying to understand the FLASH geometry settings and calculations of the addresses used for CFI query etc.
It looks as if the adresses calculated by cfi_build_cmd_addr() is the double of what my FLASH chips are using.
eg. the CFI query is written to 0xaa where my chip in word mode expects the query command to be written to 0x55
Is there any direct support in the MTD driver for differentiating between word/byte mode ?
The buswidth is set to 16 bits (=2), and interleave to 1 (I have two chips sharing the bus, not in parallel)
Stephen Mose Aaskov
Engineer, R&D
2M ELECTRONIC A/S
Malervej 10, DK-2630 Taastrup
Denmark
Tel: +45 43300555 Fax: +45 43300567
[-- Attachment #2: Type: text/html, Size: 1579 bytes --]
next reply other threads:[~2002-09-02 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 17:17 Stephen Mose Aaskov [this message]
2002-09-02 17:17 ` MTD drivers and byte/word mode Stephen Mose Aaskov
-- strict thread matches above, loose matches on Subject: below --
2002-09-03 8:28 Jon Burgess
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='00c301c252a4$9a802a00$016d100a@2m.dk' \
--to=sma@2m.dk \
--cc=linux-mips@linux-mips.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