Date: Mon, 21 Sep 2015 19:33:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203249] [patch] Patch to allow dynamic USB quirks at boot (USB 2 stack) Message-ID: <bug-203249-17@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203249 Bug ID: 203249 Summary: [patch] Patch to allow dynamic USB quirks at boot (USB 2 stack) Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: btik-fbsd@scoubidou.com Keywords: patch Created attachment 161251 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161251&action=edit usb_quirk The new USB 2 stack allows dynamic additions to the quirk table, but not at boot time. This patch resurrects the idea of bug #122819 in which Maurice Castro implemented dynamic quirks in 2008 for the USB 1 stack, allowing quirks to be defined through the environment. It allows the modification of the quirks table through the environment in the USB 2 stack. So the devices plugged in at boot time can be correctly quirk'ed even if they are not statically defined in usb_quirk.c. One can define several variables in loader.conf, like this one: usb.quirk.0="0x04d9 0xfa50 0 0xffff UQ_KBD_IGNORE" The value format is "VendorId ProductId LowRevision HighRevision Quirk1,...,QuirkN". Quirk1,...,QuirkN are the quirks names as defined in the usb_quirk_str array, seprated by commas without space. One can have usb.quirk.1, .2, ..., .99 if there is enough space in the quirks table... If a matching entry is found in the quirk_usb.c's quirk table, it is replaced by the environment defined one. If not, a new entry is created (while the table is not full.) To keep it simple, it iterates over usb.quirk.N (N = 0; N < 100) variables and stop after the first non-existent one. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203249-17>