From owner-freebsd-i386@FreeBSD.ORG Tue Nov 28 20:31:32 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 B250316A4D2 for ; Tue, 28 Nov 2006 20:31:32 +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 D99E843CD3 for ; Tue, 28 Nov 2006 20:30:44 +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 kASKUKGE001483 for ; Tue, 28 Nov 2006 20:30:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kASKUKjO001481; Tue, 28 Nov 2006 20:30:20 GMT (envelope-from gnats) Date: Tue, 28 Nov 2006 20:30:20 GMT Message-Id: <200611282030.kASKUKjO001481@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: puc-uart@oldach.net (Helge Oldach) 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: Helge Oldach List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2006 20:31:32 -0000 The following reply was made to PR i386/105616; it has been noted by GNATS. From: puc-uart@oldach.net (Helge Oldach) To: xcllnt@mac.com (Marcel Moolenaar) Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: i386/105616: UART PCI device just silent... Date: Tue, 28 Nov 2006 21:14:19 +0100 (CET) Hi Marcel, >> The only thing that may be botched is speed, or potentially also >> parity or stop bits. >It's definitely an odd failure mode. What happens if you wire one of >the UART ports on the PCI card to one of the "legacy" on-board serial >ports? Could you try both the PCI UARTs? I did. What happens is that single, typed-in characters don't make to the remote, while files piped to the remote via ~>file appear as garbage. The garbage contains a lot of 0xff characters. So there *is* some sort of communication in place. It doesn't matter whether I send on the puc uart or the on-board uart. It also doesn't make too much difference if I play with the transmit and receive speeds. This all points into the direction of speed (parity, stopbits) mismatch. Going to extremes: When I set the puc UART to 1200 bps and the on-board to 115200, I constantly receive a 0xff on the on-board for any arbitrary character typed on the puc uart. But there is silence the other way 'round. There is no difference between the two puc/uart ports. Garbage either way, but at least there is communication on both ports. So IO ports and IRQ are likely correct. Any further ideas? Is there a simple means to measure the actual speed? Helge