From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linux-Kernel List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: good example of a tty driver
Date: Thu, 2 Jul 2009 19:27:44 +0100 [thread overview]
Message-ID: <20090702192744.029620ae@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <D77CBB49-A340-4282-9ACF-2172D1BB9E43@kernel.crashing.org>
On Thu, 2 Jul 2009 11:48:09 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:
> Alan,
>
> Can you point me at any good drivers to use as an example of using the
> tty layer. I'm trying to get an out of tree driver brought up to date
> for the Avocent ESP-16 MI Serial Hubs (serial over ethernet):
Its very much in flux with the drivers getting kref support, helper
functions and the like in the current releases.
>
> http://www.connectivity.avocent.com/products/network-based/esp_16.asp
>
> Thankfully the have a GPL driver but it was last updated against 2.6.23:
>
> http://www.connectivity.avocent.com/drivers/esp_serial_hubs/dd64e069.asp
>
> However I've never worked on any tty drivers so its a bit black magic
> at this point. I was hoping that an example would at least get me
> able to bring the driver up to a point that we can get it into the
> staging tree.
I would make it build, chuck it in the staging tree and go from there
isicom has a fairly good use of the newer helper functions we have so far
and struct tty_port so is probably as good an example as any if the
driver is using drivers/char. If its using the serial layer helpers then
apart from making sure you report the actual baud rate and termios
settings back little has changed (its all been hidden in the midlayer)
next prev parent reply other threads:[~2009-07-02 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 16:48 Kumar Gala
2009-07-02 18:27 ` Alan Cox [this message]
2009-07-02 18:31 ` Greg KH
2009-07-08 22:38 ` Joe Perches
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=20090702192744.029620ae@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®