From: Jonathan Woithe <jwoithe@just42.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-serial@vger.kernel.org, jwoithe@just42.net
Subject: Re: Comments requested: driver for Quatech PCI serial cards
Date: Fri, 16 Nov 2012 08:53:46 +1030 [thread overview]
Message-ID: <20121115222346.GA28869@marvin.atrad.com.au> (raw)
In-Reply-To: <20121115155347.4be3dce8@pyramind.ukuu.org.uk>
On Thu, Nov 15, 2012 at 03:53:47PM +0000, Alan Cox wrote:
> On Thu, 15 Nov 2012 10:41:10 +1030
> Jonathan Woithe <jwoithe@just42.net> wrote:
>
> > On Wed, Nov 14, 2012 at 11:57:19PM +0000, Alan Cox wrote:
> > > > our upcoming system. I'm guessing that the difficulties with the driver as
> > > > it's currently structured may have been the reason it was never pushed to
> > > > mainline by the original author in 2007.
> > >
> > > There are not many difficulties I can see. You just add the identifiers
> > > to the 8250_pci tables and a couple of small bits of code and everything
> > > but the RS422/485 stuff just works.
> > >
> > > If you need the RS422 stuff then yes its a bit more work.
> >
> > Unfortunately we need the RS422 stuff - that's the reason for using the
> > DSC-200/300 card.
> >
> > Thanks for the comments and feedback - I'll take another look at things in
> > the light of the information. If the functionality we require requires a
> > significant amount of new code to be written, I suspect that the work will
> > be deemed too time consuming by those who call the shots. We'll see.
>
> First guess at what you need except for the RS422 registers is attached. To
> get the RS422 features working needs the tool tracing (or driver printks adding)
> to see what QMCR and QOPR bits map to which RS422 features.
>
> Given that if you just force the bits you want in with the RS422 warning I expect
> it'll just work for your case and should then be trivial to add the ioctl.
Thanks very much for taking the time to do this. I'm away from the office
today but will test it on Monday. I have been given the go-ahead to spend a
small amount of time to see if I can get the DSC card working for our case;
with this patch as a starting point I think progress will be made.
jonathan
next prev parent reply other threads:[~2012-11-15 22:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 6:07 Comments requested: driver for Quatech PCI serial cards Jonathan Woithe
2012-11-14 12:12 ` Alan Cox
2012-11-14 23:10 ` Jonathan Woithe
2012-11-14 23:57 ` Alan Cox
2012-11-15 0:11 ` Jonathan Woithe
2012-11-15 15:53 ` Alan Cox
2012-11-15 22:23 ` Jonathan Woithe [this message]
2012-11-28 2:29 ` Jonathan Woithe
2012-11-28 13:24 ` Alan Cox
2012-11-28 13:41 ` Jonathan Woithe
2012-11-28 17:30 ` Greg KH
2012-11-28 22:33 ` Jonathan Woithe
2012-12-10 0:13 ` Did quatech changes make 3.8? (was: Re: Comments requested: driver for Quatech PCI serial cards) Jonathan Woithe
2012-12-10 2:19 ` Greg KH
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=20121115222346.GA28869@marvin.atrad.com.au \
--to=jwoithe@just42.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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