Date: Wed, 19 Jan 2005 07:08:41 +1100 (EST) From: Dave Horsfall <dave@horsfall.org> To: FreeBSD STABLE list <freebsd-stable@freebsd.org>, freebsd-current@freebsd.org Subject: Re: strange ucom (uplcom) error Message-ID: <Pine.BSI.4.61.0501190701140.14586@dave.horsfall.org> In-Reply-To: <20050118151707.GA26651@nas.dgap.mipt.ru> References: <200501181306.49120.emanuel.strobl@gmx.net> <20050118151707.GA26651@nas.dgap.mipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 Jan 2005, Andrew L. Neporada wrote: > > The not working (more expensive) one gets recognized as ucom0 and I have > > ucom0, also I can receive signal but not transmit. > > > [skip] > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > It can break old (working) PL2303 chip, but it works for me with newer > revision chip (tested under 4.10). Hmmm... That could explain something I saw. I've got two cables, bought from different vendors (same chipset). Both worked under 4.10, only one under 5.3 (different platforms). I'll try it when I get a moment. -- Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.61.0501190701140.14586>