proc_mknod() replacement
Hi,
I found that proc_mknod() had been removed from kernel 2.6.x. Any replacement ?
Or how can I create file, device node or dir from device driver ?
Thanks
Regards
KC
[email protected]
Quoted 4 lines · KC
I found that
proc_mknod()had been removed from kernel 2.6.x. Any replacement ?Or how can I create file, device node or dir from device driver ?
You don't do that from a device driver in the first place. Have a look at udev, it will do what you want from userspace.
Erik
Signature · 2 lines
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
Hi,
Thanks for reply.
Quoted 8 lines · Erik Mouw
Quoted 4 lines · KC
I found that
proc_mknod()had been removed from kernel 2.6.x. Any replacement ?Or how can I create file, device node or dir from device driver ?
You don't do that from a device driver in the first place. Have a look at udev, it will do what you want from userspace.
For regular file, I do agree with you. But for device node, I don't see anything wrong by create it directly from kernel space.
In fact, I do not understand why proc_mknod() is removed from 2.6.x ... I will be happy if someone can tell me why.
Why I want to use proc_mknod() in driver ? I write a small package, ovi-dev, which can be downloaded from
http://www.sourceforge.net/projects/ovi
The ovi-dev will scan the PCI bus and if it found, eg, 3 PCI devices, it will create 3 device entries (nodes) automatically at module load time. So number of device entries (nodes) will match number of devices of the system ... well, UNIX/Linux doesn't work that way ... there are a lot of device entries ... but no corresponding hardware existed.
The proc_mknod() can fix the problems ... but it was removed from 2.6.x ...
too bad ... at least for me. So I'm looking for an alternative way to create
device entry under /dev from drivers instead of /proc ... but still don't know
how. Anyone know how to do that ? It should be done at module_init()
and the entry should be removed at module_exit().
Thanks
KC
Quoted 7 lines
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
Quoted 8 lines · KC
Why I want to use
proc_mknod()in driver ? I write a small package, ovi-dev, which can be downloaded from
http://www.sourceforge.net/projects/ovi
The ovi-dev will scan the PCI bus and if it found, eg, 3 PCI devices, it will create 3 device entries (nodes) automatically at module load time. So number of device entries (nodes) will match number of devices of the system ... well, UNIX/Linux doesn't work that way ... there are a lot of device entries ... but no corresponding hardware existed.
Congrats. You've re-invented udev.
Quoted 11 lines · On 5/10/05, [email protected] <[email protected]> wrote:
Quoted 8 lines · KC
Why I want to use
proc_mknod()in driver ? I write a small package, ovi-dev, which can be downloaded from
http://www.sourceforge.net/projects/ovi
The ovi-dev will scan the PCI bus and if it found, eg, 3 PCI devices, it will create 3 device entries (nodes) automatically at module load time. So number of device entries (nodes) will match number of devices of the system ... well, UNIX/Linux doesn't work that way ... there are a lot of device entries ... but no corresponding hardware existed.
Quoted 1 line
Congrats. You've re-invented udev.
No, it's not ... dynamic entry is not my purpose, but a good feature which I want to have in my package and I did it using proc_mknod() for 2.4.x ...
Anyway, I'll check udev to see if it's enough for me.
Thanks
KC
Quoted 3 lines
Quoted 11 lines · KC
Hi,
Thanks for reply.
Quoted 6 lines · Erik Mouw
Quoted 4 lines · KC
I found that
proc_mknod()had been removed from kernel 2.6.x. Any replacement ?Or how can I create file, device node or dir from device driver ?
Quoted 7 lines
Quoted 2 lines
You don't do that from a device driver in the first place. Have a look at udev, it will do what you want from userspace.
For regular file, I do agree with you. But for device node, I don't see anything wrong by create it directly from kernel space.
In fact, I do not understand whyproc_mknod()is removed from 2.6.x ... I will be happy if someone can tell me why.
Because naming of devices is a policy that shouldn't be defined in the kernel.
Quoted 9 lines
Why I want to use
proc_mknod()in driver ? I write a small package, ovi-dev, which can be downloaded from
http://www.sourceforge.net/projects/ovi
The ovi-dev will scan the PCI bus and if it found, eg, 3 PCI devices, it will create 3 device entries (nodes) automatically at module load time. So number of device entries (nodes) will match number of devices of the system ... well, UNIX/Linux doesn't work that way ... there are a lot of device entries ... but no corresponding hardware existed.
You must have not have converted to udev, it's sort of like devfs in that device nodes are created dynamicly but it's a userspace daemon that adds/removes device nodes in response to hotplug events generated by the kernel.
Quoted 6 lines
The
proc_mknod()can fix the problems ... but it was removed from 2.6.x ...
too bad ... at least for me. So I'm looking for an alternative way to create
device entry under /dev from drivers instead of /proc ... but still don't know
how. Anyone know how to do that ? It should be done atmodule_init()
and the entry should be removed atmodule_exit().
I believe if you use the driver core class stuff (i.e. class_simple_device_add) it should add device nodes in sysfs and generate hotplug events for udev.
Quoted 5 lines
Thanks
KC
Jim.
Hi
Quoted 8 lines
Quoted 5 lines
For regular file, I do agree with you. But for device node, I don't see anything wrong by create it directly from kernel space.
In fact, I do not understand whyproc_mknod()is removed from 2.6.x ... I will be happy if someone can tell me why.Because naming of devices is a policy that shouldn't be defined in the kernel.
Mmm ... generally speaking, I agree with that ... but IMHO, the better way should be ... kernel or driver writer should provide default policy and allow user space to overwrite the default ... so once the module is loaded, it's ready to use ... without extra deamon's help.
For example, in ovi-dev, I scan the PCI bus and if the device is found, create device entries as /proc/ovi/vendor_name/device_name-x.y where
vendor_name and device_name is defined by driver writer. x is board ID which is determine by PCI scan.
y is sub device ID (similar to minor number) which is defined by
driver writer too.
This approach may not good for general hardware such as tty, hard disk ... but is useful for DAQ system.
By using this trick, I can provide a general deivce interface (APIs) such as ovi_dev_open(vendor_name, device_name, boardID, subID, flags) ovi_dev_write[b,w,l](dev, base, offset, value) ovi_dev_read[b,w,l](dev, base,offset, *value)ovi_dev_close(dev)
And if your ISA/PCI/cPCI/PXI device only use I/O and memory access, you can have your driver done in ~ 5 min (maybe less) without any deamon's help ... Just load the driver and use the API to access the devices.
Quoted 20 lines
Quoted 9 lines
Why I want to use
proc_mknod()in driver ? I write a small package, ovi-dev, which can be downloaded from
http://www.sourceforge.net/projects/ovi
The ovi-dev will scan the PCI bus and if it found, eg, 3 PCI devices, it will create 3 device entries (nodes) automatically at module load time. So number of device entries (nodes) will match number of devices of the system ... well, UNIX/Linux doesn't work that way ... there are a lot of device entries ... but no corresponding hardware existed.You must have not have converted to udev, it's sort of like devfs in that device nodes are created dynamicly but it's a userspace daemon that adds/removes device nodes in response to hotplug events generated by the kernel.
Quoted 6 lines
The
proc_mknod()can fix the problems ... but it was removed from 2.6.x ...
too bad ... at least for me. So I'm looking for an alternative way to create
device entry under /dev from drivers instead of /proc ... but still don't know
how. Anyone know how to do that ? It should be done atmodule_init()
and the entry should be removed atmodule_exit().
Quoted 3 lines
I believe if you use the driver core class stuff (i.e.
class_simple_device_add) it should add device nodes in sysfs and generate hotplug events for udev.
Thanks, I will check that.
Regards
KC
[email protected]
Quoted 3 lines
Jim.