Hot answers tagged

4

Well, this is not an answer to the question but brings me a solution. so here it is. I fiddle quite a bit with Udev rules, could not get anything better than my Arduino persistently appear on /dev/arduino01 (will use /dev/arduino02, /dev/arduino03,... for other jigs) My testing script is in Python, I just found out that there is a nice library called ...


2

Usb devices are far more complex than simply pipes you read and write. You'll have to write code to manipulate them. You don't need to write a kernel driver. See http://libusb.org and http://libusb.sourceforge.net/api-1.0. This is possibly Linux-specific. Under Mac OS X there are user-level functions in I/O Kit that will let you access USB. Here's a little ...


2

Note: This is a linux answer, other kernels will have a slightly different way to deal with this. Context It is difficult to talk about USB buses without talking about PCI buses. A CPU cannot talk to a USB bus, what happens is that the CPU talks to a PCI bus which has a USB controller connected to it (and a USB controller/hub is what lsusb calls a USB bus)...


1

There are quite a few different ways to automount storage devices on linux. Even the location of the mounts varies quite bit. Also not all system are set up to automount devices and some desktop environments will automount when you access them others when you plug them in. Basically, to make it portable you cannot rely mount points in a location to find ...


1

Use unetbootin : https://unetbootin.github.io/. Here is a tutorial for ubuntu but you can also use it for debian just change the image :http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx


1

Create a USB flash drive with which they install OpenBSD directly from the serial console. Without external monitor. Direct with the Laptop! Port com0 speed 115200 1) Download image from: https://openbsd.delfic.org/pub/OpenBSD/snapshots/amd64/install60.fs 2) Enter on the OpenBSD host: pwd /home/tom Then vnconfig -c vnd0 /...


1

udev does not have only serials to match devices, you can use any property available. So you can use almost any thing different in udevadm info /dev/... & udevadm info -a /dev/... from both devices with same serials. If you can share those outputs for each device, I may able to help. From your answer, it seems you already got vendor/model not the same, ...



Only top voted, non community-wiki answers of a minimum length are eligible