Re: [Openocd-development] udev rules for openocd

2009-01-21 Thread John McCarthy
how about this one for the OpenOCD USB from Embedded-Projects.net: SUBSYSTEMS==usb, ATTRS{product}==Dual RS232, ATTRS{idProduct}==6010, ATTRS{idVendor}==0403, KERNEL==ttyUSB*, SYMLINK+=openocd$attr{bInterfaceNumber} creates /dev/openocd00 and /dev/openocd01 for the two serial interfaces.

Re: [Openocd-development] udev rules for openocd

2009-01-21 Thread John McCarthy
Hmm, guess I should have read the whole thread before I posted. ;-) I see the openocd.udev patch is worrying about permissions for the USB devices. For my FT2232 based OpenOCD USB device the tty devices are also important. This becomes a real headache when you have multiple ttyUSB devices

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Uwe Hermann
On Tue, Jan 20, 2009 at 07:53:14AM -0600, lou.openocd...@fixit.nospammail.net wrote: And another part for rlink: # Raisonance RLink SYSFS{idVendor}==138e, SYSFS{idProduct}==9000, MODE=664, GROUP=plugdev Does the 4 in 664 make sense? Yes, you don't want _all_ users to have write access,

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread lou . openocd012
On Tue, Jan 20, 2009 at 04:39:52PM +0100, Uwe Hermann wrote: On Tue, Jan 20, 2009 at 07:53:14AM -0600, lou.openocd...@fixit.nospammail.net wrote: And another part for rlink: # Raisonance RLink SYSFS{idVendor}==138e, SYSFS{idProduct}==9000, MODE=664, GROUP=plugdev Does the 4 in

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Uwe Hermann
On Tue, Jan 20, 2009 at 08:39:14PM +0100, Uwe Hermann wrote: On Tue, Jan 20, 2009 at 09:07:42AM -0800, Rick Altherr wrote: I await an updated file that includes all the additional device lines that have flown by on this list. Sure, attached. Oops, forgot one. Updated patch attached.

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Uwe Hermann
On Tue, Jan 20, 2009 at 10:15:42AM -0600, lou.openocd...@fixit.nospammail.net wrote: Of course. Why not 0, then? Does it make sense to give everybody read access to the node? Ah, I see. I don't know which one should be used, I don't mind either way. As far as I've seen in /etc/udev/ on my

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Michel Catudal
Rick Altherr a écrit : In terms of including this as part of OpenOCD, we suffer from supporting multiple platforms and distrubtions. The preferred install location for the udev script is likely to vary by distribution and it only applies to the Linux platform. Many other projects handle

Re: [Openocd-development] udev rules for openocd

2009-01-20 Thread Rick Altherr
On Jan 20, 2009, at 11:51 AM, Uwe Hermann wrote: On Tue, Jan 20, 2009 at 08:39:14PM +0100, Uwe Hermann wrote: On Tue, Jan 20, 2009 at 09:07:42AM -0800, Rick Altherr wrote: I await an updated file that includes all the additional device lines that have flown by on this list. Sure,