libusb-win32-devel

Re: [Libusb-win32-devel] win-libusb async read

[Stephan M. <ste...@we...>]

See 

http://sourceforge.net/mailarchive/message.php?msg_id=10083829



> I got the simple bulk write/read to work. However, I would like to have a 
> thread waiting on the read all the time and process the read data 
> independent of the write. How would I implement async read using the libusb? 
> anyone has an example?
> 
> thanks
> Andrew
> 
> 
> 
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!		
Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130

[Libusb-win32-devel] win-libusb async read

[Andrew X. <xi...@gr...>]

I got the simple bulk write/read to work. However, I would like to have a 
thread waiting on the read all the time and process the read data 
independent of the write. How would I implement async read using the libusb? 
anyone has an example?

thanks
Andrew

Re: [Libusb-win32-devel] usb_claim_interface : invalid argument

[Mark B. <mb...@ze...>]

Have you called usb_set_configuration first? You need to do that before 
claiming an interface. Also I think interfaces are numbered from 0, so 0 
might be a valid interface but not 1 (not being sure what you passed to 
usb_claim_interface, I thought that might be worth mentioning).

You probably need administrative privileges to install the driver, but 
not to run the software. If in doubt, try running it as administrator 
and see if it works.

Mark.


Ben wrote:

>Hello
>
>I am trying to use libusb on WinXP
>to operate ftdi chip in bitbang mode.
>I've created inf file and successfully
>installed the device driver (not filter driver). 
>Using supplied test program I see the device. 
>But when  I run my program usb_claim_interface
>fails. I've checked that no other drivers
>use the device.  What actually happens
>is that DeviceIoControl inside  usb_claim_interface
>returns error with description "invalid argument".
>The same code works fine on Linux.
>Do I need administrative
>privileges  to use libusb ?
>
>thanks
>
>
>
>
>
>_______________________________________________
>Libusb-win32-devel mailing list
>Lib...@li...
>https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>  
>

[Libusb-win32-devel] usb_claim_interface : invalid argument

[Ben <bn...@ya...>]

Hello

I am trying to use libusb on WinXP
to operate ftdi chip in bitbang mode.
I've created inf file and successfully
installed the device driver (not filter driver). 
Using supplied test program I see the device. 
But when  I run my program usb_claim_interface
fails. I've checked that no other drivers
use the device.  What actually happens
is that DeviceIoControl inside  usb_claim_interface
returns error with description "invalid argument".
The same code works fine on Linux.
Do I need administrative
privileges  to use libusb ?

thanks

Re: [Libusb-win32-devel] 40Hz mouse polling rate?

[Bob S. <m24...@ho...>]

That method is still going to be problematic.

The idea I had for libusb-win32 was to use it as an alternative input method 
for a Quake engine port.

The reason is that GDI input, Windows XP rawinput, and DirectInput have a 
few issues:
- Windows XP rawinput only works with Windows XP, and 2000 is a target 
platform.
- DirectInput will enumerate more than 1 mouse only under Windows 98SE or 
ME.
- GDI input can't register separate mouse inputs.
- Some gaming mice report extra information not properly handled.
- Different model mice only report certain buttons to different API. (As in 
some only report all buttons to DirectInput, some only report to GDI, some 
only to rawinput)

Thus libusb-win32 looked like a possible alternative. Unfortunately, 
considering the drop-in nature of the engine itself, the user base probably 
wouldn't be too comfortable with installing specific device drivers.

Re: [Libusb-win32-devel] 40Hz mouse polling rate?

[Stephan M. <ste...@we...>]

> There aren't any alternatives to using a specific device driver? 

There are alternatives, but none of them is easier than installing
a custom device driver.

> Unfortunately that approach just isn't user friendly enough for my needs.

You could automate the installation process by writing an installer.
I did the same some months ago by writing an installer for the 
CueCat device (http://en.wikipedia.org/wiki/Cuecat) which is some
kind of HID keyboard.

I attached the installer script I wrote. It's pretty simple and easy to modify.

Stephan


> 
> 
> 
> 
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

Re: [Libusb-win32-devel] 40Hz mouse polling rate?

[Bob S. <m24...@ho...>]

There aren't any alternatives to using a specific device driver? 
Unfortunately that approach just isn't user friendly enough for my needs.

Re: [Libusb-win32-devel] 40Hz mouse polling rate?

[Stephan M. <ste...@we...>]

> I'm trying to use libusb to retrieve mouse input, and I've noticed that =
when=20
> using a loop containing usb=5Finterrupt=5Fread in the form of a separate thr=
ead,=20
> WM=5FTIMER, or brute force iterations, that the loop runs at 40Hz (40 mous=
e=20
> inputs per second). The only exception is when I use the asynchronous re=
ad=20
> API calls and use about 8 contexts, then getting a rate of about 90-110=20
> inputs per second. I noticed by using that hack of a method that the OS=20
> cursor was getting erratic, which suggests the OS is still fighting over=
 the=20
> inputs for the device.
>=20
> The questions I have are...
> 1. What's causing this 40Hz frequency instead of the expected 125Hz=3F

That's because two driver are simultaniously reading from the mouse,
Windows' hid driver and libusb's (filter) driver.

> 2. Is it possible to get libusb-win32 to have exclusive access over the=20
> device=3F

Yes that's possible by installing libusb as a device driver for the mouse
instead of using the filter. Please note that after installing the device
driver your mouse won't work as a 'normal' mouse any more because
Windows will be unable to read from it. So I would recommend
connecting a second mouse to the system if you don't want to control
Windows using the keyboard.

To install the device driver follow these steps:

1. uninstall the filter driver

2. get the libusb-win32-device-bin-xxxx.tar.gz package

3. launch the inf-wizard.exe tool (from the /bin folder) and create an=20
.inf file for your mouse

4. go to the c:\windows\inf folder and open input.inf with Notepad

5. add some meaningless comments to the top of the file and save it
These modifications will break the hid driver's digital signature. This
is necessary to install libusb's kernel driver because it's 'unsigned'.

6. open the Device Manager, locate your mouse, and update its driver
by pointing Windows to the .inf file you created in step 3.

7. unplug und replug the mouse

8. go to the Device Manager and verify that the mouse shows up under
the 'Libusb-win32 Devices' section


Hope this helps,
Stephan


>=20
>=20
>=20
>=20
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=

Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfach!	=09
Mehr Infos unter http://freemail.web.de/home/landingpad/=3Fmc=3D021131

Re: [Libusb-win32-devel] LibUSB and Thread

[Stephan M. <ste...@we...>]

Libusb works with threads (test program attached).

Stephan


> Hello,
> 
>  
> 
> It seems that it is not possible to use the API of LibUSB in conjonction with several thread.
> 
> If I set the read bulk in a dedicated thread the API returns error.
> 
> Is there a special way to deal with thread ?
> 
> I will appreciate if someone can help me in this domain.
> 
> Jean-Michel
> 
> -----------------------------------------------------------------
> 
> -----------------------------------------------------------------
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

[Libusb-win32-devel] LibUSB and Thread

[Jean M. B. <jmb...@ie...>]

Hello,
=20
It seems that it is not possible to use the API of LibUSB in conjonction =
with several thread.
If I set the read bulk in a dedicated thread the API returns error.
Is there a special way to deal with thread ?
I will appreciate if someone can help me in this domain.
Jean-Michel

[Libusb-win32-devel] 40Hz mouse polling rate?

[Bob S. <m24...@ho...>]

I'm trying to use libusb to retrieve mouse input, and I've noticed that when 
using a loop containing usb_interrupt_read in the form of a separate thread, 
WM_TIMER, or brute force iterations, that the loop runs at 40Hz (40 mouse 
inputs per second). The only exception is when I use the asynchronous read 
API calls and use about 8 contexts, then getting a rate of about 90-110 
inputs per second. I noticed by using that hack of a method that the OS 
cursor was getting erratic, which suggests the OS is still fighting over the 
inputs for the device.

The questions I have are...
1. What's causing this 40Hz frequency instead of the expected 125Hz?
2. Is it possible to get libusb-win32 to have exclusive access over the 
device?

Re: [Libusb-win32-devel] who does the set_address?

[Stephan M. <ste...@we...>]

A detailed description of the enumeration process can be found here:

http://www.lvr.com/usbcenum.htm



> How come when I use atmel's kernel mode driver, I receive the set=5Faddres=
s command.
>=20
> But when I use libusb kernel driver, I don't get the set=5Faddress command=
=3F
>=20
> =20
>=20
> -Andrew
>=20
> =20
> =20
> ----- Original Message -----=20
> =20
> From: Dan Ellis=20
> =20
> To: Andrew Xiang ; lib...@li... ; libusb-win=
32-...@li...=20
> =20
> Sent: Wednesday, June 14, 2006 6:07 PM
> =20
> Subject: Re: [Libusb-win32-devel] who does the set=5Faddress=3F
> =20
>=20
> =20
> =20
> The operating system sets the address before the driver is loaded.
> =20
> =20
> =20
> Dan.
> =20
>=20
> =20
> -----------------------------------------------------------------
>  From: lib...@li... on behalf of And=
rew Xiang
> Sent: Wed 14/06/2006 20:54
> To: lib...@li...
> Subject: [Libusb-win32-devel] who does the set=5Faddress=3F
>=20
> =20
> =20
>=20
> I am not getting the set=5Faddress command on my SAM7S device by running t=
he=20
> libusb kernel mode driver.=20
> If the address is not set, the device does not get setup properly.=20
> =20
>=20
> I did get the set=5Faddress command if I used the driver from the atmel, b=
ut=20
> that driver only comes with binary and functions limited.=20
> =20
>=20
> Who is responsible for sending out the set=5Faddress=3F=20
> =20
>=20
> thanks=20
> Andrew=20
>=20
> =20
>=20
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=20
> Libusb-win32-devel mailing list=20
> Lib...@li...=20
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel=20
> =20
>=20
> =20
> -----------------------------------------------------------------
> =20
>=20
> =20
>=20
> =20
> -----------------------------------------------------------------
> =20
>=20
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>=20
> -----------------------------------------------------------------
>=20
> -----------------------------------------------------------------
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>=20


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=

Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfach!	=09
Mehr Infos unter http://freemail.web.de/home/landingpad/=3Fmc=3D021131

Re: [Libusb-win32-devel] who does the set_address?

[Andrew X. <xi...@gr...>]

[Libusb-win32-devel] who does the set_address?How come when I use =
atmel's kernel mode driver, I receive the set_address command.
But when I use libusb kernel driver, I don't get the set_address =
command?

-Andrew

  ----- Original Message -----=20
  From: Dan Ellis=20
  To: Andrew Xiang ; lib...@li... ; =
lib...@li...=20
  Sent: Wednesday, June 14, 2006 6:07 PM
  Subject: Re: [Libusb-win32-devel] who does the set_address?


  The operating system sets the address before the driver is loaded.

  Dan.


-------------------------------------------------------------------------=
-----
  From: lib...@li... on behalf of =
Andrew Xiang
  Sent: Wed 14/06/2006 20:54
  To: lib...@li...
  Subject: [Libusb-win32-devel] who does the set_address?


  I am not getting the set_address command on my SAM7S device by running =
the=20
  libusb kernel mode driver.=20
  If the address is not set, the device does not get setup properly.=20

  I did get the set_address command if I used the driver from the atmel, =
but=20
  that driver only comes with binary and functions limited.=20

  Who is responsible for sending out the set_address?=20

  thanks=20
  Andrew=20




  _______________________________________________=20
  Libusb-win32-devel mailing list=20
  Lib...@li...=20
  https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel=20



-------------------------------------------------------------------------=
-----




-------------------------------------------------------------------------=
-----


  _______________________________________________
  Libusb-win32-devel mailing list
  Lib...@li...
  https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Limit on Maximum Asynchronous URBs

[Stephan M. <ste...@we...>]

Libusb's kernel driver limits the maximum data size to 64k for
each URB although Windows' host controller drivers support
larger sizes.

See: http://support.microsoft.com/default.aspx=3Fscid=3Dkb;%5BLN%5D;832430



> Thank you Stephan.  That information is useful.
>=20
> One question though.  I wasn't aware that the maximum URB size was 64 kB=
 in=20
> Windows.  Is this true=3F  In Linux I believe the maximum is 16384 (and on=
ly=20
> with Kernel versions 2.6 and up).
>=20
> Gopal
>=20
>=20
> On Tuesday 13 June 2006 10:18, Stephan Meyer wrote:
> > Libusb's kernel driver doesn't have any built-in limitations because
> > it doesn't internally queue any data. It just allocates an URB for eac=
h
> > userspace request and passes that URB down the stack.
> >
> > But it should be obvious that the host controller driver has to queue
> > these request and that the size of this queue is limited since kernel
> > memory is a limited resource.
> >
> > I wrote a small test program (see attachment) to see how many requests=

> > Windows' USB stack can handle at once. And the limit on WinXP-SP2
> > (with 1GB of RAM) seems to be exactly 2500 URBs regardless of the URB'=
s
> > data size.
> >
> > The maximum amount of data I was able to request at once with the test=

> > program was 2500 URB each with 64kB of data. That's more than 150MB!
> >
> > This limit may depend on the host controller driver and the Windows
> > version.
> >
> >
> > Stephan
> >
> > > Hi all,
> > >
> > > I did some poking around on the web but have had a hard time finding=
 an
> > > answer to this question.  Maybe someone here knows.
> > >
> > > Is there a maximum number of URBs that can be submitted to an endpoi=
nt /
> > > interface / device at any given time=3F  For example, can I submit 102=
4
> > > URBs each with 16 KB data to a read endpoint or will I be restricted=
 by
> > > the driver stack, host controller, or something else=3F  If there is s=
uch a
> > > restriction, does it apply to the device as a whole, just the interf=
ace,
> > > or just the endpoint=3F
> > >
> > > Any insights would be much appreciated.
> > >
> > > Best regards,
> > > Gopal
> > >
> > >
> > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> > > Libusb-win32-devel mailing list
> > > Lib...@li...
> > > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >
> > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F
> > Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfac=
h!
> > Mehr Infos unter http://freemail.web.de/home/landingpad/=3Fmc=3D021131
>=20
>=20
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!	=09
Jetzt gratis testen! http://freemail.web.de/home/landingpad/=3Fmc=3D021130

Re: [Libusb-win32-devel] who does the set_address?

[Dan E. <Dan...@ne...>]

The operating system sets the address before the driver is loaded.
=20
Dan.

________________________________

From: lib...@li... on behalf of =
Andrew Xiang
Sent: Wed 14/06/2006 20:54
To: lib...@li...
Subject: [Libusb-win32-devel] who does the set_address?



I am not getting the set_address command on my SAM7S device by running =
the=20
libusb kernel mode driver.=20
If the address is not set, the device does not get setup properly.=20

I did get the set_address command if I used the driver from the atmel, =
but=20
that driver only comes with binary and functions limited.=20

Who is responsible for sending out the set_address?=20

thanks=20
Andrew=20



_______________________________________________=20
Libusb-win32-devel mailing list=20
Lib...@li...=20
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel=20

Re: [Libusb-win32-devel] Limit on Maximum Asynchronous URBs

[Gopal S. <go...@ne...>]

Thank you Stephan.  That information is useful.

One question though.  I wasn't aware that the maximum URB size was 64 kB in=
=20
Windows.  Is this true?  In Linux I believe the maximum is 16384 (and only=
=20
with Kernel versions 2.6 and up).

Gopal


On Tuesday 13 June 2006 10:18, Stephan Meyer wrote:
> Libusb's kernel driver doesn't have any built-in limitations because
> it doesn't internally queue any data. It just allocates an URB for each
> userspace request and passes that URB down the stack.
>
> But it should be obvious that the host controller driver has to queue
> these request and that the size of this queue is limited since kernel
> memory is a limited resource.
>
> I wrote a small test program (see attachment) to see how many requests
> Windows' USB stack can handle at once. And the limit on WinXP-SP2
> (with 1GB of RAM) seems to be exactly 2500 URBs regardless of the URB's
> data size.
>
> The maximum amount of data I was able to request at once with the test
> program was 2500 URB each with 64kB of data. That's more than 150MB!
>
> This limit may depend on the host controller driver and the Windows
> version.
>
>
> Stephan
>
> > Hi all,
> >
> > I did some poking around on the web but have had a hard time finding an
> > answer to this question.  Maybe someone here knows.
> >
> > Is there a maximum number of URBs that can be submitted to an endpoint /
> > interface / device at any given time?  For example, can I submit 1024
> > URBs each with 16 KB data to a read endpoint or will I be restricted by
> > the driver stack, host controller, or something else?  If there is such=
 a
> > restriction, does it apply to the device as a whole, just the interface,
> > or just the endpoint?
> >
> > Any insights would be much appreciated.
> >
> > Best regards,
> > Gopal
> >
> >
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
> __________________________________________________________________________
> Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfach!
> Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=3D021131

[Libusb-win32-devel] who does the set_address?

[Andrew X. <xi...@gr...>]

I am not getting the set_address command on my SAM7S device by running the
libusb kernel mode driver.
If the address is not set, the device does not get setup properly.

I did get the set_address command if I used the driver from the atmel, but
that driver only comes with binary and functions limited.

Who is responsible for sending out the set_address?

thanks
Andrew

Re: [Libusb-win32-devel] Limit on Maximum Asynchronous URBs

[Stephan M. <ste...@we...>]

Libusb's kernel driver doesn't have any built-in limitations because
it doesn't internally queue any data. It just allocates an URB for each
userspace request and passes that URB down the stack.

But it should be obvious that the host controller driver has to queue
these request and that the size of this queue is limited since kernel=20
memory is a limited resource.

I wrote a small test program (see attachment) to see how many requests
Windows' USB stack can handle at once. And the limit on WinXP-SP2=20
(with 1GB of RAM) seems to be exactly 2500 URBs regardless of the URB's=20
data size.

The maximum amount of data I was able to request at once with the test=20
program was 2500 URB each with 64kB of data. That's more than 150MB!

This limit may depend on the host controller driver and the Windows versio=
n.


Stephan



> Hi all,
>=20
> I did some poking around on the web but have had a hard time finding an =
answer=20
> to this question.  Maybe someone here knows.
>=20
> Is there a maximum number of URBs that can be submitted to an endpoint /=
=20
> interface / device at any given time=3F  For example, can I submit 1024 UR=
Bs=20
> each with 16 KB data to a read endpoint or will I be restricted by the d=
river=20
> stack, host controller, or something else=3F  If there is such a restricti=
on,=20
> does it apply to the device as a whole, just the interface, or just the=20
> endpoint=3F
>=20
> Any insights would be much appreciated.
>=20
> Best regards,
> Gopal
>=20
>=20
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=

Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfach!	=09
Mehr Infos unter http://freemail.web.de/home/landingpad/=3Fmc=3D021131

[Libusb-win32-devel] Limit on Maximum Asynchronous URBs

[Gopal S. <go...@ne...>]

Hi all,

I did some poking around on the web but have had a hard time finding an answer 
to this question.  Maybe someone here knows.

Is there a maximum number of URBs that can be submitted to an endpoint / 
interface / device at any given time?  For example, can I submit 1024 URBs 
each with 16 KB data to a read endpoint or will I be restricted by the driver 
stack, host controller, or something else?  If there is such a restriction, 
does it apply to the device as a whole, just the interface, or just the 
endpoint?

Any insights would be much appreciated.

Best regards,
Gopal

Re: [Libusb-win32-devel] libusb-win32-snapshots on WinXP fails withpyUSB

[Dan E. <Dan...@ne...>]

That's correct, you need to rebuild pyusb with the .lib file from the
release (you don't need to worry about the actual sources to the library
or the driver).
=20
To rebuild you just execute setup.py for pyusb.
=20
Dan.

________________________________

From: lib...@li...
[mailto:lib...@li...] On Behalf Of
Ray Schumacher
Sent: 08 June 2006 19:05
To: lib...@li...
Subject: [Libusb-win32-devel] libusb-win32-snapshots on WinXP fails
withpyUSB


I just tried installing the 20060518
<http://sourceforge.net/project/showfiles.php?group_id=3D78138&package_id=
=3D
121441&release_id=3D417945>  release (after uninstalling what I could of
0.1.10.1)
the test showed  0.1.10.2; running gives an "ordinal xx not found in
libusb0" error

I'm presuming that I need to compile pyUSB with the newest win32-libusb
sources, correct?

Any suggestions for upgrade procedure?
I just wanted to be sure that I had the latest bug fixes from libUSB, as
I'm debugging this Python app with a TI device. (I'm getting data drops)
Using a new Tyan MB  and Opteron

Thanks,
Ray=20

[Libusb-win32-devel] libusb-win32-snapshots on WinXP fails with pyUSB

[Ray S. <ra...@bl...>]

I just tried installing the <http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=121441&release_id=417945>20060518 release (after uninstalling what I could of 0.1.10.1)
the test showed  0.1.10.2; running gives an "ordinal xx not found in libusb0" error

I'm presuming that I need to compile pyUSB with the newest win32-libusb sources, correct?

Any suggestions for upgrade procedure?
I just wanted to be sure that I had the latest bug fixes from libUSB, as I'm debugging this Python app with a TI device. (I'm getting data drops)
Using a new Tyan MB  and Opteron

Thanks,
Ray 

[Libusb-win32-devel] making USB drive write protected

[taneem k. <tan...@ya...>]

Hi all,
 I am very new in developing applications for USB. I
am  just trying to give it a start. I am trying this
library to develop a software of mine. What I want is
to make my USB ZIP drive write protected on and off
through this library. Is it  possible? If yes, can
someone pls give me some starting boost with some
example source code? Thank you all in advance. Your
help will be really appreciated.  

Regards
Taneem Khurshed

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Libusb-win32-devel] FW: SUBJECT: SourceForge.net: CVS service offering changes

[Stephan M. <ste...@we...>]

