On Thu, Jun 25, 2009 at 04:21:09PM -0700, jack craig wrote:
>
>
> Greg KH wrote:
> > On Thu, Jun 25, 2009 at 11:12:29AM -0700, jack craig wrote:
> >> I knew the 'Big Guns' wouldnt fail me! :)
> >>
> >>
> >> Greg KH wrote:
> >>> On Thu, Jun 25, 2009 at 09:04:59AM -0700, jack craig wrote:
> >>>> i have created the rule, ...
> >>>>
> >>>> BUS=="usb", ATTRS{idVendor}=="1808", ATTRS{idProduct}=="5555", NAME="obdii", MODE="0666", SYMLINK+="obdii"
> >>>>
> >>>> when i plug in my widget, sure enough, i get a /dev/obdii created with
> >>>> my desired permissions so udev is ok (AFAIK).
> >>> It should be a symlink, right? What is the link pointing to?
> >> well, as i expect it, /dev/obdii should get created on usb hotplug
> >> event and evaporate when its unplugged.
> >
> > Again, what is that link pointing to?
>
> the intention was for it to point to the /dev/bus/usb/003/### where
> the libusb is accessing the device. i am creating this rule for the
> first time, it could easily be wrong, but it does create the
> /dev/obdii as a standalone character device file with the proper
> perms.
>
> i tried this code with and w/o the symlink and it made no difference.
And again, what exactly is this device node, or link? What does:
ls -l /dev/obdii
show?
What is this device? Does a kernel driver bind to it already? If so,
why are you trying to mess with libusb?
you are going to need to provide more information...
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
