Peter Stuge | 1 Jun 2012 03:49
Picon

Re: Polling file descriptors for synchronous transfers

Klas Lindberg wrote:
> ./main
> 
> Note that I have *not* run this yet against a home compiled libusb
> 1.0.9. That's still on my todo list, but I thought I'd at least give
> you something.

Thanks. I built current libusb.git master, and..

> The interesting parts are the calls to libadb_poll().
> They all time out even though there is data to read.

..it works for me.

/tmp/libadb $ LD_LIBRARY_PATH=/tmp/lu/lib ./main
probing device 1d6b:0002
interface with wrong number of endpoints
probing device 1d6b:0001
interface with wrong number of endpoints
probing device 1d6b:0001
interface with wrong number of endpoints
probing device 1d6b:0001
interface with wrong number of endpoints
probing device 1d6b:0001
interface with wrong number of endpoints
probing device 0483:2016
interface with wrong number of endpoints
probing device 0bb4:0cb2
endpoints: 2
7 5 0x82 2 0x200 0
(Continue reading)

Klas Lindberg | 1 Jun 2012 06:07
Picon

Re: Polling file descriptors for synchronous transfers

> ..it works for me.

Do you mean that you don't experience a 5 second "freeze" just before
the file listing? The output looks like it should, with or without the
timeout.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Peter Stuge | 1 Jun 2012 07:11
Picon

Re: Polling file descriptors for synchronous transfers

Klas Lindberg wrote:
> > ..it works for me.
> 
> Do you mean that you don't experience a 5 second "freeze" just before
> the file listing? The output looks like it should, with or without the
> timeout.

Ah - you're right that there was a bit of a delay. I expected an
actual error. I don't have access to the phone anymore, but will
try to test further later today.

//Peter

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
libusb Trac | 1 Jun 2012 10:24
Favicon

[libusb] #131: Some application programs ( gqrx, gnuradio ) crash with libusb-1.0.9

#131: Some application programs ( gqrx, gnuradio ) crash with libusb-1.0.9
---------------------------------------+----------------
  Reporter:  dl1ksv                    |     Owner:
      Type:  defect                    |    Status:  new
 Component:  libusb-1.0 Linux backend  |  Keywords:
