10-22-2013
/dev/bus/usb isn't for serial ports, it is for raw USB communication. His software would have to speak USB protocol, and know how to use it to talk to the device.
Sometimes this is necessary for strange cameras, but isn't often done.
This User Gave Thanks to Corona688 For This Post:
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
HI there. I am studying System administration right now and am stuck on a question that I have failed to find the answer for in my book.
The question is: Do device files need to be in the /dev directory and to they need to follow a naming convention?
My answer (so far) is that since the... (7 Replies)
Discussion started by: Carl1976
7 Replies
2. Android
I just upgraded to Android 2.2 from 2.1. The GPS issue that was troublesome in 2.1 seems to have been fixed. Some of web browsing seems faster, but it could just be my connection is better today ;) Flash works in some browsers but not very good and it is too slow for Flash apps designed for... (0 Replies)
Discussion started by: Neo
0 Replies
3. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
4. Android
I am looking for a way to run on top of the Linux kernel of an Android device. I want to use the existing configured Linux beneath Android rather than put a new Linux distribution onto a device.
The article "The Android boot process from power on" (sorry, forum won't let me paste the link)... (0 Replies)
Discussion started by: raoulney
0 Replies
5. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
6. UNIX for Beginners Questions & Answers
this is worked "ANDROID NOUGAT" how can i use it for "ANDROID OREO"
-plz help me...
-------------------------------------------
echo " Ã-~-DEVICE ID CHANGINGÃ-~-"
sleep 2
echo "
"
COUNT=1
while
do
;
echo "settings put secure android_id " | tr -d '\n' > X1... (4 Replies)
Discussion started by: f4is4l
4 Replies
LEARN ABOUT SUSE
usb_make_path
USB_MAKE_PATH(9) Host-Side Data Types and Macro USB_MAKE_PATH(9)
NAME
usb_make_path - returns stable device path in the usb tree
SYNOPSIS
int usb_make_path(struct usb_device * dev, char * buf, size_t size);
ARGUMENTS
dev
the device whose path is being constructed
buf
where to put the string
size
how big is "buf"?
DESCRIPTION
Returns length of the string (> 0) or negative if size was too small.
This identifier is intended to be "stable", reflecting physical paths in hardware such as physical bus addresses for host controllers or
ports on USB hubs. That makes it stay the same until systems are physically reconfigured, by re-cabling a tree of USB devices or by moving
USB host controllers. Adding and removing devices, including virtual root hubs in host controller driver modules, does not change these
path identifers; neither does rebooting or re-enumerating. These are more useful identifiers than changeable ("unstable") ones like bus
numbers or device addresses.
With a partial exception for devices connected to USB 2.0 root hubs, these identifiers are also predictable. So long as the device tree
isn't changed, plugging any USB device into a given hub port always gives it the same path. Because of the use of "companion" controllers,
devices connected to ports on USB 2.0 root hubs (EHCI host controllers) will get one path ID if they are high speed, and a different one if
they are full or low speed.
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 USB_MAKE_PATH(9)