From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 11:42:48 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 366E116A4CE for ; Wed, 24 Mar 2004 11:42:48 -0800 (PST) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 123F543D2F for ; Wed, 24 Mar 2004 11:42:48 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 3497 invoked from network); 24 Mar 2004 19:42:47 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 24 Mar 2004 19:42:47 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i2OJeoDP006146; Wed, 24 Mar 2004 14:42:36 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 24 Mar 2004 14:30:29 -0500 User-Agent: KMail/1.6 References: <20040323135932.L13222@carver.gumbysoft.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403241430.29558.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: othermark 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: Wed, 24 Mar 2004 19:42:48 -0000 On Tuesday 23 March 2004 05:58 pm, othermark wrote: > 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 }, The 0xfffc is a mask meaning that this matches 0x0180, 0x0181, 0x0182, and 0x0183 by the way, so you don't need an extra entry. Can you do a boot -v? I'm curious if the second device has its BAR's setup. > I still get a failure to attach after a full rebuild (is there > a safe way to do make -DNOCLEAN buildkernel?) -DNO_KERNELCLEAN I think. The variables for buildkernel are documented in either src/Makefile or src/Makefile.inc1. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org