From: Shane Nay <shane@agendacomputing.com>
To: mtd@infradead.org
Subject: Problems with cfi_cmdset_0001
Date: Sat, 2 Dec 2000 05:01:32 +0000 [thread overview]
Message-ID: <20001202050132.B4457@www.easysolutions.net> (raw)
Okay, I've been reading the PDF for Strataflash, by Intel. And I've traced
my problems with the write routines in MTD down to two problems, the Block
address, and the word write problem. The command address isn't properly
interpretted for this chip. I'm not sure what the CFI spec is, but I
think:
cmd_adr=adr & ~(wbufsize-1);
is wrong. (Well, maybe it's different chip to chip, but I know it's wrong
for this chip)
It should compute the top of the block via the erasesize and size.
cmd_adr=mtd->erasesize*((int)(adr/mtd->erasesize));
Now, this fixes the Block address. The other problem though is
significantly nastier.
Okay, MTD seems to think that it can write twice as much data as it can to
a device at a time in write_buffer mode, which is all together wrong. My
configuration is two x8 chips interleaved on a 16 bit bus. Basically...,
its thinking we have two x16 chips on a 32 bit bus before streaming, but
then streams the data the right way, but twice as much as it said it would.
(It says, I'm sending 16 words, then sends 32 of them instead, which as
you could imagine, is quite confusing to the poor flash chips)
In any event. I've got the block address problem fixed up in the code with
the afore mentioned code. The other problem I'm still working on.
However, my code is so removed at this point from MTD base since I had too
many other things at play with MTD code to properly trace my problem, and
now I have a cleaner version of the code for XIP. So I'm not sure I'm
going to roll all my changes into cfi_cmdset_0001. Who is the maintainer
of this file BTW? I'll try to make patches for him/her to fix these
problems.
Thanks,
Shane.
(Or maybe my extremely tired brain is mis-interpretting..., if I'm wrong,
tell me so :)
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-12-02 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-02 5:01 Shane Nay [this message]
2000-12-02 7:29 ` Problems with cfi_cmdset_0001 && XIP kernel w/MTD working Shane Nay
2000-12-02 15:23 ` Problems with cfi_cmdset_0001 Nicolas Pitre
2000-12-02 8:54 ` Shane Nay
2000-12-03 3:42 ` including doc2001 and docprobe into the kernel Adam Agnew
2000-12-03 5:52 ` Levi Khatskevitch
2000-12-03 16:32 ` David Woodhouse
2000-12-03 17:19 ` Levi Khatskevitch
2000-12-03 18:13 ` 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=20001202050132.B4457@www.easysolutions.net \
--to=shane@agendacomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox