issues getting I/O device to work with udev....

issues getting I/O device to work with udev....

[chris]

I'm trying to get an Eagle data acquisition device to work with
udev and having problems.  Any help greatly appreciated.
Please especially notice the udevtest error messages at end
of this email.....


in /etc/udev/rules.d :

::::::::::::::
10-edredaq.rules
::::::::::::::
SYSFS{edredaq_nodename}="device*", NAME="edredaq/device%m"
::::::::::::::
z-edredaq.rules
::::::::::::::
SYSFS{edredaq_nodename}="device*", NAME="edredaq/device%m"


I have a Debian Etch (testing) Intel PC with a 2.6.15 kernel
built from source.  My udev version is 0.093-1.

Here are related dmesg messages....

# dmesg | grep -i edre
edredaq_core: major number = 254
edredaq_core: Registered node 0

# dmesg | grep -i eagle
PCI703 Interface Driver (C) 2004 - 2005 Eagle Technology (v1.0.9)

Here is /sys/class/edredaq/device0 and related udevtest command
output:

# ls /sys/class/edredaq/device0
./  ../  dev  device  edredaq_nodename  uevent


# udevtest edredaq/device0
add_to_rules: invalid SYSFS operation
add_to_rules: invalid rule '/etc/udev/rules.d/10-edredaq.rules:1'
add_to_rules: invalid SYSFS operation
add_to_rules: invalid rule '/etc/udev/rules.d/z-edredaq.rules:1'
main: unable to open 'edredaq/device0'



Thanks.

Chris

-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[Marco d'Itri]

On Aug 24, chris@seberino.org wrote:

> SYSFS{edredaq_nodename}="device*", NAME="edredaq/device%m"
Use something like:

SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*", \
	NAME="edredaq/device%m"

If it does not work, use udevinfo -a -p /sys/class/edredaq/device0/ to
find the SUBSYSTEM name.

-- 
ciao,
Marco

-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[chris]

Marco

Thanks.  I changed 10-edredaq.rules and z-edredaq.rules to both be

SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*", NAME="edredaq/device%m"

Now 'udevtest edredaq/device0' has just this error message left:

main: unable to open 'edredaq/device0'


Here is 'udevinfo -a -p /sys/class/edredaq/device0' output if
useful...

cs
==========
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.

  looking at device '/class/edredaq/device0':
    KERNEL="device0"
    SUBSYSTEM="edredaq"
    SYSFS{edredaq_nodename}="device0"
    SYSFS{dev}="254:0"

  looking at device '/devices/pci0000:00/0000:00:1e.0/0000:02:0c.0':
    ID="0000:02:0c.0"
    BUS="pci"
    DRIVER="pci703drv"
    SYSFS{serial}="1000010398"
    SYSFS{modalias}="pci:v0000EA01d00000052sv00000000sd00000000bcFFsc00i00"
    SYSFS{local_cpus}="1"
    SYSFS{irq}="137"
    SYSFS{class}="0xff0000"
    SYSFS{subsystem_device}="0x0000"
    SYSFS{subsystem_vendor}="0x0000"
    SYSFS{device}="0x0052"
    SYSFS{vendor}="0xea01"

  looking at device '/devices/pci0000:00/0000:00:1e.0':
    ID="0000:00:1e.0"
    BUS="pci"
    DRIVER=""
    SYSFS{modalias}="pci:v00008086d0000244Esv00000000sd00000000bc06sc04i00"
    SYSFS{local_cpus}="1"
    SYSFS{irq}="0"
    SYSFS{class}="0x060400"
    SYSFS{subsystem_device}="0x0000"
    SYSFS{subsystem_vendor}="0x0000"
    SYSFS{device}="0x244e"
    SYSFS{vendor}="0x8086"

  looking at device '/devices/pci0000:00':
    ID="pci0000:00"
    BUS=""
    DRIVER=""

-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[Kay Sievers]

On Wed, 2006-08-23 at 16:02 -0700, chris@seberino.org wrote:
> Marco
> 
> Thanks.  I changed 10-edredaq.rules and z-edredaq.rules to both be
> 
> SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*", NAME="edredaq/device%m"
> 
> Now 'udevtest edredaq/device0' has just this error message left:

Udevtest expects the sysfs devpath, not the node name. Try:
  udevtest /class/edredaq/device0

Kay


-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[chris]

> Udevtest expects the sysfs devpath, not the node name. Try:
>   udevtest /class/edredaq/device0

Kay, thanks.  that got me more info....

# udevtest /class/edredaq/device0
main: looking at device '/class/edredaq/device0' from subsystem
'edredaq'
udev_rules_get_name: rule applied, 'device0' becomes 'edredaq/device0'
udev_db_get_device: no db file to read
/dev/.udev/db/class@edredaq@device0: No such file or directory
udev_node_add: creating device node '/dev/edredaq/device0', major '254', minor = '0', mode = '0660', uid = '0', gid = '0'
main: run: 'socket:/org/kernel/udev/monitor'

-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[Kay Sievers]

On Wed, 2006-08-23 at 16:14 -0700, chris@seberino.org wrote:
> > Udevtest expects the sysfs devpath, not the node name. Try:
> >   udevtest /class/edredaq/device0
> 
> Kay, thanks.  that got me more info....
> 
> # udevtest /class/edredaq/device0
> main: looking at device '/class/edredaq/device0' from subsystem
> 'edredaq'
> udev_rules_get_name: rule applied, 'device0' becomes 'edredaq/device0'
> udev_db_get_device: no db file to read
> /dev/.udev/db/class@edredaq@device0: No such file or directory
> udev_node_add: creating device node '/dev/edredaq/device0', major > '254', minor = '0', mode = '0660', uid = '0', gid = '0'
> main: run: 'socket:/org/kernel/udev/monitor'

Yeah, looks all fine.

To see how all that works, you may want to have a look at:
  udevmonitor
or
  udevmonoitor --env
while you load your kernel module.

There you can watch what the kernel sends to udev and what udev is doing
with it. You can also see all the devpath's, which are the kernels key
to the device, and which udevtest expects to simulate an event run.

Kay


-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[chris]

> Yeah, looks all fine.
>
> To see how all that works, you may want to have a look at:
>   udevmonitor
> or
>   udevmonoitor --env
> while you load your kernel module.

I can't rmmod these drivers to reload them with udevmonitor on...

# rmmod pci703drv
ERROR: Removing 'pci703drv': Device or resource busy
# rmmod edredaqdrv
ERROR: Module edredaqdrv is in use by pci703drv


And they always appear at reboot.

chris

-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

> -----Original Message-----
> From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> Sent: 24 August 2006 01:10 AM
> To: chris@seberino.org
> Cc: md@Linux.IT; linux-hotplug-devel@lists.sourceforge.net; John Thomas;
> jan@eagle.co.za; Ray Schumacher
> Subject: Re: issues getting I/O device to work with udev....
> 
> On Wed, 2006-08-23 at 16:02 -0700, chris@seberino.org wrote:
> > Marco
> >
> > Thanks.  I changed 10-edredaq.rules and z-edredaq.rules to both be
> >
> > SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> NAME="edredaq/device%m"
> >
> > Now 'udevtest edredaq/device0' has just this error message left:
> 
> Udevtest expects the sysfs devpath, not the node name. Try:
>   udevtest /class/edredaq/device0
[Jan Zwiegers] 
I'm the developer at Eagle who wrote all the Linux DAQ class & device
drivers (PCI, PC104 & USB) and also the udev rule. Out API depends on the
fact that the device gets created under /dev/edredaq/device0-99. This rules
worked just fine on previous systems, but suddenly it started to fail on
newer distros. Please have a look at the following. udev seems to work fine,
but I think the problem might be with PAM.

udevinfo -a -p /sys/class/edredaq/device0/

...
looking at device '/class/edredaq/device0':
    KERNEL="device0"
    SUBSYSTEM="edredaq"
    SYSFS{edredaq_nodename}="device0"
    SYSFS{dev}="253:0"
...

udevtest /class/edredaq/device0/

main: looking at device '/class/edredaq/device0' from subsystem 'edredaq'
udev_rules_get_name: rule applied, 'device0' becomes 'edredaq/device0'
create_node: creating device node '/dev/edredaq/device0', major = '253',
minor = '0', mode = '0666', uid = '0', gid = '0'
main: run: 'socket:/org/kernel/udev/monitor'
main: run: '/lib/udev/udev_run_devd'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: '/sbin/pam_console_apply /dev/edredaq/device0 '

And also the updated rule z-edredaq.rules as suggested by Marco (many thanks
Marco)
SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
NAME="edredaq/device%m"

Can you guys maybe point me to a solution?

Jan

> 
> Kay



-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Kay Sievers]

