From: Jan Evert van Grootheest <j.e.van.grootheest@caiway.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, bzolnier@gmail.com
Subject: Re: [PATCH ht6560b] Force prefetch for some devices
Date: Fri, 27 Jun 2008 21:51:59 +0200 [thread overview]
Message-ID: <486544DF.60002@caiway.nl> (raw)
In-Reply-To: <20080218143636.3394eece@core>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
Alan, Bart,
It's been a while...
Alan Cox wrote:
> On Mon, 18 Feb 2008 13:50:02 +0100
> Jan Evert van Grootheest <j.e.van.grootheest@caiway.nl> wrote:
>
>
>> Prefetch needs to be set for some ide devices to work when connected to
>> a ht6560b interface. This was not always done properly, causing a system
>> with a HD and CD on the primary interface to not work properly. Or, in
>> effect, hang hard.
>>
>> This patch forces prefetch on devices before checking whether it
>> is necessary to change the settings in the interface
>>
>
> Interesting, that is backwards to the docs and not something I've seen.
> If you are correct then pata_legacy also wants tweaking .
>
I'm testing this... but lack some knowledge.
Is there some generic way to figure out wheter a device supports it?
What devices normally support prefetching? Disks only?
I already found out that CDs do not. But tapes? Floppies? What else can
be there that might support prefetching?
Thanks,
Jan Evert
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 5185 bytes --]
next prev parent reply other threads:[~2008-06-27 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 12:50 [PATCH ht6560b] Force prefetch for some devices Jan Evert van Grootheest
2008-02-18 13:58 ` Sergei Shtylyov
2008-02-18 14:36 ` Alan Cox
2008-02-18 15:21 ` Jan Evert van Grootheest
2008-02-18 15:47 ` Alan Cox
2008-06-27 19:51 ` Jan Evert van Grootheest [this message]
2008-06-27 20:04 ` Alan Cox
2008-02-18 23:14 ` 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=486544DF.60002@caiway.nl \
--to=j.e.van.grootheest@caiway.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).