From: "Timofei V. Bondarenko" <timm@ipi.ac.ru>
To: Aras Vaichas <arasv@magellan-technology.com>
Cc: MTD-LIST <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2+NAND problem in 2.6.13-at91
Date: Wed, 14 Sep 2005 17:05:19 +0400 [thread overview]
Message-ID: <4328200F.7050306@ipi.ac.ru> (raw)
In-Reply-To: <4327A4F8.60300@magellan-technology.com>
Hi.
Aras Vaichas wrote:
> I did a diff between the nand_base.c version shipped with 2.6.13 (v1.147) and
> 2.6.12-rc1 (v1.138) and noticed that a delay loop had been moved further down
> the code, I moved this delay back to where it was in v1.138 and it is now
> working again. i assume that there was a probably a good reason to move this
> delay in the first place though and I don't wish to break anything else ...
The delay_loop calibration logic has been changed in 2.6.13.
It might break udelay() on some architectures.
--
Regards.
Tim.
next prev parent reply other threads:[~2005-09-14 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 6:28 JFFS2+NAND problem in 2.6.13-at91 Aras Vaichas
2005-09-13 8:45 ` Aras Vaichas
2005-09-14 4:20 ` Aras Vaichas
2005-09-14 13:05 ` Timofei V. Bondarenko [this message]
2005-09-14 12:34 ` Artem B. Bityuckiy
2005-09-15 1:46 ` Aras Vaichas
2005-09-15 7:30 ` Artem B. Bityuckiy
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=4328200F.7050306@ipi.ac.ru \
--to=timm@ipi.ac.ru \
--cc=arasv@magellan-technology.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