From: James Lamanna <jlamanna@gmail.com>
To: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: SIIG DP CyberSerial 4S PCIe Support
Date: Mon, 8 Mar 2010 11:07:21 -0800 [thread overview]
Message-ID: <aa4c40ff1003081107n78e9f052n2a754680e5491c68@mail.gmail.com> (raw)
Hi,
I recently purchased a SIIG DP CyberSerial 4S PCIe card, however the
kernel doesn't seem to recognize it.
There are no messages in dmesg or anything about it.
Currently I'm at 2.6.24, but looking at drivers/serial/8250_pci.c
between 2.6.24 and 2.6.32 there doesn't
seem to be real changes with SIIG cards.
Seems like other SIIG cards are supported, so are we just missing the
PCI IDs for this card?
Here's the lspci -nnvvvvvv output:
01:00.0 Serial controller [0700]: Oxford Semiconductor Ltd Unknown
device [1415:c208] (prog-if 06 [16950])
Subsystem: Siig Inc Unknown device [131f:2250]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fe8fc000 (32-bit, non-prefetchable) [size=16K]
Region 1: Memory at fe600000 (32-bit, non-prefetchable) [size=2M]
Region 2: Memory at fe400000 (32-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=55mA
PME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [70] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <128ns, L1 <2us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal+ Fatal+ Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <512ns, L1 <64us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [b0] MSI-X: Enable- Mask- TabSize=16
Vector table: BAR=1 offset=001b3000
PBA: BAR=1 offset=001b2000
Please CC me for I am not subscribed.
Thanks.
-- James
next reply other threads:[~2010-03-08 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 19:07 James Lamanna [this message]
2010-03-08 21:13 ` SIIG DP CyberSerial 4S PCIe Support James Lamanna
2010-03-09 2:19 ` Robert Hancock
2010-03-09 5:15 ` James Lamanna
2010-03-09 14:15 ` Andrey Panin
2010-03-09 15:06 ` James Lamanna
2010-03-09 15:09 ` James Lamanna
2010-03-11 13:45 ` Andrey Panin
2010-03-18 21:06 ` Andrew Morton
2010-03-20 2:05 ` James Lamanna
2010-03-24 8:32 ` Andrey Panin
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=aa4c40ff1003081107n78e9f052n2a754680e5491c68@mail.gmail.com \
--to=jlamanna@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).