How to write single driver for IP and SCSI?

Hi All,

We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two
drivers into single so that both IP and SCSI works concurrently.

Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

When I did this, I created a driver for the hardware which was a pseudo bus
driver (like the toaster bus example). This driver created PDO’s that the
NDIS miniport and SCSI miniport talked to.

Mark J. Cariddi
Consulting Associate
Open Systems Resources, Inc.
http://www.osr.com/

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com]
Sent: Thursday, June 21, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,

We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two drivers
into single so that both IP and SCSI works concurrently.

Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Write a SCSI miniport driver and then write IP as a SCSI class driver.

Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@Broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com]
Sent: Thursday, June 21, 2001 2:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,

We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two
drivers into single so that both IP and SCSI works concurrently.

Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

How did you handle interrupts, or were you polling?

Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@Broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Mark Cariddi [mailto:xxxxx@osr.com]
Sent: Thursday, June 21, 2001 4:22 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

When I did this, I created a driver for the hardware which was a pseudo bus
driver (like the toaster bus example). This driver created PDO’s that the
NDIS miniport and SCSI miniport talked to.

Mark J. Cariddi
Consulting Associate
Open Systems Resources, Inc.
http://www.osr.com/

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com]
Sent: Thursday, June 21, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,

We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two drivers
into single so that both IP and SCSI works concurrently.

Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

There was no polling involved. The NDIS and SCSI drivers sent requests to
the hardware driver. The Hardware driver did the commands, handled
interrupts, etc… and then called back the NDIS or SCSI driver and told them
that their request was complete.

-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, June 21, 2001 11:40 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

How did you handle interrupts, or were you polling?

Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@Broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Mark Cariddi [mailto:xxxxx@osr.com mailto:xxxxx]
Sent: Thursday, June 21, 2001 4:22 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

When I did this, I created a driver for the hardware which was a pseudo bus
driver (like the toaster bus example). This driver created PDO’s that the
NDIS miniport and SCSI miniport talked to.

Mark J. Cariddi
Consulting Associate
Open Systems Resources, Inc.
http://www.osr.com/ http:</http:>

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com mailto:xxxxx]
Sent: Thursday, June 21, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,

We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two drivers

into single so that both IP and SCSI works concurrently.

Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</mailto:xxxxx></mailto:xxxxx>

I tried that, with the driver set I am developing, but ended up with a 10 ms
delay lump every time the call back from the physical driver had to tell
SCSI an SRB was completed. I found that ScsiPort ignored most SCSI commands
that did not present themselves in the proper context; e.g. originate from
within the context of ScsiPort/ScsiMiniPort. My final answer was to chain
interrupts and provide an interrupt handler that ScsiPort could call to
process a queue that the call back was filling. This gave a transfer rate
within a few points of a pure miniport.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, June 22, 2001 4:00 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

There was no polling involved. The NDIS and SCSI drivers sent requests to
the hardware driver. The Hardware driver did the commands, handled
interrupts, etc… and then called back the NDIS or SCSI driver and told them
that their request was complete.
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, June 21, 2001 11:40 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?
How did you handle interrupts, or were you polling?
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@Broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Mark Cariddi [mailto:xxxxx@osr.com]
Sent: Thursday, June 21, 2001 4:22 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

When I did this, I created a driver for the hardware which was a pseudo bus
driver (like the toaster bus example). This driver created PDO’s that the
NDIS miniport and SCSI miniport talked to.
Mark J. Cariddi
Consulting Associate
Open Systems Resources, Inc.
http://www.osr.com/

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com]
Sent: Thursday, June 21, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,
We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two drivers
into single so that both IP and SCSI works concurrently.
Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

We never saw the problem you are seeing. One thing I should tell you is
that we ended up writing a SCSI Port Driver. We saw > 33% performance
improvement when we changed from a miniport to a port.
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@inland.net]
Sent: Friday, June 22, 2001 9:55 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

I tried that, with the driver set I am developing, but ended up with a 10 ms
delay lump every time the call back from the physical driver had to tell
SCSI an SRB was completed. I found that ScsiPort ignored most SCSI commands
that did not present themselves in the proper context; e.g. originate from
within the context of ScsiPort/ScsiMiniPort. My final answer was to chain
interrupts and provide an interrupt handler that ScsiPort could call to
process a queue that the call back was filling. This gave a transfer rate
within a few points of a pure miniport.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, June 22, 2001 4:00 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

There was no polling involved. The NDIS and SCSI drivers sent requests to
the hardware driver. The Hardware driver did the commands, handled
interrupts, etc… and then called back the NDIS or SCSI driver and told them
that their request was complete.
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, June 21, 2001 11:40 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?
How did you handle interrupts, or were you polling?
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@Broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Mark Cariddi [mailto:xxxxx@osr.com mailto:xxxxx]
Sent: Thursday, June 21, 2001 4:22 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

When I did this, I created a driver for the hardware which was a pseudo bus
driver (like the toaster bus example). This driver created PDO’s that the
NDIS miniport and SCSI miniport talked to.
Mark J. Cariddi
Consulting Associate
Open Systems Resources, Inc.
http://www.osr.com/ http:</http:>

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com mailto:xxxxx]
Sent: Thursday, June 21, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,
We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two drivers

into single so that both IP and SCSI works concurrently.
Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</mailto:xxxxx></mailto:xxxxx>

I can believe that ? ScsiPort is a hell of a lump of overhead.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, June 22, 2001 12:31 PM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