Blocked By:                            |    Blocks:
---------------------------------------+----------------
 Some application programs that run with libusb-1.0.8 without problems
 crash with libusb-1.0.9 ( Segmentation fault )[[BR]]
 The system is a gentoo linux 64 bit, kernel 3.3.5, gcc 4.5.3
 The backtrace shows[[BR]]
 {{{
 Program terminated with signal 11, Segmentation fault.
 #0  0x00007f23d2014a44 in add_to_flying_list (transfer=0x7f23c4000910) at
 io.c:1185
 1185if (!timerisset(cur_tv) || (cur_tv->tv_sec > timeout->tv_sec) ||
 (gdb) bt
 #0  0x00007f23d2014a44 in add_to_flying_list (transfer=0x7f23c4000910) at
 io.c:1185
 #1  0x00007f23d2014cc3 in libusb_submit_transfer (transfer=0x7f23c4000968)
 at io.c:1305
 #2  0x00007f23d66853fc in read_thread (param=0x18abd50) at
 /gnuradiocomponents/gnuradio/gr-fcd/lib/hid/hid-libusb.c:697
 #3  0x00007f23d4614f26 in start_thread () from /lib64/libpthread.so.0
 #4  0x00007f23d3b37a4d in clone () from /lib64/libc.so.6

 (gdb) p cur
 $1 = (struct usbi_transfer *) 0xfffffffffffffff8

 (gdb) p ctx->flying_transfers
(Continue reading)

libusb Trac | 3 Jun 2012 12:48
Favicon

[libusb] #132: libusb_open_device_with_vid_pid libusb 1.0.9 Segmentation fault: 11

#132: libusb_open_device_with_vid_pid libusb 1.0.9 Segmentation fault: 11
-------------------------------------+-------------------------------------
  Reporter:  thireus                 |     Owner:
      Type:  defect                  |    Status:  new
 Component:  libusb-1.0 Darwin       |  Keywords:  MacOS, Darwin,
  backend                            |  libusb_open_device_with_vid_pid,
Blocked By:                          |  1.0.8, 1.0.9
                                     |    Blocks:
-------------------------------------+-------------------------------------
 Hi there,

 With the latest version on MacOS 10.7.4 libusb 1.0.9 using
 libusb_open_device_with_vid_pid function causes Segmentation fault.

 I do not have any other log file to provide. With libusb 1.0.8 everything
 is ok with this function.

 Regards,
 Thi.

--

-- 
Ticket URL: <http://libusb.org/ticket/132>
libusb <http://libusb.org/>
C library for writing portable USB drivers in userspace
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
(Continue reading)

libusb Trac | 3 Jun 2012 12:52
Favicon

[libusb] #133: Smartcard reader not accessible via USB 3.0

#133: Smartcard reader not accessible via USB 3.0
-------------------------+------------------------------
  Reporter:  hongquan    |     Owner:
      Type:  defect      |    Status:  new
 Component:  libusb-1.0  |  Keywords:  usb3.0, smartcard
Blocked By:              |    Blocks:
-------------------------+------------------------------
 Hi,
 I'm using CryptoStick (USB security token with OpenPGP card) with OpenSC
 (it uses pcsc-lite and this in turn uses libusb).
 I tried to use the stick on USB 3.0 port but not successful, while USB 2.0
 is OK.

 Attached is the log of libusb 1.0.9.

 I use under Ubuntu 12.04.

--

-- 
Ticket URL: <http://libusb.org/ticket/133>
libusb <http://libusb.org/>
C library for writing portable USB drivers in userspace
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
libusb Trac | 3 Jun 2012 15:54
Favicon

Re: [libusb] #133: Smartcard reader not accessible via USB 3.0

#133: Smartcard reader not accessible via USB 3.0
-------------------------------+------------------
 Reporter:  hongquan           |       Owner:
     Type:  defect             |      Status:  new
Component:  libusb-1.0         |  Resolution:
 Keywords:  usb3.0, smartcard  |  Blocked By:
   Blocks:                     |
-------------------------------+------------------

Comment (by hansdegoede):

 From the log:

 libusb: 4.151209 debug [handle_bulk_completion] handling completion status
 -121 of bulk urb 1/5
 libusb: 4.151221 debug [handle_bulk_completion] short transfer 39/16384
 --> complete!
 libusb: 4.151243 debug [discard_urbs] URB not found --> assuming ready to
 be reaped
 libusb: 4.151267 debug [discard_urbs] URB not found --> assuming ready to
 be reaped
 libusb: 4.151277 debug [discard_urbs] URB not found --> assuming ready to
 be reaped
 libusb: 4.151285 debug [discard_urbs] URB not found --> assuming ready to
 be reaped

 This means that the proper function of this device depends on the
 usbdevfs: BULK_CONTINUATION flag which atm does not work properly with
 XHCI controllers.

(Continue reading)

libusb Trac | 3 Jun 2012 16:13
Favicon

Re: [libusb] #131: Some application programs ( gqrx, gnuradio ) crash with libusb-1.0.9

#131: Some application programs ( gqrx, gnuradio ) crash with libusb-1.0.9
--------------------------------------+------------------
 Reporter:  dl1ksv                    |       Owner:
     Type:  defect                    |      Status:  new
Component:  libusb-1.0 Linux backend  |  Resolution:
 Keywords:                            |  Blocked By:
   Blocks:                            |
--------------------------------------+------------------

Comment (by xiaofan):

 http://gnuradio.org/redmine/projects/gnuradio/repository/revisions/master/show
 /gr-fcd/lib/hid
 This seems to be an older version of hidapi, what if you upgrade to the
 git version of hidapi to see
 if that helps.

 HIDAPI git:
 https://github.com/signal11/hidapi

--

-- 
Ticket URL: <http://libusb.org/ticket/131#comment:1>
libusb <http://libusb.org/>
C library for writing portable USB drivers in userspace
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
(Continue reading)

libusb Trac | 3 Jun 2012 16:15
Favicon

Re: [libusb] #132: libusb_open_device_with_vid_pid libusb 1.0.9 Segmentation fault: 11

#132: libusb_open_device_with_vid_pid libusb 1.0.9 Segmentation fault: 11
-------------------------------------------------+-------------------------
 Reporter:  thireus                              |       Owner:
     Type:  defect                               |      Status:  new
Component:  libusb-1.0 Darwin backend            |  Resolution:
 Keywords:  MacOS, Darwin,                       |  Blocked By:
  libusb_open_device_with_vid_pid, 1.0.8, 1.0.9  |
   Blocks:                                       |
-------------------------------------------------+-------------------------

Comment (by xiaofan):

 Please provide the log and more details. If not, it is very difficult for
 people to help you.

--

-- 
Ticket URL: <http://libusb.org/ticket/132#comment:1>
libusb <http://libusb.org/>
C library for writing portable USB drivers in userspace
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
libusb Trac | 3 Jun 2012 16:39
Favicon

Re: [libusb] #132: libusb_open_device_with_vid_pid libusb 1.0.9 Segmentation fault: 11

#132: libusb_open_device_with_vid_pid libusb 1.0.9 Segmentation fault: 11
-------------------------------------------------+-------------------------
 Reporter:  thireus                              |       Owner:
     Type:  defect                               |      Status:  new
Component:  libusb-1.0 Darwin backend            |  Resolution:
 Keywords:  MacOS, Darwin,                       |  Blocked By:
  libusb_open_device_with_vid_pid, 1.0.8, 1.0.9  |
   Blocks:                                       |
-------------------------------------------------+-------------------------

Comment (by sping):

 Are you are of configure parameter --enable-debug-log ?

 If you would rather not touch your system installation of libusb, you do
 not have to.  This is how I made lsusb use a local version of libusb 1.0.9
 with debug logging enabled:

 {{{
 wget
 http://downloads.sourceforge.net/project/libusb/libusb-1.0/libusb-1.0.9/libusb-1.0.9.tar.bz2
 tar xf libusb-1.0.9.tar.bz2
 cd libusb-1.0.9
 ./configure --enable-debug-log --prefix="$PWD/usr"
 make
 make install

 LD_LIBRARY_PATH="$PWD/usr/lib" /usr/bin/lsusb
 }}}

(Continue reading)


Gmane