Re: udev and irda-usb trouble

[Chris Horn <chris@beefstew.net>]

On Tuesday 21 December 2004 19:52, Greg KH wrote:
> On Tue, Dec 21, 2004 at 07:43:47PM -0500, Chris Horn wrote:
> > On Tuesday 21 December 2004 19:26, Greg KH wrote:
> > > On Tue, Dec 21, 2004 at 07:05:47PM -0500, Chris Horn wrote:
> > > > On Tuesday 21 December 2004 18:50, Kay Sievers wrote:
> > > > > On Tue, 2004-12-21 at 16:17 -0500, Chris Horn wrote:
> > > > > > Generally I am quite happy with udev and USB in Linux.  One thing, 
> > > > > > though,
> > > > > > really bothers me.  I haven't been able to write a udev rule to 
pick up 
> > > > > > my
> > > > > > irda-usb based IrDA dongle.
> > > > > > 
> > > > > > I can talk to it just fine if I manually create an irda0 node 
in /dev 
> > > > > > with
> > > > > > mknod, but I don't want to keep doing that (udev keeps deleting my 
> > > > > > node).
> > > > > > Irattach connects just fine with 'irattach irda0 none -s'** 
without
> > > > > > the /dev/irda0 node, but my application (jpilot) obviously needs a 
file 
> > > > > > to
> > > > > > talk through.
> > > > > > 
> > > > > > Problems:
> > > > > > 1. I can't seem to get any info with udevinfo on any irda or 
ircomm 
> > > > > > node.
> > > > > > 2. Even if I create a /dev/irda0 node, unload all the modules and 
then 
> > > > > > have
> > > > > > usb.agent detect the device plugin event and start up all the 
modules, 
> > > > > > udev
> > > > > > will not make any nodes for me.  I even tried rebooting, even 
though I 
> > > > > > know
> > > > > > that shouldn't be necessary.
> > > > > > 3. udev works fine for my other devices.
> > > > > > 
> > > > > > The latest rule I've been trying is:
> > > > > > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="%k"
> > > > > 
> > > > > Hey, don't use the same value for NAME _and_ SYMLINK. :)
> > > > > 
> > > > > Kay
> > > > 
> > > > Thanks for the tip - I should've realized that was silly.  I've tried 
it with 
> > > > other text there (and just re-tried it), though, and it still doesn't 
work.
> > > > 
> > > > I just tried this:
> > > > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="IRdongle"
> > > 
> > > Is there really a /sys/class/usb/irda* device in sysfs for your device?
> > > I didn't think the irda driver used the usb major number.  Where in
> > > sysfs does the "dev" file for this device show up (it should be
> > > somewhere in /sys/class/.  If not there, that's why this isn't working.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > It's got information under /sys/class: 
> >  
> > # l /sys/class/net/irda0/
> > total 0
> > -r--r--r--  1 root root 4096 Dec 21 19:01 addr_len
> > -r--r--r--  1 root root 4096 Dec 21 19:01 address
> > -r--r--r--  1 root root 4096 Dec 21 19:01 broadcast
> > -r--r--r--  1 root root 4096 Dec 21 19:01 features
> > -rw-r--r--  1 root root 4096 Dec 21 19:01 flags
> > -r--r--r--  1 root root 4096 Dec 21 19:01 ifindex
> > -r--r--r--  1 root root 4096 Dec 21 19:01 iflink
> > -rw-r--r--  1 root root 4096 Dec 21 19:01 mtu
> > drwxr-xr-x  2 root root    0 Dec 21 19:01 statistics
> > -rw-r--r--  1 root root 4096 Dec 21 19:01 tx_queue_len
> > -r--r--r--  1 root root 4096 Dec 21 19:01 type
> 
> net devices do not have a /dev node :)
> 

Okay, thanks - I didn't know that.

Is there anything I can do to get udev (or whatever is responsible) from 
deleting the nodes I put in by hand?  Is there a "don't delete list 
somewhere?"

Thanks.
Chris.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel