2.4.21-pre2 IDE problems
----- Original Message -----
From: Alan Cox <[email protected]>
Date: 31 Dec 2002 16:59:36 +0000
To: Marijn Ros <[email protected]>
Subject: Re: 2.4.21-pre2 IDE problems
Quoted 10 lines · Marijn Ros
Quoted 5 lines
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
Signature · 6 lines
__________________________________________________________ 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
Configure.help renamed from Documentation/Configure.help +9 -4
@@ -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