linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <a0123195@tiscali.de>
To: linux-hotplug@vger.kernel.org
Subject: Problems defining an udev rule for usb-daq board
Date: Fri, 18 Aug 2006 10:59:34 +0000	[thread overview]
Message-ID: <7713092.1155898774121.JavaMail.root@ps14> (raw)

Hi all,
I've got trouble configuring an usb-daq board with udev. I use a 
recent self-compiled kernel (2.6.16-2-686) on Debian testing with 
comedi-0.7.72 and an usb-daq board (usbdux). The daq-board runs 
perfect, but I can't figure out how it can be automagically configured 
by udev when hotplugged. After connecting the board,  one had to 
execute the following command (as root): 

/usr/local/sbin/comedi_config -i /usr/local/share/usb/usbdux_firmware.
hex /dev/comedi0 usbdux

I tried the following udev-rule without success:

KERNEL="usbdux", SUSBSYSTEM="module",  SYSFS{refcnt}="0", RUN+="
/usr/local/bin/config_usbdux"

where "config_usbdux" is a shell-script with the comedi_config command 
above.

The following output might be helpful:

# udevinfo -a -p /sys/module/usbdux/

[...]

  looking at device '/module/usbdux':
    KERNEL="usbdux"
    SUBSYSTEM="module"
    SYSFS{refcnt}="0"

# udevinfo -a -p /sys/bus/usb/drivers/usbdux/

  looking at device '/bus/usb/drivers/usbdux':
    KERNEL="usbdux"
    SUBSYSTEM="drivers"

After connecting the daq-board, dmesg shows:

usb 5-1: new high speed USB device using ehci_hcd and address 34
usb 5-1: configuration #1 chosen from 1 choice
comedi_: usbdux_: finding a free structure for the usb-device
comedi_: usbdux: usbduxsub[0] is ready to connect to comedi.
comedi_: usbdux: ifnum=0
comedi_: usbdux0 has been successfully initialised.

After configuring with comedi_config dmesg shows

comedi0: usbdux: uploading 1471 bytes to addr 0, first byte=2.
comedi0: usbdux: usb-device 0 is attached to comedi.
comedi0: attached to usbdux.

Now the board is ready to use,. Any ideas? Thanks in advance, Sven








Endlich Sicherheit bei Computerabstuerzen - Phoenix Recover Pro. http://internetzugang.tiscali.de/internet_services/detail_rec.php


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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

             reply	other threads:[~2006-08-18 10:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 10:59 a0123195 [this message]
2006-08-18 11:31 ` Problems defining an udev rule for usb-daq board Kay Sievers
2006-08-18 12:20 ` AW: " a0123195
2006-08-18 12:26 ` Kay Sievers
2006-08-19  2:59 ` Greg KH
2006-08-21 14:55 ` AW: " a0123195
2006-08-21 16:49 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7713092.1155898774121.JavaMail.root@ps14 \
    --to=a0123195@tiscali.de \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).