On Sat, Jan 21, 2012 at 8:09 AM, Wander Lairson Costa
wrote:
> 2012/1/21 Peter Bigot :
>>
>> Yes. d.bus is always zero on openSUSE 10.3, because
>> dev.bus[0].location is always zero.
>>
>
> I have not commented on this thread because I haven't time to go
On Sat, Jan 21, 2012 at 8:09 AM, Wander Lairson Costa
wrote:
> 2012/1/21 Peter Bigot :
>>
>> Yes. d.bus is always zero on openSUSE 10.3, because
>> dev.bus[0].location is always zero.
>>
>
> I have not commented on this thread because I haven't time to go
On Sat, Jan 21, 2012 at 7:37 AM, Xiaofan Chen wrote:
> On Sat, Jan 21, 2012 at 9:17 PM, Peter Bigot
> wrote:
>> On Sat, Jan 21, 2012 at 6:50 AM, Xiaofan Chen wrote:
>>> On Sat, Jan 21, 2012 at 2:33 AM, Peter Bigot
>>> wrote:
>>>>> Could you please
On Sat, Jan 21, 2012 at 6:50 AM, Xiaofan Chen wrote:
> On Sat, Jan 21, 2012 at 2:33 AM, Peter Bigot
> wrote:
>>> Could you please post your full test codes?
>>
>> The only thing above that was "import usb". That code does assume
>> that the backend
On Fri, Jan 20, 2012 at 11:50 AM, Xiaofan Chen wrote:
> On Sat, Jan 21, 2012 at 12:06 AM, Peter Bigot
> wrote:
>> OK. You haven't said whether the patch causes problems for
>> libusb-compat; I assure you it's necessary for this particular version
>> of legacy
On Fri, Jan 20, 2012 at 8:09 AM, Xiaofan Chen wrote:
> On Fri, Jan 20, 2012 at 10:47 AM, Peter Bigot
> wrote:
>> On Thu, Jan 19, 2012 at 7:24 PM, Xiaofan Chen wrote:
>>> On Fri, Jan 20, 2012 at 12:02 AM, Peter Bigot
>>> wrote:
>>> Is this libusb-0.1.12-
On Thu, Jan 19, 2012 at 7:24 PM, Xiaofan Chen wrote:
> On Fri, Jan 20, 2012 at 12:02 AM, Peter Bigot
> wrote:
>> From: "Peter A. Bigot"
>>
>> With libusb-0.1.12-72 on openSUSE, the device bus number is encoded in the
>> dirname string, not in the locatio
From: "Peter A. Bigot"
With libusb-0.1.12-72 on openSUSE, the device bus number is encoded in the
dirname string, not in the location value. Validate this on a system that
uses the libusb01 backend by comparing lsusb output with:
for d in usb.core.find(find_all=True):
dev = d._ctx.dev
On Sat, Nov 5, 2011 at 7:54 AM, Wander Lairson Costa
wrote:
> Dear all,
>
> In the PyUSB repository (https://github.com/walac/pyusb), at master
> branch, you will find what is supposed to be the alpha 2 release of
> PyUSB. I would like to request PyUSB users to run their apps with the
> HEAD revis
AM, Wander Lairson Costa <
wander.lair...@gmail.com> wrote:
> 2011/10/17 Peter Bigot :
> > On a project I administer on SF, there's an "Admin" button at the far
> right
> > of the main trac toolbar. Clicking that on the right there's a panel
>
On a project I administer on SF, there's an "Admin" button at the far right
of the main trac toolbar. Clicking that on the right there's a panel with a
"trac.ini" section, under which is a link for "notification". The resulting
page seems to have boxes into which you can put email addresses for
n
Thanks for providing pyusb: its support for libusb-1.0 is making my life
much easier by letting me work around the cdc_acm limitations in Linux.
For your consideration: In my application, the Linux kernel driver for
cdc_acm will be loaded automatically when a device is inserted. I don't
want to b
The following program causes a segfault using libusb-1.0:
import usb
rf2500 = usb.core.find(idVendor=0x0451, idProduct=0xF432)
cfg = rf2500.get_active_configuration()
due to libusb_get_configuration being invoked with a null device
handle. The fix is as below:
diff --git a/usb/core.py b/usb/
13 matches
Mail list logo
