From owner-freebsd-current@FreeBSD.ORG Tue Mar 23 14:58:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5180916A4CE for ; Tue, 23 Mar 2004 14:58:31 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4B3043D2F for ; Tue, 23 Mar 2004 14:58:30 -0800 (PST) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1B5uqr-0005CO-00 for ; Tue, 23 Mar 2004 23:58:29 +0100 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 23 Mar 2004 23:58:28 +0100 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 23 Mar 2004 23:58:28 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Tue, 23 Mar 2004 14:58:24 -0800 Lines: 40 Message-ID: References: <20040323135932.L13222@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.7.6 Sender: news Subject: Re: puc(4) device not attaching issue in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2004 22:58:31 -0000 Doug White wrote: > On Tue, 23 Mar 2004, othermark wrote: >> none0@pci0:6:1: class=0x070002 card=0x00000000 chip=0x01811407 rev=0x00 >> hdr=0x00 >> vendor = 'Lava Computer Manufacturing Inc' >> device = 'Lava Octopus PCI Ports 5-8' >> class = simple comms >> subclass = UART >> >> device 6.1 has chip 0x018111407=and pucdata.c has only has an entry >> for 0x0180, so I'm not sure how it was picking up 0x0181 in earlier >> releases, or that it still does and something else is blocking it >> from happening... > > What happens if you add that PCI ID to the driver? If I add a duplicate the entry in pucdata.c so it looks like this: /* Lava Computers Octopus-550 serial ports */ { "Lava Computers Octopus-550 8-port serial part B", NULL, { 0x1407, 0x0181, 0, 0 }, { 0xffff, 0xfffc, 0, 0 }, { { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, { PUC_PORT_TYPE_COM, 0x18, 0x00, COM_FREQ }, { PUC_PORT_TYPE_COM, 0x1c, 0x00, COM_FREQ }, }, }, I still get a failure to attach after a full rebuild (is there a safe way to do make -DNOCLEAN buildkernel?) -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired);