A new direction for Linux for gadgets

TalkBack 5 of 7:

Next »

« Previous

• Thread View
• Flat View

who gets dibs

The way it should be / used to be done is the system admin says which code (call it a "process" or "driver") will get run (through a configuration file). Thereafter interrupt is passed to the next relevant process.
Note in a typical legacy PC, Interrupt 4 caused calling of the code to read bytes from COM1, Interrupt 3 ditto for COM2, Interrupt 7 send more data to LPT1. However these is fundamentally no problem with layering a small polling layer on top so that COM5,6, and COM1 cause IRQ4. The software checks the bytes received in all three ports, then proceeds. ("interrupt sharing"). AFAIK in any case, on PCI, sharing is no longer strictly necessary (devices are allocated unshared resources each boot).
The admin controls this in the case where there is a modification beyond the package basics.

Real Time systems are precisely FOR mission critical apps where Time is of the essence. You seem to be saying the opposite.
Software interrupts are unrelated.

I still can't see what the big deal is here.

Posted by: hipparchus2000   Posted on: 10/12/04 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Reducing Server Total Cost of Ownership with VMware Virtualization Software VMware VMware virtualization enables customers to reduce their server TCO and ... Download Now
• Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now
• Open Standards Technologies Provide the Ingredients for Delivering Security Across the Papa Gino's Enterprise Dell Papa Gino's Holdings Corporation founded by the entrepreneur operates one ... Download Now