SCOUG-HELP Mailing List Archives

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

Date:	Tue, 30 Nov 2004 23:46:23 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 <41AC579F.678F@peterskye.com>, on 11/30/04
at 03:21 AM, Peter Skye said:

>On Intel-based machines the microprocessor is connected to the PCI bus.

Indirectly via interface chipsets.

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

>If you have a PCMCIA, SCSI and/or USB bus then those buses are connected
>to the PCI bus

It depends on the HBA. PCMCIA and legacy SCSI stuff connects the the ISA
bus. Cardbus and newer SCSI HBAs connect to the PCI bus. Of course
there's nothing to stop on from connecting SCSI bus devices via PCMCIA,
Cardbus and USB.

>Can anyone give me a
>typical BASEDEV= for the PCMCIA or USB bus?)

For PCMCIA there are literally scores of different basedevs. One for each
unique socket services chipset. For USB host controllers, there are fewer
choices (OHCI, UHCI and EHCI) because the intefaces to these devices are
standardized.

>Each device is connected to a bus and you need a driver for each device.

At least one. Some devices require both a basedev and a filter driver.

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

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

>Are there any other OS/2-supported buses which I've missed?

Yes.

>I mentioned
>PCI, ISA, PCMCIA, SCSI, USB. I didn't include IDE because the IDE bus
>control is actually done at the PCI level as far as I know

Only on newer hardware. The original IDE devices hung of the ISA bus.

>LPT parallel port controlling a printer).

There are both ISA and PCI connected parallel port.

>There are lots of other buses
>-- firewire/ieee1394, hpib, gpib, esdi come to mind -- but I don't know
>if any have OS/2 drivers.

Many do. Support is just not available for every device.

Steven

--
----------------------------------------------------------------------
"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 [ 30 | November | 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.