From owner-freebsd-usb@freebsd.org Sun Jul 24 06:03:01 2016 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 45683BA1B23; Sun, 24 Jul 2016 06:03:01 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 EAD4518AF; Sun, 24 Jul 2016 06:03:00 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bRCV7-0031YY-Jw>; Sun, 24 Jul 2016 08:02:57 +0200 Received: from x4e34a127.dyn.telefonica.de ([78.52.161.39] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bRCV7-003pps-A7>; Sun, 24 Jul 2016 08:02:57 +0200 Date: Sun, 24 Jul 2016 08:03:30 +0200 From: "O. Hartmann" To: Ian Lepore Cc: freebsd-usb@freebsd.org, FreeBSD CURRENT Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU Message-ID: <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> In-Reply-To: <1469306951.84197.31.camel@freebsd.org> References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/M8+Szzb3PB+HgSWCrY8ureM"; protocol="application/pgp-signature" X-Originating-IP: 78.52.161.39 X-ZEDAT-Hint: A X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 06:03:01 -0000 --Sig_/M8+Szzb3PB+HgSWCrY8ureM Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sat, 23 Jul 2016 14:49:11 -0600 Ian Lepore schrieb: > On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote: > > Am Fri, 22 Jul 2016 10:52:54 -0600 > > Ian Lepore schrieb: > > =20 > > > On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote: =20 > > > > For temperature monitoring, we have a bunch of Digi Watchport/T > > > > sensors:=20 > > > >=20 > > > > http://ftp1.digi.com/support/documentation/90000406_H.pdf > > > >=20 > > > > =20 > > > [...] > > >=20 > > > I think the attached patch will make it show up as a ttyU*/cuaU* > > > device > > > for you. (You should probably use the /dev/cuaU* flavor, to avoid > > > problems with tty layer and modem control signals). > > >=20 > > > I keep wishing we had a mechanism, like a sysctl that could be set > > > or > > > something, that would let you supply a vendor/product pair and have > > > the > > > ugensa driver attach to that device, for quick testing of this sort > > > of > > > thing. > > >=20 > > > -- Ian =20 > >=20 > > No, it doesn't change anything. I applied the patch to most recent > > CURRENT and it is > > still the same. But thanks anyway. > >=20 > > Kind regards, > >=20 > > oh =20 >=20 > Oh, my bad, I forgot to mention: You'll have to manually "kldload > ugensa" before plugging in the device (or load it from your > loader.conf). >=20 > When the change gets committed (assuming it works), the devd usb > scripts will get regenerated, and that's what handles the auto-load of > the driver. >=20 > -- Ian man ugensa doesn't exist! As I wrote earlier, I tried everything to load wh= at I could find. It seems, the patch and the hint about ugensa.ko did the magic ;-) Th= ank you very much! Could the patch be made permanent to FreeBSD CURRENT? And also important: where is the man page for ugensa? Can the the module be= compiled staitcally into the kernel or are there pitfalls? root@localhost: [src] kldload ugensa ugen2.7: at usbus2 ugensa0: on usbus2 ugensa0: Found 1 interfaces. root@thor: [src] man ugensa No manual entry for ugensa root@localhost: [src] ll /dev/cuaU0* 203 crw-rw---- 1 uucp dialer - 0xcb Jul 24 07:51 /dev/cuaU0 204 crw-rw---- 1 uucp dialer - 0xcc Jul 24 07:51 /dev/cuaU0.init 205 crw-rw---- 1 uucp dialer - 0xcd Jul 24 07:51 /dev/cuaU0.lock I'll try now to get informations out of the device, I let you know whether = that is a success. But anyway, again, thank you for helping making the device visible= and available. Kind regards, Oliver Hartmann --Sig_/M8+Szzb3PB+HgSWCrY8ureM Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXlFoyAAoJEOgBcD7A/5N8WFUIAIKyWVMR1pEbcuu8IhGv1daI kieLrwDZpRrCJpjpb4tsL11vyv7Zuexd8UMfSNwsRLW3VeFjJFbLn/gAqvgkU2Li 6QMAyTbezqkkhHjem6po68/21dY57St3TwvkMvi5Ix1etQq/qRzh/fCULWJMd72x K0avAM/RO6qUfr35Ph2KXpas9DiwkRgHLYuoYrnuR0MPvOMhlruw4wAR1tj9wqf8 ZWHCdlZzWmEcrlEzJAg0Y7GGW23Db6C1eOqeyRhBAYnZf3Glghk3G6Mf+7fP4c9B FwSYA/LFewoAQNOAVe+JaF102NPNlI7BxmiefsbACbZnYANumiIfxwf0W9lzPDI= =j5TN -----END PGP SIGNATURE----- --Sig_/M8+Szzb3PB+HgSWCrY8ureM-- From owner-freebsd-usb@freebsd.org Sun Jul 24 06:39:14 2016 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 2B5C5B9B315; Sun, 24 Jul 2016 06:39:14 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::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 BD496160C; Sun, 24 Jul 2016 06:39:13 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x242.google.com with SMTP id o80so11943818wme.0; Sat, 23 Jul 2016 23:39:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=q9Q4lxK5Y2igg3d+ljNIhZkcmRJ48SvmbdxPZqSJibg=; b=Qf4mpQ36rQEuKfXtccpqhIGrOEQccDCUwl4cgcaiqW52TsAzCWj+dzCnNXTvVqUwBL QqQPWEJzsfn3SckwDHUB3zVr0PdWPE6TYiCNg8nxl8dW71kh++E0h2EExKGMBFNS6lG2 fCkrpr7jnARkkwNfCt013Ss1QW0YvnpzJQCTtNgRWRCB5DKzo923uO59gEJbCP1lsEl2 N8YlqgBXh/ERS0jvhgqpmTNA0Nh12hJXf9mBEA/eHa2v8SlAcgXupmfP6bgWqKHIK125 7iLgUA37TJiggwm8G0CLM2rT89wjOBdwNG0kM8WgK6hinsywyYQJVpo3M9fvTNijjlo2 K1sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=q9Q4lxK5Y2igg3d+ljNIhZkcmRJ48SvmbdxPZqSJibg=; b=LS3egDcrseL2NLFw+gG8YpcqvX5z6ZG6Ng9MARPmEQNFa6pWSiqvOo7SOjTR0U612K uvVmE0AaHjvSetKNQYeWaQ6Woa25q/e5nz59UHr0/RfibwPxFpTSjkaCJIcwGmWA7QhO tOJ0xseRrut7YLeeas73XW6F3ByAatWhGteVrQOKlg368rle6BKh1UWcZpM/su9XoQnc vdsVaLmYQO801pNS4+WVln+8vbMkn3PkzBjl1XMwWOt6HveEJQkMh8Ap23BiJwesdtik ZqZB5chkDxuj1QK5QXBklpl5uSWqiHjDBQTghbrrbJeR2Dy8w99OHf9Vif1ddCQEJisB 7vrg== X-Gm-Message-State: AEkoous0y7RYGf3vaMQaE8lhExYJ+kdJgV/fQUONMOcl7n7Rq6vM6HC8O5WH8oFN+jFAag== X-Received: by 10.28.157.148 with SMTP id g142mr14772226wme.2.1469342351317; Sat, 23 Jul 2016 23:39:11 -0700 (PDT) Received: from ernst.home (p578E0FCF.dip0.t-ipconnect.de. [87.142.15.207]) by smtp.gmail.com with ESMTPSA id r67sm20871011wmb.14.2016.07.23.23.39.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Jul 2016 23:39:10 -0700 (PDT) Date: Sun, 24 Jul 2016 08:38:59 +0200 From: Gary Jennejohn To: "O. Hartmann" Cc: Ian Lepore , freebsd-usb@freebsd.org, FreeBSD CURRENT Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU Message-ID: <20160724083859.4c0dd392@ernst.home> In-Reply-To: <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 06:39:14 -0000 On Sun, 24 Jul 2016 08:03:30 +0200 "O. Hartmann" wrote: > Am Sat, 23 Jul 2016 14:49:11 -0600 > Ian Lepore schrieb: > > > On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote: > > > Am Fri, 22 Jul 2016 10:52:54 -0600 > > > Ian Lepore schrieb: > > > > > > > On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote: > > > > > For temperature monitoring, we have a bunch of Digi Watchport/T > > > > > sensors: > > > > > > > > > > http://ftp1.digi.com/support/documentation/90000406_H.pdf > > > > > > > > > > > > > > [...] > > > > > > > > I think the attached patch will make it show up as a ttyU*/cuaU* > > > > device > > > > for you. (You should probably use the /dev/cuaU* flavor, to avoid > > > > problems with tty layer and modem control signals). > > > > > > > > I keep wishing we had a mechanism, like a sysctl that could be set > > > > or > > > > something, that would let you supply a vendor/product pair and have > > > > the > > > > ugensa driver attach to that device, for quick testing of this sort > > > > of > > > > thing. > > > > > > > > -- Ian > > > > > > No, it doesn't change anything. I applied the patch to most recent > > > CURRENT and it is > > > still the same. But thanks anyway. > > > > > > Kind regards, > > > > > > oh > > > > Oh, my bad, I forgot to mention: You'll have to manually "kldload > > ugensa" before plugging in the device (or load it from your > > loader.conf). > > > > When the change gets committed (assuming it works), the devd usb > > scripts will get regenerated, and that's what handles the auto-load of > > the driver. > > > > -- Ian > man ugensa doesn't exist! As I wrote earlier, I tried everything to load what I could > find. It seems, the patch and the hint about ugensa.ko did the magic ;-) Thank you very > much! Could the patch be made permanent to FreeBSD CURRENT? > > And also important: where is the man page for ugensa? Can the the module be compiled > staitcally into the kernel or are there pitfalls? > Even the most complete man page found in the internet, the one from Dragonfly, doesn't list your Digi International device as being one of those supported. Still, having the man page under FreeBSD would at least provide a hint that the driver even exists. I added device ugensa to my config file and the kernel was generated without an error. > root@localhost: [src] kldload ugensa > > ugen2.7: at usbus2 > ugensa0: on usbus2 > ugensa0: Found 1 interfaces. > root@thor: [src] man ugensa > No manual entry for ugensa > root@localhost: [src] ll /dev/cuaU0* > 203 crw-rw---- 1 uucp dialer - 0xcb Jul 24 07:51 /dev/cuaU0 > 204 crw-rw---- 1 uucp dialer - 0xcc Jul 24 07:51 /dev/cuaU0.init > 205 crw-rw---- 1 uucp dialer - 0xcd Jul 24 07:51 /dev/cuaU0.lock > > > I'll try now to get informations out of the device, I let you know whether that is a > success. But anyway, again, thank you for helping making the device visible and available. > -- Gary Jennejohn From owner-freebsd-usb@freebsd.org Sun Jul 24 08:51:03 2016 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 A1515BA3427; Sun, 24 Jul 2016 08:51:03 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 6086B15F8; Sun, 24 Jul 2016 08:51:03 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bRF7l-003VgV-Cf>; Sun, 24 Jul 2016 10:51:01 +0200 Received: from x4e34a127.dyn.telefonica.de ([78.52.161.39] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bRF7l-004161-3c>; Sun, 24 Jul 2016 10:51:01 +0200 Date: Sun, 24 Jul 2016 10:51:34 +0200 From: "O. Hartmann" To: Gary Jennejohn Cc: Ian Lepore , freebsd-usb@freebsd.org, FreeBSD CURRENT Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU Message-ID: <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> In-Reply-To: <20160724083859.4c0dd392@ernst.home> References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> <20160724083859.4c0dd392@ernst.home> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/o/t_pXrOJINiBb9lbfwGo_J"; protocol="application/pgp-signature" X-Originating-IP: 78.52.161.39 X-ZEDAT-Hint: A X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 08:51:03 -0000 --Sig_/o/t_pXrOJINiBb9lbfwGo_J Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 24 Jul 2016 08:38:59 +0200 Gary Jennejohn schrieb: > On Sun, 24 Jul 2016 08:03:30 +0200 > "O. Hartmann" wrote: >=20 > > Am Sat, 23 Jul 2016 14:49:11 -0600 > > Ian Lepore schrieb: > > =20 > > > On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote: =20 > > > > Am Fri, 22 Jul 2016 10:52:54 -0600 > > > > Ian Lepore schrieb: > > > > =20 > > > > > On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote: =20 > > > > > > For temperature monitoring, we have a bunch of Digi Watchport/T > > > > > > sensors:=20 > > > > > >=20 > > > > > > http://ftp1.digi.com/support/documentation/90000406_H.pdf > > > > > >=20 > > > > > > =20 > > > > > [...] > > > > >=20 > > > > > I think the attached patch will make it show up as a ttyU*/cuaU* > > > > > device > > > > > for you. (You should probably use the /dev/cuaU* flavor, to avoid > > > > > problems with tty layer and modem control signals). > > > > >=20 > > > > > I keep wishing we had a mechanism, like a sysctl that could be set > > > > > or > > > > > something, that would let you supply a vendor/product pair and ha= ve > > > > > the > > > > > ugensa driver attach to that device, for quick testing of this so= rt > > > > > of > > > > > thing. > > > > >=20 > > > > > -- Ian =20 > > > >=20 > > > > No, it doesn't change anything. I applied the patch to most recent > > > > CURRENT and it is > > > > still the same. But thanks anyway. > > > >=20 > > > > Kind regards, > > > >=20 > > > > oh =20 > > >=20 > > > Oh, my bad, I forgot to mention: You'll have to manually "kldload > > > ugensa" before plugging in the device (or load it from your > > > loader.conf). > > >=20 > > > When the change gets committed (assuming it works), the devd usb > > > scripts will get regenerated, and that's what handles the auto-load of > > > the driver. > > >=20 > > > -- Ian =20 > > man ugensa doesn't exist! As I wrote earlier, I tried everything to loa= d what I could > > find. It seems, the patch and the hint about ugensa.ko did the magic ;-= ) Thank you > > very much! Could the patch be made permanent to FreeBSD CURRENT? > >=20 > > And also important: where is the man page for ugensa? Can the the modul= e be compiled > > staitcally into the kernel or are there pitfalls? > > =20 >=20 > Even the most complete man page found in the internet, the one from > Dragonfly, doesn't list your Digi International device as being one > of those supported. Yes. That is a pity. But Linux seems to operate this serial device. I have = to check next time I get hands on a Linux box, what driver is attached to the sensor. >=20 > Still, having the man page under FreeBSD would at least provide a hint > that the driver even exists. Agreed. >=20 > I added device ugensa to my config file and the kernel was generated > without an error. Me, too. >=20 > > root@localhost: [src] kldload ugensa > >=20 > > ugen2.7: at usbus2 > > ugensa0: on usbu= s2 > > ugensa0: Found 1 interfaces. > > root@thor: [src] man ugensa > > No manual entry for ugensa > > root@localhost: [src] ll /dev/cuaU0* > > 203 crw-rw---- 1 uucp dialer - 0xcb Jul 24 07:51 /dev/cuaU0 > > 204 crw-rw---- 1 uucp dialer - 0xcc Jul 24 07:51 /dev/cuaU0.init > > 205 crw-rw---- 1 uucp dialer - 0xcd Jul 24 07:51 /dev/cuaU0.lock > >=20 > >=20 > > I'll try now to get informations out of the device, I let you know whet= her that is a > > success. But anyway, again, thank you for helping making the device vis= ible and > > available.=20 >=20 I had no luck with retrieving informations out of the device by the Perl5 s= cript provided by Nagios.org. A prerequisite for the Perl script is the FreeBSD port comms/p5-Device-SerialPort Patching the script is trivial, but I do not know whether the backend, comms/p5-Device-SerialPort, works a sexpected. So the first, dirty, trial e= nded up in nothing - since the information gained from the sensor is an empty string/n= othing. I'm not familiar with serial devices, so far, so probably there is somethin= g trivial missing. --Sig_/o/t_pXrOJINiBb9lbfwGo_J Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXlIGWAAoJEOgBcD7A/5N8CmoH/jUYDAovA8em7YRtAs64/QDV FdApj+GEjpeMfQIRbsFrqu65U5thA5stFYRCRNrRY1cbiocjm3hiYBw3yscGPhxy tZec1bmb9CLQ1GeRuZTd0cGVujPeEFOqRzr819ghupWcPhqK7MFEoaL4JJkewv8Q GNizxOnCiq5g2uHe0Q3QGUDR5GD9WCwpnXOaRRd/RoAceE1EIgFHmtlZiG6k9LKS 7BVIN3DgTq07t//P5sw3jnMKpQr0AD/EjewiZ2cc7GV1vy4tegGNFaWADp7ehhBl SlLxCyMyShoTFfLuDd51GaMF/0D6EHHeElwPU+hOR1/2EeRp5aUx25HyXdAqVec= =12BX -----END PGP SIGNATURE----- --Sig_/o/t_pXrOJINiBb9lbfwGo_J-- From owner-freebsd-usb@freebsd.org Sun Jul 24 13:58:56 2016 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 21C61BA325C for ; Sun, 24 Jul 2016 13:58:56 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) (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 D773612DE for ; Sun, 24 Jul 2016 13:58:55 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id DD302188C4E for ; Sun, 24 Jul 2016 08:58:52 -0500 (CDT) Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU To: freebsd-usb@freebsd.org References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> <20160724083859.4c0dd392@ernst.home> <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> From: Karl Denninger Message-ID: Date: Sun, 24 Jul 2016 08:58:48 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms050601030606060402080705" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 13:58:56 -0000 This is a cryptographically signed message in MIME format. --------------ms050601030606060402080705 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 7/24/2016 03:51, O. Hartmann wrote: > Am Sun, 24 Jul 2016 08:38:59 +0200 > Gary Jennejohn schrieb: > >> On Sun, 24 Jul 2016 08:03:30 +0200 >> "O. Hartmann" wrote: >> >>> Am Sat, 23 Jul 2016 14:49:11 -0600 >>> Ian Lepore schrieb: >>> =20 >>>> On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote: =20 >>>>> Am Fri, 22 Jul 2016 10:52:54 -0600 >>>>> Ian Lepore schrieb: >>>>> =20 >>>>>> On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote: =20 >>>>>>> For temperature monitoring, we have a bunch of Digi Watchport/T >>>>>>> sensors:=20 >>>>>>> >>>>>>> http://ftp1.digi.com/support/documentation/90000406_H.pdf >>>>>>> >>>>>>> =20 >>>>>> [...] >>>>>> >>>>>> I think the attached patch will make it show up as a ttyU*/cuaU* >>>>>> device >>>>>> for you. (You should probably use the /dev/cuaU* flavor, to avoid= >>>>>> problems with tty layer and modem control signals). >>>>>> >>>>>> I keep wishing we had a mechanism, like a sysctl that could be set= >>>>>> or >>>>>> something, that would let you supply a vendor/product pair and hav= e >>>>>> the >>>>>> ugensa driver attach to that device, for quick testing of this sor= t >>>>>> of >>>>>> thing. >>>>>> >>>>>> -- Ian =20 >>>>> No, it doesn't change anything. I applied the patch to most recent >>>>> CURRENT and it is >>>>> still the same. But thanks anyway. >>>>> >>>>> Kind regards, >>>>> >>>>> oh =20 >>>> Oh, my bad, I forgot to mention: You'll have to manually "kldload >>>> ugensa" before plugging in the device (or load it from your >>>> loader.conf). >>>> >>>> When the change gets committed (assuming it works), the devd usb >>>> scripts will get regenerated, and that's what handles the auto-load = of >>>> the driver. >>>> >>>> -- Ian =20 >>> man ugensa doesn't exist! As I wrote earlier, I tried everything to l= oad what I could >>> find. It seems, the patch and the hint about ugensa.ko did the magic = ;-) Thank you >>> very much! Could the patch be made permanent to FreeBSD CURRENT? >>> >>> And also important: where is the man page for ugensa? Can the the mod= ule be compiled >>> staitcally into the kernel or are there pitfalls? >>> =20 >> Even the most complete man page found in the internet, the one from >> Dragonfly, doesn't list your Digi International device as being one >> of those supported. > Yes. That is a pity. But Linux seems to operate this serial device. I h= ave to check next > time I get hands on a Linux box, what driver is attached to the sensor.= > >> Still, having the man page under FreeBSD would at least provide a hint= >> that the driver even exists. > Agreed. > >> I added device ugensa to my config file and the kernel was generated >> without an error. > Me, too. > >>> root@localhost: [src] kldload ugensa >>> >>> ugen2.7: at usbus2 >>> ugensa0: on us= bus2 >>> ugensa0: Found 1 interfaces. >>> root@thor: [src] man ugensa >>> No manual entry for ugensa >>> root@localhost: [src] ll /dev/cuaU0* >>> 203 crw-rw---- 1 uucp dialer - 0xcb Jul 24 07:51 /dev/cuaU0 >>> 204 crw-rw---- 1 uucp dialer - 0xcc Jul 24 07:51 /dev/cuaU0.init >>> 205 crw-rw---- 1 uucp dialer - 0xcd Jul 24 07:51 /dev/cuaU0.lock >>> >>> >>> I'll try now to get informations out of the device, I let you know wh= ether that is a >>> success. But anyway, again, thank you for helping making the device v= isible and >>> available.=20 > > I had no luck with retrieving informations out of the device by the Per= l5 script provided > by Nagios.org. A prerequisite for the Perl script is the FreeBSD port > > comms/p5-Device-SerialPort > > Patching the script is trivial, but I do not know whether the backend, > comms/p5-Device-SerialPort, works a sexpected. So the first, dirty, tri= al ended up in > nothing - since the information gained from the sensor is an empty stri= ng/nothing. > > I'm not familiar with serial devices, so far, so probably there is some= thing trivial > missing. I looked them up and those little SOBs are expensive! I was considering grabbing one just to play with, but not at that price :) You should be able to "cu" to the port and send the ASCII command it wants to provide a reading; that would verify it is working. --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms050601030606060402080705 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC Bl8wggZbMIIEQ6ADAgECAgEpMA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE1MDQyMTAyMjE1OVoXDTIwMDQxOTAyMjE1OVowWjEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxHjAcBgNVBAMTFUthcmwgRGVubmluZ2VyIChPQ1NQKTCCAiIwDQYJKoZIhvcNAQEBBQAD ggIPADCCAgoCggIBALmEWPhAdphrWd4K5VTvE5pxL3blRQPyGF3ApjUjgtavqU1Y8pbI3Byg XDj2/Uz9Si8XVj/kNbKEjkRh5SsNvx3Fc0oQ1uVjyCq7zC/kctF7yLzQbvWnU4grAPZ3IuAp 3/fFxIVaXpxEdKmyZAVDhk9az+IgHH43rdJRIMzxJ5vqQMb+n2EjadVqiGPbtG9aZEImlq7f IYDTnKyToi23PAnkPwwT+q1IkI2DTvf2jzWrhLR5DTX0fUYC0nxlHWbjgpiapyJWtR7K2YQO aevQb/3vN9gSojT2h+cBem7QIj6U69rEYcEDvPyCMXEV9VcXdcmW42LSRsPvZcBHFkWAJqMZ Myiz4kumaP+s+cIDaXitR/szoqDKGSHM4CPAZV9Yh8asvxQL5uDxz5wvLPgS5yS8K/o7zDR5 vNkMCyfYQuR6PAJxVOk5Arqvj9lfP3JSVapwbr01CoWDBkpuJlKfpQIEeC/pcCBKknllbMYq yHBO2TipLyO5Ocd1nhN/nOsO+C+j31lQHfOMRZaPQykXVPWG5BbhWT7ttX4vy5hOW6yJgeT/ o3apynlp1cEavkQRS8uJHoQszF6KIrQMID/JfySWvVQ4ksnfzwB2lRomrdrwnQ4eG/HBS+0l eozwOJNDIBlAP+hLe8A5oWZgooIIK/SulUAsfI6Sgd8dTZTTYmlhAgMBAAGjgfQwgfEwNwYI KwYBBQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgw CQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIB DQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUxRyULenJaFwX RtT79aNmIB/u5VkwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYw FIESa2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBPf3cYtmKowmGIYsm6 eBinJu7QVWvxi1vqnBz3KE+HapqoIZS8/PolB/hwiY0UAE1RsjBJ7yEjihVRwummSBvkoOyf G30uPn4yg4vbJkR9lTz8d21fPshWETa6DBh2jx2Qf13LZpr3Pj2fTtlu6xMYKzg7cSDgd2bO sJGH/rcvva9Spkx5Vfq0RyOrYph9boshRN3D4tbWgBAcX9POdXCVfJONDxhfBuPHsJ6vEmPb An+XL5Yl26XYFPiODQ+Qbk44Ot1kt9s7oS3dVUrh92Qv0G3J3DF+Vt6C15nED+f+bk4gScu+ JHT7RjEmfa18GT8DcT//D1zEke1Ymhb41JH+GyZchDRWtjxsS5OBFMzrju7d264zJUFtX7iJ 3xvpKN7VcZKNtB6dLShj3v/XDsQVQWXmR/1YKWZ93C3LpRs2Y5nYdn6gEOpL/WfQFThtfnat HNc7fNs5vjotaYpBl5H8+VCautKbGOs219uQbhGZLYTv6okuKcY8W+4EJEtK0xB08vqr9Jd0 FS9MGjQE++GWo+5eQxFt6nUENHbVYnsr6bYPQsZH0CRNycgTG9MwY/UIXOf4W034UpR82TBG 1LiMsYfb8ahQJhs3wdf1nzipIjRwoZKT1vGXh/cj3gwSr64GfenURBxaFZA5O1acOZUjPrRT n3ci4McYW/0WVVA3lDGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMH RmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExD MRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5 c3RlbXMgTExDIENBAgEpMA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZI hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA3MjQxMzU4NDhaME8GCSqGSIb3DQEJBDFCBEBI cCltuX+mjk0xzT17+xYgrNFjSea/PqtA+OHlaujwK06aBt7jeG3wAuAUeLFxDzdviIKoJmVj ze7X9DGO0+o1MGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAK BggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYI KoZIhvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNV BAgTB0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1z IExMQzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3Vk YSBTeXN0ZW1zIExMQyBDQQIBKTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYT AlVTMRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1 ZGEgU3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG 9w0BCQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECASkwDQYJKoZIhvcNAQEBBQAEggIAFrXCCHzG 7lcFwqdlzAJWiEWa3bvlvn1LNadclNCnco/Ib7nSjCsP8q1EJaotvVnQDhiRVzfCQzD3i3ss G+EkLFV7B6h+/yKCu2g8ICOUWcL8TkLGByaDLx3al2X6lc7lrgus4+gBtiro5FnsnRyCWIQp gltU6ZcczDXHqAR/UL6DEu7uYyQwKNmjc5I1kGALScIhu2FmVq/BsqxnPfkhgsiJ29Szeuzl VQM5lFnvaRwwOr7hmbbeLu1OqW9x+bH0uHNuWGbP48TNoDZS6qrAfiu9BgG8C+ADYqnUwe8Q NQhK0YyP+qHd0ZRAdJdr/ZEYgwfE00xKJwPbto7W8WkR4cnG3AY7DiPlZopk+5lqpCpGLj7M mUFljogdyprtL2Nfb0B6owbiwG2jovg+RlkU1Vz+xZDkR7qzkmH4ZDjSmTF9moA6azHPgcUH 6rH4rFm+WUAOFBv8dC7KuWYZfaRahJKd7sMt07SiKQLq13qMHv6qdq8+I5kBQZPQjr/qQ8JL rGV0bzUIkXy+8kVEZZwFbQiEVqZqoRP6XXUTFq7A+bfq9id+l2LJy0J1v34e4H4zPgQOGkJt 6qsR2qG8rWhVyqOugO9UJNQZh1oUh+O2zVzdEJdOdFQUA33C4zvHHov2U5eRx1HRs//QoDp2 OJnjGmZ7nm5HnumF9Nu4AWyl8Y8AAAAAAAA= --------------ms050601030606060402080705-- From owner-freebsd-usb@freebsd.org Sun Jul 24 16:55:43 2016 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 B09E2BA3DEB for ; Sun, 24 Jul 2016 16:55:43 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 9300E132C for ; Sun, 24 Jul 2016 16:55:43 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 98520d4a-51bf-11e6-8929-8ded99d5e9d7 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Sun, 24 Jul 2016 16:56:41 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u6OGtYPW013863; Sun, 24 Jul 2016 10:55:34 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1469379334.84197.40.camel@freebsd.org> Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU From: Ian Lepore To: "O. Hartmann" , Gary Jennejohn Cc: freebsd-usb@freebsd.org, FreeBSD CURRENT Date: Sun, 24 Jul 2016 10:55:34 -0600 In-Reply-To: <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> <20160724083859.4c0dd392@ernst.home> <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 16:55:43 -0000 On Sun, 2016-07-24 at 10:51 +0200, O. Hartmann wrote: > Am Sun, 24 Jul 2016 08:38:59 +0200 > Gary Jennejohn schrieb: > > > On Sun, 24 Jul 2016 08:03:30 +0200 > > "O. Hartmann" wrote: > > > > > Am Sat, 23 Jul 2016 14:49:11 -0600 > > > Ian Lepore schrieb: > > > > > > > On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote: > > > > > Am Fri, 22 Jul 2016 10:52:54 -0600 > > > > > Ian Lepore schrieb: > > > > > > > > > > > On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote: > > > > > > > For temperature monitoring, we have a bunch of Digi > > > > > > > Watchport/T > > > > > > > sensors: > > > > > > > > > > > > > > http://ftp1.digi.com/support/documentation/90000406_H.pdf > > > > > > > > > > > > > > > > > > > > [...] > > > > > > > > > > > > I think the attached patch will make it show up as a > > > > > > ttyU*/cuaU* > > > > > > device > > > > > > for you. (You should probably use the /dev/cuaU* flavor, > > > > > > to avoid > > > > > > problems with tty layer and modem control signals). > > > > > > > > > > > > I keep wishing we had a mechanism, like a sysctl that could > > > > > > be set > > > > > > or > > > > > > something, that would let you supply a vendor/product pair > > > > > > and have > > > > > > the > > > > > > ugensa driver attach to that device, for quick testing of > > > > > > this sort > > > > > > of > > > > > > thing. > > > > > > > > > > > > -- Ian > > > > > > > > > > No, it doesn't change anything. I applied the patch to most > > > > > recent > > > > > CURRENT and it is > > > > > still the same. But thanks anyway. > > > > > > > > > > Kind regards, > > > > > > > > > > oh > > > > > > > > Oh, my bad, I forgot to mention: You'll have to manually > > > > "kldload > > > > ugensa" before plugging in the device (or load it from your > > > > loader.conf). > > > > > > > > When the change gets committed (assuming it works), the devd > > > > usb > > > > scripts will get regenerated, and that's what handles the auto > > > > -load of > > > > the driver. > > > > > > > > -- Ian > > > man ugensa doesn't exist! As I wrote earlier, I tried everything > > > to load what I could > > > find. It seems, the patch and the hint about ugensa.ko did the > > > magic ;-) Thank you > > > very much! Could the patch be made permanent to FreeBSD CURRENT? > > > > > > And also important: where is the man page for ugensa? Can the the > > > module be compiled > > > staitcally into the kernel or are there pitfalls? > > > > > > > Even the most complete man page found in the internet, the one from > > Dragonfly, doesn't list your Digi International device as being one > > of those supported. > > Yes. That is a pity. But Linux seems to operate this serial device. I > have to check next > time I get hands on a Linux box, what driver is attached to the > sensor. > > > > > Still, having the man page under FreeBSD would at least provide a > > hint > > that the driver even exists. > > Agreed. > > > > > I added device ugensa to my config file and the kernel was > > generated > > without an error. > > Me, too. > > > > > > root@localhost: [src] kldload ugensa > > > > > > ugen2.7: at usbus2 > > > ugensa0: > > > on usbus2 > > > ugensa0: Found 1 interfaces. > > > root@thor: [src] man ugensa > > > No manual entry for ugensa > > > root@localhost: [src] ll /dev/cuaU0* > > > 203 crw-rw---- 1 uucp dialer - 0xcb Jul 24 07:51 /dev/cuaU0 > > > 204 crw-rw---- 1 uucp dialer - 0xcc Jul 24 07:51 > > > /dev/cuaU0.init > > > 205 crw-rw---- 1 uucp dialer - 0xcd Jul 24 07:51 > > > /dev/cuaU0.lock > > > > > > > > > I'll try now to get informations out of the device, I let you > > > know whether that is a > > > success. But anyway, again, thank you for helping making the > > > device visible and > > > available. > > > > > I had no luck with retrieving informations out of the device by the > Perl5 script provided > by Nagios.org. A prerequisite for the Perl script is the FreeBSD port > > comms/p5-Device-SerialPort > > Patching the script is trivial, but I do not know whether the > backend, > comms/p5-Device-SerialPort, works a sexpected. So the first, dirty, > trial ended up in > nothing - since the information gained from the sensor is an empty > string/nothing. > > I'm not familiar with serial devices, so far, so probably there is > something trivial > missing. I looked around for some info on these Watchport devices. Their manual indicates that they use both serial comms to send commands and receive data, and they use serial-comms modem control signals (RTS/CTS, DTR, etc). Some googling makes it look like they use a TI 5052 USB serial chip. On linux, that would be handled by the io_ti USB serial driver. All of that adds up to the freebsd ugensa driver (which is "generic serial IO") probably not working. The ugensa driver has nothing chip -specific in it, it's for accessing devices which can do bulk read/write without needing to configure any of the other serial comms parameters. The ugensa driver works with things like gps receivers that have simple text-only interfaces. I think these watchport devices will likely need real serial comms configuration -- baud rate at least, to even be able to talk to them. In other words, freebsd needs a real driver for TI 5052 chips. It looks like a fairly complete datasheet for the chip is available (but I don't have time to write a driver myself). -- Ian From owner-freebsd-usb@freebsd.org Sun Jul 24 18:42:08 2016 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 3CAD7BA18FF; Sun, 24 Jul 2016 18:42:08 +0000 (UTC) (envelope-from kob6558@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 01BB6186E; Sun, 24 Jul 2016 18:42:08 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id q83so145236752iod.1; Sun, 24 Jul 2016 11:42:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=a325cawI4RKbZ7+6/uA4y713IcPgd0azRAJKGg4Nwug=; b=hfFjUMJMebhQd70iYosnVE2KBOziz+ODO7CkUL7voQiKR5g2aQ8Z3jOcO3zPhTMPbG Xwn+yuPh1/QwwIxeY78ZRyoadNX8P+Bdo17VRkIC/1jgFds8KQ2kJ+KbSMEWFyxoGuST DlZZHqg416c8vjjmiHTXEz3eZy9auFPTsastz/OKdawa6k6al/EYiJS3FxZBabK6yNIE xiPLBUvgobG/hp7PHxwQe3rAqDlVAohoqpFuyOV3xy920vYjFaxctLu8ptX8ozlOqmwl FXVrRr3Xr2a3hCRf+Psvvr5vCNn9Axi/zWYIfnB6aANxkhTIH3ZCKXiPOgsYeaY2utPe UU9w== 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:from :date:message-id:subject:to:cc; bh=a325cawI4RKbZ7+6/uA4y713IcPgd0azRAJKGg4Nwug=; b=Fo7CfFP+O8QAKXJArEcFir+3HjE45eWNSYwynWLP7p+kccGETVEyjTnr4dTS4/Juzh OUEWOigdO453+IuCcuf1ZDTq5f8akc8+3B+x19X4ecWDomMevUNldtBlonpyEFUrayhV v4D6cYcCTv8uCzZdJsCZp8HQNJSUERBz3H377AkswE8EYnYUhlX1wQCem83sC1riLbI+ 5/iR269N8zXiYSxxgkdMjXPpaEqAKGVyBqaGfL18rsS9hgRPE9HPt26VFFymskz0na82 WqOgGlFox9ZYa0MrseWymBGe/ZtJu56V2oJOWAhYT2LaKq07qwz3jTPHN/cD5gxZgUVv +90A== X-Gm-Message-State: AEkoous8ddxcNESKVpuD5hXnmwta1l4Gf8k0lkZWO0RmnCzSwfz7qzgOfuxTEnCslKhim85gffbv348Qus26Ag== X-Received: by 10.107.129.152 with SMTP id l24mr16603246ioi.179.1469385727318; Sun, 24 Jul 2016 11:42:07 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.79.78.213 with HTTP; Sun, 24 Jul 2016 11:42:06 -0700 (PDT) In-Reply-To: <1469379334.84197.40.camel@freebsd.org> References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> <20160724083859.4c0dd392@ernst.home> <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> <1469379334.84197.40.camel@freebsd.org> From: Kevin Oberman Date: Sun, 24 Jul 2016 11:42:06 -0700 X-Google-Sender-Auth: ErFVBtR9kHSlW0SwlkLJAQwS_x8 Message-ID: Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU To: Ian Lepore Cc: "O. Hartmann" , Gary Jennejohn , "freebsd-usb@FreeBSD.org" , FreeBSD CURRENT Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 18:42:08 -0000 On Sun, Jul 24, 2016 at 9:55 AM, Ian Lepore wrote: > On Sun, 2016-07-24 at 10:51 +0200, O. Hartmann wrote: > > Am Sun, 24 Jul 2016 08:38:59 +0200 > > Gary Jennejohn schrieb: > > > > > On Sun, 24 Jul 2016 08:03:30 +0200 > > > "O. Hartmann" wrote: > > > > > > > Am Sat, 23 Jul 2016 14:49:11 -0600 > > > > Ian Lepore schrieb: > > > > > > > > > On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote: > > > > > > Am Fri, 22 Jul 2016 10:52:54 -0600 > > > > > > Ian Lepore schrieb: > > > > > > > > > > > > > On Fri, 2016-07-22 at 18:35 +0200, O. Hartmann wrote: > > > > > > > > For temperature monitoring, we have a bunch of Digi > > > > > > > > Watchport/T > > > > > > > > sensors: > > > > > > > > > > > > > > > > http://ftp1.digi.com/support/documentation/90000406_H.pdf > > > > > > > > > > > > > > > > > > > > > > > [...] > > > > > > > > > > > > > > I think the attached patch will make it show up as a > > > > > > > ttyU*/cuaU* > > > > > > > device > > > > > > > for you. (You should probably use the /dev/cuaU* flavor, > > > > > > > to avoid > > > > > > > problems with tty layer and modem control signals). > > > > > > > > > > > > > > I keep wishing we had a mechanism, like a sysctl that could > > > > > > > be set > > > > > > > or > > > > > > > something, that would let you supply a vendor/product pair > > > > > > > and have > > > > > > > the > > > > > > > ugensa driver attach to that device, for quick testing of > > > > > > > this sort > > > > > > > of > > > > > > > thing. > > > > > > > > > > > > > > -- Ian > > > > > > > > > > > > No, it doesn't change anything. I applied the patch to most > > > > > > recent > > > > > > CURRENT and it is > > > > > > still the same. But thanks anyway. > > > > > > > > > > > > Kind regards, > > > > > > > > > > > > oh > > > > > > > > > > Oh, my bad, I forgot to mention: You'll have to manually > > > > > "kldload > > > > > ugensa" before plugging in the device (or load it from your > > > > > loader.conf). > > > > > > > > > > When the change gets committed (assuming it works), the devd > > > > > usb > > > > > scripts will get regenerated, and that's what handles the auto > > > > > -load of > > > > > the driver. > > > > > > > > > > -- Ian > > > > man ugensa doesn't exist! As I wrote earlier, I tried everything > > > > to load what I could > > > > find. It seems, the patch and the hint about ugensa.ko did the > > > > magic ;-) Thank you > > > > very much! Could the patch be made permanent to FreeBSD CURRENT? > > > > > > > > And also important: where is the man page for ugensa? Can the the > > > > module be compiled > > > > staitcally into the kernel or are there pitfalls? > > > > > > > > > > Even the most complete man page found in the internet, the one from > > > Dragonfly, doesn't list your Digi International device as being one > > > of those supported. > > > > Yes. That is a pity. But Linux seems to operate this serial device. I > > have to check next > > time I get hands on a Linux box, what driver is attached to the > > sensor. > > > > > > > > Still, having the man page under FreeBSD would at least provide a > > > hint > > > that the driver even exists. > > > > Agreed. > > > > > > > > I added device ugensa to my config file and the kernel was > > > generated > > > without an error. > > > > Me, too. > > > > > > > > > root@localhost: [src] kldload ugensa > > > > > > > > ugen2.7: at usbus2 > > > > ugensa0: > > > > on usbus2 > > > > ugensa0: Found 1 interfaces. > > > > root@thor: [src] man ugensa > > > > No manual entry for ugensa > > > > root@localhost: [src] ll /dev/cuaU0* > > > > 203 crw-rw---- 1 uucp dialer - 0xcb Jul 24 07:51 /dev/cuaU0 > > > > 204 crw-rw---- 1 uucp dialer - 0xcc Jul 24 07:51 > > > > /dev/cuaU0.init > > > > 205 crw-rw---- 1 uucp dialer - 0xcd Jul 24 07:51 > > > > /dev/cuaU0.lock > > > > > > > > > > > > I'll try now to get informations out of the device, I let you > > > > know whether that is a > > > > success. But anyway, again, thank you for helping making the > > > > device visible and > > > > available. > > > > > > > > > I had no luck with retrieving informations out of the device by the > > Perl5 script provided > > by Nagios.org. A prerequisite for the Perl script is the FreeBSD port > > > > comms/p5-Device-SerialPort > > > > Patching the script is trivial, but I do not know whether the > > backend, > > comms/p5-Device-SerialPort, works a sexpected. So the first, dirty, > > trial ended up in > > nothing - since the information gained from the sensor is an empty > > string/nothing. > > > > I'm not familiar with serial devices, so far, so probably there is > > something trivial > > missing. > > I looked around for some info on these Watchport devices. Their manual > indicates that they use both serial comms to send commands and receive > data, and they use serial-comms modem control signals (RTS/CTS, DTR, > etc). Some googling makes it look like they use a TI 5052 USB serial > chip. On linux, that would be handled by the io_ti USB serial driver. > > All of that adds up to the freebsd ugensa driver (which is "generic > serial IO") probably not working. The ugensa driver has nothing chip > -specific in it, it's for accessing devices which can do bulk > read/write without needing to configure any of the other serial comms > parameters. The ugensa driver works with things like gps receivers > that have simple text-only interfaces. > > I think these watchport devices will likely need real serial comms > configuration -- baud rate at least, to even be able to talk to them. > In other words, freebsd needs a real driver for TI 5052 chips. It > looks like a fairly complete datasheet for the chip is available (but I > don't have time to write a driver myself). > > -- Ian > There are several different USB serial drivers. Off-hand I see ubser, ubsa, uchcom, ucom, ucycom, uftdi, ubgensa, umcs, umct, umoscom, uplcom, usb_serial, uslcom, and uvscom. Whether any of these will support the TI chip, I can't say. Most have man pages, but a few, as has been noted, are lacking one. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-usb@freebsd.org Sun Jul 24 18:52:42 2016 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 C1C79BA1CF1 for ; Sun, 24 Jul 2016 18:52:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 828FA1191 for ; Sun, 24 Jul 2016 18:52:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22d.google.com with SMTP id q83so145346687iod.1 for ; Sun, 24 Jul 2016 11:52:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=fHQWafWE/nnTQWULDBYQjyFAEVeOII5E0Vgdr2Ho+Qw=; b=X6JSAqbgMWgHRdsNhWh/hZDru7zEkcdw5mQitPQPQstHspnSKDC8vbIcBgLEL3ZSDT F/DzdlZ0ZVQNFW/o37xkxUN3khKoCTup2/siiCdp/B4b8YCFpdZduT68TwCBTG7s4xr1 nOtx+CEZh0AZbujLdjWA+q13Gzyd2NrGwDhZAqoA2Tit1l+Dy0jMyHI+2uef1+Xtzpyz nbFyAybUTbP5Tx7TElMNfELDz/FLJoo54Bn3r4WAy4iy2dXZ+uSBFEtI2+GntT+AwjHH 9okNZDvOrdbJxdWkdZjELdMSQHDP2Ac0eJqB8lN1Cabx9IcgsLMZgFHsjug6x9EHJvHj Ev/w== 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:from :date:message-id:subject:to:cc; bh=fHQWafWE/nnTQWULDBYQjyFAEVeOII5E0Vgdr2Ho+Qw=; b=VO9ZdDfhVn7QLlubNeZf0Vpi5Fs7UMazG8oHV000SUel6JNU47U2yE8il2TWrPTNOj euC8FhPffMpypKKbN2kSyq0lzqLulKjiA+0+OEkvWFNaZM8jGui7gY8QY0LkKlZcyUM5 dJdeltMSlDJwRvfn3ZrPQdVOE20mT1eihhnTxisBmWAgYA8uT6eRtB4lCsEhtumEPQID CUAbWGssU97GnQ+2AYz+HC6Jx6gDfu3iXNg7GJFcuBHAw91ZVYboFg0x0/xPAi1/wo66 jpz3RB2ODl+iQGZPP0XSogTDhFi6zZXhaR8mLQxjiy1U0Bmfl60mHZ8/0iHUp+JQiv5H gikw== X-Gm-Message-State: AEkoouuGOJGafVaLOUGY8P9/vtxUl11PJlsLgBoEdXldCWFLg+C/HxTU+YmMysPBzYulDGciKT2ICmASAw7njg== X-Received: by 10.107.40.133 with SMTP id o127mr15931566ioo.183.1469386361825; Sun, 24 Jul 2016 11:52:41 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.137.131 with HTTP; Sun, 24 Jul 2016 11:52:41 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> <20160724083859.4c0dd392@ernst.home> <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> <1469379334.84197.40.camel@freebsd.org> From: Warner Losh Date: Sun, 24 Jul 2016 12:52:41 -0600 X-Google-Sender-Auth: Xf-fUTjYm0fb7Ps7eK1otRDjVSM Message-ID: Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU To: Kevin Oberman Cc: Ian Lepore , FreeBSD CURRENT , "O. Hartmann" , "freebsd-usb@FreeBSD.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 18:52:42 -0000 On Sun, Jul 24, 2016 at 12:42 PM, Kevin Oberman wrote: > There are several different USB serial drivers. Off-hand I see ubser, ubsa, > uchcom, ucom, ucycom, uftdi, ubgensa, umcs, umct, umoscom, uplcom, > usb_serial, uslcom, and uvscom. Whether any of these will support the TI > chip, I can't say. Most have man pages, but a few, as has been noted, are > lacking one. I tried to automate discovery of these things. However, the only way you can really know for sure about the TI chip is to read it's datasheet and compare that with extant drivers. It's actually easier than it sounds. I've often thought of unification of the TTY USB drivers, since they are most (but not all) based on the standard plus extra bits. Warner From owner-freebsd-usb@freebsd.org Sun Jul 24 19:12:39 2016 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 0B8A6BA2131 for ; Sun, 24 Jul 2016 19:12:39 +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 DC05E1957 for ; Sun, 24 Jul 2016 19:12:38 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: b6b52ae4-51d2-11e6-a0ff-e511cd071b9b X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Sun, 24 Jul 2016 19:13:32 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u6OJCZ5e014060; Sun, 24 Jul 2016 13:12:35 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1469387555.84197.48.camel@freebsd.org> Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU From: Ian Lepore To: Warner Losh , Kevin Oberman Cc: FreeBSD CURRENT , "O. Hartmann" , "freebsd-usb@FreeBSD.org" Date: Sun, 24 Jul 2016 13:12:35 -0600 In-Reply-To: References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> <20160724083859.4c0dd392@ernst.home> <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> <1469379334.84197.40.camel@freebsd.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 19:12:39 -0000 On Sun, 2016-07-24 at 12:52 -0600, Warner Losh wrote: > On Sun, Jul 24, 2016 at 12:42 PM, Kevin Oberman > wrote: > > There are several different USB serial drivers. Off-hand I see > > ubser, ubsa, > > uchcom, ucom, ucycom, uftdi, ubgensa, umcs, umct, umoscom, uplcom, > > usb_serial, uslcom, and uvscom. Whether any of these will support > > the TI > > chip, I can't say. Most have man pages, but a few, as has been > > noted, are > > lacking one. > > I tried to automate discovery of these things. However, the only way > you can really know for sure about the TI chip is to read it's > datasheet > and compare that with extant drivers. It's actually easier than it > sounds. > > I've often thought of unification of the TTY USB drivers, since they > are > most (but not all) based on the standard plus extra bits. > > Warner To reiterate: we do not have a driver for TI 5052 chips. It's not much like other usb-serial chips. In fact it's not strictly a usb-serial chip, it's a multifunction chip that includes a software -controllable usb hub, 2 serial ports, gpio, an i2c bus master, an MCU interface, a multichannel DMA controller, and apparently even has the ability to download your own 8052-compatible microcontroller code into the 5052 and have it take over from the built-in rom code. It would be reasonable enough to write a driver that initially supported only the uart part of the chip. -- Ian From owner-freebsd-usb@freebsd.org Tue Jul 26 01:07:02 2016 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 0F81ABA3BFF for ; Tue, 26 Jul 2016 01:07:02 +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 F3A1611A4 for ; Tue, 26 Jul 2016 01:07:01 +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 u6Q171uO000334 for ; Tue, 26 Jul 2016 01:07:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 208791] USB audio playback issue Date: Tue, 26 Jul 2016 01:07:02 +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 Only Me X-Bugzilla-Who: alex@inferiorhumanorgans.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: 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.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2016 01:07:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208791 --- Comment #2 from alex@inferiorhumanorgans.com --- With this kernel: FreeBSD bloaty 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4 #0: Sat May 28 12:23= :44 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERI= C=20 amd64 And hw.snd.verbose=3D4 I see: pcm3: WARNING: PCMDIR_PLAY DMA completion too fast/slow ! hwptr=3D0, old=3D0 delta=3D0 amt=3D0 ready=3D4236 free=3D0 With hw.usb.uaudio.debug=3D15 I see: uaudio_chan_play_sync_callback: Comparing 44149 Hz :: 44100 Hz This doesn't appear to vary, and has appeared consistent with the 10.3 kern= els. The same hardware worked without fault in 9.x. Sorry for the delay, but t= his machine is unsuitable for audio playback currently so I've not tried in a while. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Wed Jul 27 14:57:07 2016 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 A1677BA6E8A for ; Wed, 27 Jul 2016 14:57:07 +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 9176C16F2 for ; Wed, 27 Jul 2016 14:57:07 +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 u6REv7mh081145 for ; Wed, 27 Jul 2016 14:57:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 208791] USB audio playback issue Date: Wed, 27 Jul 2016 14:57:07 +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 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.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2016 14:57:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208791 --- Comment #3 from Hans Petter Selasky --- Hi, Do you have a link where such a device can be bought? Used or new? There has been updates in the USB audio driver which might have broken your device, but fixed others. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.=