We never saw the problem you are seeing. One thing I should tell you is
that we ended up writing a SCSI Port Driver. We saw > 33% performance
improvement when we changed from a miniport to a port.
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@inland.net]
Sent: Friday, June 22, 2001 9:55 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?
I tried that, with the driver set I am developing, but ended up with a 10 ms
delay lump every time the call back from the physical driver had to tell
SCSI an SRB was completed. I found that ScsiPort ignored most SCSI commands
that did not present themselves in the proper context; e.g. originate from
within the context of ScsiPort/ScsiMiniPort. My final answer was to chain
interrupts and provide an interrupt handler that ScsiPort could call to
process a queue that the call back was filling. This gave a transfer rate
within a few points of a pure miniport.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, June 22, 2001 4:00 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

There was no polling involved. The NDIS and SCSI drivers sent requests to
the hardware driver. The Hardware driver did the commands, handled
interrupts, etc… and then called back the NDIS or SCSI driver and told them
that their request was complete.
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, June 21, 2001 11:40 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?
How did you handle interrupts, or were you polling?
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@Broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Mark Cariddi [mailto:xxxxx@osr.com]
Sent: Thursday, June 21, 2001 4:22 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

When I did this, I created a driver for the hardware which was a pseudo bus
driver (like the toaster bus example). This driver created PDO’s that the
NDIS miniport and SCSI miniport talked to.
Mark J. Cariddi
Consulting Associate
Open Systems Resources, Inc.
http://www.osr.com/

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com]
Sent: Thursday, June 21, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,
We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two drivers
into single so that both IP and SCSI works concurrently.
Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

MessageWe designed our own SCSI port driver with a miniport paradigm just like the MS SCSI port driver. We deseralized the interface and allow the completion of SRBs out of context. This is very fast and eliminates the need to write a new SCSI port driver for each situation.

We license this SCSI port driver (VSPORT) and provide a sample miniport that implements a virtual disk driver. Contact me via email if you are interested.

Jamey Kirby
StorageCraft, Inc.
xxxxx@storagecraft.com

----- Original Message -----
From: Mark Cariddi
To: NT Developers Interest List
Sent: Friday, June 22, 2001 11:31 PM
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

We never saw the problem you are seeing. One thing I should tell you is that we ended up writing a SCSI Port Driver. We saw > 33% performance improvement when we changed from a miniport to a port.
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@inland.net]
Sent: Friday, June 22, 2001 9:55 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

I tried that, with the driver set I am developing, but ended up with a 10 ms delay lump every time the call back from the physical driver had to tell SCSI an SRB was completed. I found that ScsiPort ignored most SCSI commands that did not present themselves in the proper context; e.g. originate from within the context of ScsiPort/ScsiMiniPort. My final answer was to chain interrupts and provide an interrupt handler that ScsiPort could call to process a queue that the call back was filling. This gave a transfer rate within a few points of a pure miniport.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, June 22, 2001 4:00 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

There was no polling involved. The NDIS and SCSI drivers sent requests to the hardware driver. The Hardware driver did the commands, handled interrupts, etc… and then called back the NDIS or SCSI driver and told them that their request was complete.

-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, June 21, 2001 11:40 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

How did you handle interrupts, or were you polling?

Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@Broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Mark Cariddi [mailto:xxxxx@osr.com]
Sent: Thursday, June 21, 2001 4:22 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

When I did this, I created a driver for the hardware which was a pseudo bus
driver (like the toaster bus example). This driver created PDO’s that the
NDIS miniport and SCSI miniport talked to.

Mark J. Cariddi
Consulting Associate
Open Systems Resources, Inc.
http://www.osr.com/

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com]
Sent: Thursday, June 21, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,

We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two drivers
into single so that both IP and SCSI works concurrently.

Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

MessageYes, using our VSPORT will eliminate the need to use a callback.

Jamey
----- Original Message -----
From: Gary G. Little
To: NT Developers Interest List
Sent: Friday, June 22, 2001 5:54 PM
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

I tried that, with the driver set I am developing, but ended up with a 10 ms delay lump every time the call back from the physical driver had to tell SCSI an SRB was completed. I found that ScsiPort ignored most SCSI commands that did not present themselves in the proper context; e.g. originate from within the context of ScsiPort/ScsiMiniPort. My final answer was to chain interrupts and provide an interrupt handler that ScsiPort could call to process a queue that the call back was filling. This gave a transfer rate within a few points of a pure miniport.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, June 22, 2001 4:00 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

There was no polling involved. The NDIS and SCSI drivers sent requests to the hardware driver. The Hardware driver did the commands, handled interrupts, etc… and then called back the NDIS or SCSI driver and told them that their request was complete.

-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, June 21, 2001 11:40 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

How did you handle interrupts, or were you polling?

Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@Broadstor.com
xxxxx@inland.net

-----Original Message-----
From: Mark Cariddi [mailto:xxxxx@osr.com]
Sent: Thursday, June 21, 2001 4:22 AM
To: NT Developers Interest List
Subject: [ntdev] RE: How to write single driver for IP and SCSI?

When I did this, I created a driver for the hardware which was a pseudo bus
driver (like the toaster bus example). This driver created PDO’s that the
NDIS miniport and SCSI miniport talked to.

Mark J. Cariddi
Consulting Associate
Open Systems Resources, Inc.
http://www.osr.com/

-----Original Message-----
From: Indira [mailto:xxxxx@uiscpl.com]
Sent: Thursday, June 21, 2001 5:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to write single driver for IP and SCSI?

Hi All,

We are developing a NDIS miniport driver and a SCSI miniport driver for
Fibre channel Protocol. Now the problem is how to combine these two drivers
into single so that both IP and SCSI works concurrently.

Thanks in advance,
Indira

You may not be the master of your fate…but
You are the captain of your soul.


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com