public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Petr Vandrovec <VANDROVE@vc.cvut.cz>,
	"A.Sajjad Zaidi" <sajjad@vgkk.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Promise, DMA and RAID5 problems running 2.4.1
Date: Fri, 9 Feb 2001 09:09:35 +0100	[thread overview]
Message-ID: <20010209090935.A1691@suse.cz> (raw)
In-Reply-To: <E14QarA-0001DC-00@the-village.bc.nu> <Pine.LNX.4.10.10102071253121.5890-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10102071253121.5890-100000@master.linux-ide.org>; from andre@linux-ide.org on Wed, Feb 07, 2001 at 12:53:36PM -0800

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

On Wed, Feb 07, 2001 at 12:53:36PM -0800, Andre Hedrick wrote:
> On Wed, 7 Feb 2001, Alan Cox wrote:
> 
> > > Iff CONFIG_BLK_DEV_IDECS is set then yes, doing schedule is better.
> > > But I do not see any benefit in doing
> > > 
> > > unsigned long timeout = jiffies + ((HZ + 19)/20) + 1;
> > > while (0 < (signed long)(timeout - jiffies));
> > 
> > On that bit we agree.
> 
> What do you want fixed?
> Send a patch and lets try it....

How about this?

-- 
Vojtech Pavlik
SuSE Labs

[-- Attachment #2: pdcpatch --]
[-- Type: text/plain, Size: 1228 bytes --]

--- pdc202xx.c.old	Fri Jul 28 21:08:30 2000
+++ pdc202xx.c	Fri Feb  9 09:08:55 2001
@@ -747,14 +747,11 @@
 {
 	unsigned long high_16	= pci_resource_start(HWIF(drive)->pci_dev, 4);
 	byte udma_speed_flag	= inb(high_16 + 0x001f);
-	int i			= 0;
 
 	OUT_BYTE(udma_speed_flag | 0x10, high_16 + 0x001f);
-	ide_delay_50ms();
-	ide_delay_50ms();
+	mdelay(100)
 	OUT_BYTE(udma_speed_flag & ~0x10, high_16 + 0x001f);
-	for (i = 0; i < 40; i++)
-		ide_delay_50ms();
+	mdelay(2000);		/* 2 seconds ?! */
 }
 
 unsigned int __init pci_init_pdc202xx (struct pci_dev *dev, const char *name)
@@ -767,7 +764,6 @@
 	if ((dev->device == PCI_DEVICE_ID_PROMISE_20262) ||
 	    (dev->device == PCI_DEVICE_ID_PROMISE_20265) ||
 	    (dev->device == PCI_DEVICE_ID_PROMISE_20267)) {
-		int i = 0;
 		/*
 		 * software reset -  this is required because the bios
 		 * will set UDMA timing on if the hdd supports it. The
@@ -779,11 +775,9 @@
 		 */
 
 		OUT_BYTE(udma_speed_flag | 0x10, high_16 + 0x001f);
-		ide_delay_50ms();
-		ide_delay_50ms();
+		mdelay(100);
 		OUT_BYTE(udma_speed_flag & ~0x10, high_16 + 0x001f);
-		for (i=0; i<40; i++)
-			ide_delay_50ms();
+		mdelay(2000);	/* 2 seconds ?! */
 	}
 
 	if (dev->resource[PCI_ROM_RESOURCE].start) {

  reply	other threads:[~2001-02-09  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07 20:40 Promise, DMA and RAID5 problems running 2.4.1 Petr Vandrovec
2001-02-07 20:06 ` Alan Cox
2001-02-07 20:53   ` Andre Hedrick
2001-02-09  8:09     ` Vojtech Pavlik [this message]
     [not found] <Pine.LNX.4.10.10102070924340.19012-100000@coffee.psychology.mcmaster.ca>
2001-02-08  2:00 ` A.Sajjad Zaidi
2001-02-08  2:06   ` Stephen Wille Padnos
  -- strict thread matches above, loose matches on Subject: below --
2001-02-07 13:15 Petr Vandrovec
2001-02-07 19:33 ` Alan Cox
2001-02-08  5:07 ` A.Sajjad Zaidi
2001-02-07 10:12 A.Sajjad Zaidi

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=20010209090935.A1691@suse.cz \
    --to=vojtech@suse.cz \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sajjad@vgkk.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