Mark is correct. I’m currently writing a bus driver that has all of above
(below).
Basically it comes down the this: If your bus driver ONLY needs to
enumerate devices it won’t have an StartIo/ISR/DPC. If it needs to take the
role of a function driver (like ScsiPort does) it will.
Daniel Nemiroff
System Software Engineering
Intel Corp.
-----Original Message-----
From: Mark Roddy [mailto:xxxxx@hollistech.com]
Sent: Friday, May 05, 2000 5:37 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Bus Driver: clarification needed
Well I completely disagree.
Take the case of a SCSI port bus driver or a USB bus driver. These drivers
have ISRs, DPCs, may or may not (hopefully not) have startio routines, may
very well queue irps, and are deeply involved in IO processing of IRPs. They
are also both Function drivers on standard busses such as PCI. This dual
role requires all the standard IO processing of a lowest leve driver in
addition to bus management activity.
Mark Roddy
Windows 2000/NT Consultant
Hollis Technology Solutions
www.hollistech.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
Sent: Thursday, May 04, 2000 2:03 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Bus Driver: clarification needed
Although the DDK has no explicit mention, my understanding is that
a Bus Driver would not have the following:
-Interrupt Service Routine
-DPC routine
-StartIO Routine
-Any driver-specific IRP-queueing mechanism
Usually yes. Bus driver usually responds to PnP IRPs only and to hardware
events (device arrival/removal) on the underlying bus.
Though nothing prevents you from having a bus driver which will have some
other semantics on PDOs - like reads, writes or IOCTLs.
Max
You are currently subscribed to ntdev as: xxxxx@wattanuck.mv.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)