SCOUG-HELP Mailing List Archives

<< Previous Message <<

Date:	Wed, 1 Dec 2004 12:01:59 PST8
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: config.sys bus support ?

=====================================================
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.
=====================================================

In <41ADECF8.546@peterskye.com>, on 12/01/04
at 08:10 AM, Peter Skye said:

>Don't need Google, I have the Intel tech manuals. They show the ISA bus
>connected to the PCI bus, similar to SCSI and other connections.

Got a link? I think the diagram you are looking at is leaving out a lot
of significant details and a lot of hardware. Consider what has to happen
between the time the code issues an in or out instruction and the time the
address and data actually make it out the PCI or ISA bus.

>Your def is a bit more broad, but I can't think of a BASEDEV or DEVICE
>that matches yours but not mine.

Look at the USBD.SYS and USBHID.SYS BASEDEVs for example. USBD.SYS in
particular does not even talk to the hardware directly. It's basically a
traffic cop.

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.60b #10183 Warp4/FP15/14.100c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------

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

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".

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

Return to [ 01 | December | 2004 ]

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.