Dear all
(This email for Numega driverworks users…)
I have found a seriouse bug in nuemega driverworks kusb.cpp file.
Bug Discr:
if you tried to change the maximum transfer size, the pipe information never altered and refuse to perform any data transfer because buffer is larger than its reprted transfer size (which is normally 0x1000).
I’m trying to overcome this bug in PreconfigureInterface and Configuere Functions.
any one have suggestions to me please inform.
bye
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
Hello,
I have found a seriouse bug in nuemega driverworks kusb.cpp file.
Bug Discr:
if you tried to change the maximum transfer size, the pipe information never altered and refuse to perform any data transfer because buffer is larger than its reprted transfer size (which is normally 0x1000).
I’m trying to overcome this bug in PreconfigureInterface and Configuere Functions.
any one have suggestions to me please inform.
what pipe type do you use ?. The transfer size from PIPE descriptor
are important. This is the fifo size of you USB hardware.
I have changed some VDW USB code and the change transfer size stuff
ist no longer running in my drivers.
elli
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
Hi Elli
I’m Using a bulk transfer pipe …??
what is the restriction
----- Original Message -----
From: “Mathias Ellinger”
To: “NT Developers Interest List”
Sent: Tuesday, February 06, 2001 3:01 PM
Subject: [ntdev] Re: Numega Driverworks USB bug
> Hello,
>
> >I have found a seriouse bug in nuemega driverworks kusb.cpp file.
> >Bug Discr:
> >if you tried to change the maximum transfer size, the pipe information
never altered and refuse to perform any data transfer because buffer is
larger than its reprted transfer size (which is normally 0x1000).
> >I’m trying to overcome this bug in PreconfigureInterface and Configuere
Functions.
> >any one have suggestions to me please inform.
>
>
> what pipe type do you use ?. The transfer size from PIPE descriptor
> are important. This is the fifo size of you USB hardware.
>
> I have changed some VDW USB code and the change transfer size stuff
> ist no longer running in my drivers.
>
> elli
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yahoo.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.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
Hallo,
I have used USB bulk transfer for ACL Pipes from Bluetooth USB
adapters. The Fifo size from USB adapter is 64 so I call the
KUsbPipe::Initialize with this value.
When I setup USB bulk Read than I use a large buffer for my
whole high level frame and set the short transfer OK flag in
the URB request.
I have written a USB libray on top of the VDW Kusb stuff. The VDW
stuff is to low level and for all USB adapter I need always the same
code, so I have classes for the control pipe, interrupts pipes,
iso pipes, bulk pipes and last not least a base class for a
USB device itself. Six drivers for different USB adapters for the
last year …
elli
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
hi elli
what are you try to say here ??
you are not using the NUMEGA usb implementation ??!
if so you will not face my problem and I will be pleased if you shared these
new implimintations with me.
anyhow I have fixed the bug of seeting maximum transfer sizes
please inform me if you want the bug fix
bye
----- Original Message -----
From: “Mathias Ellinger”
To: “NT Developers Interest List”
Sent: Tuesday, February 06, 2001 7:25 PM
Subject: [ntdev] Re: Numega Driverworks USB bug
> Hallo,
>
> I have used USB bulk transfer for ACL Pipes from Bluetooth USB
> adapters. The Fifo size from USB adapter is 64 so I call the
> KUsbPipe::Initialize with this value.
>
> When I setup USB bulk Read than I use a large buffer for my
> whole high level frame and set the short transfer OK flag in
> the URB request.
>
> I have written a USB libray on top of the VDW Kusb stuff. The VDW
> stuff is to low level and for all USB adapter I need always the same
> code, so I have classes for the control pipe, interrupts pipes,
> iso pipes, bulk pipes and last not least a base class for a
> USB device itself. Six drivers for different USB adapters for the
> last year …
>
> elli
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yahoo.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.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
hi
you are not using the NUMEGA usb implementation ??!
Often I use the implementation but some times the KUsb code is not usefull.
anyhow I have fixed the bug of seeting maximum transfer sizes
I never increase the transfer size. I don’t know why the transfer
logic is inside the code, I can see no reason to use it, so I need no fix.
Why you will increase the transfer size ?
elli
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
I am increasing the transfer size to test the speed of transferring large
amount of data usong full speed usb bulk transfer.
----- Original Message -----
From: “Mathias Ellinger”
To: “NT Developers Interest List”
Sent: Wednesday, February 07, 2001 2:44 PM
Subject: [ntdev] Re: Numega Driverworks USB bug
> hi
>
> > you are not using the NUMEGA usb implementation ??!
>
> Often I use the implementation but some times the KUsb code is not
usefull.
>
> >anyhow I have fixed the bug of seeting maximum transfer sizes
>
> I never increase the transfer size. I don’t know why the transfer
> logic is inside the code, I can see no reason to use it, so I need no fix.
> Why you will increase the transfer size ?
>
> elli
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yahoo.com
> To unsubscribe send a blank email to xxxxx@lists.osr.co
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.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
ok, you can always read/write a large block in a usbd URB request.
This size is independet from your pipe fifo size.
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