From owner-freebsd-usb@freebsd.org Sun Sep 20 20:06:33 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFFE2A05DBC for ; Sun, 20 Sep 2015 20:06:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9D87D141A for ; Sun, 20 Sep 2015 20:06:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8KK6Xgc061005 for ; Sun, 20 Sep 2015 20:06:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 137377] [usb8] request support for Huawei E180 Date: Sun, 20 Sep 2015 20:06:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 20:06:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=137377 Carlo Strub changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Open -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Sun Sep 20 21:42:10 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44E02A06D51 for ; Sun, 20 Sep 2015 21:42:10 +0000 (UTC) (envelope-from btik-fbsd@scoubidou.com) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [IPv6:2a01:e0c:1:1599::13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 134EB1441 for ; Sun, 20 Sep 2015 21:42:09 +0000 (UTC) (envelope-from btik-fbsd@scoubidou.com) Received: from max.scoubidou.com (unknown [82.237.209.39]) by smtp4-g21.free.fr (Postfix) with ESMTP id 00E824C8034; Sun, 20 Sep 2015 23:42:07 +0200 (CEST) Received: from zetta.scoubidou.com (unknown [192.168.1.18]) by max.scoubidou.com (Postfix) with ESMTP id 165A1F2E1; Sun, 20 Sep 2015 23:42:05 +0200 (CEST) To: freebsd-usb@FreeBSD.org From: =?UTF-8?Q?Maxime_Soul=c3=a9?= Subject: Patch to allow dynamic USB quirks at boot X-Enigmail-Draft-Status: N1110 Message-ID: <55FF282D.2040003@scoubidou.com> Date: Sun, 20 Sep 2015 23:42:05 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 21:42:10 -0000 Hi all, I own a X9800 Tecknet mouse with 3 side buttons. When I plug it in, a ukbd device appears handling each 3 buttons with key modifiers Control, Shift and Alt, with one device uhid. As I wanted to see these buttons as buttons under X and not as key modifiers, I first thought about using USB quirk UQ_KBD_IGNORE and devd to hack it. I succeeded (more or less) but devd starts to late during boot to be able to apply the quirk when the mouse is already plugged in, so I needed to always plug the mouse in once the system has booted... Not very cool... When the USB quirk UQ_KBD_IGNORE is applied, the ukbd device does not appear, but two uhid devices appear, including the one dedicated to the "keyboard" feature of the mouse. During my searches on the net, I found the Bug 122819 in which Maurice Castro implemented dynamic quirks in 2008, allowing quirks to be defined dynamically and also through the environment. Unfortunately, this code was for the old USB 1 stack. Indeed, the new USB 2 stack allows dynamic additions to the quirk table, but not at boot time (or I did not find the way). So, I made a patch, with the help of Maurice one, allowing the modification of the quirks table through the environment: http://scoubidou.com/usb_quirk/usb_quirk.diff Now in my loader.conf, I have: usb.quirk.0="0x04d9 0xfa50 0 0xffff UQ_KBD_IGNORE" The value format is "VendorId ProductId LowRevision HighRevision Quirk1,...,QuirkN". One can have usb.quirk.1, .2, ..., .99 if there is enough space in the quirks table... In a devd conf file: notify 1000 { match "system" "DEVFS"; match "subsystem" "CDEV"; match "type" "CREATE"; match "cdev" "uhid[0-9]+"; action "/usr/bin/usbhidctl -f /dev/$cdev \ Keyboard:Keyboard_LeftShift \ Keyboard:Keyboard_LeftAlt \ Keyboard:Keyboard_LeftControl > /dev/null 2>&1 \ && DISPLAY=:0.0 /usr/bin/usbhidaction -f $cdev \ -c /usr/local/etc/tecknet-mouse-usbhidaction.conf \ -p /var/run/usbhidaction.$cdev.pid"; }; The usbhidctl is to check that we handle the right uhid device, the one with Keyboard_LeftShift, Keyboard_LeftAlt AND Keyboard_LeftControl features. Then, usbhidaction daemon can be launched to handle all the "keyboard" events. And the contents of my /usr/local/etc/tecknet-mouse-usbhidaction.conf file: Keyboard:Keyboard_LeftShift 1 0 /usr/local/bin/xdotool mousedown 8 Keyboard:Keyboard_LeftShift 0 1 /usr/local/bin/xdotool mouseup 8 Keyboard:Keyboard_LeftAlt 1 0 /usr/local/bin/xdotool mousedown 9 Keyboard:Keyboard_LeftAlt 0 1 /usr/local/bin/xdotool mouseup 9 Keyboard:Keyboard_LeftControl 1 0 /usr/local/bin/xdotool mousedown 6 Keyboard:Keyboard_LeftControl 0 1 /usr/local/bin/xdotool mouseup 6 to translate "keyboard" actions to buttons clicks thanks to xdotool (from ports). And all works like a charm :) Finally, I have two questions: First, is there a way to link the uhid device with the USB vendor/product ID in devd? Without doing it using a script and parsing devinfo output of course... Second, when I unplug the mouse, devd did not receive the "DESTROY" event for the uhid device, until the usbhidaction daemon is killed. But I would have liked to be able to kill usbhidaction daemon automatically when the mouse is unplugged using devd... With USB vendor/product details available at uhid level, I could have done it when the corresponding ugen device is DETACHed by caching this information... Best regards, Max. From owner-freebsd-usb@freebsd.org Mon Sep 21 06:49:47 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDBBCA06A70 for ; Mon, 21 Sep 2015 06:49:47 +0000 (UTC) (envelope-from hp@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BE5C1D6A for ; Mon, 21 Sep 2015 06:49:47 +0000 (UTC) (envelope-from hp@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 5A2D41FE023; Mon, 21 Sep 2015 08:49:45 +0200 (CEST) Subject: Re: Patch to allow dynamic USB quirks at boot To: =?UTF-8?Q?Maxime_Soul=c3=a9?= , freebsd-usb@FreeBSD.org References: <55FF282D.2040003@scoubidou.com> From: Hans Petter Selasky Message-ID: <55FFA8EA.3030308@selasky.org> Date: Mon, 21 Sep 2015 08:51:22 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <55FF282D.2040003@scoubidou.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 06:49:48 -0000 On 09/20/15 23:42, Maxime Soulé wrote: > Hi all, > > I own a X9800 Tecknet mouse with 3 side buttons. When I plug it in, a > ukbd device appears handling each 3 buttons with key modifiers Control, > Shift and Alt, with one device uhid. > > As I wanted to see these buttons as buttons under X and not as key > modifiers, I first thought about using USB quirk UQ_KBD_IGNORE and devd > to hack it. I succeeded (more or less) but devd starts to late during > boot to be able to apply the quirk when the mouse is already plugged in, > so I needed to always plug the mouse in once the system has booted... > Not very cool... > > When the USB quirk UQ_KBD_IGNORE is applied, the ukbd device does not > appear, but two uhid devices appear, including the one dedicated to the > "keyboard" feature of the mouse. > > During my searches on the net, I found the Bug 122819 in which Maurice > Castro implemented dynamic quirks in 2008, allowing quirks to be defined > dynamically and also through the environment. Unfortunately, this code > was for the old USB 1 stack. > > Indeed, the new USB 2 stack allows dynamic additions to the quirk table, > but not at boot time (or I did not find the way). > > So, I made a patch, with the help of Maurice one, allowing the > modification of the quirks table through the environment: > http://scoubidou.com/usb_quirk/usb_quirk.diff Hi, Can you make this patch into a PR at FreeBSD's bugzilla and I will process it. Yes, I've been thinking about this feature, and you just implemented it! Thank you :-) > > Now in my loader.conf, I have: > > usb.quirk.0="0x04d9 0xfa50 0 0xffff UQ_KBD_IGNORE" > > The value format is "VendorId ProductId LowRevision HighRevision > Quirk1,...,QuirkN". > One can have usb.quirk.1, .2, ..., .99 if there is enough space in the > quirks table... > > In a devd conf file: > > notify 1000 { > match "system" "DEVFS"; > match "subsystem" "CDEV"; > match "type" "CREATE"; > match "cdev" "uhid[0-9]+"; > > action "/usr/bin/usbhidctl -f /dev/$cdev \ > Keyboard:Keyboard_LeftShift \ > Keyboard:Keyboard_LeftAlt \ > Keyboard:Keyboard_LeftControl > /dev/null 2>&1 \ > && DISPLAY=:0.0 /usr/bin/usbhidaction -f $cdev \ > -c /usr/local/etc/tecknet-mouse-usbhidaction.conf \ > -p /var/run/usbhidaction.$cdev.pid"; > }; > > The usbhidctl is to check that we handle the right uhid device, the one > with Keyboard_LeftShift, Keyboard_LeftAlt AND Keyboard_LeftControl > features. Then, usbhidaction daemon can be launched to handle all the > "keyboard" events. > > And the contents of my /usr/local/etc/tecknet-mouse-usbhidaction.conf file: > > Keyboard:Keyboard_LeftShift 1 0 /usr/local/bin/xdotool mousedown 8 > Keyboard:Keyboard_LeftShift 0 1 /usr/local/bin/xdotool mouseup 8 > Keyboard:Keyboard_LeftAlt 1 0 /usr/local/bin/xdotool mousedown 9 > Keyboard:Keyboard_LeftAlt 0 1 /usr/local/bin/xdotool mouseup 9 > Keyboard:Keyboard_LeftControl 1 0 /usr/local/bin/xdotool mousedown 6 > Keyboard:Keyboard_LeftControl 0 1 /usr/local/bin/xdotool mouseup 6 > > to translate "keyboard" actions to buttons clicks thanks to xdotool > (from ports). > > And all works like a charm :) > > Finally, I have two questions: > > First, is there a way to link the uhid device with the USB > vendor/product ID in devd? Without doing it using a script and parsing > devinfo output of course... > > Second, when I unplug the mouse, devd did not receive the "DESTROY" > event for the uhid device, until the usbhidaction daemon is killed. But > I would have liked to be able to kill usbhidaction daemon automatically > when the mouse is unplugged using devd... With USB vendor/product > details available at uhid level, I could have done it when the > corresponding ugen device is DETACHed by caching this information... There is a chicken-egg situation there. If your application using /dev/uhidX doesn't close its device upon receiving a read/poll error, you might not receive the detach event, depending on which kernel you use, because the kernel waits for /dev/uhidX to be detached/closed before generating the destruction event. You might want to listen to some other events. See how /usr/local/etc/devd/webcamd.conf is doing it from /usr/ports/multimedia/webcamd . --HPS > > Best regards, > > Max. > _______________________________________________ > freebsd-usb@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > From owner-freebsd-usb@freebsd.org Mon Sep 21 19:33:15 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64EF4A05EF6 for ; Mon, 21 Sep 2015 19:33:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 374681CD9 for ; Mon, 21 Sep 2015 19:33:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8LJXFgg061356 for ; Mon, 21 Sep 2015 19:33:15 GMT (envelope-from bugzilla-noreply@freebsd.org) 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) Date: Mon, 21 Sep 2015 19:33:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: btik-fbsd@scoubidou.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status keywords bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 19:33:15 -0000 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. From owner-freebsd-usb@freebsd.org Mon Sep 21 20:51:41 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4498A06534 for ; Mon, 21 Sep 2015 20:51:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0F0D1E9C for ; Mon, 21 Sep 2015 20:51:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8LKpfoq026867 for ; Mon, 21 Sep 2015 20:51:41 GMT (envelope-from bugzilla-noreply@freebsd.org) 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) Date: Mon, 21 Sep 2015 20:51:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: hselasky@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 20:51:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203249 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hselasky@FreeBSD.org Assignee|freebsd-usb@FreeBSD.org |hselasky@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Mon Sep 21 21:04:14 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E92A9A06B05 for ; Mon, 21 Sep 2015 21:04:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D6000141E for ; Mon, 21 Sep 2015 21:04:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8LL4Eqh014100 for ; Mon, 21 Sep 2015 21:04:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203252] usbhidaction does not save the right PID in daemon mode Date: Mon, 21 Sep 2015 21:04:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: btik-fbsd@scoubidou.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 21:04:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203252 Bug ID: 203252 Summary: usbhidaction does not save the right PID in daemon mode Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: btik-fbsd@scoubidou.com Created attachment 161254 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161254&action=edit usbhidaction.c diff When launched in daemon mode, usbhidaction saves its PID before calling daemon(). The proposed patch corrects this, still failing before daemon() is called, when the PID file cannot be opened. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Mon Sep 21 21:16:18 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E16D0A051D9 for ; Mon, 21 Sep 2015 21:16:17 +0000 (UTC) (envelope-from btik-fbsd@scoubidou.com) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [IPv6:2a01:e0c:1:1599::13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD6F91BFF for ; Mon, 21 Sep 2015 21:16:17 +0000 (UTC) (envelope-from btik-fbsd@scoubidou.com) Received: from max.scoubidou.com (unknown [82.237.209.39]) by smtp4-g21.free.fr (Postfix) with ESMTP id A57EE4C8069; Mon, 21 Sep 2015 23:16:06 +0200 (CEST) Received: from zetta.scoubidou.com (unknown [192.168.1.18]) by max.scoubidou.com (Postfix) with ESMTP id D542AF255; Mon, 21 Sep 2015 23:16:05 +0200 (CEST) Subject: Re: Patch to allow dynamic USB quirks at boot To: Hans Petter Selasky , freebsd-usb@FreeBSD.org References: <55FF282D.2040003@scoubidou.com> <55FFA8EA.3030308@selasky.org> From: =?UTF-8?Q?Maxime_Soul=c3=a9?= X-Enigmail-Draft-Status: N1110 Message-ID: <56007395.1010006@scoubidou.com> Date: Mon, 21 Sep 2015 23:16:05 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55FFA8EA.3030308@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 21:16:18 -0000 Le 21.09.2015 08:51, Hans Petter Selasky a écrit : > On 09/20/15 23:42, Maxime Soulé wrote: >> Hi all, >> >> I own a X9800 Tecknet mouse with 3 side buttons. When I plug it in, a >> ukbd device appears handling each 3 buttons with key modifiers Control, >> Shift and Alt, with one device uhid. >> >> As I wanted to see these buttons as buttons under X and not as key >> modifiers, I first thought about using USB quirk UQ_KBD_IGNORE and devd >> to hack it. I succeeded (more or less) but devd starts to late during >> boot to be able to apply the quirk when the mouse is already plugged in, >> so I needed to always plug the mouse in once the system has booted... >> Not very cool... >> >> When the USB quirk UQ_KBD_IGNORE is applied, the ukbd device does not >> appear, but two uhid devices appear, including the one dedicated to the >> "keyboard" feature of the mouse. >> >> During my searches on the net, I found the Bug 122819 in which Maurice >> Castro implemented dynamic quirks in 2008, allowing quirks to be defined >> dynamically and also through the environment. Unfortunately, this code >> was for the old USB 1 stack. >> >> Indeed, the new USB 2 stack allows dynamic additions to the quirk table, >> but not at boot time (or I did not find the way). >> >> So, I made a patch, with the help of Maurice one, allowing the >> modification of the quirks table through the environment: >> http://scoubidou.com/usb_quirk/usb_quirk.diff > > Hi, > > Can you make this patch into a PR at FreeBSD's bugzilla and I will > process it. Yes, I've been thinking about this feature, and you just > implemented it! Thank you :-) Hi, Done, bug 203249. > >> >> Now in my loader.conf, I have: >> >> usb.quirk.0="0x04d9 0xfa50 0 0xffff UQ_KBD_IGNORE" >> >> The value format is "VendorId ProductId LowRevision HighRevision >> Quirk1,...,QuirkN". >> One can have usb.quirk.1, .2, ..., .99 if there is enough space in the >> quirks table... >> >> In a devd conf file: >> >> notify 1000 { >> match "system" "DEVFS"; >> match "subsystem" "CDEV"; >> match "type" "CREATE"; >> match "cdev" "uhid[0-9]+"; >> >> action "/usr/bin/usbhidctl -f /dev/$cdev \ >> Keyboard:Keyboard_LeftShift \ >> Keyboard:Keyboard_LeftAlt \ >> Keyboard:Keyboard_LeftControl > /dev/null 2>&1 \ >> && DISPLAY=:0.0 /usr/bin/usbhidaction -f $cdev \ >> -c /usr/local/etc/tecknet-mouse-usbhidaction.conf \ >> -p /var/run/usbhidaction.$cdev.pid"; >> }; >> >> The usbhidctl is to check that we handle the right uhid device, the one >> with Keyboard_LeftShift, Keyboard_LeftAlt AND Keyboard_LeftControl >> features. Then, usbhidaction daemon can be launched to handle all the >> "keyboard" events. >> >> And the contents of my /usr/local/etc/tecknet-mouse-usbhidaction.conf >> file: >> >> Keyboard:Keyboard_LeftShift 1 0 /usr/local/bin/xdotool mousedown 8 >> Keyboard:Keyboard_LeftShift 0 1 /usr/local/bin/xdotool mouseup 8 >> Keyboard:Keyboard_LeftAlt 1 0 /usr/local/bin/xdotool mousedown 9 >> Keyboard:Keyboard_LeftAlt 0 1 /usr/local/bin/xdotool mouseup 9 >> Keyboard:Keyboard_LeftControl 1 0 /usr/local/bin/xdotool mousedown 6 >> Keyboard:Keyboard_LeftControl 0 1 /usr/local/bin/xdotool mouseup 6 >> >> to translate "keyboard" actions to buttons clicks thanks to xdotool >> (from ports). >> >> And all works like a charm :) >> >> Finally, I have two questions: >> >> First, is there a way to link the uhid device with the USB >> vendor/product ID in devd? Without doing it using a script and parsing >> devinfo output of course... >> >> Second, when I unplug the mouse, devd did not receive the "DESTROY" >> event for the uhid device, until the usbhidaction daemon is killed. But >> I would have liked to be able to kill usbhidaction daemon automatically >> when the mouse is unplugged using devd... With USB vendor/product >> details available at uhid level, I could have done it when the >> corresponding ugen device is DETACHed by caching this information... > > There is a chicken-egg situation there. If your application using > /dev/uhidX doesn't close its device upon receiving a read/poll error, > you might not receive the detach event, depending on which kernel you > use, because the kernel waits for /dev/uhidX to be detached/closed > before generating the destruction event. > > You might want to listen to some other events. See how > /usr/local/etc/devd/webcamd.conf is doing it from > /usr/ports/multimedia/webcamd . > > --HPS I found a solution using "attach" instead of "notice" in my devd conf file. Really devd rocks! :) attach 1000 { device-name "uhid[0-9]+"; match "vendor" "0x04d9"; match "product" "0xfa50"; match "intsubclass" "0x01"; match "intprotocol" "0x01"; action "DISPLAY=:0.0 /usr/bin/usbhidaction -f $device-name \ -c /usr/local/etc/tecknet-mouse-usbhidaction.conf \ -p /var/run/usbhidaction.$ugen.pid"; }; notify 1000 { match "system" "USB"; match "subsystem" "DEVICE"; match "type" "DETACH"; match "vendor" "0x04d9"; match "product" "0xfa50"; action "[ -e /var/run/usbhidaction.$ugen.pid ] \ && kill `cat /var/run/usbhidaction.$ugen.pid`"; }; Using "attach" instead of "notice" allows to access the $ugen device corresponding to the $device-name (here uhidN). It allows too to access "intsubclass" and "intprotocol" to filter finely, avoiding a unnecessary probe using usbhidctl as I did before. So the PID file of usbhidaction can be saved in a file whose name include $ugen. Then the "notify" of the "DETACH" can easily kill it. EXCEPT, EXCEPT, that usbhidaction does not save the right PID when launched in daemon mode! I just submitted bug 203252 to correct this. Best regards, Max. From owner-freebsd-usb@freebsd.org Mon Sep 21 22:58:43 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC3C69D04FF for ; Mon, 21 Sep 2015 22:58:43 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85DBB125A for ; Mon, 21 Sep 2015 22:58:43 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by ioiz6 with SMTP id z6so135063852ioi.2 for ; Mon, 21 Sep 2015 15:58:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=M85f1f5eJ4CwOF6CCESZsKkrujhuUzGDEawEJhkEaiw=; b=srlipeXfIzTWkpz3ok+JajOQIKoO03OSplxD3aoS1YAHC9+9LAMIFeYDJ5WVvLW5qA F0S5cNuFYG/zdD8luFB50YzcTh2DfKjgy3AckhS7JNGoZDo5MNXZW5M7cQSyaQKvAe7n aw0JRh3/SYGOzUoZ8d/sDMne5BLim/KR9WLy6stR5qvZ+YSVGzkxbWzsCKsWH9uG7ze2 YN1/QzaXoX2e9Ss+04gnIoUrf8NDYXmlCTaIM3kaeABfX/5LudEvKIEGx6plLkdt2Ddr pSfowRao9VWUFLhzBBuGseW3rTpP1euXFgbWNpxm8Bwb5DZ24+IKf59m/Ohy/8f8+dsA fSsA== MIME-Version: 1.0 X-Received: by 10.107.131.134 with SMTP id n6mr28626031ioi.192.1442876322907; Mon, 21 Sep 2015 15:58:42 -0700 (PDT) Received: by 10.65.15.33 with HTTP; Mon, 21 Sep 2015 15:58:42 -0700 (PDT) In-Reply-To: <56007395.1010006@scoubidou.com> References: <55FF282D.2040003@scoubidou.com> <55FFA8EA.3030308@selasky.org> <56007395.1010006@scoubidou.com> Date: Mon, 21 Sep 2015 15:58:42 -0700 Message-ID: Subject: Re: Patch to allow dynamic USB quirks at boot From: Mehmet Erol Sanliturk To: =?UTF-8?Q?Maxime_Soul=C3=A9?= Cc: Hans Petter Selasky , freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 22:58:43 -0000 On Mon, Sep 21, 2015 at 2:16 PM, Maxime Soul=C3=A9 wrote: > Le 21.09.2015 08:51, Hans Petter Selasky a =C3=A9crit : > > On 09/20/15 23:42, Maxime Soul=C3=A9 wrote: > >> Hi all, > >> > >> I own a X9800 Tecknet mouse with 3 side buttons. When I plug it in, a > >> ukbd device appears handling each 3 buttons with key modifiers Control= , > >> Shift and Alt, with one device uhid. > >> > >> As I wanted to see these buttons as buttons under X and not as key > >> modifiers, I first thought about using USB quirk UQ_KBD_IGNORE and dev= d > >> to hack it. I succeeded (more or less) but devd starts to late during > >> boot to be able to apply the quirk when the mouse is already plugged i= n, > >> so I needed to always plug the mouse in once the system has booted... > >> Not very cool... > >> > >> When the USB quirk UQ_KBD_IGNORE is applied, the ukbd device does not > >> appear, but two uhid devices appear, including the one dedicated to th= e > >> "keyboard" feature of the mouse. > >> > >> During my searches on the net, I found the Bug 122819 in which Maurice > >> Castro implemented dynamic quirks in 2008, allowing quirks to be defin= ed > >> dynamically and also through the environment. Unfortunately, this code > >> was for the old USB 1 stack. > >> > >> Indeed, the new USB 2 stack allows dynamic additions to the quirk tabl= e, > >> but not at boot time (or I did not find the way). > >> > >> So, I made a patch, with the help of Maurice one, allowing the > >> modification of the quirks table through the environment: > >> http://scoubidou.com/usb_quirk/usb_quirk.diff > > > > Hi, > > > > Can you make this patch into a PR at FreeBSD's bugzilla and I will > > process it. Yes, I've been thinking about this feature, and you just > > implemented it! Thank you :-) > > Hi, > > Done, bug 203249. > > > > >> > >> Now in my loader.conf, I have: > >> > >> usb.quirk.0=3D"0x04d9 0xfa50 0 0xffff UQ_KBD_IGNORE" > >> > >> The value format is "VendorId ProductId LowRevision HighRevision > >> Quirk1,...,QuirkN". > >> One can have usb.quirk.1, .2, ..., .99 if there is enough space in the > >> quirks table... > >> > >> In a devd conf file: > >> > >> notify 1000 { > >> match "system" "DEVFS"; > >> match "subsystem" "CDEV"; > >> match "type" "CREATE"; > >> match "cdev" "uhid[0-9]+"; > >> > >> action "/usr/bin/usbhidctl -f /dev/$cdev \ > >> Keyboard:Keyboard_LeftShift \ > >> Keyboard:Keyboard_LeftAlt \ > >> Keyboard:Keyboard_LeftControl > /dev/null 2>&1 \ > >> && DISPLAY=3D:0.0 /usr/bin/usbhidaction -f $cdev \ > >> -c /usr/local/etc/tecknet-mouse-usbhidaction.conf \ > >> -p /var/run/usbhidaction.$cdev.pid"; > >> }; > >> > >> The usbhidctl is to check that we handle the right uhid device, the on= e > >> with Keyboard_LeftShift, Keyboard_LeftAlt AND Keyboard_LeftControl > >> features. Then, usbhidaction daemon can be launched to handle all the > >> "keyboard" events. > >> > >> And the contents of my /usr/local/etc/tecknet-mouse-usbhidaction.conf > >> file: > >> > >> Keyboard:Keyboard_LeftShift 1 0 /usr/local/bin/xdotool mousedown 8 > >> Keyboard:Keyboard_LeftShift 0 1 /usr/local/bin/xdotool mouseup 8 > >> Keyboard:Keyboard_LeftAlt 1 0 /usr/local/bin/xdotool mousedown 9 > >> Keyboard:Keyboard_LeftAlt 0 1 /usr/local/bin/xdotool mouseup 9 > >> Keyboard:Keyboard_LeftControl 1 0 /usr/local/bin/xdotool mousedown = 6 > >> Keyboard:Keyboard_LeftControl 0 1 /usr/local/bin/xdotool mouseup 6 > >> > >> to translate "keyboard" actions to buttons clicks thanks to xdotool > >> (from ports). > >> > >> And all works like a charm :) > >> > >> Finally, I have two questions: > >> > >> First, is there a way to link the uhid device with the USB > >> vendor/product ID in devd? Without doing it using a script and parsing > >> devinfo output of course... > >> > >> Second, when I unplug the mouse, devd did not receive the "DESTROY" > >> event for the uhid device, until the usbhidaction daemon is killed. Bu= t > >> I would have liked to be able to kill usbhidaction daemon automaticall= y > >> when the mouse is unplugged using devd... With USB vendor/product > >> details available at uhid level, I could have done it when the > >> corresponding ugen device is DETACHed by caching this information... > > > > There is a chicken-egg situation there. If your application using > > /dev/uhidX doesn't close its device upon receiving a read/poll error, > > you might not receive the detach event, depending on which kernel you > > use, because the kernel waits for /dev/uhidX to be detached/closed > > before generating the destruction event. > > > > You might want to listen to some other events. See how > > /usr/local/etc/devd/webcamd.conf is doing it from > > /usr/ports/multimedia/webcamd . > > > > --HPS > > I found a solution using "attach" instead of "notice" in my devd conf > file. Really devd rocks! :) > > attach 1000 { > device-name "uhid[0-9]+"; > match "vendor" "0x04d9"; > match "product" "0xfa50"; > match "intsubclass" "0x01"; > match "intprotocol" "0x01"; > > action "DISPLAY=3D:0.0 /usr/bin/usbhidaction -f $device-name \ > -c /usr/local/etc/tecknet-mouse-usbhidaction.conf \ > -p /var/run/usbhidaction.$ugen.pid"; > }; > > notify 1000 { > match "system" "USB"; > match "subsystem" "DEVICE"; > match "type" "DETACH"; > match "vendor" "0x04d9"; > match "product" "0xfa50"; > > action "[ -e /var/run/usbhidaction.$ugen.pid ] \ > && kill `cat /var/run/usbhidaction.$ugen.pid`"; > }; > > Using "attach" instead of "notice" allows to access the $ugen device > corresponding to the $device-name (here uhidN). It allows too to access > "intsubclass" and "intprotocol" to filter finely, avoiding a unnecessary > probe using usbhidctl as I did before. > > So the PID file of usbhidaction can be saved in a file whose name > include $ugen. > > Then the "notify" of the "DETACH" can easily kill it. > > EXCEPT, EXCEPT, that usbhidaction does not save the right PID when > launched in daemon mode! > > I just submitted bug 203252 to correct this. > > Best regards, > > Max. > > _______________________________________________ > > My C programming knowledge is very weak ( I am not attempting to do it ) . One of my wishes is to move ALL of the device definition information for ( NIC , USB , and other devices ) into files where for each device ( a unique file to dedicated itself containing information presently defined as preset in internal arrays with one additional information ( at least ) which driver will be used for the device ) will be prepared . File names will be constructed from device characteristics . When a device is detected , and its definition recognized , a file name will be constructed from this definition . Then that file will be loaded into internal data structures . The driver recorded in it will be used . When a vendor produces a new device with one of the existing chips with its driver already is present , the vendor only will prepare the description file only . When a user buys such a device , the only task will be to copy its description file into a directory . For original ( new ) chips , additionally a driver should be supplied . If a manual is prepared for device driver categories , preparation of such a driver will also be easy because the producer will use predefined template driver parts to complete missing parts . Such a form will rescue the operating system from always to make modifications into OS sources and reconstruct it . Mehmet Erol Sanliturk From owner-freebsd-usb@freebsd.org Tue Sep 22 06:57:05 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D1C9A05080 for ; Tue, 22 Sep 2015 06:57:05 +0000 (UTC) (envelope-from hp@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5E811764 for ; Tue, 22 Sep 2015 06:57:04 +0000 (UTC) (envelope-from hp@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id D8ACA1FE023; Tue, 22 Sep 2015 08:57:01 +0200 (CEST) Subject: Re: Patch to allow dynamic USB quirks at boot To: Mehmet Erol Sanliturk , =?UTF-8?Q?Maxime_Soul=c3=a9?= References: <55FF282D.2040003@scoubidou.com> <55FFA8EA.3030308@selasky.org> <56007395.1010006@scoubidou.com> Cc: freebsd-usb@freebsd.org, Warner Losh From: Hans Petter Selasky Message-ID: <5600FC1E.2060206@selasky.org> Date: Tue, 22 Sep 2015 08:58:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 06:57:05 -0000 On 09/22/15 00:58, Mehmet Erol Sanliturk wrote: > On Mon, Sep 21, 2015 at 2:16 PM, Maxime Soulé > wrote: > > One of my wishes is to move ALL of the device definition information for ( > NIC , USB , and other devices ) into files where for each device ( a unique > file to dedicated itself containing information presently defined as preset > in internal arrays with one additional information ( at least ) which > driver will be used for the device ) will be prepared . > Hi Mehmet, Warner Losh is working on this currently, CC'ed. See: https://reviews.freebsd.org/D3458 Maybe you want to help out testing? --HPS From owner-freebsd-usb@freebsd.org Tue Sep 22 07:12:02 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BEDF0A05966 for ; Tue, 22 Sep 2015 07:12:02 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 839571F0E for ; Tue, 22 Sep 2015 07:12:02 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by igbni9 with SMTP id ni9so4728641igb.0 for ; Tue, 22 Sep 2015 00:12:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CcYizChyZbMsklxE2dtJNqNrzyOlAOc0t9yZY1n8Bu8=; b=lonJNjTZ19qWmB1SyqKQHJvqDXQ89SNLb4bLyndCl0sGbUmaIgYdqTtjwZBm2RXVks lP10k3TAo/ICXliGhyw/yxdsR/SVnuM49YLpP/EDMJhF689BWbab/jgiJnrsrcfJdbQL 2H8pX58PBjtg+t999FKhgdgGz+Lhv6/qpSZ0qD/diQR5VeYeiRRClF7fJ5XnI/U7ORu5 GuD7P8Q4mFRPeFZjshExsZJKPA+0rdeWOik465b3pRq2nLLCWJ+LYkcZtm77sm5A30wh n/UH/QAwu74aQUVE6sNVL/M9S1TV1jsHHwnGfmcOv4nljv+vtN/WH1SQB4Ze5eLiShvO gw/A== MIME-Version: 1.0 X-Received: by 10.50.61.166 with SMTP id q6mr9095965igr.12.1442905921850; Tue, 22 Sep 2015 00:12:01 -0700 (PDT) Received: by 10.65.15.33 with HTTP; Tue, 22 Sep 2015 00:12:01 -0700 (PDT) In-Reply-To: <5600FC1E.2060206@selasky.org> References: <55FF282D.2040003@scoubidou.com> <55FFA8EA.3030308@selasky.org> <56007395.1010006@scoubidou.com> <5600FC1E.2060206@selasky.org> Date: Tue, 22 Sep 2015 00:12:01 -0700 Message-ID: Subject: Re: Patch to allow dynamic USB quirks at boot From: Mehmet Erol Sanliturk To: Hans Petter Selasky Cc: =?UTF-8?Q?Maxime_Soul=C3=A9?= , freebsd-usb@freebsd.org, Warner Losh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 07:12:02 -0000 On Mon, Sep 21, 2015 at 11:58 PM, Hans Petter Selasky wrote: > On 09/22/15 00:58, Mehmet Erol Sanliturk wrote: > >> On Mon, Sep 21, 2015 at 2:16 PM, Maxime Soul=C3=A9 >> wrote: >> >> One of my wishes is to move ALL of the device definition information for= ( >> NIC , USB , and other devices ) into files where for each device ( a >> unique >> file to dedicated itself containing information presently defined as >> preset >> in internal arrays with one additional information ( at least ) which >> driver will be used for the device ) will be prepared . >> >> > Hi Mehmet, > > Warner Losh is working on this currently, CC'ed. See: > > https://reviews.freebsd.org/D3458 > > Maybe you want to help out testing? > > --HPS > If I can help in any way , I will do it . Mehmet Erol Sanliturk From owner-freebsd-usb@freebsd.org Tue Sep 22 21:39:03 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB71AA069C2 for ; Tue, 22 Sep 2015 21:39:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E89C1C6E for ; Tue, 22 Sep 2015 21:39:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: by pacbt3 with SMTP id bt3so1856885pac.3 for ; Tue, 22 Sep 2015 14:39:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=linRRg/9gPkLzW9kKfAn6/Ot7SGFk0ficSlubdjC418=; b=cDYpGpSTmErpm+UjxX/5t02HmVvRecyuB8KExftNf1JbmOaKChJTOi6W/feG6dbUn2 JFY92iTE8WvyvTPjwSd2+y9ujugcJ2fP45i9gThyoYQcYu4Div1auhuDBR/Ey2fuZL/A nhw/iebKj72FUDPVqrHC5Cbg8WVaDlSDDH/NgXAGWeL5/UEFt6m0YmBzLguW5kwMIEEn xHAdaVj2HKK944CSPo8PzJX0k6297cdKaDfXJ1oYTyqjdnTGhJoM0zKt7yxazRFmVouu eMHZ6crrMv1MZdErFW+ustaT4vlYXfY5szeWAVBuWppAdbS753hVaf22rT8UvTtsuW8z Ux9w== X-Gm-Message-State: ALoCoQmnz/MiiFNA3jqnIB9rPN5kIWa6n001XuAychZEhb/JtunNwezE+QWCoE/M1fglCpYVrIbX X-Received: by 10.66.165.5 with SMTP id yu5mr33188549pab.109.1442957942521; Tue, 22 Sep 2015 14:39:02 -0700 (PDT) Received: from [172.22.25.118] ([40.140.178.190]) by smtp.gmail.com with ESMTPSA id e6sm4033585pas.35.2015.09.22.14.39.01 (version=TLS1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Sep 2015 14:39:01 -0700 (PDT) Sender: Warner Losh Subject: Re: Patch to allow dynamic USB quirks at boot Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Content-Type: multipart/signed; boundary="Apple-Mail=_92F6DE54-5982-49F9-855D-DB3AB236B1A8"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5.1 From: Warner Losh In-Reply-To: Date: Tue, 22 Sep 2015 15:38:58 -0600 Cc: Hans Petter Selasky , =?utf-8?Q?Maxime_Soul=C3=A9?= , freebsd-usb@freebsd.org Message-Id: <7E6FCC35-5CA5-4B07-A1F1-41B73EA5B0FC@bsdimp.com> References: <55FF282D.2040003@scoubidou.com> <55FFA8EA.3030308@selasky.org> <56007395.1010006@scoubidou.com> <5600FC1E.2060206@selasky.org> To: Mehmet Erol Sanliturk X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 21:39:03 -0000 --Apple-Mail=_92F6DE54-5982-49F9-855D-DB3AB236B1A8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I need help with PCI driver marking. Grab my patches and we can talk. Basically, it marks all the .ko modules in a similar way that we do = inter-module dependencies with plug and play info. kldxref then takes this data and = stuffs it in loader.hints. I also need to write something that will parse this = data and either generate a devd.conf file (easy to do from kldxref sources) or = queues the load drive in the kernel (kinda hard). Bonus points for similar code = in /boot/loader for any storage device that=E2=80=99s found. Warner > On Sep 22, 2015, at 1:12 AM, Mehmet Erol Sanliturk = wrote: >=20 >=20 >=20 > On Mon, Sep 21, 2015 at 11:58 PM, Hans Petter Selasky = wrote: > On 09/22/15 00:58, Mehmet Erol Sanliturk wrote: > On Mon, Sep 21, 2015 at 2:16 PM, Maxime = Soul=C3=A9 > wrote: >=20 > One of my wishes is to move ALL of the device definition information = for ( > NIC , USB , and other devices ) into files where for each device ( a = unique > file to dedicated itself containing information presently defined as = preset > in internal arrays with one additional information ( at least ) which > driver will be used for the device ) will be prepared . >=20 >=20 > Hi Mehmet, >=20 > Warner Losh is working on this currently, CC'ed. See: >=20 > https://reviews.freebsd.org/D3458 >=20 > Maybe you want to help out testing? >=20 > --HPS >=20 >=20 >=20 > If I can help in any way , I will do it . >=20 >=20 > Mehmet Erol Sanliturk >=20 >=20 --Apple-Mail=_92F6DE54-5982-49F9-855D-DB3AB236B1A8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWAcpzAAoJEGwc0Sh9sBEAqOkP+waRK2bDYEwseiC1Z8fcnJOr u2pM0xkfvAfC46pM+0O4N64An6S/gTgX5PiXbcRSK53GtyCG+HjE1aR4Wk0n4FK6 J1TY17RLl4Cm+JJTdbkugTxfN91Y+jgSnBjEU54q+/Ew2q0xv2JNI9MiwlfmIa18 ThwOTISnb41NItN4MNC2LGMESSs/XmB6f3vVJEc3QvBr7NabZAmnvBOlqthELbk+ eFBTkM7sRNitlHClSQ4ufO6IYHVmmQUWWuRfwE2yhxBBZP0MK3lNB9wCUN91G7QD QFFsi187uuUHC8XP0uclOEdXSMrUJxhIJ8vwZ2ccSDfaWePHWXbEM50JSOZeXoRr X5v+nwgoK0F6aagjuANLzKM+iD6nfu7aYfInL7xahINSzqnBdRUH39ES6lQbyXRM UvlVu4o9vkBpWYp8LD2dX9LB/TzY3aQToQGVj64gpeQmLcAHWeEyVcBkEDkArngf IZeAkVJErzLbNrMCIkRAagkhSG5IPoJ8++jxQAaAcOjdcOGPgRDevqg0jAXtuuA1 NwBxc70s6bT1PLfRHpqo5ymKk3rvY2oA8iVueKKxUrdghEq1GD4dC4yheJ+xLq5I D3Hl3/4RDH8QyWaAz0eKSD9FjUNiojDTkQ/+O1I3nSXxpb3VaaeugfZneR0G1cdc DS/uQDLoJJ/QFl+VkC2J =EsLY -----END PGP SIGNATURE----- --Apple-Mail=_92F6DE54-5982-49F9-855D-DB3AB236B1A8-- From owner-freebsd-usb@freebsd.org Wed Sep 23 00:38:12 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71D8AA062F6 for ; Wed, 23 Sep 2015 00:38:12 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3844E1AD7 for ; Wed, 23 Sep 2015 00:38:12 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by igxx6 with SMTP id x6so19794503igx.1 for ; Tue, 22 Sep 2015 17:38:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dGhNPMsMfV5juf3BVSe20lbKit2r+yh58faly9tYq9E=; b=ewqaMHaspBgTV5i9k2pPsSy10OawOi4s8DgpX6lfVYEdZNEr1SSBGIOa9YAYg/lz4A udo8ORms0Yi7vYQRMzmv5KsIvuByYEU9lXcdRubGzs5YgjDvSPtLfJ/ds9S/pISZyhol mXzlbPyt1yKWnyQWicsc6RadLsrEKl+wSuRY+l0ZdaqhtZoR1db0n3++kw7lX2yFcuI/ +j7yIrRCTDaVwmNyOzFOSmSd0JmxaQqM9iAhmVnhKhwSLjUmtQbJMvGeiaBej3tVk3kr 8yRDUTrBeVFGUtUh4RA1A58LUhpjHU5iY7i3j0Abd+m44BhbV0Ew+SbVFdB/58BTJAJA Wr1A== MIME-Version: 1.0 X-Received: by 10.50.61.166 with SMTP id q6mr14118443igr.12.1442968691687; Tue, 22 Sep 2015 17:38:11 -0700 (PDT) Received: by 10.64.96.74 with HTTP; Tue, 22 Sep 2015 17:38:11 -0700 (PDT) In-Reply-To: <7E6FCC35-5CA5-4B07-A1F1-41B73EA5B0FC@bsdimp.com> References: <55FF282D.2040003@scoubidou.com> <55FFA8EA.3030308@selasky.org> <56007395.1010006@scoubidou.com> <5600FC1E.2060206@selasky.org> <7E6FCC35-5CA5-4B07-A1F1-41B73EA5B0FC@bsdimp.com> Date: Tue, 22 Sep 2015 17:38:11 -0700 Message-ID: Subject: Re: Patch to allow dynamic USB quirks at boot From: Mehmet Erol Sanliturk To: Warner Losh Cc: Hans Petter Selasky , =?UTF-8?Q?Maxime_Soul=C3=A9?= , freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 00:38:12 -0000 On Tue, Sep 22, 2015 at 2:38 PM, Warner Losh wrote: > I need help with PCI driver marking. Grab my patches and we can talk. > > Basically, it marks all the .ko modules in a similar way that we do > inter-module > dependencies with plug and play info. kldxref then takes this data and > stuffs > it in loader.hints. I also need to write something that will parse this > data and > either generate a devd.conf file (easy to do from kldxref sources) or > queues > the load drive in the kernel (kinda hard). Bonus points for similar code = in > /boot/loader for any storage device that=E2=80=99s found. > > Warner > > > > On Sep 22, 2015, at 1:12 AM, Mehmet Erol Sanliturk < > m.e.sanliturk@gmail.com> wrote: > > > > > > > > On Mon, Sep 21, 2015 at 11:58 PM, Hans Petter Selasky > wrote: > > On 09/22/15 00:58, Mehmet Erol Sanliturk wrote: > > On Mon, Sep 21, 2015 at 2:16 PM, Maxime Soul=C3=A9 > > wrote: > > > > One of my wishes is to move ALL of the device definition information fo= r > ( > > NIC , USB , and other devices ) into files where for each device ( a > unique > > file to dedicated itself containing information presently defined as > preset > > in internal arrays with one additional information ( at least ) which > > driver will be used for the device ) will be prepared . > > > > > > Hi Mehmet, > > > > Warner Losh is working on this currently, CC'ed. See: > > > > https://reviews.freebsd.org/D3458 > > > > Maybe you want to help out testing? > > > > --HPS > > > > > > > > If I can help in any way , I will do it . > > > > > > Mehmet Erol Sanliturk > > > > > > What does "PCI driver marking" mean ? Mehmet Erol Sanliturk From owner-freebsd-usb@freebsd.org Wed Sep 23 16:26:45 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60A92A07EE3 for ; Wed, 23 Sep 2015 16:26:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qg0-f45.google.com (mail-qg0-f45.google.com [209.85.192.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F1AA18FE for ; Wed, 23 Sep 2015 16:26:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by qgt47 with SMTP id 47so23490319qgt.2 for ; Wed, 23 Sep 2015 09:26:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8ppalc+a7S5za7pbMxHwUht5B2sYbLXg/JLx8TZ+9sY=; b=ejaoPY5h2RPiBrZhR8SVcTh+HtLQWf0HbPGstk1C2xYpj9d/Kb3pIusipLpSkV2sFs OEigFCBzbergNwy594lfSvpitCsODXw4smOQKFI6KN3gt0nnztH6It6il/qBpp7ghzJ5 knS797IURCZU/20Bckw32+B6T3PkbC5J26+dYvWT6UOsYdoVDForeGOy9TeJ+5/mr5ad WSQox0z1PzU0e56c1NbyDfEXxZqvNG/7nBCDN10X+EajxJi9hAuKskmupns2PdnOpfRT sNuzCmqjzkHJT9LVWZGkzcFeI9120JufdK1NTWOPnpEdhc+Z/G601Gj263dvmo/Uw3Fl iJnw== X-Gm-Message-State: ALoCoQnKyzqF0oFbJ9TtlYuJwO7kbUgE3Q5UyywYhFGkPRJ8+lIwyh+XbyR21WtH6OMvS+ZG25bS MIME-Version: 1.0 X-Received: by 10.140.234.78 with SMTP id f75mr40748497qhc.20.1443025598248; Wed, 23 Sep 2015 09:26:38 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.140.80.167 with HTTP; Wed, 23 Sep 2015 09:26:38 -0700 (PDT) X-Originating-IP: [40.140.178.190] In-Reply-To: References: <55FF282D.2040003@scoubidou.com> <55FFA8EA.3030308@selasky.org> <56007395.1010006@scoubidou.com> <5600FC1E.2060206@selasky.org> <7E6FCC35-5CA5-4B07-A1F1-41B73EA5B0FC@bsdimp.com> Date: Wed, 23 Sep 2015 09:26:38 -0700 X-Google-Sender-Auth: ycdgsmo1HCsqntn70ghAS6-mkHM Message-ID: Subject: Re: Patch to allow dynamic USB quirks at boot From: Warner Losh To: Mehmet Erol Sanliturk Cc: Hans Petter Selasky , =?UTF-8?Q?Maxime_Soul=C3=A9?= , freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 16:26:45 -0000 Nearly all the PCI drivers have tables of vendor/device IDs. They all have slightly different forms, and none of them use a common macro / format like USB. So each driver needs a line or two to describe the table so we can extract the data from the .ko. Some drivers don't have lists, and those will need to be dealt with on a case-by-case basis. I also have another set of work to do PNP translations at run time. The bus will lie about the PNP IDs of the device so that drivers can treat new hardware just like old hardware. The obvious (and wrong) approach of forcing drivers to "take" devices only works for the most trivial drivers as nearly all of them have a table that tells about the "quirks" of the hardware since not all of that can be determined from registers alone. Warner On Tue, Sep 22, 2015 at 5:38 PM, Mehmet Erol Sanliturk < m.e.sanliturk@gmail.com> wrote: > > > On Tue, Sep 22, 2015 at 2:38 PM, Warner Losh wrote: > >> I need help with PCI driver marking. Grab my patches and we can talk. >> >> Basically, it marks all the .ko modules in a similar way that we do >> inter-module >> dependencies with plug and play info. kldxref then takes this data and >> stuffs >> it in loader.hints. I also need to write something that will parse this >> data and >> either generate a devd.conf file (easy to do from kldxref sources) or >> queues >> the load drive in the kernel (kinda hard). Bonus points for similar code >> in >> /boot/loader for any storage device that=E2=80=99s found. >> >> Warner >> >> >> > On Sep 22, 2015, at 1:12 AM, Mehmet Erol Sanliturk < >> m.e.sanliturk@gmail.com> wrote: >> > >> > >> > >> > On Mon, Sep 21, 2015 at 11:58 PM, Hans Petter Selasky >> wrote: >> > On 09/22/15 00:58, Mehmet Erol Sanliturk wrote: >> > On Mon, Sep 21, 2015 at 2:16 PM, Maxime Soul=C3=A9 >> > wrote: >> > >> > One of my wishes is to move ALL of the device definition information >> for ( >> > NIC , USB , and other devices ) into files where for each device ( a >> unique >> > file to dedicated itself containing information presently defined as >> preset >> > in internal arrays with one additional information ( at least ) which >> > driver will be used for the device ) will be prepared . >> > >> > >> > Hi Mehmet, >> > >> > Warner Losh is working on this currently, CC'ed. See: >> > >> > https://reviews.freebsd.org/D3458 >> > >> > Maybe you want to help out testing? >> > >> > --HPS >> > >> > >> > >> > If I can help in any way , I will do it . >> > >> > >> > Mehmet Erol Sanliturk >> > >> > >> >> > > > What does "PCI driver marking" mean ? > > > Mehmet Erol Sanliturk > > > > From owner-freebsd-usb@freebsd.org Wed Sep 23 18:15:56 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2878CA079CD for ; Wed, 23 Sep 2015 18:15:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F03E41BD9 for ; Wed, 23 Sep 2015 18:15:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8NIFtKt048893 for ; Wed, 23 Sep 2015 18:15:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203289] BeagleBone Black invalid USB target descriptors Date: Wed, 23 Sep 2015 18:15:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 18:15:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289 Bug ID: 203289 Summary: BeagleBone Black invalid USB target descriptors Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: emaste@freebsd.org BeagleBone Black image has a number of issues with the USB target, found while using http://www.usblyzer.com/ to get the BBB serial console working with Windows. # usbconfig -d ugen1.5 dump_device_desc ugen1.5: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (50mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0002 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0001 idProduct = 0x0001 bcdDevice = 0x0100 iManufacturer = 0x0007 iProduct = 0x0008 iSerialNumber = 0x0009 bNumConfigurations = 0x0001 The image presents a composite device and it seems that this typically requires either bDeviceClass to be zero, or bDeviceClass, bDeviceSubClass and bDeviceProtocol are 0xEF, 0x02, and 0x01 respectively. usblyzer also reports (for the Device Qualifier Descriptor): bMaxPacketSize0 00h Should be 64 bytes for high-speed devices bNumConfigurations 00h Should be greater than zero Note that Device Descriptor bMaxPacketSize is 64 and bNumConfigurations is 1 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Wed Sep 23 18:17:16 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44F70A07A49 for ; Wed, 23 Sep 2015 18:17:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 322A61C20 for ; Wed, 23 Sep 2015 18:17:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8NIHGI1050129 for ; Wed, 23 Sep 2015 18:17:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203289] BeagleBone Black invalid USB target descriptors Date: Wed, 23 Sep 2015 18:17:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 18:17:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289 --- Comment #1 from Ed Maste --- For reference here is the Device Descriptor for the stock Linux BBB image: ugen1.5: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ef bDeviceSubClass = 0x0002 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x1d6b idProduct = 0x0104 bcdDevice = 0x0308 iManufacturer = 0x0002 iProduct = 0x0003 iSerialNumber = 0x0004 <5A-1513BBBK3026> bNumConfigurations = 0x0001 and dump_all_config_desc: ugen1.5: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x00a4 bNumInterfaces = 0x0005 bConfigurationValue = 0x0001 iConfiguration = 0x0005 bmAttributes = 0x00c0 bMaxPower = 0x0001 Additional Descriptor bLength = 0x08 bDescriptorType = 0x0b bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x08, 0x0b, 0x00, 0x02, 0x02, 0x06, 0x00, 0x09 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0002 bInterfaceSubClass = 0x0002 bInterfaceProtocol = 0x00ff iInterface = 0x0007 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x05, 0x24, 0x00, 0x10, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x01 RAW dump: 0x00 | 0x05, 0x24, 0x01, 0x00, 0x01 Additional Descriptor bLength = 0x04 bDescriptorType = 0x24 bDescriptorSubType = 0x02 RAW dump: 0x00 | 0x04, 0x24, 0x02, 0x00 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x06 RAW dump: 0x00 | 0x05, 0x24, 0x06, 0x00, 0x01 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x0009 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x000a bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0008 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x08 bDescriptorType = 0x0b bDescriptorSubType = 0x02 RAW dump: 0x00 | 0x08, 0x0b, 0x02, 0x02, 0x02, 0x02, 0x01, 0x0c Interface 2 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0002 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0002 bInterfaceSubClass = 0x0002 bInterfaceProtocol = 0x0001 iInterface = 0x000a Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x05, 0x24, 0x00, 0x10, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x01 RAW dump: 0x00 | 0x05, 0x24, 0x01, 0x00, 0x03 Additional Descriptor bLength = 0x04 bDescriptorType = 0x24 bDescriptorSubType = 0x02 RAW dump: 0x00 | 0x04, 0x24, 0x02, 0x02 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x06 RAW dump: 0x00 | 0x05, 0x24, 0x06, 0x02, 0x03 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0084 bmAttributes = 0x0003 wMaxPacketSize = 0x000a bInterval = 0x0009 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 3 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0003 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x000a bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x000b Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 4 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0004 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0050 iInterface = 0x0001 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0085 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Wed Sep 23 18:52:27 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB0DEA06EB0 for ; Wed, 23 Sep 2015 18:52:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 98B091951 for ; Wed, 23 Sep 2015 18:52:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8NIqR27010192 for ; Wed, 23 Sep 2015 18:52:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203289] BeagleBone Black invalid USB target descriptors Date: Wed, 23 Sep 2015 18:52:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 18:52:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hselasky@FreeBSD.org --- Comment #2 from Hans Petter Selasky --- Hi, You can change the descriptors values in sys/dev/usb/template/usb_template_serialnet.c . Are you able to make a patch? Regarding the device qualifier descriptor, I'll have a look. It is currently not used for enumeration, only when trying to switch the device to another USB speed. --HPS -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Wed Sep 23 18:58:59 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FC95A071C9 for ; Wed, 23 Sep 2015 18:58:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1B8881C6D for ; Wed, 23 Sep 2015 18:58:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8NIww63016213 for ; Wed, 23 Sep 2015 18:58:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203289] BeagleBone Black invalid USB target descriptors Date: Wed, 23 Sep 2015 18:58:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 18:58:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289 --- Comment #3 from Hans Petter Selasky --- More specifically this structure: const struct usb_temp_device_desc usb_template_serialnet = { .getStringDesc = &serialnet_get_string_desc, .ppConfigDesc = serialnet_configs, .idVendor = USB_TEMPLATE_VENDOR, .idProduct = 0x0001, .bcdDevice = 0x0100, .bDeviceClass = UDCLASS_COMM, .bDeviceSubClass = 0, .bDeviceProtocol = 0, .iManufacturer = STRING_VENDOR_INDEX, .iProduct = STRING_PRODUCT_INDEX, .iSerialNumber = STRING_SERIAL_INDEX, }; --HPS -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Wed Sep 23 20:04:03 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0C66A08FB4 for ; Wed, 23 Sep 2015 20:04:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE7FB1B2C for ; Wed, 23 Sep 2015 20:04:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8NK43ll088408 for ; Wed, 23 Sep 2015 20:04:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203289] BeagleBone Black invalid USB target descriptors Date: Wed, 23 Sep 2015 20:04:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 20:04:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289 --- Comment #4 from Ed Maste --- Hi HPS, thanks for the reply. I put this in to keep track of this issue while investigating it; I'll have a look at updating the descriptor values in the template when I get set up for BBB builds in a bit. I was able to get a functional USB serial port in Windows with the BBB image despite the device qualifier descriptor issue, it's just that the USB tool complained. As an aside, we'll need to do something different to support the network interface with Windows hosts. This page makes it sound like Windows has support for the CDC Ethernet Networking Control Model: https://msdn.microsoft.com/en-us/library/windows/hardware/ff537037%28v=vs.85%29.aspx but I wasn't able to actually find any evidence of that (looking for Class_02 and SubClass_06). It looks like the options are: * 3rd party CDC Ethernet class drivers for Windows http://www.thesycon.de/eng/usb_network.shtml These are proprietary and Windows 10 is "coming soon" * Implement CDC MBIM target in FreeBSD Likely fairly straightforward. MBIM does not Ethernet encapsulate frames, I think it's just IP. * Implement RNDIS target in FreeBSD The host side (if_urndis.c) is pretty small - we could probably implement it without much trouble. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Wed Sep 23 20:52:34 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39C1FA07F42 for ; Wed, 23 Sep 2015 20:52:34 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 008071F8E for ; Wed, 23 Sep 2015 20:52:34 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by igcpb10 with SMTP id pb10so1007037igc.1 for ; Wed, 23 Sep 2015 13:52:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i7R6eiyhdU9C5RIoqnzzYCzd5MwbcNkQ4NFN8vyq+So=; b=WIwtNTUYjHOnl1VLJvftcvTTmAQgFK0lgGi9QV/KvhDlIlbLGUvNag6XCZHYOkr1an 1v1DDaxkNFxm3Veo4a3J9cML2Fsoay6XwNNCbgcTTjesKPGFTsOljrTWCLtCALhUCepw FVqn56ylAHVhdjntvYzyNZKA+TiNme3efR4tIgoa1q9EGczHqWDp84sIzOmQj4QimloG /7sUfjp895EZe9Ug45MqxbYeGsQS9vbUvZtoekJ6EJ5O61V+IcK9z/7op+HVLod8+AE5 uAsLneyVEyzy1fIF/LFvFQ+ZyYGfQpiHgvsAuFz/CWETckWdRTi5bP6ym7HcjdfFBTyf B9HA== MIME-Version: 1.0 X-Received: by 10.50.79.129 with SMTP id j1mr24352990igx.63.1443041553204; Wed, 23 Sep 2015 13:52:33 -0700 (PDT) Received: by 10.64.96.74 with HTTP; Wed, 23 Sep 2015 13:52:33 -0700 (PDT) In-Reply-To: References: <55FF282D.2040003@scoubidou.com> <55FFA8EA.3030308@selasky.org> <56007395.1010006@scoubidou.com> <5600FC1E.2060206@selasky.org> <7E6FCC35-5CA5-4B07-A1F1-41B73EA5B0FC@bsdimp.com> Date: Wed, 23 Sep 2015 13:52:33 -0700 Message-ID: Subject: Re: Patch to allow dynamic USB quirks at boot From: Mehmet Erol Sanliturk To: Warner Losh Cc: Hans Petter Selasky , =?UTF-8?Q?Maxime_Soul=C3=A9?= , freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 20:52:34 -0000 On Wed, Sep 23, 2015 at 9:26 AM, Warner Losh wrote: > Nearly all the PCI drivers have tables of vendor/device IDs. > They all have slightly different forms, and none of them use > a common macro / format like USB. So each driver needs a > line or two to describe the table so we can extract the data > from the .ko. Some drivers don't have lists, and those will > need to be dealt with on a case-by-case basis. > > I also have another set of work to do PNP translations at run > time. The bus will lie about the PNP IDs of the device so that > drivers can treat new hardware just like old hardware. The obvious > (and wrong) approach of forcing drivers to "take" devices only > works for the most trivial drivers as nearly all of them have a > table that tells about the "quirks" of the hardware since not > all of that can be determined from registers alone. > > Warner > > All over the world , almost all of the products have a "Bar Code" identifier , which approximately may be considered "Unique" . Is there a possibility to associate PCI and USB and other devices with their bar code identifiers ? For computers assembled already , it will be necessary to ask to sellers to supply bar codes of included devices . By using product bar codes , I think , it will be possible to identify uniquely a large number of devices . In that way , it will also be possible to define device characteristics correctly even they lie about their parameters . Mehmet Erol Sanliturk > On Tue, Sep 22, 2015 at 5:38 PM, Mehmet Erol Sanliturk < > m.e.sanliturk@gmail.com> wrote: > >> >> >> On Tue, Sep 22, 2015 at 2:38 PM, Warner Losh wrote: >> >>> I need help with PCI driver marking. Grab my patches and we can talk. >>> >>> Basically, it marks all the .ko modules in a similar way that we do >>> inter-module >>> dependencies with plug and play info. kldxref then takes this data and >>> stuffs >>> it in loader.hints. I also need to write something that will parse this >>> data and >>> either generate a devd.conf file (easy to do from kldxref sources) or >>> queues >>> the load drive in the kernel (kinda hard). Bonus points for similar cod= e >>> in >>> /boot/loader for any storage device that=E2=80=99s found. >>> >>> Warner >>> >>> >>> > On Sep 22, 2015, at 1:12 AM, Mehmet Erol Sanliturk < >>> m.e.sanliturk@gmail.com> wrote: >>> > >>> > >>> > >>> > On Mon, Sep 21, 2015 at 11:58 PM, Hans Petter Selasky >>> wrote: >>> > On 09/22/15 00:58, Mehmet Erol Sanliturk wrote: >>> > On Mon, Sep 21, 2015 at 2:16 PM, Maxime Soul=C3=A9 >>> > wrote: >>> > >>> > One of my wishes is to move ALL of the device definition information >>> for ( >>> > NIC , USB , and other devices ) into files where for each device ( a >>> unique >>> > file to dedicated itself containing information presently defined as >>> preset >>> > in internal arrays with one additional information ( at least ) whic= h >>> > driver will be used for the device ) will be prepared . >>> > >>> > >>> > Hi Mehmet, >>> > >>> > Warner Losh is working on this currently, CC'ed. See: >>> > >>> > https://reviews.freebsd.org/D3458 >>> > >>> > Maybe you want to help out testing? >>> > >>> > --HPS >>> > >>> > >>> > >>> > If I can help in any way , I will do it . >>> > >>> > >>> > Mehmet Erol Sanliturk >>> > >>> > >>> >>> >> >> >> What does "PCI driver marking" mean ? >> >> >> Mehmet Erol Sanliturk >> >> >> >> > From owner-freebsd-usb@freebsd.org Thu Sep 24 20:08:34 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B9E2A08EDF for ; Thu, 24 Sep 2015 20:08:34 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5BC7B1AF7 for ; Thu, 24 Sep 2015 20:08:33 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 90CC61FE023; Thu, 24 Sep 2015 22:08:30 +0200 (CEST) Subject: Re: usb_event_thread/usb_discover called when block transfer in progress [FreeBSD 6.x] To: Shrikanth Kamath , freebsd-usb@freebsd.org References: From: Hans Petter Selasky Message-ID: <5604589C.6070306@selasky.org> Date: Thu, 24 Sep 2015 22:10:04 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 20:08:34 -0000 On 09/10/15 00:04, Shrikanth Kamath wrote: > Basic query is it okay for usb_event_thread/usb_discover to get called > when a block transfer is in progress and there was no USB > attach/detach event? > > Is it triggered by usb controller? Hi, This event is typically triggered by a port-status change event. Are you seeing a particular problem? > > Are there any documents on the FreeBSD 6.x USB stack? Not as I'm aware about. > > USB_DEBUG logs > > usb_transfer_complete: repeat=0 new head=0 > usbd_start_next: pipe=0x82acd7d0, xfer=0 > usb_event_thread: woke up > usb_discover > usbd_transfer: xfer=0x82b7a320, flags=0, pipe=0x82acd820, running=0 > usbd_dump_queue: pipe=0x82acd820 > usb_allocmem: use frag=0x9507df00 size=31 > usb_insert_transfer: pipe=0x82acd820 running=0 timeout=65000 > usb_transfer_complete: pipe=0x82acd820 xfer=0x82b7a320 status=0 actlen=31 > --HPS From owner-freebsd-usb@freebsd.org Fri Sep 25 17:52:49 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2991A0913E for ; Fri, 25 Sep 2015 17:52:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F2B51882 for ; Fri, 25 Sep 2015 17:52:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8PHqnS8035671 for ; Fri, 25 Sep 2015 17:52:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 171197] ADATA Classic CH11 USB HDD doesn't work in FreeBSD 9.1-RC1 Date: Fri, 25 Sep 2015 17:52:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 17:52:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171197 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed Resolution|--- |Overcome By Events CC| |emaste@freebsd.org --- Comment #2 from Ed Maste --- Closed due to lack of feedback on followup questions. If you can still reproduce this issue and are willing to try the patch please reopen. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Fri Sep 25 18:20:36 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 255BEA084A1 for ; Fri, 25 Sep 2015 18:20:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 126661B3B for ; Fri, 25 Sep 2015 18:20:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8PIKZkG034139 for ; Fri, 25 Sep 2015 18:20:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203289] BeagleBone Black invalid USB target descriptors Date: Fri, 25 Sep 2015 18:20:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: blocked Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 18:20:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203289 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |203349 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Sat Sep 26 09:34:22 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C4DB9B8E90 for ; Sat, 26 Sep 2015 09:34:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 38FB5B8 for ; Sat, 26 Sep 2015 09:34:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8Q9YMbp011965 for ; Sat, 26 Sep 2015 09:34:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203252] [patch] usbhidaction does not save the right PID in daemon mode Date: Sat, 26 Sep 2015 09:34:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: btik-fbsd@scoubidou.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 09:34:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203252 Maxime Soul=C3=A9 changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|usbhidaction does not save |[patch] usbhidaction does |the right PID in daemon |not save the right PID in |mode |daemon mode --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Sep 26 17:31:08 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C64DA086DE for ; Sat, 26 Sep 2015 17:31:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 59523200 for ; Sat, 26 Sep 2015 17:31:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8QHV8nk034858 for ; Sat, 26 Sep 2015 17:31:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 203252] [patch] usbhidaction does not save the right PID in daemon mode Date: Sat, 26 Sep 2015 17:31:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 17:31:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203252 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Sat Sep 26 22:41:22 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4AC1A09AAF for ; Sat, 26 Sep 2015 22:41:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A131F1DA7 for ; Sat, 26 Sep 2015 22:41:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8QMfMZ1024565 for ; Sat, 26 Sep 2015 22:41:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 200938] service moused restart required after resume from suspend Date: Sat, 26 Sep 2015 22:41:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ted@xy0.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 22:41:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200938 Ted W. changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ted@xy0.org --- Comment #14 from Ted W. --- (In reply to Joseph Mingrone from comment #5) X61 on 10.2 RELEASE. Workaround ineffective. Here's what I've tried. Only fix is to `/etc/rc.d/moused restart` after resume. * hw.psm.synaptics.touchpad_off=1 #/etc/sysctl.conf * hw.psm.synaptics_support=1 #/boot/loader.conf * hint.psm.0.flags="0x6000" #/boot/devices.hints * /etc/rc.d/moused restart #/etc/rc.resume * /etc/rc.d/moused forcerestart #/etc/rc.resume I am running both moused and hald. I have disabled hald, however, and this had no effect. -- You are receiving this mail because: You are the assignee for the bug.