Identify target USB Pipe

NTDEV
1

Hello,

my USB device has several bulk-in-pipes. How can tell my application my
driver from which endpoint it should try to read?
Is it possible to send this information with the CreateFile or Readfile
operation? If yes, how can I get that information in my DispatchReadWrite
function?

Best regards

Frank

2

Look at the bulkusb sample in the DDK. It demonstrates exactly what you
are asking, how to address different components in a create file call.

D

This posting is provided “AS IS” with no warranties, and confers no
rights

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmx.com
Sent: Tuesday, December 02, 2003 5:01 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Identify target USB Pipe

Hello,

my USB device has several bulk-in-pipes. How can tell my application my
driver from which endpoint it should try to read?
Is it possible to send this information with the CreateFile or Readfile
operation? If yes, how can I get that information in my
DispatchReadWrite
function?

Best regards

Frank

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

A traditional way would be to use the pipe number as part of the device file
name, and assume the application knows the pipe number it wants to talk to.
This has the disadvantage of tying the application to that one
implementation, and if the device changes later (for instance, you use a
cheaper chip that only supports different pipe numbers) then you have to do
a mapping in the driver or application.

Or, on rereading your post, is your question that you have multipe input
pipes, and data will sometimes appear at one and sometimes another, and the
application has to somehow know where the data is appearing? If so, you
could either multiplex the input pipes to a single file interface and
preface the device data with a pipe indicator. Or you could create an
interface for each pipe and let the application hang async reads on all of
them and do a multiple wait on the overlapped events.

Loren