initialized, but I just didn't register the ISR on the
right intline.
Thanks,
-Howie
> -Original Message-
> From: Mike Smith [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 19, 2001 8:03 PM
> To: Howie Xu
> Cc: [EMAIL PROTECTED]
> Subject: Re: ISR not triggered
> The bug was solved and it was because the BIOS advertises wrong interrupt
> line. It should be 5, not 12. So I registered ISR for line 12, of course
> never triggered.
Er, can you be more specific here? Where is the interrupt line
"advertised"? Is the BIOS incorrectly populating the intline
1 AM
> To: Mike Smith
> Cc: [EMAIL PROTECTED]
> Subject: RE: ISR not triggered upon the interrupts and OS hangs
>
>
> I am using FreeBSD 3.2, and all the sample drivers in
> /usr/src/sys/pci/*.c uses pci_map_int().
>
> How can I debug it in 3.2 to know what the OS thinks
> Sent: Wednesday, January 17, 2001 2:20 AM
> To: Howie Xu
> Cc: [EMAIL PROTECTED]
> Subject: Re: ISR not triggered upon the interrupts and OS hangs
>
>
> > Dear Freebsd Hackers,
> >
> > Here is a question regarding my bsd device drivers:
> >
> > I u
> Dear Freebsd Hackers,
>
> Here is a question regarding my bsd device drivers:
>
> I used the pci_map_int() to register an interrupt handler for my PCI device
> (intline = 12). But when the interrupt comes in, the handler (ISR) is not
> triggered at all. But the OS hangs and I can see continuou
Dear Freebsd Hackers,
Here is a question regarding my bsd device drivers:
I used the pci_map_int() to register an interrupt handler for my PCI device
(intline = 12). But when the interrupt comes in, the handler (ISR) is not
triggered at all. But the OS hangs and I can see continuous interrupts
c
6 matches
Mail list logo
