Re: CFT: Re: linux libusb again, I made an updated port...

2014-02-11 Thread Wojciech A. Koszek
On Tue, Feb 11, 2014 at 12:11:09AM +0100, Juergen Lock wrote:
 On Mon, Feb 10, 2014 at 11:06:27AM +, Bjoern A. Zeeb wrote:
  
  On 10 Feb 2014, at 04:18 , Wojciech A. Koszek wkos...@freebsd.org wrote:
  
   On nie, lut 09, 2014 at 02:59:06 +0100, Juergen Lock wrote:
   On Sun, Feb 09, 2014 at 02:56:24AM +, Wojciech A. Koszek wrote:
   On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote:
   On Fri, Feb 07, 2014 at 08:49:28PM +, Wojciech A. Koszek wrote:
   On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote:
   Hi!
   
   This came up on irc so I tried to build a linux libusb port (before
   I learned about ports/146895), mine uses linux_base-gentoo-stage3
   like linux_kdump with a src/lib/libusb head snapshot so it's more
   up to date than wkoszek's build (ports/146895), and it's really
   easy to update it again.  Also maybe it can be used as linux
   libusb-1.0.so too; I didn't actually test it tho.
   
   Should this be committed?  Is wkoszek's version better since it
   also builds on  10.x?  Comments welcome...
   
   wkoszek's version:
   
http://www.freebsd.org/cgi/query-pr.cgi?pr=146895
   
   Mine:
   
