From owner-freebsd-bugs@FreeBSD.ORG Tue May 10 00:50:10 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0DD61065679 for ; Tue, 10 May 2011 00:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 97CE28FC1A for ; Tue, 10 May 2011 00:50:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4A0o7HC018617 for ; Tue, 10 May 2011 00:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4A0o7Mi018616; Tue, 10 May 2011 00:50:07 GMT (envelope-from gnats) Date: Tue, 10 May 2011 00:50:07 GMT Message-Id: <201105100050.p4A0o7Mi018616@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Craig Leres Cc: Subject: Re: kern/147583: [puc] [patch] sys/dev/puc/pucdata.c: incorrect clock value for Oxford OX16PCI954 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Craig Leres List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2011 00:50:13 -0000 The following reply was made to PR kern/147583; it has been noted by GNATS. From: Craig Leres To: John Baldwin Cc: bug-followup@freebsd.org Subject: Re: kern/147583: [puc] [patch] sys/dev/puc/pucdata.c: incorrect clock value for Oxford OX16PCI954 Date: Mon, 09 May 2011 17:48:34 -0700 On 05/03/11 05:17, John Baldwin wrote: > Can you add some printfs to that to verify that that is failing > and what error it is returning? Might need to add some more > printfs to figure out why uart is failing to probe as well in the > uart driver. I started to add printf's to puc.c but decided it was time to get gdb over serial working again. By the time I got that set up, the puc ports were working. Anyway, I can now verify that the patch you sent me (PR: kern/147583) works: puc0: port 0x3020-0x303f,0x3000-0x301f mem 0xd0205000-0xd0205fff,0xd0204000-0xd0204fff irq 20 at device 0.0 on pci17 I connected it to one of the motherboard ports using a crossover cable and was able to send characters in both directions. Craig