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 [ 02 | January | 2002 ]

<< Previous Message << >> Next Message >>


Date: Wed, 2 Jan 2002 04:57:44 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:
>
> >as I recall there's a bit in the driver header which the driver
> >programmer can set to choose either type of behavior.
>
> You're thinking of the shared access bit. This has nothing
> to do with IRQ sharing. IRQ sharing is determined when
> the IRQ is allocated via a DevHlp call.

Thanks, it's been several years and I can't remember. I do remember
creating the header in assembler (mostly fields, almost no logic other
than a jump) and having to write 18 small routines in C, then compiling
using Watcom. I still think there was some logic in one of those
routines that determined whether the interrupt had been handled or not,
and if you polled your hardware and found it didn't need service (and
therefore hadn't issued the interrupt) you could still claim the
interrupt as your own thereby shutting out any other driver on that
interrupt. I don't recall what happens when two hardware devices set
the same IRQ line at the same instant.

> The OS/2 device driver implementation is quite
> different and most of your statements don't apply.

Which ones don't you like? :))

- 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 << >> Next Message >>

Return to [ 02 | 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.