From: chip@pobox.com (Chip Salzenberg)
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.3-rc3 - missing IDE hunk from bk4; good or bad?
Date: Sun, 15 Feb 2004 10:22:45 -0500 [thread overview]
Message-ID: <E1AsO6X-0003hW-1u@tytlal> (raw)
In-Reply-To: <1pliv-6ya-5@gated-at.bofh.it>
Linus writes:
>More merges, although most of them are architecture updates. IA64,
>ppc32/64, SuperH and ARM.
One non-arch difference between rc3 and bk4 seems to involve IDE DMA.
When I ran briefly ran bk4 I got a few IDE DMA errors (ThinkPad A30,
TOSHIBA MK8025GAS). Makes one wonder. Thus:
Is the IDE patch in bk4 (that's missing from rc3) going to be in
2.6.3? Does it only come into play with SCSI, as it seems to, or
does it affect a non-SCSI setup?
Here's the diff between bk4 and rc3:
diff -ru2 linux-2.6.3rc2bk4/drivers/scsi/libata-core.c linux-2.6.3rc3/drivers/scsi/libata-core.c
--- linux-2.6.3rc2bk4/drivers/scsi/libata-core.c 2004-02-14 23:40:19.000000000 -0500
+++ linux-2.6.3rc3/drivers/scsi/libata-core.c 2004-02-15 01:51:34.000000000 -0500
@@ -2387,39 +2387,4 @@
/**
- * ata_chk_spurious_int - Check for spurious interrupts
- * @ap: port to which command is being issued
- *
- * Examines the DMA status registers and clears
- * unexpected interrupts. Created to work around
- * hardware bug on Intel ICH5, but is applied to all
- * chipsets using the standard irq handler, just for safety.
- * If the bug is not present, this is simply a single
- * PIO or MMIO read addition to the irq handler.
- *
- * LOCKING:
- */
-static inline void ata_chk_spurious_int(struct ata_port *ap) {
- int host_stat;
-
- if (ap->flags & ATA_FLAG_MMIO) {
- void *mmio = (void *) ap->ioaddr.bmdma_addr;
- host_stat = readb(mmio + ATA_DMA_STATUS);
- } else
- host_stat = inb(ap->ioaddr.bmdma_addr + ATA_DMA_STATUS);
-
- if ((host_stat & (ATA_DMA_INTR | ATA_DMA_ERR | ATA_DMA_ACTIVE)) == ATA_DMA_INTR) {
- if (ap->flags & ATA_FLAG_MMIO) {
- void *mmio = (void *) ap->ioaddr.bmdma_addr;
- writeb(host_stat & ~ATA_DMA_ERR, mmio + ATA_DMA_STATUS);
- } else
- outb(host_stat & ~ATA_DMA_ERR, ap->ioaddr.bmdma_addr + ATA_DMA_STATUS);
-
- DPRINTK("ata%u: Caught spurious interrupt, status 0x%X\n", ap->id, host_stat);
- udelay(1);
- }
-}
-
-
-/**
* ata_interrupt -
* @irq:
@@ -2453,5 +2418,4 @@
if (qc && ((qc->flags & ATA_QCFLAG_POLL) == 0))
handled += ata_host_intr(ap, qc);
- ata_chk_spurious_int(ap);
}
}
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
next parent reply other threads:[~2004-02-15 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1pliv-6ya-5@gated-at.bofh.it>
2004-02-15 15:22 ` Chip Salzenberg [this message]
2004-02-15 15:58 ` Bartlomiej Zolnierkiewicz
2004-02-15 16:34 ` Linux 2.6.3-rc3 - IDE DMA errors on Thinkpad A30 Chip Salzenberg
2004-02-15 17:08 ` Bartlomiej Zolnierkiewicz
2004-02-16 0:55 ` Chip Salzenberg
2004-02-16 2:14 ` Jeff Garzik
2004-02-16 3:37 ` Chip Salzenberg
2004-02-16 3:47 ` Jeff Garzik
2004-02-16 3:58 ` Valdis.Kletnieks
2004-02-16 4:09 ` Jeff Garzik
2004-02-16 4:29 ` Valdis.Kletnieks
2004-02-16 12:06 ` Bill Davidsen
2004-02-16 4:08 ` Chip Salzenberg
2004-02-16 4:24 ` Bartlomiej Zolnierkiewicz
2004-02-16 19:27 ` Eric D. Mudama
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=E1AsO6X-0003hW-1u@tytlal \
--to=chip@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®