Timeda 8-multiport adapter: only 2 ports available
bsam at ipt.ru
Wed Dec 10 16:19:44 UTC 2008
Eygene Ryabinkin <rea-fbsd at codelabs.ru> writes:
> Boris, good day.
> Wed, Dec 10, 2008 at 05:13:48PM +0300, Boris Samorodov wrote:
>> Boris Samorodov <bsam at ipt.ru> writes:
>> > I've got a Sunix PCI Serial 8-channel Multiport adapter (Timedia chipset):
>> > -----
>> > puc0 at pci0:5:2:0: class=0x070002 card=0x40661409 chip=0x71681409 rev=0x01 hdr=0x00
>> > vendor = 'Timedia Technology Co Ltd'
>> > device = '40371409 PCI / ISA Asynchronous UART Signal Chips Solution'
>> Actually the card is 4066, while 4037 (according to pucdata.c) is indeed
>> a dual-port card. May be the card is wrongly interpreted by the OS?
> pciconf just don't know about 4066, so is prints what it has in the
> database. This is irrelevant to the driver -- it discovers the correct
> chip with 8 ports:
>> > puc0: <Timedia technology 8 Port Serial> port 0xec00-0xec1f,0xe880-0xe88f,0xe800-0xe807,0xe480-0xe487,0xe400-0xe407,0xe080-0xe087 irq 18 at device 2.0 on pci5
>> > puc0: Reserved 0x20 bytes for rid 0x10 type 4 at 0xec00
>> > puc0: Reserved 0x10 bytes for rid 0x14 type 4 at 0xe880
>> > puc0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xe800
>> > puc0: Reserved 0x8 bytes for rid 0x1c type 4 at 0xe480
>> > puc0: Reserved 0x8 bytes for rid 0x20 type 4 at 0xe400
>> > puc0: Reserved 0x8 bytes for rid 0x24 type 4 at 0xe080
>> > puc0: [FILTER]
>> > uart4: <16550 or compatible> on puc0
>> > uart4: [FILTER]
>> > uart4: fast interrupt
>> > uart5: <16550 or compatible> on puc0
>> > uart5: [FILTER]
>> > uart5: fast interrupt
>> > -----
> Judging by this output, the 6 ports that got their reservations at
> dev/pci/pci.c are the ones that aren't recognized by uart. You may need
Thanks for your explanation.
> to add trace printfs to uart_puc_probe (uart_bus_puc.c) and to
> uart_bus_probe (uart_core.c), just around the register resource
> allocator. This should show what devices are passed to the probe
> routines and which are rejected. Be sure to include 'rid' values to
> your debug output to get the idea what ports we're speaking about.
I wish I can. :-( Can you give me an example / forward to howto or like?
BTW, our mailservers don't like each other:
2008-12-10 18:39:07 1LAR9W-000Ka0-VK H=0.mx.codelabs.ru [18.104.22.168] sender verify fail for <rea-fbsd at codelabs.ru>: response to "MAIL FROM:<>" from 0.mx.codelabs.ru [22.214.171.124] was: 550 failed
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
More information about the freebsd-current