From: Osamu Tomita <tomita@cinet.co.jp>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.5.13 IDE PIO mode Fix
Date: Sat, 04 May 2002 08:08:51 +0900 [thread overview]
Message-ID: <3CD31883.E41E0DFA@cinet.co.jp> (raw)
I found this bug in 2.5.10 first. And caused ext2 FS corruption.
We are porting Linux to PC-9801 architecture (made by NEC Japan).
It has PIO ONLY IDE I/F. So please check PIO mode too.
# Our porting status - 2.2.x/2.4.x done and updating. 2.5.x partial.
diff -urN linux-2.5.10/drivers/ide/ide-taskfile.c linux/drivers/ide/ide-taskfile.c
--- linux-2.5.10/drivers/ide/ide-taskfile.c Wed Apr 24 16:15:19 2002
+++ linux/drivers/ide/ide-taskfile.c Fri Apr 26 15:44:42 2002
@@ -202,7 +202,7 @@
ata_write_slow(drive, buffer, wcount);
else
#endif
- ata_write_16(drive, buffer, wcount<<1);
+ ata_write_16(drive, buffer, wcount);
}
}
next reply other threads:[~2002-05-03 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 23:08 Osamu Tomita [this message]
2002-05-05 0:06 ` [PATCH] 2.5.13 IDE PIO mode Fix Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 10:15 Andries.Brouwer
2002-05-05 0:10 ` Martin Dalecki
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=3CD31883.E41E0DFA@cinet.co.jp \
--to=tomita@cinet.co.jp \
--cc=linux-kernel@vger.kernel.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