On Sat, Jan 20, 2001 at 03:54:22PM +, Stephen Kitchener wrote:
> Any, I thought that it had cured the problem, but after a few scans,
> admittedly more than before, the scan head didn't return on the last scan
> that was successfully started.
It sounds like you did solve the "lock the machin
On Friday 19 January 2001 01:41, Bob Frey wrote:
> On Thu, Jan 18, 2001 at 11:24:54PM +, Stephen Kitchener wrote:
> > The only thing that might be odd is that the scanner's scsi card and the
> > display card are using the same IRQ, but I thought that IRQ sharing was
> > ok in the new kernels.
On Fri, 19 Jan 2001, Bob Frey wrote:
> On Thu, Jan 18, 2001 at 11:24:54PM +, Stephen Kitchener wrote:
> > The only thing that might be odd is that the scanner's scsi card and the
> > display card are using the same IRQ, but I thought that IRQ sharing was ok in
> > the new kernels. The dis
[EMAIL PROTECTED] said:
> For Linux I think the right way to handle this is to have each
> (SA_SHIRQ) sharing capable interrupt handler return a TRUE or FALSE
> value indicating whether the interrupt belongs to the driver. In
> kernel/irq.c:handle_IRQ_event() check the return value. If after one
On Thu, Jan 18, 2001 at 11:24:54PM +, Stephen Kitchener wrote:
> The only thing that might be odd is that the scanner's scsi card and the
> display card are using the same IRQ, but I thought that IRQ sharing was ok in
> the new kernels. The display card is an AGP type and the scsi card is pc
5 matches
Mail list logo
