From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Willy Tarreau <willy@w.ods.org>
Cc: Jason Papadopoulos <jasonp@boo.net>,
linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: Linux 2.4.21-rc3 : IDE pb on Alpha
Date: Tue, 27 May 2003 18:04:03 +0400 [thread overview]
Message-ID: <20030527180403.A2292@jurassic.park.msu.ru> (raw)
In-Reply-To: <20030527123152.GA24849@alpha.home.local>; from willy@w.ods.org on Tue, May 27, 2003 at 02:31:52PM +0200
On Tue, May 27, 2003 at 02:31:52PM +0200, Willy Tarreau wrote:
> Sorry, I pasted the .config that I used just after, and which allowed me to
> boot. Later I set CONFIG_BLK_DEV_ALI15X3 again and CONFIG_BLK_DEV_IDEDMA_PCI,
> but I left CONFIG_IDEDMA_PCI_AUTO disabled. I now can boot and enable DMA
> later. That's weird, but it works.
Perhaps not that weird. From my experience, ALi DMA is sensitive to
some of "PIO timings". That is, if SRM hasn't initialized the chipset
properly (on Nautilus it has, BTW), DMA won't work. When you boot with
DMA disabled, driver has to set right PIO mode, so you can safely
enable DMA later.
Can you (and Jason) try this patch with CONFIG_IDEDMA_PCI_AUTO=y?
Ivan.
--- linux/drivers/ide/pci/alim15x3.c.orig Tue Apr 22 19:17:22 2003
+++ linux/drivers/ide/pci/alim15x3.c Tue May 27 17:42:17 2003
@@ -525,10 +525,14 @@ static int ali15x3_config_drive_for_dma(
drive->init_speed = 0;
+ /* Set reasonable PIO timings first - some of them are needed
+ for DMA as well. */
+ hwif->tuneproc(drive, 255);
+
if ((id->capability & 1) != 0 && drive->autodma) {
/* Consult the list of known "bad" drives */
if (hwif->ide_dma_bad_drive(drive))
- goto ata_pio;
+ goto no_dma_set;
if ((id->field_valid & 4) && (m5229_revision >= 0xC2)) {
if (id->dma_ultra & hwif->ultra_mask) {
/* Force if Capable UltraDMA */
@@ -550,11 +554,9 @@ try_dma_modes:
if (!config_chipset_for_dma(drive))
goto no_dma_set;
} else {
- goto ata_pio;
+ goto no_dma_set;
}
} else {
-ata_pio:
- hwif->tuneproc(drive, 255);
no_dma_set:
return hwif->ide_dma_off_quietly(drive);
}
next prev parent reply other threads:[~2003-05-27 13:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 3:37 Jason Papadopoulos
2003-05-27 4:53 ` Willy Tarreau
2003-05-27 9:40 ` Ivan Kokshaysky
2003-05-27 12:31 ` Willy Tarreau
2003-05-27 14:04 ` Ivan Kokshaysky [this message]
2003-05-27 14:37 ` Willy Tarreau
2003-05-28 0:38 ` Willy Tarreau
2003-05-28 1:41 ` Jason Papadopoulos
2003-05-28 3:12 ` Jeff Garzik
2003-05-29 0:35 ` Jason Papadopoulos
2003-05-29 1:10 ` Jeff Garzik
2003-05-28 14:45 ` Ivan Kokshaysky
2003-05-31 15:24 ` Ben Collins
2003-06-01 18:40 ` Ivan Kokshaysky
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 22:19 Linux 2.4.21-rc3 Marcelo Tosatti
2003-05-25 17:36 ` Linux 2.4.21-rc3 : IDE pb on Alpha Willy Tarreau
2003-05-25 17:00 ` Willy Tarreau
2003-05-25 20:37 ` Mike Fedyk
2003-05-25 20:45 ` Bartlomiej Zolnierkiewicz
2003-05-25 20:55 ` Mike Fedyk
2003-05-25 21:23 ` 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=20030527180403.A2292@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=jasonp@boo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=willy@w.ods.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®