SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 01 | January | 2002 ]

<< Previous Message <<


Date: Tue, 1 Jan 2002 23:06:55 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: SBLive setup

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven Levine wrote:
>
> There's a bit more overhead to check both interrupt
> sources each time an interrupt occurs, but you save
> a context switch when the interrupts are pending for
> both sources at the same time.

The drivers are chained. Typically the first driver asks its hardware
if it needs service; if the hardware does want service then the driver
INs/OUTs the necessary ports. The driver can then either pass the
interrupt down the chain to any other driver which might want it, or
return without passing the interrupt. If the driver doesn't attempt to
pass along the interrupt then that driver can't "share" and should be
loaded first so it receives the interrupt last. Two such drivers cannot
share an interrupt since neither will pass to the other. It's been a
while but as I recall there's a bit in the driver header which the
driver programmer can set to choose either type of behavior.

*Therefore*, you can either disassemble the drivers to see how the
headers are set up *or* you can play with the sequence of the drivers
until you find a sequence that works. :)

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message <<

Return to [ 01 | January | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.