From owner-freebsd-current@FreeBSD.ORG  Tue Mar 23 13:59:56 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B3FE016A4FE
	for <freebsd-current@freebsd.org>;
	Tue, 23 Mar 2004 13:59:56 -0800 (PST)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8222A43D1D
	for <freebsd-current@freebsd.org>;
	Tue, 23 Mar 2004 13:59:56 -0800 (PST)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 77A6972DCB; Tue, 23 Mar 2004 13:59:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 72B9272DB5; Tue, 23 Mar 2004 13:59:56 -0800 (PST)
Date: Tue, 23 Mar 2004 13:59:56 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: othermark <atkin901@yahoo.com>
In-Reply-To: <c3qbq4$s0n$1@sea.gmane.org>
Message-ID: <20040323135932.L13222@carver.gumbysoft.com>
References: <c3qbq4$s0n$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2004 21:59:56 -0000

On Tue, 23 Mar 2004, othermark wrote:

> that it was working in 4.7-RELEASE, with the same entry in pucdata.c
>
> I note that:
> puc0@pci0:6:0:  class=0x070002 card=0x00000000 chip=0x01801407 rev=0x00
> hdr=0x00
>     vendor   = 'Lava Computer Manufacturing Inc'
>     device   = 'Lava Octopus PCI Ports 1-4'
>     class    = simple comms
>     subclass = UART
> 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?

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org