public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "marijn ros" <marijn@mad.scientist.com>
To: linux-kernel@vger.kernel.org
Subject: [Documentation PATCH] Re: 2.4.21-pre2 IDE problems
Date: Wed, 01 Jan 2003 17:48:53 -0500	[thread overview]
Message-ID: <20030101224854.38161.qmail@mail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

----- Original Message -----
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: 31 Dec 2002 16:59:36 +0000
To: Marijn Ros <marijn@mad.scientist.com>
Subject: Re: 2.4.21-pre2 IDE problems

> On Tue, 2002-12-31 at 12:18, Marijn Ros wrote:
> > However, when I try the new 2.4.21-pre2 taskfile IO setting, I get a
> > 'hda: lost interrupt' message every 30 seconds (the timeout period I
> > guess) during disk IO, making the machine unusable. I know this
> > setting is experimental, but I guess you would like to know about my
> > problems before the old code is phased out completely.
> 
> Taskfile I/O as opposed to ioctl is broken for PIO. I know about this
> and I've disabled it. I don't plan to fix that path for 2.4 but to keep
> the old read/write paths to reduce risk

Thanks. The attached patch tries to clarify the Configure.help based on this.

Bye,
 Marijn
-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Meet Singles
http://corp.mail.com/lavalife


[-- Attachment #2: taskfile-io-doc.diff --]
[-- Type: application/octet-stream, Size: 1600 bytes --]

--- linux-2.4.21-pre2/Documentation/Configure.help	2002-12-29 18:53:54.000000000 +0100
+++ Configure.help	2003-01-01 23:40:25.000000000 +0100
@@ -808,21 +808,26 @@
 Use Taskfile I/O
 CONFIG_IDE_TASKFILE_IO
   This is the "Jewel" of the patch.  It will go away and become the new
-  driver core.  Since all the chipsets/host side hardware deal w/ their
-  exceptions in "their local code" currently, adoption of a
-  standardized data-transport is the only logical solution.
+  driver core, but probably not in the 2.4 timeframe.  Since all the
+  chipsets/host side hardware deal w/ their exceptions in "their local
+  code" currently, adoption of a standardized data-transport is the only
+  logical solution.
   Additionally we packetize the requests and gain rapid performance and
   a reduction in system latency.  Additionally by using a memory struct
   for the commands we can redirect to a MMIO host hardware in the next
   generation of controllers, specifically second generation Ultra133
   and Serial ATA.
 
+  This code only works for controllers in DMA mode at the moment.  If you
+  want or have to run your controller in PIO mode, don't use this option
+  as it will fail horribly.
+
   Since this is a major transition, it was deemed necessary to make the
   driver paths buildable in separate models.  Therefore if using this
   option fails for your arch then we need to address the needs for that
   arch.
 
-  If you want to test this functionality, say Y here.
+  If you want to test this functionality, say Y here.  Otherwise, say N.
 
 Force DMA
 CONFIG_BLK_DEV_IDEDMA_FORCED

                 reply	other threads:[~2003-01-01 22:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030101224854.38161.qmail@mail.com \
    --to=marijn@mad.scientist.com \
    --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