From: Greg KH <greg@kroah.com>
To: Philip Prindeville <philipp@redfish-solutions.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: Support for Perle Systems Speed/LE-8
Date: Tue, 24 Jan 2012 09:11:41 -0800 [thread overview]
Message-ID: <20120124171141.GA26908@kroah.com> (raw)
In-Reply-To: <4F1E4D69.3040907@redfish-solutions.com>
On Mon, Jan 23, 2012 at 11:19:21PM -0700, Philip Prindeville wrote:
> Hi.
>
> I have a Perle Speed/LE-8 card that's poorly supported (cough) by the vendor.
>
> The design seems to be plain-vanilla enough: it uses Oxford 9501 and 9511 chips.
>
> $ lspci -v -n -s 04:07
> 04:07.0 0700: 155f:b008 (prog-if 06 [16950])
> Subsystem: 1415:9501
> Flags: medium devsel, IRQ 21
> I/O ports at ec00 [size=32]
> Memory at fbfff000 (32-bit, non-prefetchable) [size=4K]
> I/O ports at e880 [size=32]
> Memory at fbffe000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [40] Power Management version 1
> Kernel driver in use: perle-serial
> Kernel modules: perle-serial
>
> 04:07.1 0680: 155f:b008
> Subsystem: 1415:9511
> Flags: medium devsel, IRQ 21
> I/O ports at e800 [size=32]
> Memory at fbffd000 (32-bit, non-prefetchable) [size=4K]
> I/O ports at e480 [size=32]
> Memory at fbffc000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [40] Power Management version 1
> Kernel driver in use: perle-serial
> Kernel modules: perle-serial
>
>
> $
>
> There's nothing funky about this card except that one of the lines is
> either DTR or RTS if I've understood the scarce documentation.
>
> Anyway, I was wondering what's involved in getting the
> drivers/tty/serial/8250_pci.c to support this?
Have you tried adding the pci device ids to the driver and see how well
it works, or not?
greg k-h
prev parent reply other threads:[~2012-01-24 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 6:19 Support for Perle Systems Speed/LE-8 Philip Prindeville
2012-01-24 17:11 ` Greg KH [this message]
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=20120124171141.GA26908@kroah.com \
--to=greg@kroah.com \
--cc=linux-serial@vger.kernel.org \
--cc=philipp@redfish-solutions.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.