Date: Sun, 18 Jan 2015 15:12:01 +0100 From: Jan Beich <jbeich@vfemail.net> To: Mason Loring Bliss <mason@blisses.org> Cc: Hans Petter Selasky <hps@selasky.org>, freebsd-hackers@freebsd.org Subject: Re: usbhidctl / Logitech Message-ID: <d26c-w53i-wny@vfemail.net> References: <20150106000213.GT4187@blisses.org> <54AB8F81.8070702@selasky.org> <20150106165926.GU4187@blisses.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mason Loring Bliss <mason@blisses.org> writes: >> Did you checkout "sysutils/uhidd" in ports yet? > > The docs say: > > "Note that before you can use uhidd with certain ugenX.Y device, you need > to make sure there is no kernel HID device driver attached to that > device. You could either remove 'device ukbd', 'device ums' and 'device > uhid' from your kernel config file and recomplie the kernel, or if these > drivers are loaded as kernel modules, kldunload(8) them." Only uhid(4) may conflict with -o (cc_attach) mode. Try $ kldload usb_quirk $ usbconfig add_dev_quirk_vplh 0x046d 0 0 0xffff UQ_HID_IGNORE $ usbconfig add_dev_quirk_vplh 0x046d 0 0 0xffff UQ_MATCH_VENDOR_ONLY $ kldunload uhid Otherwise, add forced_attach=YES to uhidd.conf after applying https://code.google.com/p/uhidd/source/detail?r=215 > > It would be unfortunate to have to build a custom kernel and resort to > something from ports when the in-tree tool is one bugfix away from supporting > my hardware perfectly. > > I guess I need to understand more of the background to figure out what the > most reasonable fix would be. I'll do some more research. ------------------------------------------------- VFEmail.net - http://www.vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d26c-w53i-wny>