On Sat, Feb 22, 2014 at 07:24:52AM -0800, Duane Ellis wrote: > I figured out the problem, this was *NOT* very clear
So what was wrong? > The user manual could be improved as follows: > > ------------------ > a) In section 4, change: > FROM: On Linux, this usually involves installing a file in /etc/udev/rules.d, > TO: On Linux, this requires a rules file in /etc/udev/rules.d [See the FAQ > for > more details] This is distro-specific and belongs to sysadmin realm of responsibility, they're supposed to know better... > b) Add a new entry to the FAQ > Debugging Linux USB and UDEV rules > First, determine if your adapter is being recognized, use: "lsusb" and > verify your adapter is listed. If needed, try the lsusb command with your > adapter plugged in, and with it removed. This has nothing to do with udev at all, right? > Second has to do with permissions which are handled by Linux UDEV > Openocd provides a UDEV file named: "openocd.udev" you must copy/rename > this > file to exactly: > /etc/udev/rules.d/60-openocd.rules So you mean it should end in .rules and not .udev? I guess we might want to rename openocd.udev to openocd.rules instead? > The number 60 is an example, can be any number you choose, I wonder if it can go without the number altogether. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
