From: Chris Bergeron <chris@pcburn.com>
To: Andrey Panin <pazke@donpac.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Syba 8-Port Serial Card Unidentified By Kernel
Date: Tue, 16 Oct 2007 15:03:34 -0400 [thread overview]
Message-ID: <47150B06.3040306@pcburn.com> (raw)
In-Reply-To: <20071012120826.GB23378@pazke.donpac.ru>
Andrey Panin wrote:
> On 284, 10 11, 2007 at 01:02:12PM -0400, Chris Bergeron wrote:
>
>> Andrey Panin wrote:
>>
>>> On 278, 10 05, 2007 at 05:31:05PM -0400, Chris Bergeron wrote:
>>>
>>>
>>>> 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.
>>>>
>>>>
>>> Are you sure ? IIRC IT887x are PCI-ISA bridges with additional periphery
>>> and your lspci shows PLX chip. Can you send complete lspci -vv output ?
>>> Output of dmesg could be useful too.
>>>
>>>
>> I'm sure that's what it says on the largest chip on the PCI card. It could
>> be that the other two chips are more relevant... the numbers from them are
>> included below.
>>
>> I've posted up a quick text only page with the diagnostic information from
>> the system (full dmesg, lspci, etc) plus links to pictures of the board
>> (since others might see something important that I'm not aware of). You
>> can access that at
>> http://pcburn.com/files/Syba_serial_controller/index.html
>>
>
> Can you try an attached patch ? I hope it should at least detect UARTs on
> your board. Be ready that baudrate could be wrong, because we do not know
> what frequency is used to clock these UARTs.
>
>
Alright,finally had another machine to try the attached patch. I get an
odd error regarding IRQ 17:
"irq 17: nobody cared (try booting with the "irqpoll" option)"
along with a long error message (but the kernel continues to load).
Aside from that the ports now allow me to run a getty on them and the
DTR line lights up on my serial tester (as it does with a working port)
but the device on the other end doesn't function.
I've updated the web page with lspci -vv and dmesg output. I can also
post it here if that's desirable, just figured I'd save everyone the
inbox flooding :).
-- Chris
next prev parent reply other threads:[~2007-10-16 19:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 21:31 Syba 8-Port Serial Card Unidentified By Kernel Chris Bergeron
2007-10-05 22:43 ` 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 [this message]
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=47150B06.3040306@pcburn.com \
--to=chris@pcburn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@donpac.ru \
/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