From owner-freebsd-usb@freebsd.org Tue Sep 26 14:31:10 2017 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 9DD57E0D3A6; Tue, 26 Sep 2017 14:31:10 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (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 582D267ED3; Tue, 26 Sep 2017 14:31:10 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by mail-vk0-x22e.google.com with SMTP id q190so3770802vkd.13; Tue, 26 Sep 2017 07:31:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=xOyPwskdA6frPfhl6cBxoZKMMwQaEftRLifWMR8Ncno=; b=avVXNe5VWCBBkq7v1cxm2y0XSa3BkALeDIF3bxPVGCN5sI/58VoDC39VrrO4Tgyem3 li5J+jIzpB2xhXcdQMM0dkrf40Ox5FkpeOuRZjr+yDeufWE+G2vbmI8JeJBqkPt7T/XV G2zdhm4FJJARbTlDJ6JLjrJU4lx2WmY4CpwGK8ikSRFx3oOH4SouxZjSvwHjFeFki2Tk UjpVbBfzZVi79CPtfmZptb2MwoaGHDgx7dNDuRsUqxCFqOoD7cz3AYS0FwjT5M3AIvW3 uERop2rX4ISs1I1/XWn1nW+aWxEpETDwb0zlHK6CI2VV+g1kULIEThbdryHDRInNoofw DP7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=xOyPwskdA6frPfhl6cBxoZKMMwQaEftRLifWMR8Ncno=; b=LbaTKmG9krDkQf9EJQVYmMp2pojZ+no2+g0wl9xnR2il0meu7CrMJTZZvWjM2CCFY8 4foxl5BGt6qtFVdUtMKyVCTCuCRGsdY1coNzuQx33PVVbF3XocsFiQgDmCik+ietYFVM +LtEE1Ikor+6HNBya5d42qEMcY0EpJWvpjQkyJ0q5ix4Y9sRpPjGQouWowPSVPSVgIvm SsILTmjevvmmkbZHHi7iQZ8/tDoYWxNd2B0PQPX/f7NKSbnP5BEQIsSZAbmb/cLQLrmE 4p0IJW38UL+zGScH3ZGZIrq/huL/AVVtiPtCFf8UuUbO5r1E/KN1yKb4drvs6XmvHFRo 8HwQ== X-Gm-Message-State: AHPjjUg3s3FtsHqH6rSpCKzgY8qjfYx3Fy11aGuDE70/oCU0vI4RZ0x1 v5iqc5EUqPIpo/F4a+yy/ZBhAapc+z1Vw5/CfptPLviB X-Google-Smtp-Source: AOwi7QDgjFWC763/FKwkvDLLgh+6O5yYvf+DiUJHJtmWdtAwgwutANhwKCu0hpATCwLElhv5R9/WwIFp2h38KgsYrEE= X-Received: by 10.31.167.71 with SMTP id q68mr8547908vke.49.1506436268722; Tue, 26 Sep 2017 07:31:08 -0700 (PDT) MIME-Version: 1.0 Sender: tomek.cedro@gmail.com Received: by 10.176.20.35 with HTTP; Tue, 26 Sep 2017 07:30:48 -0700 (PDT) From: Tomasz CEDRO Date: Tue, 26 Sep 2017 16:30:48 +0200 X-Google-Sender-Auth: Tg_bzUrjNgVbqxK-3ZkuZSzZj94 Message-ID: Subject: USB Device self-umount To: FreeBSD Questions Mailing List , "freebsd-usb@FreeBSD.org" , freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 14:31:10 -0000 Hello world! :-) I am working on a device that implements USB MSC mass storage for firmware programming [1]. After receiving file, it flashes the firmware image to the target MCU, then reboots and starts the program or waits debug session.. The question is how to gracefully self-umount from a device point of view in a way not to confuse automounter and/or usb / mass storage drivers? Is there any way of doing that in SCSI+USB? Something like CD-ROM eject, then device removal.. Any hints appreciated :-) Tomek [1] https://github.com/mbedmicro/DAPLink -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-usb@freebsd.org Tue Sep 26 18:04:06 2017 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 23EE2E1269A for ; Tue, 26 Sep 2017 18:04:06 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay15.qsc.de (mailrelay15.qsc.de [212.99.187.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C4026FAE2 for ; Tue, 26 Sep 2017 18:04:04 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay15.qsc.de; Tue, 26 Sep 2017 20:03:10 +0200 Received: from r56.edvax.de (port-92-195-63-92.dynamic.qsc.de [92.195.63.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 8F5453CBF9; Tue, 26 Sep 2017 20:03:09 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v8QI38t4002034; Tue, 26 Sep 2017 20:03:09 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 26 Sep 2017 20:03:08 +0200 From: Polytropon To: Tomasz CEDRO Cc: FreeBSD Questions Mailing List , "freebsd-usb@FreeBSD.org" , freebsd-hardware@freebsd.org Subject: Re: USB Device self-umount Message-Id: <20170926200308.5a9fb785.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-usb@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay15.qsc.de with 17146683678 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1407 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 18:04:06 -0000 On Tue, 26 Sep 2017 16:30:48 +0200, Tomasz CEDRO wrote: > The question is how to gracefully self-umount from a device point of > view in a way not to confuse automounter and/or usb / mass storage > drivers? Is there any way of doing that in SCSI+USB? Something like > CD-ROM eject, then device removal.. This is a _very_ good question of high relevance which hasn't been solved across many operating systems. :-) Basically, a normal (clean) unmount can only be initiated by the OS. You can program the controller (on the USB device) to disconnect on its own, but that doesn't cause the OS to call unmount(), it just makes the device disappear. One thing I could imagine is the use of SCSI status messages and a modified (!) storage access driver in the OS which could act upon a specific status code with a call to unmount(), but that is, as far as I know, not implemented yet anywhere. The primary problem with disconnecting is that it happens _before_ the unmount() call, and keep in mind that unmounting also requires some time. The OS can issue a certain direct access action, but it's up to the device to perform that action. Until it has successfully been performed, the device may not be deconnected. Timing is hard. :-) For CD-ROM, or optical media in general, it's not a problem because it's read-only. The CAM EJECT command - again issued by the OS, not by the device -, when performed _before_ unmount, leaves the OS in a problematic state: Something is still mounted, but it doesn't exist anymore. Okay, umount -f, no damage done. But with read-write media such as USB direct access storage... well... that looks much more complicated. That's why you alway unmount first, then wait, then disconnect. Sorry I couldn't provide more helpful suggestions... ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-usb@freebsd.org Tue Sep 26 20:52:50 2017 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 AB1E9E212F5; Tue, 26 Sep 2017 20:52:50 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-vk0-x242.google.com (mail-vk0-x242.google.com [IPv6:2607:f8b0:400c:c05::242]) (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 62B2E75CED; Tue, 26 Sep 2017 20:52:50 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by mail-vk0-x242.google.com with SMTP id 78so3065338vkc.1; Tue, 26 Sep 2017 13:52:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=j5RaMmrS1C62CAfBnTI5StJl0NtGlHoWuc3meD3ozSg=; b=n0BTTweTOTWsXxnf2lx7lzhu2UwUyOzeUEkxFqAgW2hxXl+q3XQyzQP0UhQMy/eJmi z9sT2XN+yYfetC+NJX7+xuteikmXz0j4AhvTvD24DgJUsAuqPujYbMVjdWbWCu4kf+vR FBL2zn+udz2WprRKzyHtmcQIcLJRX7/C4/yW62YMsbPFdFqp7zjVUII7cMXrfafRuvNZ wI3Rm5FhQJghavJBXyTukktUmEqu6xdyH+hTN4WXkNLbQYi+yuE9OwRoiFNPp/uM1VI+ 3qHKq7rCgGRxsYOluazBNJ/CZanLzXOur1Cvrwcz5W4gx4wiRoQed8fwkwiFa2HSO0SX XGLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=j5RaMmrS1C62CAfBnTI5StJl0NtGlHoWuc3meD3ozSg=; b=FFEwEVlqerGXfg7njblljioa0xmvBUZaLycnWWqx27U04rnFjQkNwwR6EWvAUl58Tc yKmgL1F9erxEq7wWEKh0ZHuOztuasLCzcItotMviODbQygM7roVqpfAQdCMJbUEwmVZV 1+/q8/wRYAY7pd9YZlirDVqHCY4hoOWnaoZRtU7Cay/rOlSJWl3hUQIO8XbKEh+q6kUd jZSQC93adUX0kH5Fb7MAbGyV0c1EBzriVuwhCf4lmBedAnM1OuP4pOw5JT0AWmjsqwcC csO5MCYQFVHtk1OjVLdQ3gSm9UnA/AfAZoQLKeHV2AR0Hdr75sDZnhH9YdcDu+XZsrAK kM4A== X-Gm-Message-State: AHPjjUjZdkiZi7mc1y+pVCqvXYlkDNuL5XNL86l9Wl6JYA9pyuWXdYn9 h8WA53aQIJ++6d1NvLu9vybunQPibrggW7gNcVbmfuDo X-Google-Smtp-Source: AOwi7QCmV2VBO9GBCMTBGhBi+0bV1XN1Z5HDGtUbasrQNhrokf2oebMjrVCVp+tz6Uem5bXwt+xTJYU3ArQZ9WXB9WE= X-Received: by 10.31.82.3 with SMTP id g3mr9254182vkb.76.1506459169368; Tue, 26 Sep 2017 13:52:49 -0700 (PDT) MIME-Version: 1.0 Sender: tomek.cedro@gmail.com Received: by 10.176.20.35 with HTTP; Tue, 26 Sep 2017 13:52:28 -0700 (PDT) In-Reply-To: <20170926200308.5a9fb785.freebsd@edvax.de> References: <20170926200308.5a9fb785.freebsd@edvax.de> From: Tomasz CEDRO Date: Tue, 26 Sep 2017 22:52:28 +0200 X-Google-Sender-Auth: tXjEV8Ng_JoaHs2xKwNz8sHls8g Message-ID: Subject: Re: USB Device self-umount To: Polytropon Cc: FreeBSD Questions Mailing List , "freebsd-usb@FreeBSD.org" , freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 20:52:50 -0000 Hey Polytropon! :-) Thanks for ideas! I am at the moment at point where I sniff out the USB traffic and analyze SCSI packets.. and also I got into SCSI specification to search for some possibilities.. :-) I will have to see how Windoze handles ATAPI EJECT, maybe that could bring some insight on how to umount ejectable media triggered by the device-eject-button-press.. As for now the device reports CHECK-CONDITION to mark media missing, then reboots and re-appeares, but that causes "device not cleanly unmounted" warnings on macOS for instance.. Will report back when I find anything interesting :-) Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-usb@freebsd.org Tue Sep 26 21:02:05 2017 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 8FF29E2171E for ; Tue, 26 Sep 2017 21:02:05 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay12.qsc.de (mailrelay12.qsc.de [212.99.163.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01CF176170 for ; Tue, 26 Sep 2017 21:02:04 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay12.qsc.de; Tue, 26 Sep 2017 23:01:31 +0200 Received: from r56.edvax.de (port-92-195-63-92.dynamic.qsc.de [92.195.63.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 1F1AA3CC42; Tue, 26 Sep 2017 23:01:29 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v8QL1TBp002712; Tue, 26 Sep 2017 23:01:29 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 26 Sep 2017 23:01:29 +0200 From: Polytropon To: Tomasz CEDRO Cc: FreeBSD Questions Mailing List , "freebsd-usb@FreeBSD.org" , freebsd-hardware@freebsd.org Subject: Re: USB Device self-umount Message-Id: <20170926230129.7b00d9a7.freebsd@edvax.de> In-Reply-To: References: <20170926200308.5a9fb785.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-usb@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay12.qsc.de with 88B456A3827 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1473 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 21:02:05 -0000 On Tue, 26 Sep 2017 22:52:28 +0200, Tomasz CEDRO wrote: > I will have to see how Windoze handles ATAPI EJECT, maybe that could > bring some insight on how to umount ejectable media triggered by the > device-eject-button-press.. Hmmm... I don't think this is what happens. ATAPI EJECT is issued by the OS (ATAPI device driver) and the device simply ejects. If this action is "prefixed" with an unmount() call and a certain delay, everything is well. This is how a typical GUI file manager on Linux or FreeBSD works. But pressing the device's eject button will simply eject the media. Subsequent TUR inquiries by the OS will result in "device not ready", and that may cause the umount() call, but _after_ the device has been removed. > As for now the device reports CHECK-CONDITION to mark media missing, > then reboots and re-appeares, but that causes "device not cleanly > unmounted" warnings on macOS for instance.. Of course it does. :-) With filesystems mounted read-only, this typically isn't a problem, but those with read-write access might be left in an inconsistent state, and depending on the OS, cannot be mounted again (or require a run of fsck, or in case of "Windows", a kind of "repair" that often leads to data loss and corrupted files). Examining the USB traffic and checking for the CAM packets exchanged between the device and the OS could help you find a way to implement the impossible. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-usb@freebsd.org Tue Sep 26 22:11:42 2017 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 40482E238A2 for ; Tue, 26 Sep 2017 22:11:42 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 005AA7CE98 for ; Tue, 26 Sep 2017 22:11:41 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by mail-vk0-x230.google.com with SMTP id h63so468323vka.4 for ; Tue, 26 Sep 2017 15:11:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=Qayv7iqxf8g5C1BWlDg5TCJdmVEjllrETQFj2wum8T4=; b=eVACPjR781XYEbU8TIrlOPQq6B85Wr655S0Ofn4fXAAOMb96D7dc1Jp084vmrd1xZB m4VlSm4RYVONGXNJGGjiQRam5HNQ3DaZv3rhEd1y6K5zTcwl3gYX3sU+I+SvFeVi15GE x8uPFrsuL8GAPt+cEHkrOe61DySjLr04chq8xxpOJyvWNL/dlx7LS6wTsCRvwQg4wzLH JPCHI4ZfuYFR4GGNxzD10YPdAQEfXi089mrj6q0oF62q0yrrJeBpYUjlmKH9NzzM4w1j zdsFeGwK2XZWSUoWzoLXYv1z0My+V0L4grrU9o+9b/MBfJiKbfdYaNJcX6lxcG72OTaA oiBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=Qayv7iqxf8g5C1BWlDg5TCJdmVEjllrETQFj2wum8T4=; b=uKlbidh83ndHN117OGc/XTtR6qBSH5UkbnDOUnF3l5IxVrQorMk0ohebqSQoZEpXV0 YbvAXoYAITYqqna7LjAEU0MeGLw/WzhWwCCg16VrE7esEoU02UyDsPRwQ25vTOoz9ynv MNimoA54ml7nLYk4C2TKIrm6o1b3+XIj/ZuVexzbqQ9Nd1rK5W3h3tN4gMLa9f0cguui smYQs98buanNIBqDwrBzQxcYGN0V7YwsDkTpMmw4Pf6hqXr+VP27fNbN9fYhu4sCFZEx YwzEV1GzJkND2deOVl2VAOI5RFQq9fCxAssmLNZpLPLgUEOtgz3WGNIoSyycctwMuaSQ nmoQ== X-Gm-Message-State: AHPjjUgT6QzFfK+OpQLckpZ5G3C5poKawBEw3zTULDSVIOFaZ1tc5Ew/ c83j2IBNhPb/o72ehJlGyZOjGiRkgS9G9NCkhMlzEhN7 X-Google-Smtp-Source: AOwi7QAGq3iAiKEdWBBzZ9+v+bY2H2EeB4oNCC8HQ1seywDqjZeaB6XoKCaB1nlBGfnXUagDPxeEvbOcbpTMPObnoiw= X-Received: by 10.31.10.19 with SMTP id 19mr9972314vkk.3.1506463900703; Tue, 26 Sep 2017 15:11:40 -0700 (PDT) MIME-Version: 1.0 Sender: tomek.cedro@gmail.com Received: by 10.176.20.35 with HTTP; Tue, 26 Sep 2017 15:11:20 -0700 (PDT) From: Tomasz CEDRO Date: Wed, 27 Sep 2017 00:11:20 +0200 X-Google-Sender-Auth: cD7qsyndGY5VI72JtcmlfHMmZzM Message-ID: Subject: USB/U3G: Added support for Panasonic CF-F9 GOBI 3G modem to U3G module To: "freebsd-usb@FreeBSD.org" , Hans Petter Selasky Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 22:11:42 -0000 https://github.com/freebsd/freebsd/pull/115 :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-usb@freebsd.org Tue Sep 26 22:33:32 2017 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 512BEE24192 for ; Tue, 26 Sep 2017 22:33:32 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 1B6B97DDB1 for ; Tue, 26 Sep 2017 22:33:32 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (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 A51D4260072; Wed, 27 Sep 2017 00:33:29 +0200 (CEST) Subject: Re: USB/U3G: Added support for Panasonic CF-F9 GOBI 3G modem to U3G module To: Tomasz CEDRO , "freebsd-usb@FreeBSD.org" References: From: Hans Petter Selasky Message-ID: Date: Wed, 27 Sep 2017 00:30:58 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 22:33:32 -0000 On 09/27/17 00:11, Tomasz CEDRO wrote: > https://github.com/freebsd/freebsd/pull/115 > > :-) > The devd.conf rule should match more than just vendor and product: +# Load GOBI 2000/3000 U3G QDL modem firmware on attach / boot. +# Note: This requires additional "gobi_loader" utility to be installed, +# as well as valid QDL driver firmware files placed in /boot/firmware/gobi. +# If modem does not accept valid firmware try gobi_loader -2000 switch. +# Please adjust modem VID/PID to match your device supported by u3g module. +#attach 100 { +# match "vendor" "0x04da"; +# match "product" "0x250e"; +# action "/usr/local/sbin/gobi_loader /dev/cuaU0 /boot/firmware/gobi/"; +#}; Else patch looks good. --HPS From owner-freebsd-usb@freebsd.org Tue Sep 26 22:37:48 2017 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 4A43EE24264 for ; Tue, 26 Sep 2017 22:37:48 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 2D9397DEDE for ; Tue, 26 Sep 2017 22:37:47 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 4fda4d02-a30b-11e7-a937-4f970e858fdb X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 4fda4d02-a30b-11e7-a937-4f970e858fdb; Tue, 26 Sep 2017 22:37:44 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v8QMbdcD002090; Tue, 26 Sep 2017 16:37:39 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1506465459.73082.168.camel@freebsd.org> Subject: Re: USB/U3G: Added support for Panasonic CF-F9 GOBI 3G modem to U3G module From: Ian Lepore To: Hans Petter Selasky , Tomasz CEDRO , "freebsd-usb@FreeBSD.org" Date: Tue, 26 Sep 2017 16:37:39 -0600 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 22:37:48 -0000 On Wed, 2017-09-27 at 00:30 +0200, Hans Petter Selasky wrote: > On 09/27/17 00:11, Tomasz CEDRO wrote: > > > > https://github.com/freebsd/freebsd/pull/115 > > > > :-) > > > The devd.conf rule should match more than just vendor and product: > > > +# Load GOBI 2000/3000 U3G QDL modem firmware on attach / boot. > +# Note: This requires additional "gobi_loader" utility to be > installed, > +#   as well as valid QDL driver firmware files placed in  > /boot/firmware/gobi. > +#   If modem does not accept valid firmware try gobi_loader -2000 > switch. > +#   Please adjust modem VID/PID to match your device supported by > u3g  > module. > +#attach 100 { > +# match "vendor" "0x04da"; > +# match "product" "0x250e"; > +# action "/usr/local/sbin/gobi_loader /dev/cuaU0 > /boot/firmware/gobi/"; > +#}; > > Else patch looks good. > > --HPS Hard-coding /dev/cuaU0 cannot possibly be right. -- Ian From owner-freebsd-usb@freebsd.org Tue Sep 26 22:59:12 2017 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 B4B5AE24A8B for ; Tue, 26 Sep 2017 22:59:12 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (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 6C6737EB03; Tue, 26 Sep 2017 22:59:12 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by mail-ua0-x233.google.com with SMTP id c27so7446503uah.2; Tue, 26 Sep 2017 15:59:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ChqovzVJI3HyzfOGaiovSIeWaMTJUfZJPytRxLt0Gis=; b=b8aK1BL5t1GTVu7j/AHFqisdxI5mfPO3RIdNaZkvesxkmV0/6T14Oz+hDynTwVhmYu 0E/x5wLbN9E6TbyMOdfdWI5gYuJj63npjZL9JHVn3RauHPMABgK5xte/7l6ijplr9IYm 1a4zG0BUDAig7EKut4PX9xneO2EvElcu/IzKFQC+eLYrPKXVx0g3qzFiuLoLe4v5L9m6 +2HJHFku9iL7DJna4kqUBiou4UACmum/JRnUIAXaBlZJHaG4g8eXkgF/MehahpLmApo0 4N5CEDyPe+UqY5WSaey80Vj1BeEGVvwSOmwHIVRfTHkB4psJrHkSDTKv5+eFWsjjJyDW WkfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ChqovzVJI3HyzfOGaiovSIeWaMTJUfZJPytRxLt0Gis=; b=lXz1sRMy2AZXyTLqIRNdmbGX8u2CUdiEG1vobZogn0Sk0e8sUivYAsNUnEfS5znLtJ mtHW8qRoRtVyLn8OKd64Fi2+Li9vwAuk+SY4Y8EnJMSqw2D0d5rMhPju5po4RdoOYJ2L MEX5Kp7PVGtPBSk0eQY6K6idYJv7Uy+cqA+gONBDJ8g1QBAzUuaEhHEwgQimBxPy9wU6 HezWYsEUPx0uPoICCsQLdEzeBMbFILAOeYUmYp/N+eITYfxbgLI/TxXu+kmoW7mSBVmC P1rMinpDnZKF185yw6LhexK9Vgkatze+q44ltCvw6WC6Y2TbCskvEzt8RdwJeL6NOlYk wyyw== X-Gm-Message-State: AHPjjUhaqfDet9U4xSxfHZu/pWl7FmopeFiLZEIqudSvWMbnmHS1pWrw 3hr9LXkzWShzZKVNKCqTs8gu9t7tLMnX0cPwg0S3zA== X-Google-Smtp-Source: AOwi7QA8BRe+XNTrn4TczDJ5IFWClAUbIdXgyZbxNkcw2rHhz+V03CSKp/3w7HYCMWxgh2eYH6y4BdrQKsodv1xa+xg= X-Received: by 10.176.74.8 with SMTP id q8mr10509237uae.129.1506466751408; Tue, 26 Sep 2017 15:59:11 -0700 (PDT) MIME-Version: 1.0 Sender: tomek.cedro@gmail.com Received: by 10.176.20.35 with HTTP; Tue, 26 Sep 2017 15:58:50 -0700 (PDT) In-Reply-To: References: From: Tomasz CEDRO Date: Wed, 27 Sep 2017 00:58:50 +0200 X-Google-Sender-Auth: nS-L-EKl5ds0OzssvyTo_qYbJH0 Message-ID: Subject: Re: USB/U3G: Added support for Panasonic CF-F9 GOBI 3G modem to U3G module To: Hans Petter Selasky , Ian Lepore Cc: "freebsd-usb@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 22:59:12 -0000 Its all commented out, just an example on how to configure "this kind of device".. not really mandatory but nice to have I thought :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-usb@freebsd.org Wed Sep 27 02:11:31 2017 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 155B7E28881 for ; Wed, 27 Sep 2017 02:11:31 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from bit0.com (chunkhead.bit0.com [52.14.199.164]) (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 D79D78430A for ; Wed, 27 Sep 2017 02:11:30 +0000 (UTC) (envelope-from mandrews@bit0.com) Received: from chunkhead.bit0.com (localhost [127.0.0.1]) by bit0.com (Postfix) with ESMTP id 4DC5C24FE4; Tue, 26 Sep 2017 22:11:24 -0400 (EDT) X-Virus-Scanned: amavisd-new at bit0.com Received: from bit0.com ([127.0.0.1]) by chunkhead.bit0.com (chunkhead.bit0.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvlk-9Veb1Sm; Tue, 26 Sep 2017 22:11:23 -0400 (EDT) Received: from beast.int.bit0.com (cpe-74-129-151-147.kya.res.rr.com [74.129.151.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bit0.com (Postfix) with ESMTPSA; Tue, 26 Sep 2017 22:11:22 -0400 (EDT) Date: Tue, 26 Sep 2017 22:11:22 -0400 (EDT) From: Mike Andrews X-X-Sender: mandrews@beast.int.bit0.com To: Hans Petter Selasky cc: freebsd-usb@freebsd.org Subject: Re: umodem0, Cisco USB serial console, and quirks In-Reply-To: <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> Message-ID: References: <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2017 02:11:31 -0000 On Tue, 19 Sep 2017, Hans Petter Selasky wrote: > On 09/19/17 18:15, Mike Andrews wrote: >> >> 12:03:37.726830 usbus4.3 SUBM-BULK-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=0 >> frame[0] READ 1024 bytes >> flags 0xa >> status 0xcf023 > > Hi, > > Look for: > > XXXX-BULK-EP=00000082 > > This is the USB read transfer. The other side is not returning any data, so > neither is "cu" printing anything. Maybe you can try to get a similar trace > from the system where it works? > > Looks to me like some kind of protocol error, that the Cisco USB serial > console needs some kind of activation. Took me a few days to get around to getting usbmon going on Linux. The verbose dump is too large for the list, so: https://www.bit0.com/tmp/usbmon-ciscoasa-verbose.txt https://www.bit0.com/tmp/usbmon-ciscoasa.txt From owner-freebsd-usb@freebsd.org Wed Sep 27 06:35:27 2017 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 7400DE2C76F for ; Wed, 27 Sep 2017 06:35:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 3C80A65F33; Wed, 27 Sep 2017 06:35:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (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 EE82E2601AB; Wed, 27 Sep 2017 08:35:24 +0200 (CEST) Subject: Re: USB/U3G: Added support for Panasonic CF-F9 GOBI 3G modem to U3G module To: Ian Lepore , Tomasz CEDRO , "freebsd-usb@FreeBSD.org" References: <1506465459.73082.168.camel@freebsd.org> From: Hans Petter Selasky Message-ID: <165556bc-c011-bebd-feee-5bbd4cb5943e@selasky.org> Date: Wed, 27 Sep 2017 08:32:52 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1506465459.73082.168.camel@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2017 06:35:27 -0000 On 09/27/17 00:37, Ian Lepore wrote: > On Wed, 2017-09-27 at 00:30 +0200, Hans Petter Selasky wrote: >> On 09/27/17 00:11, Tomasz CEDRO wrote: >>> >>> https://github.com/freebsd/freebsd/pull/115 >>> >>> :-) >>> >> The devd.conf rule should match more than just vendor and product: >> >> >> +# Load GOBI 2000/3000 U3G QDL modem firmware on attach / boot. >> +# Note: This requires additional "gobi_loader" utility to be >> installed, >> +#   as well as valid QDL driver firmware files placed in >> /boot/firmware/gobi. >> +#   If modem does not accept valid firmware try gobi_loader -2000 >> switch. >> +#   Please adjust modem VID/PID to match your device supported by >> u3g >> module. >> +#attach 100 { >> +# match "vendor" "0x04da"; >> +# match "product" "0x250e"; >> +# action "/usr/local/sbin/gobi_loader /dev/cuaU0 >> /boot/firmware/gobi/"; >> +#}; >> >> Else patch looks good. >> >> --HPS > > Hard-coding /dev/cuaU0 cannot possibly be right. > > -- Ian > These three lines are missing: match "system" "DEVFS"; match "subsystem" "CDEV"; match "type" "CREATE"; --HPS From owner-freebsd-usb@freebsd.org Thu Sep 28 04:11:08 2017 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 AAD46E279FD for ; Thu, 28 Sep 2017 04:11: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 9974F6E514 for ; Thu, 28 Sep 2017 04:11: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 v8S4B7L7067055 for ; Thu, 28 Sep 2017 04:11:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Thu, 28 Sep 2017 04:11:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org 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: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 04:11:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hselasky@FreeBSD.org Assignee|freebsd-bugs@FreeBSD.org |freebsd-usb@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 04:11:22 2017 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 6F417E27A4E for ; Thu, 28 Sep 2017 04:11: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 5CA726E5B7 for ; Thu, 28 Sep 2017 04:11: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 v8S4BMge069270 for ; Thu, 28 Sep 2017 04:11:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Thu, 28 Sep 2017 04:11:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 04:11:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 07:42:34 2017 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 BFDB8E2B93C for ; Thu, 28 Sep 2017 07:42:34 +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 AED6A73E48 for ; Thu, 28 Sep 2017 07:42:34 +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 v8S7gYZX048566 for ; Thu, 28 Sep 2017 07:42:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Thu, 28 Sep 2017 07:42:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 07:42:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 --- Comment #1 from Hans Petter Selasky --- Hi, I think it is clever to add a check: if (data !=3D 0) ->>> if (sc->sc_ndata.keycode[0] =3D=3D KEY_ERROR && data !=3D 0) So that you don't override valid key input. Or else scan the keycode array and place data last. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 07:48:54 2017 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 A7FDDE2BB26 for ; Thu, 28 Sep 2017 07:48:54 +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 968917405A for ; Thu, 28 Sep 2017 07:48:54 +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 v8S7msW5057203 for ; Thu, 28 Sep 2017 07:48:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222659] Add quirk UQ_MSC_NO_PREVENT_ALLOW to SMI USB DISK 3000 Date: Thu, 28 Sep 2017 07:48:54 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rfraile@rfraile.eu X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org 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: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 07:48:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222659 Bug ID: 222659 Summary: Add quirk UQ_MSC_NO_PREVENT_ALLOW to SMI USB DISK 3000 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: rfraile@rfraile.eu Plugin the following usb storage device (usbconfig report): ugen0.2: at usbus0, cfg=3D0 md=3DHOST spd=3DFULL= (12Mbps) pwr=3DON (100mA) bLength =3D 0x0012=20 bDescriptorType =3D 0x0001=20 bcdUSB =3D 0x0200=20 bDeviceClass =3D 0x0000 bDeviceSubClass =3D 0x0000=20 bDeviceProtocol =3D 0x0000=20 bMaxPacketSize0 =3D 0x0040=20 idVendor =3D 0x090c=20 idProduct =3D 0x1000=20 bcdDevice =3D 0x3000=20 iManufacturer =3D 0x0001 iProduct =3D 0x0002 iSerialNumber =3D 0x0003 <2010121200000149> bNumConfigurations =3D 0x0001=20 Produces the following errors: (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 ee ff fe 00 00 01 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 ee ff fe 00 00 01 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Error 5, Retries exhausted Which makes it impossible to mount and use it. After adding the following lines to the loader.conf file, the problem was fixed: usb_quirk_load=3D"YES" hw.usb.quirk.0=3D"0x090c 0x1000 0 0xffff UQ_MSC_NO_PREVENT_ALLOW" And the dmesg log don't have any issue registered: uhub0: 2 ports with 2 removable, self powered ugen0.2: at usbus0 umass0: on us= bus0 umass0: SCSI over Bulk-Only; quirks =3D 0xc000 umass0:2:0: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 da0: Removable Direct Access SCSI device da0: Serial Number 2010121200000149 da0: 1.000MB/s transfers da0: 7648MB (15663104 512 byte sectors) da0: quirks=3D0x3 Thanks, --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 07:53:00 2017 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 9E378E2BCC1 for ; Thu, 28 Sep 2017 07:53:00 +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 8BE8D7431D for ; Thu, 28 Sep 2017 07:53:00 +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 v8S7r0IS070753 for ; Thu, 28 Sep 2017 07:53:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222659] Add quirk UQ_MSC_NO_PREVENT_ALLOW to SMI USB DISK 3000 Date: Thu, 28 Sep 2017 07:53:00 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 07:53:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222659 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hselasky@FreeBSD.org --- Comment #1 from Hans Petter Selasky --- Hi, Please make a patch for: sys/dev/usb/quirk/usb_quirk.c and sys/dev/usb/usbdevs --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 12:46:36 2017 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 92DE8E319B9 for ; Thu, 28 Sep 2017 12:46: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 81322823D9 for ; Thu, 28 Sep 2017 12:46: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 v8SCka7R062462 for ; Thu, 28 Sep 2017 12:46:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222665] Cannot send anything if characters received ahead of first use of ftdi chip Date: Thu, 28 Sep 2017 12:46:36 +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.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nkoch@demig.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org 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: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 12:46:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222665 Bug ID: 222665 Summary: Cannot send anything if characters received ahead of first use of ftdi chip Product: Base System Version: 10.3-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Some People Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: nkoch@demig.de In an embedded system we use an ftdi chip FT4232HL for serial communication. Channels 1 and 2 are unused, channel 3 is RS485, channel 4 is RS232. The system is a kind of terminal which responds to messages coming in via serial communication. We previously used FreeBSD 8.2 without any problems. With FreeBSD 10.3 we found the following situation: 1. Turn on power. 2. Wait until BIOS finishes and boot loader starts. 3. Immediately begin transmitting messages via RS485 to this device. 4. Application starts and opens /dev/cuaU2. 5. Application sees message and posts answer, but answer is not being sent. 6. Close application and outstanding characters are being sent. 7. Reopen application and all works fine. This problem seems to only occur with RS485 at cuaU2, *not* with RS232 at cuaU3. If nothing is being sent before step 4 all seems ok. With hw.usb.ucom.debug=3D1 I can see that ucom_outwakeup() seems never being called in error case. The first ucom_outwakeup() I then see comes from close(). Having put additional debug messages in ucom_get_data() and ucom_put_data() I can see that my application tries to send the expected response. ioctl(UFTDIIOC_RESET_IO) after open() seems to solve that problem for me. But I am unsure if this is a fix of a chip problem or a workaround for a kernel/driver/locking problem (which could also come from the upper tty layer). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 12:46:56 2017 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 E02ABE319E7 for ; Thu, 28 Sep 2017 12:46: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 CE95E82417 for ; Thu, 28 Sep 2017 12:46:56 +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 v8SCkucs063006 for ; Thu, 28 Sep 2017 12:46:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222665] [uftdi] Cannot send anything if characters received ahead of first use of ftdi chip Date: Thu, 28 Sep 2017 12:46:57 +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.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nkoch@demig.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 12:46:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222665 nkoch@demig.de changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Cannot send anything if |[uftdi] Cannot send |characters received ahead |anything if characters |of first use of ftdi chip |received ahead of first use | |of ftdi chip --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 12:49:22 2017 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 E58FDE31A33 for ; Thu, 28 Sep 2017 12:49: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 D38F582608 for ; Thu, 28 Sep 2017 12:49: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 v8SCnM3g066259 for ; Thu, 28 Sep 2017 12:49:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222665] [uftdi] Cannot send anything if characters received ahead of first use of ftdi chip Date: Thu, 28 Sep 2017 12:49: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.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 12:49:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222665 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hselasky@FreeBSD.org --- Comment #1 from Hans Petter Selasky --- Hi, Some ideas: Have a look at the USB traffic using usbdump tool. It will show what is goi= ng on at the lowest level. Are you using libftdi? Are there any other applications which use libusb to communicate with the F= TDI chip instead of /dev/cuaUX ? --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 14:06:00 2017 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 3EC4AE32A69 for ; Thu, 28 Sep 2017 14:06:00 +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 200D38AD for ; Thu, 28 Sep 2017 14:06:00 +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 v8SE5xPX060873 for ; Thu, 28 Sep 2017 14:05:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222665] [uftdi] Cannot send anything if characters received ahead of first use of ftdi chip Date: Thu, 28 Sep 2017 14:06:00 +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.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nkoch@demig.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 14:06:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222665 --- Comment #2 from nkoch@demig.de --- Created attachment 186784 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D186784&action= =3Dedit 3 different usbdumps usb.err.dump - The error scenario as described in the ticket: serial data coming in before opening /dev/cuaUx usb.ok.dump - No serial communication before opening /dev/cuauX usb.ioctl.dump - ioctl(UFTDIIOC_RESET_IO) after open() --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 14:06:17 2017 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 9FC38E32A86 for ; Thu, 28 Sep 2017 14:06:17 +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 8E7848E7 for ; Thu, 28 Sep 2017 14:06:17 +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 v8SE6FxO061246 for ; Thu, 28 Sep 2017 14:06:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222659] Add quirk UQ_MSC_NO_PREVENT_ALLOW to SMI USB DISK 3000 Date: Thu, 28 Sep 2017 14:06: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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: roabertwelain@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 14:06:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222659 Robert Welain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roabertwelain@gmail.com --- Comment #2 from Robert Welain --- Visit https://spying.ninja guys. YOu;ll like the apps --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Sep 28 15:11:47 2017 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 CC4B9E33D45 for ; Thu, 28 Sep 2017 15:11:47 +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 B548E2B73 for ; Thu, 28 Sep 2017 15:11:47 +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 v8SFBlPj052343 for ; Thu, 28 Sep 2017 15:11:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222665] [uftdi] Cannot send anything if characters received ahead of first use of ftdi chip Date: Thu, 28 Sep 2017 15:11:47 +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.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ian@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ian@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 15:11:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222665 Ian Lepore changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Assignee|freebsd-usb@FreeBSD.org |ian@FreeBSD.org --- Comment #3 from Ian Lepore --- I'll look into this. I can confirm that a large change in the ftdi driver between 8.2 and 10.x w= as that the old code would reset the chip on open(), and now that doesn't happ= en.=20 The reset was harmful for some embedded uses, such as when the chip is used= in mpsse or bitbang mode. How is your rs485 transceiver connected to the ftdi? Is the transmitter connected to #TXDEN, and if so, are you using the eeprom to reconfigure that pin from RI to TXDEN? Is the receive side squelched in hardware (as sugges= ted in the ftdi datasheet, or otherwise) when the transmit side is active? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Fri Sep 29 14:45:06 2017 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 55B89E2E6F9 for ; Fri, 29 Sep 2017 14:45:06 +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 42FB7687C1 for ; Fri, 29 Sep 2017 14:45:06 +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 v8TEj6ow088787 for ; Fri, 29 Sep 2017 14:45:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222624] [usb] [panic] thread's sleep queue 0 is not empty at usb_process.c:193 Date: Fri, 29 Sep 2017 14:45:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2017 14:45:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222624 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-usb@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Fri Sep 29 14:58:40 2017 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 6C6ABE2E9A1 for ; Fri, 29 Sep 2017 14:58:40 +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 5AF07692B8 for ; Fri, 29 Sep 2017 14:58:40 +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 v8TEweG9019344 for ; Fri, 29 Sep 2017 14:58:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222624] [usb] [panic] thread's sleep queue 0 is not empty at usb_process.c:193 Date: Fri, 29 Sep 2017 14:58:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2017 14:58:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222624 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hselasky@FreeBSD.org --- Comment #1 from Hans Petter Selasky --- Did you do anything special to trigger this? Might be a generic kernel issu= e. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Fri Sep 29 17:18:40 2017 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 EE379E3112E for ; Fri, 29 Sep 2017 17:18:40 +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 DC8786E8BF for ; Fri, 29 Sep 2017 17:18:40 +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 v8THIdXE097839 for ; Fri, 29 Sep 2017 17:18:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Fri, 29 Sep 2017 17:18:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: wulf@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2017 17:18:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 Vladimir Kondratyev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wulf@freebsd.org --- Comment #2 from Vladimir Kondratyev --- (In reply to Greg V from comment #0) Did you check events generated by your patched ukbd when two HID consumer-p= age keys are pressed and then released simultaneously? I think you will get pre= ss events for both keys but release event only for a one of them. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Fri Sep 29 19:33:59 2017 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 73655E33B6B for ; Fri, 29 Sep 2017 19:33: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 59F7C72C64 for ; Fri, 29 Sep 2017 19:33: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 v8TJXwch049023 for ; Fri, 29 Sep 2017 19:33:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Fri, 29 Sep 2017 19:33:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@unrelenting.technology X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2017 19:33:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 --- Comment #3 from Greg V --- (In reply to Hans Petter Selasky from comment #1) (In reply to Vladimir Kondratyev from comment #2) >From what I understand, consumer control packets are completely separate packets that cannot contain keyboard keypresses (totally different usage pa= ge than keyboard keys, 0xC vs 0x7). Just confirmed at https://deskthority.net/wiki/Media_key#USB Pressing both volume buttons on my mouse results in the two keys pressed-released in order. Some devices *might* support simultaneous presse= s of multiple media keys, but I think in that case, we would just lose the extra= key presses. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Fri Sep 29 19:40:34 2017 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 876EFE33C39 for ; Fri, 29 Sep 2017 19:40:34 +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 75E1272E33 for ; Fri, 29 Sep 2017 19:40:34 +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 v8TJeYQd057630 for ; Fri, 29 Sep 2017 19:40:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222624] [usb] [panic] thread's sleep queue 0 is not empty at usb_process.c:193 Date: Fri, 29 Sep 2017 19:40:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: decke@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2017 19:40:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222624 --- Comment #2 from Bernhard Froehlich --- No it happens around every 1-5 days on two similar Supermicro boards. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Fri Sep 29 22:04:27 2017 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 1FEFDE35F4F for ; Fri, 29 Sep 2017 22:04: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 01D1376B1D for ; Fri, 29 Sep 2017 22:04: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 v8TM4QSf046851 for ; Fri, 29 Sep 2017 22:04:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Fri, 29 Sep 2017 22:04:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: wulf@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2017 22:04:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 --- Comment #4 from Vladimir Kondratyev --- (In reply to Greg V from comment #3) > Pressing both volume buttons on my mouse results in the two keys pressed-= released in order. Did you observed it with evemu or with libinput? Please use former as it connects directly to input device and gives raw data. > Some devices *might* support simultaneous presses of multiple media keys,= but I think in that case, we would just lose the extra key presses. I recently implemented evdev support for consumer page for bluetooth keyboa= rds (not publicly available yet) and found out that my bt-keyboard loses *relea= se* events on simultaneous presses as it is unable to report "which key has been depressed" at HID-protocol level. It is capable only to say that "last/all = key has been depressed" so my driver has to generate release event at next interrupt at his own. I do not see how your patch does such "autorelease". Maybe ukbd does this automagically? I should look deeper in its internals. Unfortunately I cant do hardware testing now --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Sep 30 08:40:38 2017 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 55E16E15F49 for ; Sat, 30 Sep 2017 08:40:38 +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 3CB11669FE for ; Sat, 30 Sep 2017 08:40:38 +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 v8U8ebB2005648 for ; Sat, 30 Sep 2017 08:40:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222624] [usb] [panic] thread's sleep queue 0 is not empty at usb_process.c:193 Date: Sat, 30 Sep 2017 08:40:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2017 08:40:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222624 --- Comment #3 from Hans Petter Selasky --- Hi, I see you have kernel built with INVARIANTS. There is a chance that the ass= erts triggering this issue are false. I've added some more people to analyze this issue. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Sep 30 11:40:42 2017 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 01888E25939 for ; Sat, 30 Sep 2017 11:40:42 +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 E46286CE79 for ; Sat, 30 Sep 2017 11:40: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 v8UBefMb059447 for ; Sat, 30 Sep 2017 11:40:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Sat, 30 Sep 2017 11:40:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@unrelenting.technology X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2017 11:40:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 --- Comment #5 from Greg V --- (In reply to Vladimir Kondratyev from comment #4) Didn't know about evemu, nice tool. Just tried it, events are always sequential: 1, 0, 1, 0=E2=80=A6 My mouse does not support simultaneous media key presses, it always returns only one key. ukbd gets the report with all zeros and generates the release event. My pat= ch only allows one media key to be pressed, others are lost, so the release ev= ent will always release that key. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Sep 30 12:15:47 2017 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 E78ABE26D20 for ; Sat, 30 Sep 2017 12:15:47 +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 D65DD6EAD3 for ; Sat, 30 Sep 2017 12:15:47 +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 v8UCFlXD026755 for ; Sat, 30 Sep 2017 12:15:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Sat, 30 Sep 2017 12:15:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2017 12:15:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 --- Comment #6 from Hans Petter Selasky --- Can you make the patch so that no other keys are lost. For example by exten= ding the key array? --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Sep 30 15:30:26 2017 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 CA712E2957B for ; Sat, 30 Sep 2017 15:30:26 +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 B886272B3C for ; Sat, 30 Sep 2017 15:30:26 +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 v8UFUQdW086504 for ; Sat, 30 Sep 2017 15:30:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Date: Sat, 30 Sep 2017 15:30:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@unrelenting.technology X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2017 15:30:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 Greg V changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #186765|0 |1 is obsolete| | --- Comment #7 from Greg V --- Created attachment 186814 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D186814&action= =3Dedit ukbd_consumer_ctl.patch v2 ok here's a version that supports multiple keys. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Sep 30 17:26:52 2017 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 1B151E2B72F for ; Sat, 30 Sep 2017 17:26:52 +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 08ADD75A1C for ; Sat, 30 Sep 2017 17:26:52 +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 v8UHQpiR063961 for ; Sat, 30 Sep 2017 17:26:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222624] [usb] [panic] thread's sleep queue 0 is not empty at usb_process.c:193 Date: Sat, 30 Sep 2017 17:26:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: decke@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2017 17:26:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222624 --- Comment #4 from Bernhard Froehlich --- I also do have this panics with the release kernel but never got any useful info from it when it happened because it just stopped and did not even show= a panic. What makes me confident that it's not a faulty hardware is that 10.3= was running very solid on it for around a year and that I have two of those machines with the exact same symptoms. --=20 You are receiving this mail because: You are the assignee for the bug.=