From: Robin Gilks <robin.gilks@taitradio.com>
To: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Progress but stuck on write_buffers/write_words without fixup
Date: Wed, 23 Jun 2010 13:07:01 +1200 [thread overview]
Message-ID: <4C215E35.7050503@taitradio.com> (raw)
OK - I've found a lot of the issues with updating 5 years in one hop -
mtdblocks start from 1 because 0 is the whole phys mapped device, name
of the partition list is hardcoded to 'phys' but I've still got a
problem with the ST Micro M28W640ECB not supporting write_buffers in a
CFI compliant fashion - I can get round it by setting the
FORCE_WORD_WRITE in cfi_cmdset_0001.c but I'm hoping someone can tell me
there is a better way
Cheers
--
Robin Gilks
Senior Design Engineer
Tait Radio Communications
DDI: 64 3 3571569
www.taitradio.com
robin.gilks@tait.co.nz
TAIT: THE RIGHT FIT
reply other threads:[~2010-06-23 1:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C215E35.7050503@taitradio.com \
--to=robin.gilks@taitradio.com \
--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;
as well as URLs for NNTP newsgroup(s).