On Fri, 2006-08-25 at 11:19 +0200, Jan Zwiegers wrote:
> > -----Original Message-----
> > From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> > Sent: 24 August 2006 01:10 AM
> > To: chris@seberino.org
> > Cc: md@Linux.IT; linux-hotplug-devel@lists.sourceforge.net; John Thomas;
> > jan@eagle.co.za; Ray Schumacher
> > Subject: Re: issues getting I/O device to work with udev....
> > 
> > On Wed, 2006-08-23 at 16:02 -0700, chris@seberino.org wrote:
> > > Marco
> > >
> > > Thanks.  I changed 10-edredaq.rules and z-edredaq.rules to both be
> > >
> > > SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> > NAME="edredaq/device%m"
> > >
> > > Now 'udevtest edredaq/device0' has just this error message left:
> > 
> > Udevtest expects the sysfs devpath, not the node name. Try:
> >   udevtest /class/edredaq/device0
> [Jan Zwiegers] 
> I'm the developer at Eagle who wrote all the Linux DAQ class & device
> drivers (PCI, PC104 & USB) and also the udev rule. Out API depends on the
> fact that the device gets created under /dev/edredaq/device0-99. This rules
> worked just fine on previous systems, but suddenly it started to fail on
> newer distros. Please have a look at the following. udev seems to work fine,
> but I think the problem might be with PAM.
> 
> udevinfo -a -p /sys/class/edredaq/device0/
> 
> ...
> looking at device '/class/edredaq/device0':
>     KERNEL="device0"
>     SUBSYSTEM="edredaq"
>     SYSFS{edredaq_nodename}="device0"
>     SYSFS{dev}="253:0"
> ...
> 
> udevtest /class/edredaq/device0/
> 
> main: looking at device '/class/edredaq/device0' from subsystem 'edredaq'
> udev_rules_get_name: rule applied, 'device0' becomes 'edredaq/device0'
> create_node: creating device node '/dev/edredaq/device0', major = '253',
> minor = '0', mode = '0666', uid = '0', gid = '0'
> main: run: 'socket:/org/kernel/udev/monitor'
> main: run: '/lib/udev/udev_run_devd'
> main: run: 'socket:/org/freedesktop/hal/udev_event'
> main: run: '/sbin/pam_console_apply /dev/edredaq/device0 '
> 
> And also the updated rule z-edredaq.rules as suggested by Marco (many thanks
> Marco)
> SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> NAME="edredaq/device%m"
> 
> Can you guys maybe point me to a solution?

Hmm, what exactly is the problem? What suddenly started to fail?

Can you paste the output of 'udevmonitor' when you load the kernel
module? Or the output when connect the USB device, if you only have it
built-in.

Kay


-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

> -----Original Message-----
> From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay Sievers
> Sent: 25 August 2006 12:37 PM
> To: jan@eagle.co.za
> Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> Schumacher'; md@Linux.IT
> Subject: RE: issues getting I/O device to work with udev....
> 
> On Fri, 2006-08-25 at 11:19 +0200, Jan Zwiegers wrote:
> > > -----Original Message-----
> > > From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> > > Sent: 24 August 2006 01:10 AM
> > > To: chris@seberino.org
> > > Cc: md@Linux.IT; linux-hotplug-devel@lists.sourceforge.net; John
> Thomas;
> > > jan@eagle.co.za; Ray Schumacher
> > > Subject: Re: issues getting I/O device to work with udev....
> > >
> > > On Wed, 2006-08-23 at 16:02 -0700, chris@seberino.org wrote:
> > > > Marco
> > > >
> > > > Thanks.  I changed 10-edredaq.rules and z-edredaq.rules to both be
> > > >
> > > > SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> > > NAME="edredaq/device%m"
> > > >
> > > > Now 'udevtest edredaq/device0' has just this error message left:
> > >
> > > Udevtest expects the sysfs devpath, not the node name. Try:
> > >   udevtest /class/edredaq/device0
> > [Jan Zwiegers]
> > I'm the developer at Eagle who wrote all the Linux DAQ class & device
> > drivers (PCI, PC104 & USB) and also the udev rule. Out API depends on
> the
> > fact that the device gets created under /dev/edredaq/device0-99. This
> rules
> > worked just fine on previous systems, but suddenly it started to fail on
> > newer distros. Please have a look at the following. udev seems to work
> fine,
> > but I think the problem might be with PAM.
> >
> > udevinfo -a -p /sys/class/edredaq/device0/
> >
> > ...
> > looking at device '/class/edredaq/device0':
> >     KERNEL="device0"
> >     SUBSYSTEM="edredaq"
> >     SYSFS{edredaq_nodename}="device0"
> >     SYSFS{dev}="253:0"
> > ...
> >
> > udevtest /class/edredaq/device0/
> >
> > main: looking at device '/class/edredaq/device0' from subsystem
> 'edredaq'
> > udev_rules_get_name: rule applied, 'device0' becomes 'edredaq/device0'
> > create_node: creating device node '/dev/edredaq/device0', major = '253',
> > minor = '0', mode = '0666', uid = '0', gid = '0'
> > main: run: 'socket:/org/kernel/udev/monitor'
> > main: run: '/lib/udev/udev_run_devd'
> > main: run: 'socket:/org/freedesktop/hal/udev_event'
> > main: run: '/sbin/pam_console_apply /dev/edredaq/device0 '
> >
> > And also the updated rule z-edredaq.rules as suggested by Marco (many
> thanks
> > Marco)
> > SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> > NAME="edredaq/device%m"
> >
> > Can you guys maybe point me to a solution?
> 
> Hmm, what exactly is the problem? What suddenly started to fail?
[Jan Zwiegers] 
The node /dev/edredaq/device0 never get created, or it does not show up in
the file system (maybe it's permission / security related). Unfortunately I
have left work already and cannot do the 'udevmonitor' for you. 
> 
> Can you paste the output of 'udevmonitor' when you load the kernel
> module? Or the output when connect the USB device, if you only have it
> built-in.
> 
> Kay
> 
> 
> -------------------------------------------------------------------------
> 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



-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

> -----Original Message-----
> From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> Sent: 25 August 2006 12:37 PM
> To: jan@eagle.co.za
> Cc: chris@seberino.org; 'John Thomas'; linux-hotplug-
> devel@lists.sourceforge.net; 'Ray Schumacher'; md@Linux.IT
> Subject: RE: issues getting I/O device to work with udev....
> 
> On Fri, 2006-08-25 at 11:19 +0200, Jan Zwiegers wrote:
> > > -----Original Message-----
> > > From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> > > Sent: 24 August 2006 01:10 AM
> > > To: chris@seberino.org
> > > Cc: md@Linux.IT; linux-hotplug-devel@lists.sourceforge.net; John
> Thomas;
> > > jan@eagle.co.za; Ray Schumacher
> > > Subject: Re: issues getting I/O device to work with udev....
> > >
> > > On Wed, 2006-08-23 at 16:02 -0700, chris@seberino.org wrote:
> > > > Marco
> > > >
> > > > Thanks.  I changed 10-edredaq.rules and z-edredaq.rules to both be
> > > >
> > > > SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> > > NAME="edredaq/device%m"
> > > >
> > > > Now 'udevtest edredaq/device0' has just this error message left:
> > >
> > > Udevtest expects the sysfs devpath, not the node name. Try:
> > >   udevtest /class/edredaq/device0
> > [Jan Zwiegers]
> > I'm the developer at Eagle who wrote all the Linux DAQ class & device
> > drivers (PCI, PC104 & USB) and also the udev rule. Out API depends on
> the
> > fact that the device gets created under /dev/edredaq/device0-99. This
> rules
> > worked just fine on previous systems, but suddenly it started to fail on
> > newer distros. Please have a look at the following. udev seems to work
> fine,
> > but I think the problem might be with PAM.
> >
> > udevinfo -a -p /sys/class/edredaq/device0/
> >
> > ...
> > looking at device '/class/edredaq/device0':
> >     KERNEL="device0"
> >     SUBSYSTEM="edredaq"
> >     SYSFS{edredaq_nodename}="device0"
> >     SYSFS{dev}="253:0"
> > ...
> >
> > udevtest /class/edredaq/device0/
> >
> > main: looking at device '/class/edredaq/device0' from subsystem
> 'edredaq'
> > udev_rules_get_name: rule applied, 'device0' becomes 'edredaq/device0'
> > create_node: creating device node '/dev/edredaq/device0', major = '253',
> > minor = '0', mode = '0666', uid = '0', gid = '0'
> > main: run: 'socket:/org/kernel/udev/monitor'
> > main: run: '/lib/udev/udev_run_devd'
> > main: run: 'socket:/org/freedesktop/hal/udev_event'
> > main: run: '/sbin/pam_console_apply /dev/edredaq/device0 '
> >
> > And also the updated rule z-edredaq.rules as suggested by Marco (many
> thanks
> > Marco)
> > SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> > NAME="edredaq/device%m"
> >
> > Can you guys maybe point me to a solution?
> 
> Hmm, what exactly is the problem? What suddenly started to fail?
[Jan Zwiegers] 
Sorry I forgot to add, this particular device is PCI, but the same happends
with my USB & PC104/ISA drivers. All the drivers register with the my DAQ
class driver, which intern does the SYSFS & file interface part.
> 
> Can you paste the output of 'udevmonitor' when you load the kernel
> module? Or the output when connect the USB device, if you only have it
> built-in.
> 
> Kay



-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Kay Sievers]

On Fri, 2006-08-25 at 13:38 +0200, Jan Zwiegers wrote:
> > > fact that the device gets created under /dev/edredaq/device0-99. This
> > rules
> > > worked just fine on previous systems, but suddenly it started to fail on
> > > newer distros.

> > > Can you guys maybe point me to a solution?
> > 
> > Hmm, what exactly is the problem? What suddenly started to fail?
> > Can you paste the output of 'udevmonitor' when you load the kernel
> > module? Or the output when connect the USB device, if you only have it
> > built-in.

> The node /dev/edredaq/device0 never get created, or it does not show up in
> the file system (maybe it's permission / security related). Unfortunately I
> have left work already and cannot do the 'udevmonitor' for you. 

Oh, that all sounds very much like you don't use the right driver core
functions and you create the "dev" file yourself in sysfs. You must use
the right functions in the kernel and pass the correct dev_t to the
device registration. That will automatically create the "dev" file and
add the needed data to the uevent environment, to let udev create the
node.

But again, to verify this, we need the output of "udevmonitor --env",
while you plug in a device or re-trigger the event by writing "add" to
the "uevent" file in the sysfs device directory.

Kay 


-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

> -----Original Message-----
> From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay Sievers
> Sent: 25 August 2006 03:00 PM
> To: jan@eagle.co.za
> Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> Schumacher'; md@Linux.IT
> Subject: RE: issues getting I/O device to work with udev....
> 
> On Fri, 2006-08-25 at 13:38 +0200, Jan Zwiegers wrote:
> > > > fact that the device gets created under /dev/edredaq/device0-99.
> This
> > > rules
> > > > worked just fine on previous systems, but suddenly it started to
> fail on
> > > > newer distros.
> 
> > > > Can you guys maybe point me to a solution?
> > >
> > > Hmm, what exactly is the problem? What suddenly started to fail?
> > > Can you paste the output of 'udevmonitor' when you load the kernel
> > > module? Or the output when connect the USB device, if you only have it
> > > built-in.
> 
> > The node /dev/edredaq/device0 never get created, or it does not show up
> in
> > the file system (maybe it's permission / security related).
> Unfortunately I
> > have left work already and cannot do the 'udevmonitor' for you.
> 
> Oh, that all sounds very much like you don't use the right driver core
> functions and you create the "dev" file yourself in sysfs. You must use
> the right functions in the kernel and pass the correct dev_t to the
> device registration. That will automatically create the "dev" file and
> add the needed data to the uevent environment, to let udev create the
> node.
> 
> But again, to verify this, we need the output of "udevmonitor --env",
> while you plug in a device or re-trigger the event by writing "add" to
> the "uevent" file in the sysfs device directory.


I just create a simple device class by making use of:

'class_device_register' &
'class_device_createfile'
to create /sys/class/edredaq/device0 &
/sys/class/edredaq/device0/edredaq_nodename

Jan

> 
> Kay
> 
> 
> -------------------------------------------------------------------------
> 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



-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Kay Sievers]

On Fri, 2006-08-25 at 15:47 +0200, Jan Zwiegers wrote:
> > -----Original Message-----
> > From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> > hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay Sievers
> > Sent: 25 August 2006 03:00 PM
> > To: jan@eagle.co.za
> > Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> > Schumacher'; md@Linux.IT
> > Subject: RE: issues getting I/O device to work with udev....
> > 
> > On Fri, 2006-08-25 at 13:38 +0200, Jan Zwiegers wrote:
> > > > > fact that the device gets created under /dev/edredaq/device0-99.
> > This
> > > > rules
> > > > > worked just fine on previous systems, but suddenly it started to
> > fail on
> > > > > newer distros.
> > 
> > > > > Can you guys maybe point me to a solution?
> > > >
> > > > Hmm, what exactly is the problem? What suddenly started to fail?
> > > > Can you paste the output of 'udevmonitor' when you load the kernel
> > > > module? Or the output when connect the USB device, if you only have it
> > > > built-in.
> > 
> > > The node /dev/edredaq/device0 never get created, or it does not show up
> > in
> > > the file system (maybe it's permission / security related).
> > Unfortunately I
> > > have left work already and cannot do the 'udevmonitor' for you.
> > 
> > Oh, that all sounds very much like you don't use the right driver core
> > functions and you create the "dev" file yourself in sysfs. You must use
> > the right functions in the kernel and pass the correct dev_t to the
> > device registration. That will automatically create the "dev" file and
> > add the needed data to the uevent environment, to let udev create the
> > node.
> > 
> > But again, to verify this, we need the output of "udevmonitor --env",
> > while you plug in a device or re-trigger the event by writing "add" to
> > the "uevent" file in the sysfs device directory.
> 
> 
> I just create a simple device class by making use of:
> 
> 'class_device_register' &
> 'class_device_createfile'
> to create /sys/class/edredaq/device0 &
> /sys/class/edredaq/device0/edredaq_nodename

See how class_device_create() works and fills in dev_t, you need to
convert to that function or do the same with the dev_t value. You also
need to set the 'device' pointer like that function does, to make
userspace happy.

Kay


-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

> -----Original Message-----
> From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> Sent: 25 August 2006 04:02 PM
> To: jan@eagle.co.za
> Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> Schumacher'; md@Linux.IT
> Subject: RE: issues getting I/O device to work with udev....
> 
> On Fri, 2006-08-25 at 15:47 +0200, Jan Zwiegers wrote:
> > > -----Original Message-----
> > > From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> > > hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay Sievers
> > > Sent: 25 August 2006 03:00 PM
> > > To: jan@eagle.co.za
> > > Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> > > Schumacher'; md@Linux.IT
> > > Subject: RE: issues getting I/O device to work with udev....
> > >
> > > On Fri, 2006-08-25 at 13:38 +0200, Jan Zwiegers wrote:
> > > > > > fact that the device gets created under /dev/edredaq/device0-99.
> > > This
> > > > > rules
> > > > > > worked just fine on previous systems, but suddenly it started to
> > > fail on
> > > > > > newer distros.
> > >
> > > > > > Can you guys maybe point me to a solution?
> > > > >
> > > > > Hmm, what exactly is the problem? What suddenly started to fail?
> > > > > Can you paste the output of 'udevmonitor' when you load the kernel
> > > > > module? Or the output when connect the USB device, if you only
> have it
> > > > > built-in.
> > >
> > > > The node /dev/edredaq/device0 never get created, or it does not show
> up
> > > in
> > > > the file system (maybe it's permission / security related).
> > > Unfortunately I
> > > > have left work already and cannot do the 'udevmonitor' for you.
> > >
> > > Oh, that all sounds very much like you don't use the right driver core
> > > functions and you create the "dev" file yourself in sysfs. You must
> use
> > > the right functions in the kernel and pass the correct dev_t to the
> > > device registration. That will automatically create the "dev" file and
> > > add the needed data to the uevent environment, to let udev create the
> > > node.
> > >
> > > But again, to verify this, we need the output of "udevmonitor --env",
> > > while you plug in a device or re-trigger the event by writing "add" to
> > > the "uevent" file in the sysfs device directory.
> >
> >
> > I just create a simple device class by making use of:
> >
> > 'class_device_register' &
> > 'class_device_createfile'
> > to create /sys/class/edredaq/device0 &
> > /sys/class/edredaq/device0/edredaq_nodename
> 
> See how class_device_create() works and fills in dev_t, you need to
> convert to that function or do the same with the dev_t value. You also
> need to set the 'device' pointer like that function does, to make
> userspace happy.

Kay I think I'm a bit stupid here, but I don' really follow what you mean.
Do you say that I need to look at how I implemented the
class_device_create_file? Mine seems the same as others. Do you think this
is the cause of my problem? 
> 
> Kay



-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[Greg KH]

On Fri, Aug 25, 2006 at 09:22:56PM +0200, Jan Zwiegers wrote:
> > -----Original Message-----
> > From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> > Sent: 25 August 2006 04:02 PM
> > To: jan@eagle.co.za
> > Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> > Schumacher'; md@Linux.IT
> > Subject: RE: issues getting I/O device to work with udev....
> > 
> > On Fri, 2006-08-25 at 15:47 +0200, Jan Zwiegers wrote:
> > > > -----Original Message-----
> > > > From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> > > > hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay Sievers
> > > > Sent: 25 August 2006 03:00 PM
> > > > To: jan@eagle.co.za
> > > > Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> > > > Schumacher'; md@Linux.IT
> > > > Subject: RE: issues getting I/O device to work with udev....
> > > >
> > > > On Fri, 2006-08-25 at 13:38 +0200, Jan Zwiegers wrote:
> > > > > > > fact that the device gets created under /dev/edredaq/device0-99.
> > > > This
> > > > > > rules
> > > > > > > worked just fine on previous systems, but suddenly it started to
> > > > fail on
> > > > > > > newer distros.
> > > >
> > > > > > > Can you guys maybe point me to a solution?
> > > > > >
> > > > > > Hmm, what exactly is the problem? What suddenly started to fail?
> > > > > > Can you paste the output of 'udevmonitor' when you load the kernel
> > > > > > module? Or the output when connect the USB device, if you only
> > have it
> > > > > > built-in.
> > > >
> > > > > The node /dev/edredaq/device0 never get created, or it does not show
> > up
> > > > in
> > > > > the file system (maybe it's permission / security related).
> > > > Unfortunately I
> > > > > have left work already and cannot do the 'udevmonitor' for you.
> > > >
> > > > Oh, that all sounds very much like you don't use the right driver core
> > > > functions and you create the "dev" file yourself in sysfs. You must
> > use
> > > > the right functions in the kernel and pass the correct dev_t to the
> > > > device registration. That will automatically create the "dev" file and
> > > > add the needed data to the uevent environment, to let udev create the
> > > > node.
> > > >
> > > > But again, to verify this, we need the output of "udevmonitor --env",
> > > > while you plug in a device or re-trigger the event by writing "add" to
> > > > the "uevent" file in the sysfs device directory.
> > >
> > >
> > > I just create a simple device class by making use of:
> > >
> > > 'class_device_register' &
> > > 'class_device_createfile'
> > > to create /sys/class/edredaq/device0 &
> > > /sys/class/edredaq/device0/edredaq_nodename
> > 
> > See how class_device_create() works and fills in dev_t, you need to
> > convert to that function or do the same with the dev_t value. You also
> > need to set the 'device' pointer like that function does, to make
> > userspace happy.
> 
> Kay I think I'm a bit stupid here, but I don' really follow what you mean.
> Do you say that I need to look at how I implemented the
> class_device_create_file? Mine seems the same as others. Do you think this
> is the cause of my problem? 

Do you have a pointer to your source code so that we can look to see if
there is a problem with it?

thanks,

greg k-h

-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: 26 August 2006 06:48 AM
> To: Jan Zwiegers
> Cc: 'Kay Sievers'; 'John Thomas'; linux-hotplug-
> devel@lists.sourceforge.net; 'Ray Schumacher'; md@Linux.IT
> Subject: Re: issues getting I/O device to work with udev....
> 
> On Fri, Aug 25, 2006 at 09:22:56PM +0200, Jan Zwiegers wrote:
> > > -----Original Message-----
> > > From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> > > Sent: 25 August 2006 04:02 PM
> > > To: jan@eagle.co.za
> > > Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> > > Schumacher'; md@Linux.IT
> > > Subject: RE: issues getting I/O device to work with udev....
> > >
> > > On Fri, 2006-08-25 at 15:47 +0200, Jan Zwiegers wrote:
> > > > > -----Original Message-----
> > > > > From: linux-hotplug-devel-bounces@lists.sourceforge.net
> [mailto:linux-
> > > > > hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay
> Sievers
> > > > > Sent: 25 August 2006 03:00 PM
> > > > > To: jan@eagle.co.za
> > > > > Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> > > > > Schumacher'; md@Linux.IT
> > > > > Subject: RE: issues getting I/O device to work with udev....
> > > > >
> > > > > On Fri, 2006-08-25 at 13:38 +0200, Jan Zwiegers wrote:
> > > > > > > > fact that the device gets created under
> /dev/edredaq/device0-99.
> > > > > This
> > > > > > > rules
> > > > > > > > worked just fine on previous systems, but suddenly it
> started to
> > > > > fail on
> > > > > > > > newer distros.
> > > > >
> > > > > > > > Can you guys maybe point me to a solution?
> > > > > > >
> > > > > > > Hmm, what exactly is the problem? What suddenly started to
> fail?
> > > > > > > Can you paste the output of 'udevmonitor' when you load the
> kernel
> > > > > > > module? Or the output when connect the USB device, if you only
> > > have it
> > > > > > > built-in.
> > > > >
> > > > > > The node /dev/edredaq/device0 never get created, or it does not
> show
> > > up
> > > > > in
> > > > > > the file system (maybe it's permission / security related).
> > > > > Unfortunately I
> > > > > > have left work already and cannot do the 'udevmonitor' for you.
> > > > >
> > > > > Oh, that all sounds very much like you don't use the right driver
> core
> > > > > functions and you create the "dev" file yourself in sysfs. You
> must
> > > use
> > > > > the right functions in the kernel and pass the correct dev_t to
> the
> > > > > device registration. That will automatically create the "dev" file
> and
> > > > > add the needed data to the uevent environment, to let udev create
> the
> > > > > node.
> > > > >
> > > > > But again, to verify this, we need the output of "udevmonitor --
> env",
> > > > > while you plug in a device or re-trigger the event by writing
> "add" to
> > > > > the "uevent" file in the sysfs device directory.
> > > >
> > > >
> > > > I just create a simple device class by making use of:
> > > >
> > > > 'class_device_register' &
> > > > 'class_device_createfile'
> > > > to create /sys/class/edredaq/device0 &
> > > > /sys/class/edredaq/device0/edredaq_nodename
> > >
> > > See how class_device_create() works and fills in dev_t, you need to
> > > convert to that function or do the same with the dev_t value. You also
> > > need to set the 'device' pointer like that function does, to make
> > > userspace happy.
> >
> > Kay I think I'm a bit stupid here, but I don' really follow what you
> mean.
> > Do you say that I need to look at how I implemented the
> > class_device_create_file? Mine seems the same as others. Do you think
> this
> > is the cause of my problem?
> 
> Do you have a pointer to your source code so that we can look to see if
> there is a problem with it?

Can I email it directly to you Greg? It's about 1MB.

> 
> thanks,
> 
> greg k-h



-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[Greg KH]

On Sat, Aug 26, 2006 at 08:04:33AM +0200, Jan Zwiegers wrote:
> > 
> > Do you have a pointer to your source code so that we can look to see if
> > there is a problem with it?
> 
> Can I email it directly to you Greg? It's about 1MB.

How about a pointer to where everyone can download it on the net?
Or is there a license issue that prevents this from being public?

thanks,

greg k-h

-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: 26 August 2006 08:08 PM
> To: Jan Zwiegers
> Cc: 'Kay Sievers'; 'John Thomas'; linux-hotplug-
> devel@lists.sourceforge.net; 'Ray Schumacher'; md@Linux.IT
> Subject: Re: issues getting I/O device to work with udev....
> 
> On Sat, Aug 26, 2006 at 08:04:33AM +0200, Jan Zwiegers wrote:
> > >
> > > Do you have a pointer to your source code so that we can look to see
> if
> > > there is a problem with it?
> >
> > Can I email it directly to you Greg? It's about 1MB.
> 
> How about a pointer to where everyone can download it on the net?
> Or is there a license issue that prevents this from being public?
> 
[Jan Zwiegers] 
No license issues at all. It's open source and for everybody to use, copy
etc. I got most of it from your skeleton drivers anyhow or digging through
other drivers. The current version on the web is different to what I want
you to look at. I will update the source tomorrow and send you the link.
Many thanks to you and Kay for the help!
> thanks,
> 
> greg k-h



-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Kay Sievers]

On Fri, 2006-08-25 at 21:22 +0200, Jan Zwiegers wrote:
> > > > Oh, that all sounds very much like you don't use the right driver core
> > > > functions and you create the "dev" file yourself in sysfs. You must use
> > > > the right functions in the kernel and pass the correct dev_t to the
> > > > device registration. That will automatically create the "dev" file and
> > > > add the needed data to the uevent environment, to let udev create the
> > > > node.
> > > >
> > > > But again, to verify this, we need the output of "udevmonitor --env",
> > > > while you plug in a device or re-trigger the event by writing "add" to
> > > > the "uevent" file in the sysfs device directory.
> > >
> > >
> > > I just create a simple device class by making use of:
> > >
> > > 'class_device_register' &
> > > 'class_device_createfile'
> > > to create /sys/class/edredaq/device0 &
> > > /sys/class/edredaq/device0/edredaq_nodename
> > 
> > See how class_device_create() works and fills in dev_t, you need to
> > convert to that function or do the same with the dev_t value. You also
> > need to set the 'device' pointer like that function does, to make
> > userspace happy.

> Do you say that I need to look at how I implemented the
> class_device_create_file? Mine seems the same as others. Do you think this
> is the cause of my problem? 

I'm just guessing, but I expect you create the file with the name "dev"
which contains the major/minor number yourself in your driver. If that's
the case, you shouldn't do that and just set the dev_t value in the
device structure before registering the device, that will instruct the
driver core to create that file, along with environment variables needed
for udev to create a node.

The best way to do this, would probably be to use the class_device_create() function in /linux/drivers/base/class.c, which expects all the needed values as parameters.

Kay


-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

> -----Original Message-----
> From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay Sievers
> Sent: 27 August 2006 02:18 AM
> To: jan@eagle.co.za
> Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> Schumacher'; md@Linux.IT
> Subject: RE: issues getting I/O device to work with udev....
> 
> On Fri, 2006-08-25 at 21:22 +0200, Jan Zwiegers wrote:
> > > > > Oh, that all sounds very much like you don't use the right driver
> core
> > > > > functions and you create the "dev" file yourself in sysfs. You
> must use
> > > > > the right functions in the kernel and pass the correct dev_t to
> the
> > > > > device registration. That will automatically create the "dev" file
> and
> > > > > add the needed data to the uevent environment, to let udev create
> the
> > > > > node.
> > > > >
> > > > > But again, to verify this, we need the output of "udevmonitor --
> env",
> > > > > while you plug in a device or re-trigger the event by writing
> "add" to
> > > > > the "uevent" file in the sysfs device directory.
> > > >
> > > >
> > > > I just create a simple device class by making use of:
> > > >
> > > > 'class_device_register' &
> > > > 'class_device_createfile'
> > > > to create /sys/class/edredaq/device0 &
> > > > /sys/class/edredaq/device0/edredaq_nodename
> > >
> > > See how class_device_create() works and fills in dev_t, you need to
> > > convert to that function or do the same with the dev_t value. You also
> > > need to set the 'device' pointer like that function does, to make
> > > userspace happy.
> 
> > Do you say that I need to look at how I implemented the
> > class_device_create_file? Mine seems the same as others. Do you think
> this
> > is the cause of my problem?
> 
> I'm just guessing, but I expect you create the file with the name "dev"
> which contains the major/minor number yourself in your driver. If that's
> the case, you shouldn't do that and just set the dev_t value in the
> device structure before registering the device, that will instruct the
> driver core to create that file, along with environment variables needed
> for udev to create a node.
> 
> The best way to do this, would probably be to use the
> class_device_create() function in /linux/drivers/base/class.c, which
> expects all the needed values as parameters.
[Jan Zwiegers] 
Hi Kay & Greg

Sorry for taking so long to get back to you. 

The source code is downloadable at
http://www.eagle.co.za/download/download/edre_linux_drivers_2_0_8.tar.gz

If you can maybe have a quick look at the class driver. The code is very
short, so you should be able to quickly understand what is wrong.

Many thanks
Jan

> 
> Kay
> 
> 
> -------------------------------------------------------------------------
> 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



-------------------------------------------------------------------------
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

Re: issues getting I/O device to work with udev....

[Greg KH]

On Wed, Aug 30, 2006 at 03:52:39PM +0200, Jan Zwiegers wrote:
> > -----Original Message-----
> > From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> > hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay Sievers
> > Sent: 27 August 2006 02:18 AM
> > To: jan@eagle.co.za
> > Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> > Schumacher'; md@Linux.IT
> > Subject: RE: issues getting I/O device to work with udev....
> > 
> > On Fri, 2006-08-25 at 21:22 +0200, Jan Zwiegers wrote:
> > > > > > Oh, that all sounds very much like you don't use the right driver
> > core
> > > > > > functions and you create the "dev" file yourself in sysfs. You
> > must use
> > > > > > the right functions in the kernel and pass the correct dev_t to
> > the
> > > > > > device registration. That will automatically create the "dev" file
> > and
> > > > > > add the needed data to the uevent environment, to let udev create
> > the
> > > > > > node.
> > > > > >
> > > > > > But again, to verify this, we need the output of "udevmonitor --
> > env",
> > > > > > while you plug in a device or re-trigger the event by writing
> > "add" to
> > > > > > the "uevent" file in the sysfs device directory.
> > > > >
> > > > >
> > > > > I just create a simple device class by making use of:
> > > > >
> > > > > 'class_device_register' &
> > > > > 'class_device_createfile'
> > > > > to create /sys/class/edredaq/device0 &
> > > > > /sys/class/edredaq/device0/edredaq_nodename
> > > >
> > > > See how class_device_create() works and fills in dev_t, you need to
> > > > convert to that function or do the same with the dev_t value. You also
> > > > need to set the 'device' pointer like that function does, to make
> > > > userspace happy.
> > 
> > > Do you say that I need to look at how I implemented the
> > > class_device_create_file? Mine seems the same as others. Do you think
> > this
> > > is the cause of my problem?
> > 
> > I'm just guessing, but I expect you create the file with the name "dev"
> > which contains the major/minor number yourself in your driver. If that's
> > the case, you shouldn't do that and just set the dev_t value in the
> > device structure before registering the device, that will instruct the
> > driver core to create that file, along with environment variables needed
> > for udev to create a node.
> > 
> > The best way to do this, would probably be to use the
> > class_device_create() function in /linux/drivers/base/class.c, which
> > expects all the needed values as parameters.
> [Jan Zwiegers] 
> Hi Kay & Greg
> 
> Sorry for taking so long to get back to you. 
> 
> The source code is downloadable at
> http://www.eagle.co.za/download/download/edre_linux_drivers_2_0_8.tar.gz
> 
> If you can maybe have a quick look at the class driver. The code is very
> short, so you should be able to quickly understand what is wrong.

Just like Kay guessed, you are not using the proper function call.
Please use the class_device_create() call instead of rolling your own.
That will fix your problem.

And why aren't these drivers in the main kernel tree?  That would make
this a whole lot easier, and save you a lot of time on maintenance.

As it is, I get a whole lot of warnings and errors when trying to build
this code against the latest kernel version :(

If you want, I can help you out in getting this into the kernel tree.
Overall the code looks pretty sane, only a few small cleanups would be
needed (becides the warning fixes...)

thanks,

greg k-h

-------------------------------------------------------------------------
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

RE: issues getting I/O device to work with udev....

[Jan Zwiegers]

 
> -----Original Message-----
> From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Greg KH
> Sent: 30 August 2006 07:51 PM
> To: Jan Zwiegers
> Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Kay
> Sievers'; md@Linux.IT; 'Ray Schumacher'
> Subject: Re: issues getting I/O device to work with udev....
> 
> On Wed, Aug 30, 2006 at 03:52:39PM +0200, Jan Zwiegers wrote:
> > > -----Original Message-----
> > > From: linux-hotplug-devel-bounces@lists.sourceforge.net [mailto:linux-
> > > hotplug-devel-bounces@lists.sourceforge.net] On Behalf Of Kay Sievers
> > > Sent: 27 August 2006 02:18 AM
> > > To: jan@eagle.co.za
> > > Cc: 'John Thomas'; linux-hotplug-devel@lists.sourceforge.net; 'Ray
> > > Schumacher'; md@Linux.IT
> > > Subject: RE: issues getting I/O device to work with udev....
> > >
> > > On Fri, 2006-08-25 at 21:22 +0200, Jan Zwiegers wrote:
> > > > > > > Oh, that all sounds very much like you don't use the right
> driver
> > > core
> > > > > > > functions and you create the "dev" file yourself in sysfs. You
> > > must use
> > > > > > > the right functions in the kernel and pass the correct dev_t
> to
> > > the
> > > > > > > device registration. That will automatically create the "dev"
> file
> > > and
> > > > > > > add the needed data to the uevent environment, to let udev
> create
> > > the
> > > > > > > node.
> > > > > > >
> > > > > > > But again, to verify this, we need the output of "udevmonitor
> --
> > > env",
> > > > > > > while you plug in a device or re-trigger the event by writing
> > > "add" to
> > > > > > > the "uevent" file in the sysfs device directory.
> > > > > >
> > > > > >
> > > > > > I just create a simple device class by making use of:
> > > > > >
> > > > > > 'class_device_register' &
> > > > > > 'class_device_createfile'
> > > > > > to create /sys/class/edredaq/device0 &
> > > > > > /sys/class/edredaq/device0/edredaq_nodename
> > > > >
> > > > > See how class_device_create() works and fills in dev_t, you need
> to
> > > > > convert to that function or do the same with the dev_t value. You
> also
> > > > > need to set the 'device' pointer like that function does, to make
> > > > > userspace happy.
> > >
> > > > Do you say that I need to look at how I implemented the
> > > > class_device_create_file? Mine seems the same as others. Do you
> think
> > > this
> > > > is the cause of my problem?
> > >
> > > I'm just guessing, but I expect you create the file with the name
> "dev"
> > > which contains the major/minor number yourself in your driver. If
> that's
> > > the case, you shouldn't do that and just set the dev_t value in the
> > > device structure before registering the device, that will instruct the
> > > driver core to create that file, along with environment variables
> needed
> > > for udev to create a node.
> > >
> > > The best way to do this, would probably be to use the
> > > class_device_create() function in /linux/drivers/base/class.c, which
> > > expects all the needed values as parameters.
> > [Jan Zwiegers]
> > Hi Kay & Greg
> >
> > Sorry for taking so long to get back to you.
> >
> > The source code is downloadable at
> > http://www.eagle.co.za/download/download/edre_linux_drivers_2_0_8.tar.gz
> >
> > If you can maybe have a quick look at the class driver. The code is very
> > short, so you should be able to quickly understand what is wrong.
> 
> Just like Kay guessed, you are not using the proper function call.
> Please use the class_device_create() call instead of rolling your own.
> That will fix your problem.
[Jan Zwiegers] 
Yes this was the problem indeed. I have updated the code to make use of
class_device_create() and the problem is resolved.

http://www.eagle.co.za/download/download/edre_linux_drivers_2_0_8_tar.gz


> 
> And why aren't these drivers in the main kernel tree?  That would make
> this a whole lot easier, and save you a lot of time on maintenance.

[Jan Zwiegers] 
I do wish to add this code to the kernel tree. Due to lack of development
time I have only played catch-up the last year or two. We add support and
migrate to later kernel when only required. However the code is very stable
now and minor changes are needed to support the latest kernel. The other
issue is we package the driver code with our API, examples, docs and
applications, but the kernel tree will be a much better solution.

> 
> As it is, I get a whole lot of warnings and errors when trying to build
> this code against the latest kernel version :(

[Jan Zwiegers] 
Yes, I'm aware of this and as soon as I have a bit of spare time I will make
the necessary updates.

> 
> If you want, I can help you out in getting this into the kernel tree.
> Overall the code looks pretty sane, only a few small cleanups would be
> needed (becides the warning fixes...)

[Jan Zwiegers] 
Your help will be really appreciated. I don't really understand the process
of getting it into the kernel tree, but if you can point me in the right
direction I can do all the work and you can guide me. So maybe we can first
start with updating the code to be able to integrate into the kernel tree.

Many thanks to Greg and Kay helping me to resolve this problem!
> 
> thanks,
> 
> greg k-h
> 
> -------------------------------------------------------------------------
> 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



-------------------------------------------------------------------------
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