Dan Williams wrote:
The error interrupt handling code is still in there and is working. The
following patch works for me.
---
sata_vsc: handle unexpected interrupts when executing a polled IDENTIFY
From: Dan Williams <[EMAIL PROTECTED]>
Signed-off-by: Dan Williams <[EMAIL PROTECTED]>
---
dr
Jeff Garzik wrote:
As I recall, the 31244 and VSC-7174 always send an interrupt, so the
driver should account for this. I thought we had code already in the
driver to handle this, but perhaps recent changes stomped that.
It would be good to standardize the way we handle these sorts of
cont
Jeff Garzik wrote:
Williams, Dan J wrote:
When I fire up 2.6.20 with an iq3124h I get:
ata1: SATA max UDMA/133 cmd 0xC8822200 ctl 0xC889 bmdma 0xC8822270
irq 25
ata2: SATA max UDMA/133 cmd 0xC8822400 ctl 0xC8822429 bmdma 0xC8822470
irq 25
ata3: SATA max UDMA/133 cmd 0xC8822600 ctl 0xC882262
> As I recall, the 31244 and VSC-7174 always send an interrupt, so the
> driver should account for this. I thought we had code already in the
> driver to handle this, but perhaps recent changes stomped that.
>
> It would be good to standardize the way we handle these sorts of
> controllers, becau
Williams, Dan J wrote:
When I fire up 2.6.20 with an iq3124h I get:
ata1: SATA max UDMA/133 cmd 0xC8822200 ctl 0xC889 bmdma 0xC8822270
irq 25
ata2: SATA max UDMA/133 cmd 0xC8822400 ctl 0xC8822429 bmdma 0xC8822470
irq 25
ata3: SATA max UDMA/133 cmd 0xC8822600 ctl 0xC8822629 bmdma 0xC8822670
i
When I fire up 2.6.20 with an iq3124h I get:
ata1: SATA max UDMA/133 cmd 0xC8822200 ctl 0xC889 bmdma 0xC8822270
irq 25
ata2: SATA max UDMA/133 cmd 0xC8822400 ctl 0xC8822429 bmdma 0xC8822470
irq 25
ata3: SATA max UDMA/133 cmd 0xC8822600 ctl 0xC8822629 bmdma 0xC8822670
irq 25
ata4: SATA max UDMA
