Date: Tue, 23 Mar 2004 13:59:56 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: othermark <atkin901@yahoo.com> Cc: freebsd-current@freebsd.org Subject: Re: puc(4) device not attaching issue in -current Message-ID: <20040323135932.L13222@carver.gumbysoft.com> In-Reply-To: <c3qbq4$s0n$1@sea.gmane.org> References: <c3qbq4$s0n$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040323135932.L13222>