From owner-freebsd-stable@FreeBSD.ORG Wed Aug 17 01:24:11 2011 Return-Path: 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 C9965106566C for ; Wed, 17 Aug 2011 01:24:11 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from midgard.transactionware.com (mail2.transactionware.com [203.14.245.36]) by mx1.freebsd.org (Postfix) with SMTP id 3173F8FC13 for ; Wed, 17 Aug 2011 01:24:10 +0000 (UTC) Received: (qmail 65962 invoked by uid 907); 17 Aug 2011 01:24:09 -0000 Received: from jmmacpro.transactionware.com (HELO jmmacpro.transactionware.com) (192.168.1.33) by midgard.transactionware.com (qpsmtpd/0.82) with ESMTP; Wed, 17 Aug 2011 11:24:09 +1000 Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-1 From: Jan Mikkelsen In-Reply-To: <4E4AD9B6.2030001@rawbw.com> Date: Wed, 17 Aug 2011 11:24:09 +1000 Content-Transfer-Encoding: quoted-printable Message-Id: <16D60EA7-85C7-486D-A722-50299407DC69@transactionware.com> References: <4E4A0C81.7020501@rawbw.com> <4E4A20BE.3060603@delphij.net> <4E4A3788.3030605@rawbw.com> <201108161157.20890.jhb@freebsd.org> <4E4ACAAD.3030506@rawbw.com> <4E4AD50E.6050906@delphij.net> <4E4AD9B6.2030001@rawbw.com> To: Yuri X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-stable@freebsd.org, d@delphij.net, John Baldwin , Xin LI 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2011 01:24:11 -0000 On 17/08/2011, at 6:57 AM, Yuri wrote: > On 08/16/2011 13:37, Xin LI wrote: >> And I think John's patch is right, I've added a new PCI ID for it >> though, found from the datasheet. Did you have uart(4) in your = kernel >> (remove my old patch)? >=20 > Yes, uart(4) is in kernel and puc(4) is the loaded module. I think = this might be a problem that puc(4) is a module loaded later and that's = why serial device isn't registered. I found the reference to the similar = situation with some other card that got cured when puc(4) was compiled = into kernel. = (http://www.adras.com/Quadtech-DSC-100-PCI-dual-serial-port-on-8-0R-i386.t= 6999-79.html) >=20 > I have yet to try building puc(4) into kernel, but the way how I have = it now is the default in GENERIC. Should uart(4) instead be removed from = kernel and made loadable too to prevent such initialization order issue? = Or what would be the right fix? Have too much stuff in kernel isn't = right too. uart probably isn't used by 99% of users. For my recent Moxa 2 port serial card addition, I had to include puc in = the kernel config; it didn't work as a module. Jan.