> Hi!
>
> > uart is the new thing. sio info should be ignored.
> >
> > Chances are good that this device doesn't have the proper entries in the
> > puc driver. Do you have any pci devices that show up as unclaimed?
>
> In a different box, I got this:
>
> none1@pci0:7:4:0: class=0x070002 card=0x000814a1 chip=0x000814a1
> rev=0xb0 hdr=0x00
> vendor = 'Systembase Co Ltd'
> class = simple comms
> subclass = UART
> bar [10] = type I/O Port, range 32, base 0x1040, size 64, enabled
> bar [14] = type I/O Port, range 32, base 0x1000, size 64, enabled
>
> and:
>
> pcib7@pci0:6:0:0: class=0x060400 card=0x00000000 chip=0x10801b21
> rev=0x04 hdr=0x01
> vendor = 'ASMedia Technology Inc.'
> device = 'ASM1083/1085 PCIe to PCI Bridge'
> class = bridge
> subclass = PCI-PCI
>
> The chips on the card are:
>
> ASMedia asm1083 b0bk4911b3 1543 (?)
> SystemBase SB16C1058PCI 1624
>
> It only detects four (or six?) serials...
Are perhaps 2 of them being consumed by sio?
>
> So I think I found a 'somehow' working setup and have to add stuff to
> sys/dev/puc/pucdata.c to match it. Thanks for the pointer!
Ok, heading in the right direction, try
pciconf -lB
that should show the hierarchy with the simple comms connected
behind the pci-pci bridge. More readable without the -v your
using above.
Please do post the complete output of exactly:
pciconf -lB
--
Rod Grimes rgri...@freebsd.org
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
