From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: [PATCH][IDE] update qd65xx driver
Date: Sat, 13 Sep 2003 01:34:41 +0200 [thread overview]
Message-ID: <200309130134.41702.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <UTC200309122309.h8CN9wn08090.aeb@smtp.cwi.nl>
On Saturday 13 of September 2003 01:09, Andries.Brouwer@cwi.nl wrote:
> From B.Zolnierkiewicz@elka.pw.edu.pl Fri Sep 12 00:44:48 2003
>
> > That reminds me, did I ever send you this?
> >
> > Andries
>
> No, only similar patch for hpt366.c.
>
> I think the (almost) correct scheme is following ...
>
> Yes, larger changes are possible - and in fact I have a directory
> full of IDE stuff, polishing, cleanup, non-urgent.
Great! Please push'em.
> I sent this mainly because the hpt366.c analog was needed to
> prevent filesystem corruption (on my own system). Similarly,
> I imagine this patch is needed to prevent filesystem corruption -
> no need to wait until someone actually reports a corrupted filesystem.
>
> Patches that allow people to set lower PIO modes than the max
> may be nice, but are less urgent than preventing modes higher
> than the max.
Eeeh... please re-read my mail.
As stated before you got corruption with hpt366.c because it was calling
hpt3xx_tune_drive() *internally* with pio argument equal to 5 instead of 255.
qd65xx.c is not calling qd*_tune_drive() internally et all -> no possibility
of corruption unless user *manually* sets mode higher than supported.
--bartlomiej
> Andries
>
> > - pio = ide_get_best_pio_mode(drive, pio, 255, &d);
> > + pio = ide_get_best_pio_mode(drive, 255, pio, &d);
next prev parent reply other threads:[~2003-09-12 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 23:09 Andries.Brouwer
2003-09-12 23:34 ` Bartlomiej Zolnierkiewicz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-13 17:31 Andries.Brouwer
2003-09-11 21:51 Andries.Brouwer
2003-09-11 22:46 ` Bartlomiej Zolnierkiewicz
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=200309130134.41702.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=Andries.Brouwer@cwi.nl \
--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
all inboxes | Powered by JetHome®