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 | December | 2004 ]

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


Date: Wed, 1 Dec 2004 08:10:40 PST8
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: config.sys bus support ?

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:
>
> >OS/2 has kernel support for the PCI bus. There is also a legacy ISA bus
> >which is connected to the PCI bus, and OS/2 also has kernel support for
> >the ISA bus. Yes?
>
> PCI and ISA are separate buses. You sould be able to find reasonable
> accurate connection diagrams with Google.

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.

> PCMCIA and legacy SCSI stuff connects the the ISA bus.
> Cardbus and newer SCSI HBAs connect to the PCI bus.

Good point, thanks.

> For USB host controllers, there are fewer
> choices (OHCI, UHCI and EHCI) because the
> intefaces to these devices are standardized.

So *that's* what OHCI, UHCI and EHCI are. Thanks.

> >Each device driver is specific to a particular bus and device.
>
> No. The driver is specific to whatever set of hardware the implementor
> chooses to support.

Your def is a bit more broad, but I can't think of a BASEDEV or DEVICE
that matches yours but not mine. I'd like to add one to my notes as an
example if you can think of one offhand.

> >The
> >device drivers are loaded after the bus drivers (otherwise the driver
> >can't communicate with the device because the bus isn't available yet).
> >Yes?
>
> Not really. Where this matters, the basedevs know to hold off until the
> init complete strategy call before attempting to take to other basedevs.

Good, thanks.

- 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 [ 01 | December | 2004 ]



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.