Date: Thu, 06 Jan 2000 17:43:37 -0500 From: Brian McGovern <bmcgover@cisco.com> To: hackers@freebsd.org Subject: Question on mapping PCI interrupts... (or rather, not...) Message-ID: <200001062243.RAA00334@bmcgover-pc.cisco.com>
next in thread | raw e-mail | index | archive | help
I'm running in to a PCI interface question. I have a board that I can select whether it will run in Interrupt or "Polled mode" (ie - no interrupt assigned). It appears that when I have it in interrupt mode, the IRQ (cfg->intline) is set to a relatively valid (0-15) setting. When it is in polled mode, it reads as 255 (I'm assuming all-bits-on). However, pci_map_int is returning the same value reguardless of whether the interrupt is valid (0-15) or not (255). In the 2.x tree, it would return an error if the register was set at 255, and I used this in the driver to determine whether to be in polled mode or interrupt driven. Given the new behavior, should I: a.) Consider this a bug, and send in a pr (after all, it didn't _really_ map a valid interrupt)... b.) Leave it as is, but check the real interrupt register value, and if its not valid (0-15), assume its in polled mode. This scares me the most, for someday there may be more (up to 255) real interrupts... c.) Be told about a better way to check for this condition... -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001062243.RAA00334>