public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, tomita@cinet.co.jp, torvalds@transmeta.com
Subject: Re: [PATCH] 2.5.13 IDE PIO mode Fix
Date: Sun, 05 May 2002 02:10:26 +0200	[thread overview]
Message-ID: <3CD47872.30104@evision-ventures.com> (raw)
In-Reply-To: <UTC200205041015.g44AFIV16086.aeb@smtp.cwi.nl>

Użytkownik Andries.Brouwer@cwi.nl napisał:
>     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);
>             }
>      }
> 
> Excellent!

Thank you for confirmations. This even streamlines the code to what
it was intendid to be.

BTW.> The next thing I plan to break is host chips initialization,
since Jens introduced several additional ide_dma_action_t fields
for no good reaons... I decided to remove them all as next... :-).


  reply	other threads:[~2002-05-05  1:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 10:15 [PATCH] 2.5.13 IDE PIO mode Fix Andries.Brouwer
2002-05-05  0:10 ` Martin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-03 23:08 Osamu Tomita
2002-05-05  0:06 ` 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=3CD47872.30104@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomita@cinet.co.jp \
    --cc=torvalds@transmeta.com \
    /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