From: Ole A. <ol...@gn...> - 2000-04-11 20:22:47
|
confirm 858959 |
From: Nader A. <nab...@pa...> - 2003-04-09 18:45:58
|
Hi , I have a 3Com HomeConnect USB digital Web Camera and I was looking on the Internet for a driver to run the Camera with RedHat Linux 8.0 (Kernel 2.4.18-14). I was only able to find a patch file located at the following site: http://homeconnectusb.sourceforge.net/ I noticed that you contributed to this driver and I figured you might be able to provide me with some help. I took a look at the patch file but I was unable to understand how to go about installing it. I thought I might be missing some files since there is a mention of "vicam.c" file which is a C/C++ file which I don't have. Also I made a search for vicam* and only located the object file "vicam.o". Also I noticed that the patch file seemed to display a diff output between two releases, diff -urN linux-2.4.19/drivers/usb/Makefile linux-2.4.19-vicam/drivers/usb/Makefile Could you please provide me with instructions on how to go about installing the Linux driver and how to obtain any needed files besides the vicam_patch the have downloaded from the above mentioned site. For convinience I have attached the vicam_patch file. I appreciate your kind help and support in this manner. Sincerely, Nader Abusaad |
From: Scott C. <sco...@li...> - 2004-02-23 05:49:21
|
I just downloaded libusb version 0.1.7. Couldn't find the source for the "usb_interrupt_read()" and "usb_interrupt_write()" functions. Also, the home page says that 0.1.8 is available, but wasn't there on the download page. Could someone clue me in ? Thanks for the good work. |
From: Johannes E. <joh...@er...> - 2004-02-23 06:31:18
|
On Sun, Feb 22, 2004, Scott Cowley <sco...@li...> wrote: > I just downloaded libusb version 0.1.7. > Couldn't find the source for the "usb_interrupt_read()" and > "usb_interrupt_write()" functions. > Also, the home page says that 0.1.8 is available, but wasn't there > on the download page. > Could someone clue me in ? http://sourceforge.net/project/showfiles.php?group_id=1674&package_id=1632 0.1.8 is on the downloads page. JE |
From: Ned K. <ne...@bi...> - 2006-04-03 02:00:34
|
I believe that Rick Mann was trying to get avarice working using libusb on Mac OS X 10.4.5 (which I'd love to do, too). Then Charles Lepple asked: ---- Just a wild guess, but does the program fork? I seem to recall some trouble with an OS X port of a program that opened libusb in the parent process, and tried to access the device in a child process. It isn't a 1:1 correspondence, but the ktrace/kdump programs provide system call tracing similar to strace. ---- So I looked at the code, and found exactly that in src/jtagusb2.cc in the avarice sources: ---- if (usb_set_configuration(udev, dev->config[0].bConfigurationValue)) { statusOut("error setting configuration %d: %s\n", dev->config[0].bConfigurationValue, usb_strerror()); goto fail; } usb_interface = dev->config[0].interface[0].altsetting [0].bInterfaceNumber; if (usb_claim_interface(udev, usb_interface)) { statusOut("error claiming interface %d: %s\n", usb_interface, usb_strerror()); goto fail; } pid_t p; int pype[2]; unixCheck(socketpair(AF_UNIX, SOCK_STREAM, PF_UNSPEC, pype) == 0, "cannot create pipe"); switch ((p = fork())) { case 0: close(pype[0]); usb_daemon(udev, pype[1], usb_interface); ---- I'm going to try moving all the opening stuff into the child to see what happens. -- Ned Konz ne...@bi... |
From: Ned K. <ne...@bi...> - 2006-04-03 03:17:23
Attachments:
avariceDebug.tar.gz
|
[Sorry about the prior lack of a subject] On Apr 2, 2006, at 7:00 PM, I wrote: > I believe that Rick Mann was trying to get avarice working using > libusb on Mac OS X 10.4.5 (which I'd love to do, too). > > Then Charles Lepple asked: > ---- > Just a wild guess, but does the program fork? I seem to recall some > trouble with an OS X port of a program that opened libusb in the > parent process, and tried to access the device in a child process. > > It isn't a 1:1 correspondence, but the ktrace/kdump programs provide > system call tracing similar to strace. > ---- ... And then I wrote: > I'm going to try moving all the opening stuff into the child to see > what happens. Which I did, without really trying to understand what was going on with the forking and IPC. In openUSB() I just moved all the initialization stuff down to after the fork() in the child process. That's all. Anyway, the results look promising: though it still quits after a while, it gets quite a bit further. It had been dying right after it forked. Attached are three debug logs made as follows: USB_DEBUG=255 avarice -d -2 -j usb:00:a0:00:00:33:a6 localhost:4242 >oldAvariceDebug.txt 2>&1 USB_DEBUG=255 ./avarice -d -2 -j usb:00:a0:00:00:33:a6 localhost: 4242 >newAvariceDebug.txt 2>&1 USB_DEBUG=255 ./avarice -D -d -2 -j usb:00:a0:00:00:33:a6 localhost: 4242 >detachednewAvariceDebug.txt 2>&1 The new ones won't exactly correspond with the old one because I set the stdout and stderr buffering to line buffering at the top of main () in main.cc for the new version. setlinebuf(stdout); setlinebuf(stderr); But you can see pretty much what's going on anyway. Now to get this done right... -- Ned Konz ne...@bi... |
From: Ned K. <ne...@bi...> - 2006-04-03 19:28:36
|
[Sorry about the prior lack of a subject] [I sent this earlier, but apparently SF rejected it silently because it had an attachment] On Apr 2, 2006, at 7:00 PM, I wrote: > I believe that Rick Mann was trying to get avarice working using > libusb on Mac OS X 10.4.5 (which I'd love to do, too). > > Then Charles Lepple asked: > ---- > Just a wild guess, but does the program fork? I seem to recall some > trouble with an OS X port of a program that opened libusb in the > parent process, and tried to access the device in a child process. > > It isn't a 1:1 correspondence, but the ktrace/kdump programs provide > system call tracing similar to strace. > ---- ... And then I wrote: > I'm going to try moving all the opening stuff into the child to see > what happens. Which I did, without really trying to understand what was going on with the forking and IPC. In openUSB() I just moved all the initialization stuff down to after the fork() in the child process. That's all. Anyway, the results look promising: though it still quits after a while, it gets quite a bit further. It had been dying right after it forked. Attached are three debug logs made as follows: USB_DEBUG=255 avarice -d -2 -j usb:00:a0:00:00:33:a6 localhost:4242 >oldAvariceDebug.txt 2>&1 USB_DEBUG=255 ./avarice -d -2 -j usb:00:a0:00:00:33:a6 localhost: 4242 >newAvariceDebug.txt 2>&1 USB_DEBUG=255 ./avarice -D -d -2 -j usb:00:a0:00:00:33:a6 localhost: 4242 >detachednewAvariceDebug.txt 2>&1 The new ones won't exactly correspond with the old one because I set the stdout and stderr buffering to line buffering at the top of main () in main.cc for the new version. setlinebuf(stdout); setlinebuf(stderr); But you can see pretty much what's going on anyway. Now to get this done right... -- Ned Konz ne...@bi... |
From: <cao...@ho...> - 2007-01-10 10:54:09
|
Now I want to put libusb into IpodLinux, what should I do? _________________________________________________________________ 最新の Windows Live メッセンジャを今すぐトライ! http://promotion.live.jp/messenger/ |
From: Tim R. <ti...@pr...> - 2007-01-10 19:00:51
|
=D3=F0 =E1=BF wrote: > Now I want to put libusb into IpodLinux, what should I do? Give up. There is no USB host controller in the iPod. --=20 Tim Roberts, ti...@pr... Providenza & Boekelheide, Inc. |
From: make <sab...@ya...> - 2007-01-19 18:20:29
|
Tim Roberts <timr <at> probo.com> writes: > > 羽 峥 wrote: > > Now I want �to� put �libusb� into �IpodLinux�, what should I do? > > Give up. There is no USB host controller in the iPod. > What? Do I need USB host controller to put libusb int iPodLinux? |
From: Tim R. <ti...@pr...> - 2007-01-19 19:09:41
|
make wrote: > Tim Roberts <timr <at> probo.com> writes: > =20 >> =E7=BE=BD =E5=B3=A5 wrote: >> =20 >>> Now I want =EF=BF=BD=EF=B7=AFto=EF=B7=AF=EF=BF=BD put =EF=BF=BD=EF=B7= =AFlibusb=EF=B7=AF=EF=BF=BD into =EF=BF=BD=EF=B7=AFIpodLinux=EF=B7=AF=EF=BF= =BD, what should I do? >>> =20 >> Give up. There is no USB host controller in the iPod. >> =20 > What? > Do I need USB host controller to put =EF=B7=AFlibusb=EF=B7=AF int =EF=B7= =AFiPodLinux=EF=B7=AF? > =20 Yes. USB is a master/slave bus. Everything with a USB connector is either a host or a device,[1] and a given USB bus can have only one host. The host controls everything; a device cannot send anything unless its host asks for it. The iPod is a USB device, not a host. You cannot plug a camera or a USB memory stick into the iPod. Its USB connector can only be used to plug the iPod into a host. The purpose of libusb is to allow a computer to access the USB devices that are plugged in to it, and that can only be done by a USB host.=20 Thus, there is nothing for libusb to do on an iPod. What were you hoping to do? - - - [1] There is a variant of USB called "USB On-The-Go" that allows a device and a host to negotiate trading places. I haven't seen any such devices yet. --=20 Tim Roberts, ti...@pr... Providenza & Boekelheide, Inc. |
From: make <sab...@ya...> - 2007-01-20 06:49:06
|
> Yes. USB is a master/slave bus. Everything with a USB connector is > either a host or a device,[1] and a given USB bus can have only one > host. The host controls everything; a device cannot send anything > unless its host asks for it. > > The iPod is a USB device, not a host. You cannot plug a camera or a USB > memory stick into the iPod. Its USB connector can only be used ��to�� plug > the iPod into a host. > > The purpose of ��libusb�� is ��to�� allow a computer ��to�� access the USB devices > that are plugged in ��to�� it, and that can only be done by a USB host. > Thus, there is nothing for ��libusb�� ��to�� do on an iPod. > > What were you hoping ��to�� do? > - - - > [1] There is a variant of USB called "USB On-The-Go" that allows a > device and a host ��to�� negotiate trading places. I haven't seen any such > devices yet. > I want �to� connect ipod �to� the network through PC. First, I installed �iPodLinux� in ipod. Then, I thought that I need �libusb� �to� access �to� PC from iPod. But, I knew it is impossible when I read your sentences. If I can't use �libusb� �to� do this, the only way I should do is improve USB driver of �iPodLinux�? |
From: <ti...@pr...> - 2007-01-21 08:36:35
|
On Sat, Jan 20, 2007 at 06:48:52AM +0000, make wrote: > > I want to connect ipod to the network through PC. > First, I installed iPodLinux in ipod. > Then, I thought that I need libusb to access to PC from iPod. > > But, I knew it is impossible when I read your sentences. > If I can't use libusb to do this, the only way I should do is > improve USB driver of iPodLinux? No. I don't know how I can make this any clearer. It does not matter how much software you have or how much time you spend fixing it up. The iPod IS NOT a USB host. It does not have the right HARDWARE. YOU cannot fix that. What you ask is IMPOSSIBLE. It's like asking, "How can I insert a CD into my iPod?" You can't because there is no CD drive, and no amount of driver software can change that. You can access your iPod from a PC, but you cannot acccess your PC from your iPod. -- Tim Roberts, ti...@pr... Providenza & Boeklheide, Inc. |
From: Peter S. <stu...@cd...> - 2007-01-21 09:02:51
|
On Sun, Jan 21, 2007 at 12:36:31AM -0800, ti...@pr... wrote: > > But, I knew it is impossible when I read your sentences. > > If I can't use libusb to do this, the only way I should do is > > improve USB driver of iPodLinux? [..] > You can access your iPod from a PC, but you cannot acccess your PC > from your iPod. With open source software there really aren't any limits. :) IP over USB (using the TUN driver and a simplistic libusb app on the PC, and some expansion of the iPodLinux USB driver on the iPod) could be used for networking. Bit of a hack, 512 byte MTU, but it should work just fine. Note that most of that will be off-topic for this list, however. //Peter |
From: Dan E. <Dan...@di...> - 2007-01-22 09:13:13
|
ti...@pr... wrote: > On Sat, Jan 20, 2007 at 06:48:52AM +0000, make wrote: >>=20 >> I want to connect ipod to the network through PC. >> First, I installed iPodLinux in ipod. >> Then, I thought that I need libusb to access to PC from iPod. >>=20 >> But, I knew it is impossible when I read your sentences. >> If I can't use libusb to do this, the only way I should do is improve >> USB driver of iPodLinux? >=20 > No. I don't know how I can make this any clearer. It does not > matter how much software you have or how much time you spend fixing > it up. =20 > The iPod IS NOT a USB host. It does not have the right HARDWARE. > YOU cannot fix that. What you ask is IMPOSSIBLE. It's like asking, > "How can I insert a CD into my iPod?" You can't because there is no > CD drive, and no amount of driver software can change that. =20 >=20 > You can access your iPod from a PC, but you cannot acccess your PC > from your iPod.=20 But you could in theory make the iPod USB interface appear as a CDC ethernet device, and have linux running on it connect to that somehow. Dan. |
From: M m. <m.m...@gm...> - 2011-10-31 13:39:34
|
m.m...@gm... |
From: rohan v. <roh...@gm...> - 2013-07-18 05:59:09
|
dear all, i am tring to install the libusb on my red hat linux (RHEL 5) but facing problem while using it. i am trying to use it and compile my code its giving me error like /usr/bin/ld: cannot found the -lusb-1.0 i have used libusb on my ubuntu machine there i got whole package include example codes and how to compile it n all i can get some help in this please let me know Thanks Rohaan |
From: Mostafa.Y <mos...@gm...> - 2014-10-31 17:51:12
|
From: dark h. <dar...@gm...> - 2014-12-17 15:25:14
|
Hello; I did all steps to compile libusb for android app.However while doing that i recive make: Nothing to be done for `Android.mk'. this massage in ubuntu can you help me as soon as possible or dou you have a tutorial video or something to that without any error Have a nice day |
From: Xiaofan C. <xia...@gm...> - 2014-12-18 02:34:52
|
On Wed, Dec 17, 2014 at 11:25 PM, dark hun <dar...@gm...> wrote: > Hello; > > I did all steps to compile libusb for android app. Maybe you want to tell us what you mean by "all steps". Have you followed the steps here? https://github.com/libusb/libusb/tree/master/android > However while doing that i recive > > make: Nothing to be done for `Android.mk'. > > this massage in ubuntu > > can you help me as soon as possible > or dou you have a tutorial video or something to that without any error > I do not know if there are any tutorial video available for this topic. -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2014-12-18 09:28:53
|
On Thu, Dec 18, 2014 at 5:19 PM, dark hun <dar...@gm...> wrote: > Yes, I try to did the steps written in github ( or the read me file in > libusb folder; they are same :) ). > > For more detailed information; I try to do that "NDK global variable set to > the directory" with using "export > PATH=$PATH:/home/...../........./ndk/android-ndk-r10d". (points for the hide > the name) with that comand i can use ndk-build script. > As the below > ndk-build Android.mk > > However, I must do something in a wrong way, because I receive "make: > Nothing to be done for `Android.mk'." this message > > (I installed the NDK exactly in androids' home page and I installed Android > Studio and SDK as well ) > > Besides, this command "$NDK/ndk-build" return this "bash: /ndk-build: No > such file or directory" message Isn't the issue obvious? What is "$NDK" if you "export PATH=..."? -- Xiaofan |
From: dark h. <dar...@gm...> - 2014-12-18 11:10:26
|
---------- Forwarded message ---------- From: dark hun <dar...@gm...> Date: 2014-12-18 12:03 GMT+02:00 Subject: Re: [libusb] (no subject) To: Xiaofan Chen <xia...@gm...> You mean; " (1) export PATH=$PATH:/home/...../........./ndk/android-ndk-r10d " running this command and using "ndk-build" as command is wrong i should run this " (2) export NDK=$NDK:/home/...../........./ndk/android-ndk-r10d" and run "$NDK/ndk-build". doing number 1 and using "ndk-build Android.mk" command gives me this message ** "make: > Nothing to be done for `Android.mk'." and doing number 2 and using "$NDK/ndk-build Android.mk" command gives me directory fault for me to give you for detailed information can you explain like for dummies instruction. Because it is first time to me use ubuntu for development 2014-12-18 11:28 GMT+02:00 Xiaofan Chen <xia...@gm...>: > > On Thu, Dec 18, 2014 at 5:19 PM, dark hun <dar...@gm...> wrote: > > Yes, I try to did the steps written in github ( or the read me file in > > libusb folder; they are same :) ). > > > > For more detailed information; I try to do that "NDK global variable set > to > > the directory" with using "export > > PATH=$PATH:/home/...../........./ndk/android-ndk-r10d". (points for the > hide > > the name) with that comand i can use ndk-build script. > > As the below > > ndk-build Android.mk > > > > However, I must do something in a wrong way, because I receive "make: > > Nothing to be done for `Android.mk'." this message > > > > (I installed the NDK exactly in androids' home page and I installed > Android > > Studio and SDK as well ) > > > > Besides, this command "$NDK/ndk-build" return this "bash: /ndk-build: No > > such file or directory" message > > Isn't the issue obvious? What is "$NDK" if you "export PATH=..."? > > > -- > Xiaofan > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > libusb-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-devel > |
From: Xiaofan C. <xia...@gm...> - 2014-12-18 13:55:30
|
On Thu, Dec 18, 2014 at 7:10 PM, dark hun <dar...@gm...> wrote: > > You mean; " (1) export PATH=$PATH:/home/...../........./ndk/android-ndk-r10d > " running this command and using "ndk-build" as command is wrong I meant to say if you did not set the NDK environment variable, then of-course "$NDK/ndk-build" will return the "bash: /ndk-build: No such file or directory" message since $NDK is not present. But your method of set the PATH and run "ndk-build" should work if you have a correct environment setup for Android development. > i should run this " (2) export > NDK=$NDK:/home/...../........./ndk/android-ndk-r10d" and run > "$NDK/ndk-build". That is as per README. > doing number 1 and using "ndk-build Android.mk" command gives me this > message > ** "make: > Nothing to be done for `Android.mk'." Maybe your build is already successful. Check out the output directory as per the README file. You should just run "ndk-build" to follow the README file. > and doing number 2 and using "$NDK/ndk-build Android.mk" command gives me > directory fault I am not so sure what you mean by directory fault. Maybe your setup of Android SDK/NDK is not correct. > for me to give you for detailed information can you explain like for dummies > instruction. Because it is first time to me use ubuntu for development > I am not so sure what kind of detailed information you need other than the README file. But I admit I am not an expert in Android development (never really did anything related to Android). Still I have no problems to build libusb with Android NDK, just blindly following the README instruction. But again I am not using Ubuntu but Mac OS X with homebrew. Anyway, here is what I do after installing Android-SDK and Android-NDK under Mac OS X. MyMacMini:jni xiaofanc$ pwd /Users/xiaofanc/work/libusb/libusb/android/jni MyMacMini:jni xiaofanc$ export NDK=/usr/local/Cellar/android-ndk/r10d/ MyMacMini:jni xiaofanc$ $NDK/ndk-build [arm64-v8a] Compile : dpfp <= dpfp.c [arm64-v8a] Compile : usb1.0 <= core.c [arm64-v8a] Compile : usb1.0 <= descriptor.c [arm64-v8a] Compile : usb1.0 <= hotplug.c [arm64-v8a] Compile : usb1.0 <= io.c [arm64-v8a] Compile : usb1.0 <= sync.c [arm64-v8a] Compile : usb1.0 <= strerror.c [arm64-v8a] Compile : usb1.0 <= linux_usbfs.c [arm64-v8a] Compile : usb1.0 <= poll_posix.c [arm64-v8a] Compile : usb1.0 <= threads_posix.c [arm64-v8a] Compile : usb1.0 <= linux_netlink.c [arm64-v8a] SharedLibrary : libusb1.0.so [arm64-v8a] Executable : dpfp [arm64-v8a] Install : dpfp => libs/arm64-v8a/dpfp [arm64-v8a] Compile : dpfp_threaded <= dpfp_threaded.c [arm64-v8a] Executable : dpfp_threaded [arm64-v8a] Install : dpfp_threaded => libs/arm64-v8a/dpfp_threaded [arm64-v8a] Compile : fxload <= fxload.c [arm64-v8a] Compile : fxload <= ezusb.c [arm64-v8a] Executable : fxload [arm64-v8a] Install : fxload => libs/arm64-v8a/fxload [arm64-v8a] Compile : hotplugtest <= hotplugtest.c [arm64-v8a] Executable : hotplugtest [arm64-v8a] Install : hotplugtest => libs/arm64-v8a/hotplugtest [arm64-v8a] Compile : listdevs <= listdevs.c [arm64-v8a] Executable : listdevs [arm64-v8a] Install : listdevs => libs/arm64-v8a/listdevs [arm64-v8a] Compile : sam3u_benchmark <= sam3u_benchmark.c [arm64-v8a] Executable : sam3u_benchmark [arm64-v8a] Install : sam3u_benchmark => libs/arm64-v8a/sam3u_benchmark [arm64-v8a] Compile : stress <= stress.c [arm64-v8a] Compile : testlib <= testlib.c [arm64-v8a] StaticLibrary : libtestlib.a [arm64-v8a] Executable : stress [arm64-v8a] Install : stress => libs/arm64-v8a/stress [arm64-v8a] Install : libusb1.0.so => libs/arm64-v8a/libusb1.0.so [arm64-v8a] Compile : xusb <= xusb.c [arm64-v8a] Executable : xusb [arm64-v8a] Install : xusb => libs/arm64-v8a/xusb ... (skipped other arch) ... MyMacMini:jni xiaofanc$ ls ../libs/ arm64-v8a/ armeabi-v7a/ mips64/ x86_64/ armeabi/ mips/ x86/ MyMacMini:jni xiaofanc$ ls ../libs/arm64-v8a/ dpfp fxload libusb1.0.so sam3u_benchmark xusb dpfp_threaded hotplugtest listdevs stress MyMacMini:jni xiaofanc$ ls ../libs/armeabi-v7a/ dpfp fxload libusb1.0.so sam3u_benchmark xusb dpfp_threaded hotplugtest listdevs stress -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2014-12-20 13:54:47
|
On Fri, Dec 19, 2014 at 4:25 PM, dark hun <dar...@gm...> wrote: > Thanks for your help; I successfully compile for android :D > Glad that you made it. -- Xiaofan |
From: David K. <dk7...@gm...> - 2018-05-28 08:18:27
|
Test going good david |