public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Bergeron <chris@pcburn.com>
To: linux-kernel@vger.kernel.org
Subject: Syba 8-Port Serial Card Unidentified By Kernel
Date: Fri, 05 Oct 2007 17:31:05 -0400	[thread overview]
Message-ID: <4706AD19.4040605@pcburn.com> (raw)

Hello all,

I've just installed a multiport serial card released by an outfit called 
Syba.  This is an 8 port serial-only card with an Octopus style breakout 
cable.  The main chipset on it is an ITE IT8871F.

I've got two questions on this: Is there a driver I should try force 
loading on it (and if so, what options to use)?  and is there any useful 
testing I can do to report back to the LKML on this card?

Thanks for your time, diagnostic output follows.
-- Chris

The following comes up from an "lspci -vv"

01:06.0 Serial controller: PLX Technology, Inc. Unknown device 9016 (rev 
01) (prog-if 02 [16550])
        Subsystem: Unknown device 544e:0008
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 16
        Region 0: I/O ports at a000 [size=64]
        Region 1: I/O ports at a400 [size=16]
        Region 2: I/O ports at a800 [size=16]
        Region 3: Memory at f5000000 (32-bit, non-prefetchable) [size=4K]
        Region 4: Memory at f5001000 (32-bit, non-prefetchable) [size=4K]
        Region 5: Memory at f5002000 (32-bit, non-prefetchable) [size=4K]

and "lshw" outputs:

        *-communication UNCLAIMED
             description: Serial controller
             product: PLX Technology, Inc.
             vendor: PLX Technology, Inc.
             physical id: 6
             bus info: pci@0000:01:06.0
             version: 01
             width: 32 bits
             clock: 33MHz
             capabilities: 16550
             configuration: latency=0


             reply	other threads:[~2007-10-05 21:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 21:31 Chris Bergeron [this message]
2007-10-05 22:43 ` Syba 8-Port Serial Card Unidentified By Kernel Nicholas Miell
2007-10-09 18:14 ` Lennart Sorensen
2007-10-09 19:25   ` Chris Bergeron
2007-10-10  9:54 ` Andrey Panin
2007-10-11 17:02   ` Chris Bergeron
2007-10-11 19:01     ` Lennart Sorensen
2007-10-11 20:48       ` Chris Bergeron
2007-10-12 12:08     ` Andrey Panin
2007-10-16 19:03       ` Chris Bergeron
2007-10-17  6:42         ` Andrey Panin
2007-10-17 22:16           ` Chris Bergeron
2007-10-18  5:57             ` Andrey Panin
2007-10-18 17:00               ` Chris Bergeron
2007-10-22 15:33                 ` Andrey Panin
2007-10-22 16:18                   ` Lennart Sorensen
2007-10-26 11:35                     ` Andrey Panin
2007-10-22 17:14                   ` Chris Bergeron
2007-10-28 15:42                     ` Andrey Panin
2008-09-04  3:59                       ` Bjorn Helgaas
2008-09-10 19:26                         ` Bjorn Helgaas
     [not found]   ` <200809181512.43523.bjorn.helgaas@hp.com>
     [not found]     ` <48D3EEDD.70403@pcburn.com>
2008-09-20 23:21       ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2007-10-19 14:17 kyle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4706AD19.4040605@pcburn.com \
    --to=chris@pcburn.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox