On 02/02/2012 02:59 PM, Natanael Copa wrote:
On Thu, Feb 2, 2012 at 2:21 PM, Peter Korsgaard<[email protected]> wrote:
Natanael> Maybe I was wrong.
We're atleast doing devtmpfs together with mdev in Buildroot, but as I
mentioned it isn't a configuration that I use personally.
Super! I will play around with it.
Thanks!
For some time now i have had DEVTMPFS + MDEV, working without real
problems, but (there is always a but), there seems to be some cases that
mdev does not work as expected when using it with DEVTMPFS.
An example: ARM embedded module configured as:
kernel:
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
mdev.conf:
ttymxc([0-9]) 0:0 0660 >ttyS%1
One expects that with that configuration a coldplug 'mdev -s' creates
the real nodes and then symlinks to the standard 'ttySx' for serial
devices. Instead because the nodes are already created by the kernel
what you have is:
crw------- 1 root root 207, 16 Jan 1 00:09 /dev/ttyS0
crw-rw---- 1 root root 207, 17 Jan 1 00:00 /dev/ttyS1
crw-rw---- 1 root root 207, 18 Jan 1 00:00 /dev/ttyS2
crw-rw---- 1 root root 207, 19 Jan 1 00:00 /dev/ttyS3
crw-rw---- 1 root root 207, 20 Jan 1 00:00 /dev/ttyS4
crw------- 1 root root 207, 16 Jan 1 1970 /dev/ttymxc0
crw------- 1 root root 207, 17 Jan 1 1970 /dev/ttymxc1
crw------- 1 root root 207, 18 Jan 1 1970 /dev/ttymxc2
crw------- 1 root root 207, 19 Jan 1 1970 /dev/ttymxc3
crw------- 1 root root 207, 20 Jan 1 1970 /dev/ttymxc4
It creates copies (same major and minor) instead of symlinks.
Off course it still works, but not as expected.
--
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
