From owner-freebsd-current@FreeBSD.ORG  Tue Jan 18 20:08:47 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D502016A4CE; Tue, 18 Jan 2005 20:08:47 +0000 (GMT)
Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 43BB543D1D; Tue, 18 Jan 2005 20:08:45 +0000 (GMT)
	(envelope-from dave@horsfall.org)
Received: from localhost (dave@localhost)
	by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id j0IK8gt16746;
	Wed, 19 Jan 2005 07:08:42 +1100 (EST)
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
In-Reply-To: <20050118151707.GA26651@nas.dgap.mipt.ru>
Message-ID: <Pine.BSI.4.61.0501190701140.14586@dave.horsfall.org>
References: <200501181306.49120.emanuel.strobl@gmx.net>
 <20050118151707.GA26651@nas.dgap.mipt.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 19 Jan 2005 13:22:32 +0000
Subject: Re: strange ucom (uplcom) error
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2005 20:08:48 -0000

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