FYI.



Greetings,

You are receiving this mail because you are a project admin for
a SourceForge.net-hosted project. One of our primary services,
CVS, suffered a series of interrelated, critical hardware failures
in recent weeks. We understand how frustrating this CVS outage
must be to you and your users; however, our top priority remains
preservation of the integrity of your data.

The series of CVS hardware failures prompted us to expedite the
deployment of planed improvements to our CVS infrastructure,
drawing upon much of the knowledge that we gained from our
Subversion deployment. Our improved CVS service architecture,
which we plan to deploy tomorrow afternoon (2006-05-12), will
offer greater performance and stability and will eliminate several
single points of failure.

The Site Status page (https://www.sf.net/docs/A04) will be
updated as soon as the new infrastructure is rolled out. In the
interim, please read the important information provided below
to learn about how these changes will affect your project.


Summary of changes, effective 2006-05-12:


1. Hostname for CVS service

Old: cvs.sourceforge.net

New: PROJECT_UNIX_NAME.cvs.sourceforge.net

This change will require new working copies to be checked out of all
repositories (so control files in the working copy will point to the
right place). We will be updating the instructions we supply, but
instructions that your team has written within documentation, etc. will
need to be updated.

cvs -d:pserver:ano...@cv...:/cvsroot/gaim co gaim

would be changed to

cvs -d:pserver:ano...@ga...:/cvsroot/gaim co gaim



2. ViewCVS

We are moving from ViewCVS to its successor, ViewVC. ViewVC is
currently in use for our Subversion service.



3. Sync delay

Old: CVS pserver, tarballs and ViewCVS provided against a separate
server which is a minimum of three hours behind developer CVS.

New: ViewVC will be provided against developer CVS (it will be current).
CVS pserver will be provided against a secondary server (not developer
server) with a maximum expected delay of two hours.

Follow-up work is planned (this infrastructure takes us 80% of the way)
to essentially eliminate the sync delay.



4. Read-only rsync service

As a new service offering, we are now providing read-only rsync access
against developer CVS. This allows projects to efficiently make
on-demand backups of their entire CVS repository.

All projects should be making regular backups of their CVS repository
contents using this service.



5. Nightly tarball service

Nightly tarball service is being dropped in lieu of read-only rsync
service. Projects which currently depend on nightly tarballs for
repository backups will need to begin using rsync to make a backup copy
of their repository contents.

We see this as a major functional improvement. For a number of reasons,
tarballs have fallen out of sync with the data in the repository at
times in the past few years. Tarballs required a substantial amount of
additional disk, and I/O to generate. The move to read-only rsync
allows backups to be produced on-demand, with an update frequency chosen
by the project.



6. Points of failure

In the past, developer CVS service for all projects was provided from a
single host. CVS pserver service was provided from individual backend
heads based on a split of the data.

Under our new design, developer CVS and most of our CVS-related services
are provided from one of ten CVS hosts (count subject to increase with
growth). Each host is independent, and makes a backup copy of the
repository data of another host (which is used to provide the pserver
CVS service).

Failure of a single host will impact only the availability of data on
that host. Since the data is split among a larger number of hosts, the
size of data impacted by an individual host outage is substantially
smaller, and the time required for us to restore service will be
substantially shorter.

This rapid architecture change has been made possible specifically using
the research we performed for our recent launch of Subversion service.
We've applied our best practices, produced a substantial amount of
internal documentation, and kept an eye toward maintainability.
This effort has allowed us to deploy this new architecture quickly
once hardware was received, and will permit us to quickly scale
this service horizontally as growth and demand requires. 



Many other minor improvements have also been made to improve the service
offering and make it less trouble-prone. The most important of which are
listed above. For a full description of the new service offering, and
for information on how to use the services described above, please refer
to the site documentation for the CVS service after the service has been
launched: https://www.sf.net/docs/E04


Thank you,

The SourceForge.net Team 

.


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

Re: [Libusb-win32-devel] Fix for coming out of standby

[Stephan M. <ste...@we...>]

Thanks for the patch, Dan. I'll apply it by adding a third parameter
to power_set_device_state():


void power_set_device_state(libusb_device_t *dev, 
                            DEVICE_POWER_STATE device_state, bool_t block)
{
  NTSTATUS status;
  KEVENT event;
  POWER_STATE power_state;

  power_state.DeviceState = device_state;

  if(block) /* wait for IRP to complete */
    {
      KeInitializeEvent(&event, NotificationEvent, FALSE);
      
      /* set the device power state and wait for completion */
      status = PoRequestPowerIrp(dev->physical_device_object, 
                                 IRP_MN_SET_POWER, 
                                 power_state,
                                 on_power_set_device_state_complete, 
                                 &event, NULL);
      
      if(status == STATUS_PENDING)
        {
          KeWaitForSingleObject(&event, Executive, KernelMode, FALSE, NULL);
        }
    }
  else
    {
      PoRequestPowerIrp(dev->physical_device_object, IRP_MN_SET_POWER,
                        power_state, NULL, NULL, NULL);
    }
}			


 

> After much exploration I've discovered the cause of the inability for
> some laptops to coming out of standby is.
>  
> The power irp for changing device state is being issued in the
> completion routine for the system power irp, and then the thread is
> blocked waiting for the device power irp to complete.
>  
> Before the blocking takes place, the power manager attempts to send the
> irp all the way, the power dispatcher sees the device power irp, and
> tries to send it down the stack, but the usbhub below returns status
> pending so the completion handler isn't called at that point.
>  
> The libusb thread then blocks waiting for the irp to complete, but it
> never does because the thread which would go on to call the completion
> routing is being blocked!
>  
> Replacing the call to on_power_set_device_state_complete with :
>  
> power_state.DeviceState =
> dev->device_power_states[power_state.SystemState];
> 
> /* set the device power state and don't wait for completion */
> 
> (void) PoRequestPowerIrp(dev->physical_device_object, 
>                          IRP_MN_SET_POWER, 
>                          power_state,
>                          NULL,
>                          NULL, NULL);
> 
> Seems to resolve the problem.
> 
> I've attached this as a patch.
> 
> Comments?
> 
> Cheers,
>  
> -- 
> Dan Ellis
> Newnham Research
> 
> 
> <hr>
> 
> <hr>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

[Libusb-win32-devel] Fix for coming out of standby

[Dan E. <Dan...@ne...>]

After much exploration I've discovered the cause of the inability for
some laptops to coming out of standby is.
=20
The power irp for changing device state is being issued in the
completion routine for the system power irp, and then the thread is
blocked waiting for the device power irp to complete.
=20
Before the blocking takes place, the power manager attempts to send the
irp all the way, the power dispatcher sees the device power irp, and
tries to send it down the stack, but the usbhub below returns status
pending so the completion handler isn't called at that point.
=20
The libusb thread then blocks waiting for the irp to complete, but it
never does because the thread which would go on to call the completion
routing is being blocked!
=20
Replacing the call to on_power_set_device_state_complete with :
=20
power_state.DeviceState =3D
dev->device_power_states[power_state.SystemState];

/* set the device power state and don't wait for completion */

(void) PoRequestPowerIrp(dev->physical_device_object,=20
                         IRP_MN_SET_POWER,=20
                         power_state,
                         NULL,
                         NULL, NULL);

Seems to resolve the problem.

I've attached this as a patch.

Comments?

Cheers,
=20
--=20
Dan Ellis
Newnham Research