From owner-freebsd-stable@FreeBSD.ORG  Tue Aug 16 09:25:41 2011
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E5C7D106566C
	for <freebsd-stable@freebsd.org>; Tue, 16 Aug 2011 09:25:41 +0000 (UTC)
	(envelope-from yuri@rawbw.com)
Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45])
	by mx1.freebsd.org (Postfix) with ESMTP id CF8A88FC0C
	for <freebsd-stable@freebsd.org>; Tue, 16 Aug 2011 09:25:41 +0000 (UTC)
Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1])
	(authenticated bits=0)
	by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id p7G9PSsK061099;
	Tue, 16 Aug 2011 02:25:29 -0700 (PDT) (envelope-from yuri@rawbw.com)
Message-ID: <4E4A3788.3030605@rawbw.com>
Date: Tue, 16 Aug 2011 02:25:28 -0700
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:5.0) Gecko/20110716 Thunderbird/5.0
MIME-Version: 1.0
To: d@delphij.net
References: <4E4A0C81.7020501@rawbw.com> <4E4A20BE.3060603@delphij.net>
In-Reply-To: <4E4A20BE.3060603@delphij.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org, Xin LI <delphij@delphij.net>
Subject: Re: How to use unrecognized COM port card?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 09:25:42 -0000

On 08/16/2011 00:48, Xin LI wrote:
> A wild guess...  (You gotta to provide more details rather than just PCI
> IDs).
>
> My guess is that it's using these chips:
>
> http://www.winchiphead.com/product/ch365detail.htm
> http://www.winchiphead.com/product/ch353detail.htm
>
> It didn't talked about possible cards' configuration so I used BAR0,
> which could be 0x14, 0x18, etc.

Actually, the main chip there is CH352L. Plus there are two more chips 
ST75185C, one per COM port.

Your patch made this pci device to connect to uart driver: uart2@pci0:8:1:0.

uart2: <16550 or compatible> port 0xe880-0xe887,0xe800-0xe807 irq 17 at 
device 1.0 on pci8
uart2: [FILTER]

Also new devices showed up:
/dev/cuau2
/dev/cuau2.init
/dev/cuau2.lock
/dev/ttyu2
/dev/ttyu2.init
/dev/ttyu2.lock

cuau2 is probably the same as COM port. I don't have an easy way to 
check now.
I believe adding another entry with 0x14 would add the second COM port.

Thank you!
Yuri