kern/124128: puc driver doesn't support VScom PCIex-800H 8-port
serial cards
Maxim Frolov
maxim.frolov.07 at gmail.com
Wed Jun 4 14:10:04 UTC 2008
The following reply was made to PR kern/124128; it has been noted by GNATS.
From: "Maxim Frolov" <maxim.frolov.07 at gmail.com>
To: "Remko Lodder" <remko at freebsd.org>
Cc: freebsd-gnats-submit at freebsd.org
Subject: Re: kern/124128: puc driver doesn't support VScom PCIex-800H 8-port serial cards
Date: Wed, 4 Jun 2008 17:39:39 +0400
------=_Part_3942_7310068.1212586779473
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hello,
I found temporary workaround for the problem. Doing dmesg after boot -v I
noticed dev=0xa007 for the 8-port card in the pci3. Here is the partial
output of the dmesg:
pci3: domain=0, physical bus=3
found-> vendor=0x14d2, dev=0xa007, revid=0x00
domain=0, bus=3, slot=0, func=0
class=07-00-06, hdrtype=0x00, mfdev=1
cmdreg=0x0003, statreg=0x0290, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=10
powerspec 1 supports D0 D2 D3 current D0
map[10]: type I/O Port, range 32, base 0x7800, size 5, enabled
Then I noticed 0xa003 and 0xa004 codes for the VScom PCI-800H card in the
pucdata.c file. Next I changed 0xa003 to 0xa007 and 0xa004 to 0xa008 in the
pucdata.c and recompiled it. After that the puc driver was successfully
attached to the card.
Generally speaking I don't understand much in what do those codes mean so
the long term solution for the problem might still be required.
Thank you.
Best regards,
Maxim
2008/5/30 Remko Lodder <remko at freebsd.org>:
> Maxim Frolov wrote:
>
> Please submit a 'boot -v' or verbose boot in the boot options,
> and a pciconf -vl.
>
> Thanks.
>
> --
>
> /"\ Best regards, | remko at FreeBSD.org
> \ / Remko Lodder | remko at EFnet
> X http://www.evilcoder.org/ |
> / \ ASCII Ribbon Campaign | Against HTML Mail and News
>
------=_Part_3942_7310068.1212586779473
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hello,<br><br>I found temporary workaround for the problem. Doing dmesg after boot -v I noticed dev=0xa007 for the 8-port card in the pci3. Here is the partial output of the dmesg:<br><br>pci3: domain=0, physical bus=3<br>
found-> vendor=0x14d2, dev=0xa007, revid=0x00<br> domain=0, bus=3, slot=0, func=0<br> class=07-00-06, hdrtype=0x00, mfdev=1<br> cmdreg=0x0003, statreg=0x0290, cachelnsz=0 (dwords)<br> lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)<br>
intpin=a, irq=10<br> powerspec 1 supports D0 D2 D3 current D0<br> map[10]: type I/O Port, range 32, base 0x7800, size 5, enabled<br><br>Then I noticed 0xa003 and 0xa004 codes for the VScom PCI-800H card in the pucdata.c file. Next I changed 0xa003 to 0xa007 and 0xa004 to 0xa008 in the pucdata.c and recompiled it. After that the puc driver was successfully attached to the card.<br>
<br>Generally speaking I don't understand much in what do those codes mean so the long term solution for the problem might still be required.<br><br>Thank you.<br><br>Best regards,<br>Maxim<br><br><div class="gmail_quote">
2008/5/30 Remko Lodder <<a href="mailto:remko at freebsd.org">remko at freebsd.org</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Maxim Frolov wrote:<br>
<br>
Please submit a 'boot -v' or verbose boot in the boot options,<br>
and a pciconf -vl.<br>
<br>
Thanks.<br><font color="#888888">
<br>
-- <br>
<br>
/"\ Best regards, | remko at FreeBSD.org<br>
\ / Remko Lodder | remko at EFnet<br>
X <a href="http://www.evilcoder.org/" target="_blank">http://www.evilcoder.org/</a> |<br>
/ \ ASCII Ribbon Campaign | Against HTML Mail and News<br>
</font></blockquote></div><br>
------=_Part_3942_7310068.1212586779473--
More information about the freebsd-bugs
mailing list