Matteo Azzali wrote:
> Till now the cinergy T2 remote driver is the only driver I know that
> doesn't exports
> any SYSFS parameter for udev hooking. (at least 99% of the drivers are
> doin this).
>
> Is not needed anything too much complex, even just exporting
> SYSFS{model}="cinergyT2remote" would do, using instead the PROGRAM==""
> rules in udev (with program doin a cat of
> /proc/bus/input/devices) gives lots of issues (I filled a kilometric
> bug-report for udev,
> but from 0.65 to 0.70 this bug is unresolved, may be that
> /proc/bus/input/devices isn't
> ready before udev at boottime or some similar shame...).
>
> Hooking in udev is NEEDED since eventX devices would change (ie:X move
> from 2 to 3) any time
> a usb device is plugged in/out.
>
> So please, if anyone can correct this in /drivers/media/dvb/cinergyT2
> (which already exports
> the card SYSFS parameters, but not the remote ones) or just point me to
> a tutorial/explanation
> on how export SYSFS parameter to try to patch myself, thanks.
Matteo-
Have you made any progress with this? I've looked at the cinergyT2
code, and it doesn't look like the fix is going to be as simple as what
was done with the v4l cards. Here is how we got this done for
saa7134-based boards:
===================================================================
RCS file:
/cvs/video4linux/v4l-kernel/linux/drivers/media/video/saa7134/saa7134-input.c,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- v4l-kernel/linux/drivers/media/video/saa7134/saa7134-input.c
2005/07/15 21:44:14 1.22
+++ v4l-kernel/linux/drivers/media/video/saa7134/saa7134-input.c
2005/09/02 22:00:49 1.23
@@ -569,6 +569,7 @@
ir->dev.id.vendor = dev->pci->vendor;
ir->dev.id.product = dev->pci->device;
}
+ ir->dev.dev = &dev->pci->dev;
#endif
/* all done */
If you get something working, please send in a patch to the list.
Good Luck.
--
Michael Krufky