http://people.freebsd.org/~nox/tmp/linux_libusb.shar
   
   Distfile:
   

   http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.bz2
   
   10/amd64 package:
   

   http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r261448.txz
   
   (built via:
   
poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb
   
   - btw for some reason the dependency 
   emulators/linux_base-gentoo-stage3
   doesn't build for 10i386 in poudriere bulk, I get a pkg segfault.  
   bapt
   Cc'd...)
   
   
   Juergen,
   Hi!
   
   What would be the reason for this update?
   
   My stuff may be out of date, but it was all tested and working. I 
   verified
   it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for 
   which
   this stuff was written.
   
   I was just thinking an updated version may be useful, but if it's
   already working for everyone maybe less so...
   
   Or would it work as a linux libusb-1.0.so too?  I know the libusb 1.0
   stuff added some functions since 9.x at least... maybe hps would know
   (Cc'd.)
   
   
   Juergen,
   
   I think this package is useful and is looking for maintainer, so if you 
   have
   time and energy, I'm OK with upgrading it, but I suggest testing it 
   first.
   Bjoern might be interested too.
   
   You mean bz@ ?  Cc'd.  I tried testing lsusb from debian sid but it 
   printed
   nothing, neither with my nor with your older version, but maybe it's just
   `too new' for our current linuxolator.
   
   I assume you have at least 1 USB device while trying this. I don't 
   remember
   exactly, but while trying within Linuxolator, you may need devfs/procfs to
   be mounted under Linuxolator's root directory.
  
  My understanding and from looking at trace is that if we cannot find it in 
  /compat/linux we ale search in /; so no need for an extra mount unless 
  maybe you run chrooted.
  
  
   So you'll have to figure this out.
   
   Does it return with 0 exit code?
   
   If not, lsusb should be simple enough to let you place printf() all over 
   the
   place and understand out when it's failing. 
  
  For me the problem was a clock_gettime() call in the libusb which my glibc 
  did not provide.   That made all things fail (silently) until I used linux 
  ?rtld tracing to see the unresolved symbol from libusb/the commercial 3rd 
  party software dynamically loading libusb.
  
 And my linux_kdump ends like this:
 
  35607 lsusbCALL  munmap(0x28247000,0x8000)
  35607 lsusbRET   munmap 0
  35607 lsusbCALL  linux_open(0x28090c31,0,0x28081e00)
  35607 lsusbNAMI  /compat/linux/dev/usbctl
  35607 lsusbNAMI  /dev/usbctl
  35607 lsusbRET   linux_open 3
  35607 lsusbCALL  linux_ioctl(0x3,0xffe5 ,0xc5d8)
  35607 lsusbRET   linux_ioctl 0
  35607 lsusbCALL  close(0x3)
  35607 lsusbRET   close 0
  35607 lsusbCALL  linux_exit_group(0x1)
  35607 lsusbUNKNOWN(11)
 
 and the exit code is 1, so I guess it's failing on an unhandled
 syscall or something like that.

Juergen

Can you send the full trace with all eventual child processes? If you could
copypaste:

open libusb
for each bus
for each device
open device

to a separate program, we could make it libusb/Linuxolator regression test.
This would also help us match ptrace-line number output.

Which FreeBSD are you using?

This may indicate some relationship with

http://www.freebsd.org/cgi/query-pr.cgi?pr=141439

-- 
Wojciech A. Koszek
wkos...@freebsd.czest.pl
http://FreeBSD.czest.pl/~wkoszek/
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to 

Re: CFT: Re: linux libusb again, I made an updated port...

2014-02-11 Thread Juergen Lock
On Tue, Feb 11, 2014 at 07:56:50PM +, Wojciech A. Koszek wrote:
 On Tue, Feb 11, 2014 at 12:11:09AM +0100, Juergen Lock wrote:
  On Mon, Feb 10, 2014 at 11:06:27AM +, Bjoern A. Zeeb wrote:
   
   On 10 Feb 2014, at 04:18 , Wojciech A. Koszek wkos...@freebsd.org wrote:
   
On nie, lut 09, 2014 at 02:59:06 +0100, Juergen Lock wrote:
On Sun, Feb 09, 2014 at 02:56:24AM +, Wojciech A. Koszek wrote:
On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote:
On Fri, Feb 07, 2014 at 08:49:28PM +, Wojciech A. Koszek wrote:
On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote:
Hi!

This came up on irc so I tried to build a linux libusb port (before
I learned about ports/146895), mine uses linux_base-gentoo-stage3
like linux_kdump with a src/lib/libusb head snapshot so it's more
up to date than wkoszek's build (ports/146895), and it's really
easy to update it again.  Also maybe it can be used as linux
libusb-1.0.so too; I didn't actually test it tho.

Should this be committed?  Is wkoszek's version better since it
also builds on  10.x?  Comments welcome...

wkoszek's version:

   http://www.freebsd.org/cgi/query-pr.cgi?pr=146895

Mine:

   http://people.freebsd.org/~nox/tmp/linux_libusb.shar

Distfile:

   
http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.bz2

10/amd64 package:

   
http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r261448.txz

(built via:

   poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb

- btw for some reason the dependency 
emulators/linux_base-gentoo-stage3
doesn't build for 10i386 in poudriere bulk, I get a pkg segfault.  
bapt
Cc'd...)


Juergen,
Hi!

What would be the reason for this update?

My stuff may be out of date, but it was all tested and working. I 
verified
it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for 
which
this stuff was written.

I was just thinking an updated version may be useful, but if it's
already working for everyone maybe less so...

Or would it work as a linux libusb-1.0.so too?  I know the libusb 1.0
stuff added some functions since 9.x at least... maybe hps would know
(Cc'd.)


Juergen,

I think this package is useful and is looking for maintainer, so if 
you have
time and energy, I'm OK with upgrading it, but I suggest testing it 
first.
Bjoern might be interested too.

You mean bz@ ?  Cc'd.  I tried testing lsusb from debian sid but it 
printed
nothing, neither with my nor with your older version, but maybe it's 
just
`too new' for our current linuxolator.

I assume you have at least 1 USB device while trying this. I don't 
remember
exactly, but while trying within Linuxolator, you may need devfs/procfs 
to
be mounted under Linuxolator's root directory.
   
   My understanding and from looking at trace is that if we cannot find it 
   in /compat/linux we ale search in /; so no need for an extra mount unless 
   maybe you run chrooted.
   
   
So you'll have to figure this out.

Does it return with 0 exit code?

If not, lsusb should be simple enough to let you place printf() all 
over the
place and understand out when it's failing. 
   
   For me the problem was a clock_gettime() call in the libusb which my 
   glibc did not provide.   That made all things fail (silently) until I 
   used linux ?rtld tracing to see the unresolved symbol from libusb/the 
   commercial 3rd party software dynamically loading libusb.
   
  And my linux_kdump ends like this:
  
   35607 lsusbCALL  munmap(0x28247000,0x8000)
   35607 lsusbRET   munmap 0
   35607 lsusbCALL  linux_open(0x28090c31,0,0x28081e00)
   35607 lsusbNAMI  /compat/linux/dev/usbctl
   35607 lsusbNAMI  /dev/usbctl
   35607 lsusbRET   linux_open 3
   35607 lsusbCALL  linux_ioctl(0x3,0xffe5 ,0xc5d8)
   35607 lsusbRET   linux_ioctl 0
   35607 lsusbCALL  close(0x3)
   35607 lsusbRET   close 0
   35607 lsusbCALL  linux_exit_group(0x1)
   35607 lsusbUNKNOWN(11)
  
  and the exit code is 1, so I guess it's failing on an unhandled
  syscall or something like that.
 
 Juergen
 
 Can you send the full trace with all eventual child processes? If you could
 copypaste:
 
   open libusb
   for each bus
   for each device
   open device
 
 to a separate program, we could make it libusb/Linuxolator regression test.
 This would also help us match ptrace-line number output.
 
There are no child processes and it seems it doesn't even get to
enumerate buses, i.e. the /dev/usbctl above is the only usb-related
thing it opens.  I've put the full kdump here:


Re: CFT: Re: linux libusb again, I made an updated port...

2014-02-10 Thread Bjoern A. Zeeb

On 10 Feb 2014, at 04:18 , Wojciech A. Koszek wkos...@freebsd.org wrote:

 On nie, lut 09, 2014 at 02:59:06 +0100, Juergen Lock wrote:
 On Sun, Feb 09, 2014 at 02:56:24AM +, Wojciech A. Koszek wrote:
 On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote:
 On Fri, Feb 07, 2014 at 08:49:28PM +, Wojciech A. Koszek wrote:
 On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote:
 Hi!
 
 This came up on irc so I tried to build a linux libusb port (before
 I learned about ports/146895), mine uses linux_base-gentoo-stage3
 like linux_kdump with a src/lib/libusb head snapshot so it's more
 up to date than wkoszek's build (ports/146895), and it's really
 easy to update it again.  Also maybe it can be used as linux
 libusb-1.0.so too; I didn't actually test it tho.
 
 Should this be committed?  Is wkoszek's version better since it
 also builds on  10.x?  Comments welcome...
 
 wkoszek's version:
 
  http://www.freebsd.org/cgi/query-pr.cgi?pr=146895
 
 Mine:
 
  http://people.freebsd.org/~nox/tmp/linux_libusb.shar
 
 Distfile:
 
  
 http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.bz2
 
 10/amd64 package:
 
  
 http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r261448.txz
 
 (built via:
 
  poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb
 
 - btw for some reason the dependency emulators/linux_base-gentoo-stage3
 doesn't build for 10i386 in poudriere bulk, I get a pkg segfault.  bapt
 Cc'd...)
 
 
 Juergen,
 Hi!
 
 What would be the reason for this update?
 
 My stuff may be out of date, but it was all tested and working. I verified
 it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for which
 this stuff was written.
 
 I was just thinking an updated version may be useful, but if it's
 already working for everyone maybe less so...
 
 Or would it work as a linux libusb-1.0.so too?  I know the libusb 1.0
 stuff added some functions since 9.x at least... maybe hps would know
 (Cc'd.)
 
 
 Juergen,
 
 I think this package is useful and is looking for maintainer, so if you have
 time and energy, I'm OK with upgrading it, but I suggest testing it first.
 Bjoern might be interested too.
 
 You mean bz@ ?  Cc'd.  I tried testing lsusb from debian sid but it printed
 nothing, neither with my nor with your older version, but maybe it's just
 `too new' for our current linuxolator.
 
 I assume you have at least 1 USB device while trying this. I don't remember
 exactly, but while trying within Linuxolator, you may need devfs/procfs to
 be mounted under Linuxolator's root directory.

My understanding and from looking at trace is that if we cannot find it in 
/compat/linux we ale search in /; so no need for an extra mount unless maybe 
you run chrooted.


 So you'll have to figure this out.
 
 Does it return with 0 exit code?
 
 If not, lsusb should be simple enough to let you place printf() all over the
 place and understand out when it's failing. 

For me the problem was a clock_gettime() call in the libusb which my glibc did 
not provide.   That made all things fail (silently) until I used linux “rtld 
tracing to see the unresolved symbol from libusb/the commercial 3rd party 
software dynamically loading libusb.


— 
Bjoern A. Zeeb ? ??? ??? ??:
'??? ???  ??  ??? ?? ?? ??? ??? ??? ? ? 
?? ?? ? ',  ? ?, ??? ? ?? ?, ?.???

___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: CFT: Re: linux libusb again, I made an updated port...

2014-02-10 Thread Juergen Lock
On Mon, Feb 10, 2014 at 11:06:27AM +, Bjoern A. Zeeb wrote:
 
 On 10 Feb 2014, at 04:18 , Wojciech A. Koszek wkos...@freebsd.org wrote:
 
  On nie, lut 09, 2014 at 02:59:06 +0100, Juergen Lock wrote:
  On Sun, Feb 09, 2014 at 02:56:24AM +, Wojciech A. Koszek wrote:
  On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote:
  On Fri, Feb 07, 2014 at 08:49:28PM +, Wojciech A. Koszek wrote:
  On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote:
  Hi!
  
  This came up on irc so I tried to build a linux libusb port (before
  I learned about ports/146895), mine uses linux_base-gentoo-stage3
  like linux_kdump with a src/lib/libusb head snapshot so it's more
  up to date than wkoszek's build (ports/146895), and it's really
  easy to update it again.  Also maybe it can be used as linux
  libusb-1.0.so too; I didn't actually test it tho.
  
  Should this be committed?  Is wkoszek's version better since it
  also builds on  10.x?  Comments welcome...
  
  wkoszek's version:
  
 http://www.freebsd.org/cgi/query-pr.cgi?pr=146895
  
  Mine:
  
 http://people.freebsd.org/~nox/tmp/linux_libusb.shar
  
  Distfile:
  
 
  http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.bz2
  
  10/amd64 package:
  
 
  http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r261448.txz
  
  (built via:
  
 poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb
  
  - btw for some reason the dependency emulators/linux_base-gentoo-stage3
  doesn't build for 10i386 in poudriere bulk, I get a pkg segfault.  bapt
  Cc'd...)
  
  
  Juergen,
  Hi!
  
  What would be the reason for this update?
  
  My stuff may be out of date, but it was all tested and working. I 
  verified
  it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for which
  this stuff was written.
  
  I was just thinking an updated version may be useful, but if it's
  already working for everyone maybe less so...
  
  Or would it work as a linux libusb-1.0.so too?  I know the libusb 1.0
  stuff added some functions since 9.x at least... maybe hps would know
  (Cc'd.)
  
  
  Juergen,
  
  I think this package is useful and is looking for maintainer, so if you 
  have
  time and energy, I'm OK with upgrading it, but I suggest testing it first.
  Bjoern might be interested too.
  
  You mean bz@ ?  Cc'd.  I tried testing lsusb from debian sid but it printed
  nothing, neither with my nor with your older version, but maybe it's just
  `too new' for our current linuxolator.
  
  I assume you have at least 1 USB device while trying this. I don't remember
  exactly, but while trying within Linuxolator, you may need devfs/procfs to
  be mounted under Linuxolator's root directory.
 
 My understanding and from looking at trace is that if we cannot find it in 
 /compat/linux we ale search in /; so no need for an extra mount unless maybe 
 you run chrooted.
 
 
  So you'll have to figure this out.
  
  Does it return with 0 exit code?
  
  If not, lsusb should be simple enough to let you place printf() all over the
  place and understand out when it's failing. 
 
 For me the problem was a clock_gettime() call in the libusb which my glibc 
 did not provide.   That made all things fail (silently) until I used linux 
 ?rtld tracing to see the unresolved symbol from libusb/the commercial 3rd 
 party software dynamically loading libusb.
 
And my linux_kdump ends like this:

 35607 lsusbCALL  munmap(0x28247000,0x8000)
 35607 lsusbRET   munmap 0
 35607 lsusbCALL  linux_open(0x28090c31,0,0x28081e00)
 35607 lsusbNAMI  /compat/linux/dev/usbctl
 35607 lsusbNAMI  /dev/usbctl
 35607 lsusbRET   linux_open 3
 35607 lsusbCALL  linux_ioctl(0x3,0xffe5 ,0xc5d8)
 35607 lsusbRET   linux_ioctl 0
 35607 lsusbCALL  close(0x3)
 35607 lsusbRET   close 0
 35607 lsusbCALL  linux_exit_group(0x1)
 35607 lsusbUNKNOWN(11)

and the exit code is 1, so I guess it's failing on an unhandled
syscall or something like that.

Juergen
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: CFT: Re: linux libusb again, I made an updated port...

2014-02-09 Thread Bjoern A. Zeeb
On 09 Feb 2014, at 13:59 , Juergen Lock n...@jelal.kn-bremen.de wrote:

Hi guys,

 On Sun, Feb 09, 2014 at 02:56:24AM +, Wojciech A. Koszek wrote:
 On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote:
 On Fri, Feb 07, 2014 at 08:49:28PM +, Wojciech A. Koszek wrote:
 On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote:
 Hi!
 
 This came up on irc so I tried to build a linux libusb port (before
 I learned about ports/146895), mine uses linux_base-gentoo-stage3
 like linux_kdump with a src/lib/libusb head snapshot so it's more
 up to date than wkoszek's build (ports/146895), and it's really
 easy to update it again.  Also maybe it can be used as linux
 libusb-1.0.so too; I didn't actually test it tho.
 
 Should this be committed?  Is wkoszek's version better since it
 also builds on  10.x?  Comments welcome...
 
 wkoszek's version:
 
   http://www.freebsd.org/cgi/query-pr.cgi?pr=146895
 
 Mine:
 
   http://people.freebsd.org/~nox/tmp/linux_libusb.shar
 
 Distfile:
 
   
 http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.bz2
 
 10/amd64 package:
 
   
 http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r261448.txz
 
 (built via:
 
   poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb
 
 - btw for some reason the dependency emulators/linux_base-gentoo-stage3
 doesn't build for 10i386 in poudriere bulk, I get a pkg segfault.  bapt
 Cc'd...)
 
 
 Juergen,
 Hi!
 
 What would be the reason for this update?
 
 My stuff may be out of date, but it was all tested and working. I verified
 it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for which
 this stuff was written.
 
 I was just thinking an updated version may be useful, but if it's
 already working for everyone maybe less so...
 
 Or would it work as a linux libusb-1.0.so too?  I know the libusb 1.0
 stuff added some functions since 9.x at least... maybe hps would know
 (Cc'd.)
 
 
 Juergen,
 
 I think this package is useful and is looking for maintainer, so if you have
 time and energy, I'm OK with upgrading it, but I suggest testing it first.
 Bjoern might be interested too.
 
 You mean bz@ ?  Cc'd.  I tried testing lsusb from debian sid but it printed

Thanks.

 nothing, neither with my nor with your older version, but maybe it's just
 `too new' for our current linuxolator.

I got a lsusb to work after a bit more hacking.  But that wasn’t the end of the 
story.



 
 Can you show the diff between USB code from src/lib and from the distfile?
 
 That's just a checkout from head, see the port Makefile for how it's
 generated. (.if defined(BOOTSTRAP)...)
 
 Instead of having a port with .c code, I'd drive towards having src/lib
 changes (if any) be commited. And then that port only has to do:
 
cp -rf src/lib/libusb port/tmp/dir
 
 and build it with different -DDEFINES if necessary.
 
 That's what I orginally had but hps suggested I check out from head
 instead.  (Tho that was when I couldn't get it building at first, which
 turned out to be just a CFLAGS -I problem so the 10.0 code should now
 build this way as well.)
 
 I guess it's the same stuff if the code is there with no modification. If we
 could have this port checked in to the ports/ repository, this would be
 great.  Basically I'd concentrate on delivering good end-user experience
 
 Thanks for working on it. Lots of people will apprecite it.
 
 Ok so let's wait for more testers then?

I’ll give it a spin the next days.

Since I last talked to some of you I had a lot of findings yet I had not been 
able to make any possible solution to fully work yet.  The in-tree which 
supposedly should compile with a Ubuntu was unfortunately ruled out the 
earliest:(  Some had glibc dependencies I kicked out which the F10 (our current 
default) environment didn’t provide, others are just not doing the right thing 
in some cases and required hacking.  In the end I stayed with Wojciech’s 
version as it was the best option to start with and I could make the most 
progress quickly.

/bz

— 
Bjoern A. Zeeb ? ??? ??? ??:
'??? ???  ??  ??? ?? ?? ??? ??? ??? ? ? 
?? ?? ? ',  ? ?, ??? ? ?? ?, ?.???

___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org


Re: CFT: Re: linux libusb again, I made an updated port...

2014-02-09 Thread Wojciech A. Koszek
On nie, lut 09, 2014 at 02:59:06 +0100, Juergen Lock wrote:
 On Sun, Feb 09, 2014 at 02:56:24AM +, Wojciech A. Koszek wrote:
  On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote:
   On Fri, Feb 07, 2014 at 08:49:28PM +, Wojciech A. Koszek wrote:
On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote:
 Hi!
 
  This came up on irc so I tried to build a linux libusb port (before
 I learned about ports/146895), mine uses linux_base-gentoo-stage3
 like linux_kdump with a src/lib/libusb head snapshot so it's more
 up to date than wkoszek's build (ports/146895), and it's really
 easy to update it again.  Also maybe it can be used as linux
 libusb-1.0.so too; I didn't actually test it tho.
 
  Should this be committed?  Is wkoszek's version better since it
 also builds on  10.x?  Comments welcome...
 
  wkoszek's version:
 
   http://www.freebsd.org/cgi/query-pr.cgi?pr=146895
 
  Mine:
 
   http://people.freebsd.org/~nox/tmp/linux_libusb.shar
 
  Distfile:
 
   
 http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.bz2
 
  10/amd64 package:
 
   
 http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r261448.txz
 
 (built via:
 
   poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb
 
 - btw for some reason the dependency 
 emulators/linux_base-gentoo-stage3
 doesn't build for 10i386 in poudriere bulk, I get a pkg segfault.  
 bapt
 Cc'd...)
 

Juergen,
   Hi!

What would be the reason for this update?

My stuff may be out of date, but it was all tested and working. I 
verified
it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for which
this stuff was written.

I was just thinking an updated version may be useful, but if it's
   already working for everyone maybe less so...
   
Or would it work as a linux libusb-1.0.so too?  I know the libusb 1.0
   stuff added some functions since 9.x at least... maybe hps would know
   (Cc'd.)
   
  
  Juergen,
  
  I think this package is useful and is looking for maintainer, so if you have
  time and energy, I'm OK with upgrading it, but I suggest testing it first.
  Bjoern might be interested too.
  
 You mean bz@ ?  Cc'd.  I tried testing lsusb from debian sid but it printed
 nothing, neither with my nor with your older version, but maybe it's just
 `too new' for our current linuxolator.

I assume you have at least 1 USB device while trying this. I don't remember
exactly, but while trying within Linuxolator, you may need devfs/procfs to
be mounted under Linuxolator's root directory.

So you'll have to figure this out.

Does it return with 0 exit code?

If not, lsusb should be simple enough to let you place printf() all over the
place and understand out when it's failing. 

-- 
Wojciech A. Koszek
wkos...@freebsd.czest.pl
http://FreeBSD.czest.pl/~wkoszek/
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org