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