Date: Sun, 24 Jul 2016 08:03:30 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-usb@freebsd.org, FreeBSD CURRENT <freebsd-current@freebsd.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <ian@freebsd.org> schrieb: > On Sat, 2016-07-23 at 22:04 +0200, O. Hartmann wrote: > > Am Fri, 22 Jul 2016 10:52:54 -0600 > > Ian Lepore <ian@freebsd.org> 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: <Digi International> at usbus2 ugensa0: <Digi International WatchportT, rev 1.10/1.00, addr 7> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160724080330.3a27e875.ohartman>