When write a 'device driver' and this device can generate an IRQ, the code must include an 'interrupt driver'?
How must the OS handle the hardware interrupts?
If the 'device driver' runs as a process, is necesary another process for the 'interrupt driver'?
Device driver vs. Interrupt driver
RE:Device driver vs. Interrupt driver
A device driver is what an OS uses to communiate with a certain type of device. An interrupt driver, if that's what I'm thinking of, is a piece of code run when a hardware interrupt is generated (IRQ). All of my interrupt handlers ("drivers") are completely seperate from my device drivers because, in my case, it makes it easier for me to work with hardware. How you do it all depends on how you want your hardware to work and how your OS is written.
RE:Device driver vs. Interrupt driver
Thank you,
I want other programers can write 'device drivers' for my OS, then if they need to use a hardware interrupt they need a way to hook an interrupt with a ISR. How could I do it?
pepito
I want other programers can write 'device drivers' for my OS, then if they need to use a hardware interrupt they need a way to hook an interrupt with a ISR. How could I do it?
pepito