From: Shane Nay <shane@agendacomputing.com>
To: "D. Vrabel" <dv207@cam.ac.uk>, Nicolas Pitre <nico@cam.org>
Cc: mtd@infradead.org
Subject: Re: cfi_cmdset_0001.c: do_write_buffer: wrong length
Date: Mon, 18 Dec 2000 22:24:16 +0000 [thread overview]
Message-ID: <0012182224162J.11759@www.easysolutions.net> (raw)
In-Reply-To: <3A313CE7.DFF1BC4E@cam.ac.uk>
Okay, last message was way cryptic again..., I'm not a master communicator.
Anyway, I have succesfully tested the following change on two interleaves.
First device:
two x16 devices in x8 mode interleaved
Second device:
one x16 device in x16 mode
It's only one change... cfi_cmdset_0001.c:
/* Write length of data to come */
-cfi_write(map,CMD((len/(cfi->device_type*CFIDEV_INTERLEAVE))-1),cmd_adr);
+cfi_write(map,CMD((len/(cfi->device_type))-1),cmd_adr);
Dividing by CFIDEV_INTERLEAVE there I think is wrong. The interleave
_increases_ not decreases the number of bytes/words you are going to write.
Thanks,
Shane.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-12-19 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 14:45 cfi_cmdset_0001.c: do_write_buffer: wrong length David Vrabel
2000-12-08 18:21 ` Nicolas Pitre
2000-12-08 19:56 ` D. Vrabel
2000-12-18 22:13 ` Shane Nay
2000-12-18 22:24 ` Shane Nay [this message]
2000-12-19 9:41 ` David Vrabel
2000-12-18 23:07 ` Shane Nay
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=0012182224162J.11759@www.easysolutions.net \
--to=shane@agendacomputing.com \
--cc=dv207@cam.ac.uk \
--cc=mtd@infradead.org \
--cc=nico@cam.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.