public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kumar Gala <galak@kernel.crashing.org>,
	Linux-Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: good example of a tty driver
Date: Thu, 2 Jul 2009 11:31:49 -0700	[thread overview]
Message-ID: <20090702183149.GA11720@kroah.com> (raw)
In-Reply-To: <20090702192744.029620ae@lxorguk.ukuu.org.uk>

On Thu, Jul 02, 2009 at 07:27:44PM +0100, Alan Cox wrote:
> 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

That sounds good to me as well.  Kumar, feel free to send me a patch :)

thanks,

greg k-h

  reply	other threads:[~2009-07-02 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 16:48 good example of a tty driver Kumar Gala
2009-07-02 18:27 ` Alan Cox
2009-07-02 18:31   ` Greg KH [this message]
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=20090702183149.GA11720@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=galak@kernel.crashing.org \
    --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