Re: Tablets with webcamd (was: wacom and x11 and webcamd)
Hi, The drivers mentioned does not compile as-is, but you are free to send a patch to make them compile. Should not be too hard! --HPS Index: config === --- config (revision 2525) +++ config (working copy) @@ -220,6 +220,9 @@ CONFIG_TABLET_USB_HANWANG=y CONFIG_TABLET_USB_KBTAB=y CONFIG_TABLET_USB_WACOM=y +CONFIG_HID_KYE=y +CONFIG_HID_UCLOGIC=y +CONFIG_HID_WALTOP=y CONFIG_TOUCHSCREEN_USB_3M=y CONFIG_TOUCHSCREEN_USB_COMPOSITE=y CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y @@ -363,3 +366,5 @@ CONFIG_VIDEO_VP27SMPX=y CONFIG_VIDEO_WM8739=y CONFIG_VIDEO_WM8775=y +CONFIG_USB_MA901=y +CONFIG_HID=y Index: Makefile === --- Makefile(revision 2526) +++ Makefile(working copy) @@ -292,5 +292,6 @@ -i media_tree/drivers/media \ -i media_tree/drivers/staging/media \ -i media_tree/sound/i2c/other \ + -i media_tree/drivers/hid \ -i contrib/dvb-usb \ -o build/ media_tree/drivers/hid/hid-core.c:55: error: redefinition of 'mod_param_debug_init_desc' media_tree/drivers/hid/hid-core.c:50: error: previous definition of 'mod_param_debug_init_desc' was here media_tree/drivers/hid/hid-core.c:55: error: redefinition of 'mod_param_debug_init_desc_p' media_tree/drivers/hid/hid-core.c:50: error: previous definition of 'mod_param_debug_init_desc_p' was here media_tree/drivers/hid/hid-core.c: In function 'implement': media_tree/drivers/hid/hid-core.c:961: warning: implicit declaration of function 'put_unaligned_le64' media_tree/drivers/hid/hid-core.c: At top level: media_tree/drivers/hid/hid-core.c:1379: error: unknown field 'attr' specified in initializer media_tree/drivers/hid/hid-core.c:1379: warning: braces around scalar initializer media_tree/drivers/hid/hid-core.c:1379: warning: (near initialization for 'dev_bin_attr_report_desc.name') media_tree/drivers/hid/hid-core.c:1379: error: field name not in record or union initializer media_tree/drivers/hid/hid-core.c:1379: error: (near initialization for 'dev_bin_attr_report_desc.name') media_tree/drivers/hid/hid-core.c:1379: error: field name not in record or union initializer media_tree/drivers/hid/hid-core.c:1379: error: (near initialization for 'dev_bin_attr_report_desc.name') media_tree/drivers/hid/hid-core.c:1379: warning: excess elements in scalar initializer media_tree/drivers/hid/hid-core.c:1379: warning: (near initialization for 'dev_bin_attr_report_desc.name') media_tree/drivers/hid/hid-core.c:1380: error: unknown field 'read' specified in initializer media_tree/drivers/hid/hid-core.c:1380: warning: initialization makes integer from pointer without a cast media_tree/drivers/hid/hid-core.c:1380: error: initializer element is not computable at load time media_tree/drivers/hid/hid-core.c:1380: error: (near initialization for 'dev_bin_attr_report_desc.mode') media_tree/drivers/hid/hid-core.c:1381: error: unknown field 'size' specified in initializer media_tree/drivers/hid/hid-core.c:1381: warning: excess elements in struct initializer media_tree/drivers/hid/hid-core.c:1381: warning: (near initialization for 'dev_bin_attr_report_desc') media_tree/drivers/hid/hid-core.c: In function 'hid_connect': media_tree/drivers/hid/hid-core.c:1459: warning: implicit declaration of function 'device_create_bin_file' media_tree/drivers/hid/hid-core.c: In function 'hid_disconnect': media_tree/drivers/hid/hid-core.c:1474: warning: implicit declaration of function 'device_remove_bin_file' media_tree/drivers/hid/hid-core.c: In function 'store_new_id': media_tree/drivers/hid/hid-core.c:1788: warning: implicit declaration of function 'driver_attach' media_tree/drivers/hid/hid-core.c: At top level: media_tree/drivers/hid/hid-core.c:1792: error: expected ')' before numeric constant media_tree/drivers/hid/hid-core.c:1930: error: variable 'hid_bus_type' has initializer but incomplete type media_tree/drivers/hid/hid-core.c:1931: error: unknown field 'name' specified in initializer media_tree/drivers/hid/hid-core.c:1931: warning: excess elements in struct initializer media_tree/drivers/hid/hid-core.c:1931: warning: (near initialization for 'hid_bus_type') media_tree/drivers/hid/hid-core.c:1932: error: unknown field 'dev_attrs' specified in initializer media_tree/drivers/hid/hid-core.c:1932: warning: excess elements in struct initializer media_tree/drivers/hid/hid-core.c:1932: warning: (near initialization for 'hid_bus_type') media_tree/drivers/hid/hid-core.c:1933: error: unknown field 'match' specified in initializer media_tree/drivers/hid/hid-core.c:1933: warning: excess elements in struct initializer media_tree/drivers/hid/hid-core.c:1933: warning: (near initialization for 'hid_bus_type') media_tree/drivers/hid/hid-core.c:1934: error: unknown field 'probe' specified in initializer media_tree/drivers/hid/hid-core.c:1934: warning:
Re: Tablets with webcamd (was: wacom and x11 and webcamd)
Hans Petter Selasky hsela...@c2i.net wrote: The drivers mentioned does not compile as-is, That is my conclusion as well. but you are free to send a patch to make them compile. Should not be too hard! In that case I will look into it as time permits. No promises though. Thank you for your help. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Tablets with webcamd (was: wacom and x11 and webcamd)
On Sunday 13 January 2013 02:38:40 Vitaly Magerya wrote: Hans Petter Selasky wrote: I've created a Wiki Page for Wacom Tablets: https://wiki.freebsd.org/WacomTablet I have a more general question: does webcamd contain Linux code for non-Wacom tablets (there's quite a few in drivers/hid), i.e. will it create /dev/input/* devices for them too? If so, is my understanding correct that we'll need xf86-input-evdev to make use of that? If not so, is there a plan to add those drivers too, and is it at all possible? Feel free to suggest more information which might be added there. Do add a note that UQ_UMS_IGNORE is only available on 9-STABLE and 10-CURRENT. Hi, The following tables are supported in the latest version of webcamd: CONFIG_TABLET_USB_ACECAD=y CONFIG_TABLET_USB_AIPTEK=y CONFIG_TABLET_USB_GTCO=y CONFIG_TABLET_USB_HANWANG=y CONFIG_TABLET_USB_KBTAB=y CONFIG_TABLET_USB_WACOM=y --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Tablets with webcamd (was: wacom and x11 and webcamd)
Hans Petter Selasky hsela...@c2i.net wrote: The following tables are supported in the latest version of webcamd: CONFIG_TABLET_USB_ACECAD=y CONFIG_TABLET_USB_AIPTEK=y CONFIG_TABLET_USB_GTCO=y CONFIG_TABLET_USB_HANWANG=y CONFIG_TABLET_USB_KBTAB=y CONFIG_TABLET_USB_WACOM=y I see. Any plans for CONFIG_HID_KYE, CONFIG_HID_UCLOGIC and CONFIG_HID_WALTOP? ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Tablets with webcamd (was: wacom and x11 and webcamd)
On Sunday 13 January 2013 15:15:16 Vitaly Magerya wrote: Hans Petter Selasky hsela...@c2i.net wrote: The following tables are supported in the latest version of webcamd: CONFIG_TABLET_USB_ACECAD=y CONFIG_TABLET_USB_AIPTEK=y CONFIG_TABLET_USB_GTCO=y CONFIG_TABLET_USB_HANWANG=y CONFIG_TABLET_USB_KBTAB=y CONFIG_TABLET_USB_WACOM=y I see. Any plans for CONFIG_HID_KYE, CONFIG_HID_UCLOGIC and CONFIG_HID_WALTOP? It is just to edit the config in the root directory of webcamd, add those options and see if it compiles. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Tablets with webcamd (was: wacom and x11 and webcamd)
Hans Petter Selasky hsela...@c2i.net wrote: Any plans for CONFIG_HID_KYE, CONFIG_HID_UCLOGIC and CONFIG_HID_WALTOP? It is just to edit the config in the root directory of webcamd, add those options and see if it compiles. It compiles, but webcamd wouldn't attach to the hardware those drivers are supposed to support. It seems that webcamd doesn't contain the needed sources at the moment. In particular drivers/hid/hid-{kye,uclogic,waltop}.c are definitely needed, as well as a bunch of other files (I don't really know which though). Should I try just copying over those files? Is editing 'config' file enough for the rest of the system to pick them up? (I don't think it's that easy, but no harm in asking, right?) ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Tablets with webcamd (was: wacom and x11 and webcamd)
On Sunday 13 January 2013 16:56:59 Vitaly Magerya wrote: Hans Petter Selasky hsela...@c2i.net wrote: Any plans for CONFIG_HID_KYE, CONFIG_HID_UCLOGIC and CONFIG_HID_WALTOP? It is just to edit the config in the root directory of webcamd, add those options and see if it compiles. It compiles, but webcamd wouldn't attach to the hardware those drivers are supposed to support. It seems that webcamd doesn't contain the needed sources at the moment. In particular drivers/hid/hid-{kye,uclogic,waltop}.c are definitely needed, as well as a bunch of other files (I don't really know which though). Should I try just copying over those files? Is editing 'config' file enough for the rest of the system to pick them up? (I don't think it's that easy, but no harm in asking, right?) You need to copy those files and include the hid directory at the bottom of the main Makefile too. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Tablets with webcamd (was: wacom and x11 and webcamd)
Hans Petter Selasky wrote: I've created a Wiki Page for Wacom Tablets: https://wiki.freebsd.org/WacomTablet I have a more general question: does webcamd contain Linux code for non-Wacom tablets (there's quite a few in drivers/hid), i.e. will it create /dev/input/* devices for them too? If so, is my understanding correct that we'll need xf86-input-evdev to make use of that? If not so, is there a plan to add those drivers too, and is it at all possible? Feel free to suggest more information which might be added there. Do add a note that UQ_UMS_IGNORE is only available on 9-STABLE and 10-CURRENT. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS I don't get anything with that command on my 8.2-STABLE system. Is that something that will work on 9 but not 8? Thanks, Denver ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
On Monday 09 April 2012 19:59:17 Denver Hull wrote: Hans Petter Selasky wrote: On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS I don't get anything with that command on my 8.2-STABLE system. Is that something that will work on 9 but not 8? Did you kldload usb_quirk ? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Monday 09 April 2012 19:59:17 Denver Hull wrote: Hans Petter Selasky wrote: On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd.at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS I don't get anything with that command on my 8.2-STABLE system. Is that something that will work on 9 but not 8? Did you kldload usb_quirk ? --HPS Well, that reports kldload: can't load usb_quirk: File exists, but usb_quirk isn't listed in kldstat. The man page for usb_quirk(4) doesn't show anything for UMS. However, everything listed in the man page is reported by usbconfig dump_quirk_names. Or at least it looks that way. I didn't do a line by line check. I checked my kernel conf file, and there's no device usb_quirk line, and it's not in loader.conf, so I'm not sure where it's coming from. In my experience that kldload error usually just means it's compiled in. But it's not listed in my kernel conf file. So that's kind of a mystery. Thanks, Denver ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Monday 09 April 2012 21:28:02 Denver Hull wrote: Hans Petter Selasky wrote: On Monday 09 April 2012 19:59:17 Denver Hull wrote: Hans Petter Selasky wrote: On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS I don't get anything with that command on my 8.2-STABLE system. Is that something that will work on 9 but not 8? Did you kldload usb_quirk ? --HPS Well, that reports kldload: can't load usb_quirk: File exists, but usb_quirk isn't listed in kldstat. The man page for usb_quirk(4) doesn't show anything for UMS. However, everything listed in the man page is reported by usbconfig dump_quirk_names. Or at least it looks that way. I didn't do a line by line check. I checked my kernel conf file, and there's no device usb_quirk line, and it's not in loader.conf, so I'm not sure where it's coming from. In my experience that kldload error usually just means it's compiled in. But it's not listed in my kernel conf file. So that's kind of a mystery. Did you run the usbconfig command like root ? --HPS Yes. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Monday 09 April 2012 21:41:30 Denver Hull wrote: Hans Petter Selasky wrote: Did you run the usbconfig command like root ? --HPS Yes. Hi, It looks like we currently don't have a quirk for UMS, like the following. Adding one such though would be trivial. UQ_HID_IGNORE UQ_KBD_IGNORE --HPS Ok, so until we do have one, I'll continue to use devd.conf to specify the exact device for moused. Thanks, Denver ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Denver ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS Hi Hans, Thanks for the reply. I did have trouble figuring out how to get webcamd started properly. The start script in /usr/local/etc/rc.d looks like it needs at least two parameters, but it wasn't clear what they should be. When I get a chance I'll look at that again see if I can figure something out. I'll let you know how I do. The Protocol not supported problem was something else, not related to the tablet or webcamd. Thanks again, Denver ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2: Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2: Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Regards, Denver ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: wacom and x11 and webcamd
(because uwacom does not compile and probably it is not necessary, either). Sadly, this is true. I did most of the changes required to make uwacom work with FreeBSD 8/9/10 but never quite finished that work. Real life and my PhD just got in the way too much :(. I noticed that webcamd supports the Linux Wacom driver now as well and have been wanting to try this out myself. I am especially curious whether it supports multiple input devices properly (stylus, eraser, puck, all via the same /dev/input/event0). If so, this should give FreeBSD the same level of Wacom tablet support as Linux has, out of the box, without the need for a dedicated driver. - Bartosz ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org