struct pci-device and irq
From: Bob888y (bob888y_at_wmconnect.com)
Date: 08/22/03
- Next message: Peter Wallace: "Re: modding IDE cable to write-protect compact flash?"
- Previous message: Todd: "Re: C++ in embedded systems"
- Next in thread: Matt Porter: "Re: struct pci-device and irq"
- Reply: Matt Porter: "Re: struct pci-device and irq"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 22 Aug 2003 02:39:49 GMT
I want to knwo how this is implemented in Linux. When a struct pci_device *dev
is returned by the kernel (after having found that a pci device the driver
registered for), the field dev->irq, is that original hardware irq# or some
number Linux uses, maybe different from the original irq#?
I am asking this question, because someother RTOSs might define their own irq#
that is not necessary the hardware irq#, which in somecase is convenient, for
soem platform that has a interrupt controler, like mpc860. In that case, the OS
can give much more "irq# numbers" to the applications by adding that portion of
chacking interrupt control software into the OS.
Any comments would be helpful.
B
- Next message: Peter Wallace: "Re: modding IDE cable to write-protect compact flash?"
- Previous message: Todd: "Re: C++ in embedded systems"
- Next in thread: Matt Porter: "Re: struct pci-device and irq"
- Reply: Matt Porter: "Re: struct pci-device and irq"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
