From: Matt Schulte <matts@commtech-fastcom.com>
To: linux-serial@vger.kernel.org
Subject: New serial card development
Date: Tue, 09 Oct 2012 13:43:10 -0500 [thread overview]
Message-ID: <5074703E.408@commtech-fastcom.com> (raw)
Hello, my name is Matt and I have recently developed a PCIe card based
on the Exar 17v35x series of PCIe multiport UART chips.
We have written Linux drivers for our other products in the past but
they have never been what I would call the best practice for Linux
development.
This time I would like to write a driver that uses the best practices
and possibly submit it to the kernel when I'm done.
I am a little bit confused about what method would be best for this
device. I have been examining the sample driver provided by Exar
and it seems that the only things that they have that are really
different from the generic 8250 serial driver are the interrupt
handler (optimized for their multiple ports), the transmit and
receive character functions (modified to use their 256 byte FIFOs)
and the function that calculates the baud. Also I have two features
specific to my card that I would likely need to use an ioctl for.
If these are the only differences would I be able to create a driver
like what is seen in the /drivers/tty/serial/8250 directory (8250_dw.c
for example)? Or would I need to do something similar to what I find in
the /drviers/tty/serial directory?
Thank you for your time.
Matt Schulte
next reply other threads:[~2012-10-09 18:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 18:43 Matt Schulte [this message]
2012-10-14 9:37 ` New serial card development Theodore Ts'o
2012-10-15 19:08 ` Matt Schulte
2012-10-15 23:26 ` Alan Cox
2012-10-16 2:32 ` Theodore Ts'o
2012-10-17 20:24 ` Matt Schulte
2012-10-19 21:21 ` Theodore Ts'o
2012-10-23 16:27 ` Matt Schulte
2012-10-23 16:31 ` Matt Schulte
2012-10-23 18:38 ` Greg KH
2012-10-29 20:04 ` Matt Schulte
2012-10-31 21:55 ` Matt Schulte
2012-11-01 22:03 ` Matt Schulte
2012-11-01 22:26 ` Alan Cox
2012-11-02 18:47 ` Matt Schulte
2012-11-02 20:21 ` Alan Cox
2012-10-23 18:06 ` Grant Edwards
2012-10-23 18:26 ` Alan Cox
2012-10-23 18:45 ` Grant Edwards
2012-10-23 19:16 ` Greg KH
2012-10-23 19:42 ` Grant Edwards
2012-10-23 20:10 ` Greg KH
2012-10-23 19:24 ` Alan Cox
2012-10-23 19:48 ` Grant Edwards
2012-10-23 20:31 ` Theodore Ts'o
2012-10-23 20:41 ` Grant Edwards
[not found] ` <CAJp1Oe6k7NWqdbYkJnd787JiT55-wSbG+tX1tP7Cy-oPShdVaA@mail.gmail.com>
2012-10-17 20:23 ` Matt Schulte
2012-10-17 21:53 ` Alan Cox
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=5074703E.408@commtech-fastcom.com \
--to=matts@commtech-fastcom.com \
--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).