Re: [PATCH 10/29] ncr5380: Fix SCSI_IRQ_NONE bugs

2014-10-03 Thread Geert Uytterhoeven
On Thu, Oct 2, 2014 at 8:56 AM, Finn Thain fth...@telegraphics.com.au wrote: Oak scsi doesn't use any IRQ, but it sets irq = IRQ_NONE rather than SCSI_IRQ_NONE. Problem is, the core NCR5380 driver expects SCSI_IRQ_NONE if it is to issue IDENTIFY commands that prevent target disconnection.

Re: [PATCH 10/29] ncr5380: Fix SCSI_IRQ_NONE bugs

2014-10-03 Thread Finn Thain
On Fri, 3 Oct 2014, Geert Uytterhoeven wrote: On Thu, Oct 2, 2014 at 8:56 AM, Finn Thain fth...@telegraphics.com.au wrote: Oak scsi doesn't use any IRQ, but it sets irq = IRQ_NONE rather than SCSI_IRQ_NONE. Problem is, the core NCR5380 driver expects SCSI_IRQ_NONE if it is to issue

[PATCH 10/29] ncr5380: Fix SCSI_IRQ_NONE bugs

2014-10-02 Thread Finn Thain
Oak scsi doesn't use any IRQ, but it sets irq = IRQ_NONE rather than SCSI_IRQ_NONE. Problem is, the core NCR5380 driver expects SCSI_IRQ_NONE if it is to issue IDENTIFY commands that prevent target disconnection. Other drivers, when they can't get an IRQ or can't use one, will set host-irq =