Date: Wed, 24 Mar 2004 14:30:29 -0500 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-current@freebsd.org Cc: othermark <atkin901@yahoo.com> Subject: Re: puc(4) device not attaching issue in -current Message-ID: <200403241430.29558.jhb@FreeBSD.org> In-Reply-To: <c3qfeh$ce$1@sea.gmane.org> References: <c3qbq4$s0n$1@sea.gmane.org> <20040323135932.L13222@carver.gumbysoft.com> <c3qfeh$ce$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403241430.29558.jhb>