Date: Tue, 5 Jun 2018 08:02:32 -0400 From: Ian FREISLICH <ian.freislich@capeaugusta.com> To: freebsd-usb@freebsd.org, FreeBSD Current <freebsd-current@FreeBSD.org> Cc: freebsd-stable List <freebsd-stable@FreeBSD.org> Subject: Re: uchcom update Message-ID: <83f7a6dd-5d7e-cfd2-e580-4db0c7134220@capeaugusta.com> In-Reply-To: <eb56d9bc-a915-fa56-d1c2-b24cc30c8aa2@FreeBSD.org> References: <eb56d9bc-a915-fa56-d1c2-b24cc30c8aa2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/22/2018 09:44 AM, Andriy Gapon wrote: > Yesterday I committed some changes to uchcom (so far, only in CURRENT). > Commits are r333997 - r334002. > > If you have a CH340/341 based USB<->RS232 adapter and it works for you, could > you please test that it still does? > If you tried your adapter in the past and it did not work, there is a chance it > might start working now. Could you please test that as well? ugen5.4: <vendor 0x1a86 USB2.0-Serial> at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (96mA) ugen5.4.0: uchcom0: <vendor 0x1a86 USB2.0-Serial, rev 1.10/2.54, addr 3> It's not made it any worse. I'm not using this adapter by choice - it's a USB to Maxim (Dallas) one-wire bus adapter. The manual used to state that these are possibly the worst chips ever. Is that still the prevailing opinion? Ian --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83f7a6dd-5d7e-cfd2-e580-4db0c7134220>