From owner-freebsd-i386@FreeBSD.ORG Sat Nov 18 18:16:09 2006 Return-Path: X-Original-To: freebsd-i386@hub.freebsd.org Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01B3E16A8BA for ; Sat, 18 Nov 2006 18:16:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7641644306 for ; Sat, 18 Nov 2006 18:10:37 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kAIIAQMr086697 for ; Sat, 18 Nov 2006 18:10:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kAIIAQHO086694; Sat, 18 Nov 2006 18:10:26 GMT (envelope-from gnats) Date: Sat, 18 Nov 2006 18:10:26 GMT Message-Id: <200611181810.kAIIAQHO086694@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Marcel Moolenaar Cc: Subject: Re: i386/105616: UART PCI device just silent... X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcel Moolenaar List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2006 18:16:09 -0000 The following reply was made to PR i386/105616; it has been noted by GNATS. From: Marcel Moolenaar To: Helge Oldach Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: i386/105616: UART PCI device just silent... Date: Sat, 18 Nov 2006 09:47:39 -0800 On Nov 16, 2006, at 12:46 PM, Helge Oldach wrote: > --- sys/dev/uart/uart_bus_pci.c.ctm Wed Aug 2 16:24:19 2006 > +++ sys/dev/uart/uart_bus_pci.c Wed Nov 15 10:18:56 2006 > @@ -101,6 +101,8 @@ > 8 * DEFAULT_RCLK }, > { 0x1409, 0x7168, 0x1409, 0x4028, "Timedia Technology Serial > Port", 0x10, > 8 * DEFAULT_RCLK }, > +{ 0x1409, 0x7168, 0x1409, 0x4037, "Timedia Technology Serial > Port", 0x10, > + 8 * DEFAULT_RCLK }, > { 0x1409, 0x7168, 0x1409, 0x5025, "Timedia Technology Serial > Port", 0x10, > 8 * DEFAULT_RCLK }, > { 0x1409, 0x7168, 0x1409, 0x5027, "Timedia Technology Serial > Port", 0x10, > The patch is not right. The PCI device you talk about is a *dual* serial I/O card. As such, puc(4) needs to attach to it, not uart(4). Adding the PCI ids to uart(4) will only cause a conflict, not to mention that if uart(4) attaches, it only attaches to the first. However, the patch shows that the clock on these cards is 8 times the default clock. I think that is why puc(4)+uart(4) doesn't work. If you select a baudrate that 8 times lower than what you know the baudrate should be, then you should be able to transmit and receive data. If that's the case, then puc(4) needs to be fixed to have the correct clock value for these boards. Note also that I have not heard of uart(4) being wrong in classifying the type as 16550, 1660 or otherwise. FYI, -- Marcel Moolenaar xcllnt@mac.com