| 1 |
J. Patrick Campbell wrote: |
| 2 |
> i'm on udev and have compiled in support for my webcam and video for linux |
| 3 |
> yet my /dev/v4l and /dev/video0 are missing. |
| 4 |
> sorry if someone already answered, my router locked up overnight so i've |
| 5 |
> been bouncing email. |
| 6 |
> how do i create devices with udev? didn't see anything on the gentoo udev |
| 7 |
> guide. |
| 8 |
> |
| 9 |
> Thanks, |
| 10 |
> |
| 11 |
> ~P |
| 12 |
|
| 13 |
Inexpert suggestion; corrections gratefully accepted: |
| 14 |
|
| 15 |
Udev creates devices on the fly. This means that it creates the devices |
| 16 |
when something calls for them to be created. |
| 17 |
|
| 18 |
The easiest way I find to create devices like this (devices which will |
| 19 |
be used later, but are not "called" by anything during boot) is to make |
| 20 |
the drivers for such devices modular rather than compiling them directly |
| 21 |
in, and then adding them to /etc/modules.autoload.d/kernel-2.6; that |
| 22 |
way, when the module loads, the device is created. This is how I get my |
| 23 |
Sidewinder gamepad to work (creating the device /dev/js0), for example-- |
| 24 |
if I compile support directly into the kernel, udev isn't running when |
| 25 |
the driver is loaded, because the device is detected during an earlier |
| 26 |
stage of the boot process, so no device is created. I suppose I could |
| 27 |
create a device in the udev config, but I have no interest in that, |
| 28 |
since it's not a "special device that udev doesn't know about" (which is |
| 29 |
the situation in which you are supposed to specifically configure udev |
| 30 |
to create a device). It's supposed to do it automatically; this way, it |
| 31 |
does. |
| 32 |
|
| 33 |
I would suggest that you modularize your video devices as well. |
| 34 |
|
| 35 |
Hope this helps. |
| 36 |
Holly |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-user@g.o mailing list |
Archives