From: Manfred Gruber <gruber.m@utanet.at>
To: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 with AM29LV256M
Date: Thu, 19 Aug 2004 14:30:39 +0200 [thread overview]
Message-ID: <200408191430.39167.gruber.m@utanet.at> (raw)
In-Reply-To: <m33c2j76eb.fsf@maxwell.lnxi.com>
Hi !
Am Donnerstag, 19. August 2004 12:45 schrieben Sie:
> > Hmmm ok, so it's do_write_oneword() which is broken.
>
> Possibly it still could be the chip. do_write_oneword since it
> is read the data back anyway confirms that the data read back is
> what was written. I don't believe the write_buffer code path
> does any but the most rudimentary sanity checks.
This is correct. read_oneword does a check but also with paching this out the
problem is there.
I found out that the first write one block works the secound not, any idea ?
copy a file first come in the write one block function:
MTD do_write_buffer(): WRITE 0x0028e9c0(0x00000069)
MTD do_write_oneword(): WRITE 0x0028e9d8(0x6161616a)
MTD do_write_oneword(): WRITE addr 0x0028e9d8
MTD do_write_oneword(): WRITE oldd 0x6161616a curd (0x6161616a)
MTD do_write_oneword(): WRITE oldd 0x6161616a curd (0x6161616a)
MTD do_write_oneword(): WRITE 0x0028e9dc(0xffffff61)
MTD do_write_oneword(): WRITE addr 0x0028e9dc
MTD do_write_oneword(): WRITE oldd 0xffffff61 curd (0xffffff61)
MTD do_write_oneword(): WRITE oldd 0xffffff61 curd (0xffffff61)
secound come in the write one block function:
MTD do_write_buffer(): WRITE 0x0028e9e0(0xe0021985)
MTD do_write_buffer(): WRITE 0x0028f0c0(0x728ea668)
MTD do_write_buffer(): WRITE 0x0028f100(0xbc68ad56)
MTD do_write_oneword(): WRITE 0x0028ea24(0x978d0902)
MTD do_write_oneword(): WRITE addr 0x0028ea24
MTD do_write_oneword(): WRITE oldd 0xff640800 curd (0xff240800)
MTD do_write_oneword(): software timeout
MTD do_write_oneword(): WRITE addr 0x0028ea24
MTD do_write_oneword(): WRITE oldd 0xff640800 curd (0xff240800)
MTD do_write_oneword(): software timeout
MTD do_write_oneword(): WRITE addr 0x0028ea24
MTD do_write_oneword(): WRITE oldd 0xff640800 curd (0xff240800)
Any idea ?
Thanks,regards
prev parent reply other threads:[~2004-08-19 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 8:06 JFFS2 with AM29LV256M Manfred Gruber
2004-08-19 8:32 ` David Woodhouse
2004-08-19 9:40 ` Manfred Gruber
2004-08-19 10:16 ` David Woodhouse
2004-08-19 10:45 ` Eric W. Biederman
2004-08-19 12:30 ` Manfred Gruber [this message]
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=200408191430.39167.gruber.m@utanet.at \
--to=gruber.m@utanet.at \
--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