mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Lamanna <jlamanna@gmail.com>
To: Andrey Panin <pazke@centrinvest.ru>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: SIIG DP CyberSerial 4S PCIe Support
Date: Tue, 9 Mar 2010 07:09:21 -0800	[thread overview]
Message-ID: <8DFD46FA-A938-41D6-97EC-F6E5324C9FAA@gmail.com> (raw)
In-Reply-To: <20100309141552.GD30538@centrinvest.ru>

On Mar 9, 2010, at 6:15, "Andrey Panin" <pazke@centrinvest.ru> wrote:

> On 067, 03 08, 2010 at 09:15:26PM -0800, James Lamanna wrote:
>
>> That's probably the case.
>> It looks like 8250 doesn't know about this PCIe device at all.
>> The Oxford PCI ID is not in pci_ids.h nor is the SIIG subsystem ID.
>> I'll see if I can maybe work up a patch to support this device,  
>> since I've found
>> the datasheet for the Oxford 4 port UART controller, but I may need  
>> some help.
>> Or if anyone else (who has more experience with this) wants to  
>> formulate one,
>> it would be greatly appreciated.
>
> Looks like you card can use existing code for Oxford Semiconductor  
> UARTs.
> Can you test the attached patch for 2.6.33 ?

Hi Andrey,
Coincidentally I found your patch for 2.6.28 that I was able to  
backport to 2.6.24. The card seems to be working great!
Is this patch in mainline now?

Thanks.

-- James

  parent reply	other threads:[~2010-03-09 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 19:07 James Lamanna
2010-03-08 21:13 ` 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 [this message]
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=8DFD46FA-A938-41D6-97EC-F6E5324C9FAA@gmail.com \
    --to=jlamanna@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=pazke@centrinvest.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
all inboxes | Powered by JetHome®