linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: markh@compro.net
Cc: linux-serial@vger.kernel.org, Mark Hounschell <dmarkh@cfl.rr.com>
Subject: Re: Out of tree GPL serial tty driver help?
Date: Fri, 26 Apr 2013 15:51:06 -0400	[thread overview]
Message-ID: <1367005866.3971.15.camel@thor.lan> (raw)
In-Reply-To: <517AC4C2.3010702@compro.net>

On Fri, 2013-04-26 at 14:17 -0400, Mark Hounschell wrote:
> On 04/26/2013 12:37 PM, Peter Hurley wrote:
> > These drivers weren't really current at 3.4 though, either. I'm not sure
> > what else you're going to find that doesn't work.
> >
> 
> No, I have kept them current, or I should say functional, to the best of 
> my ability from 2.6 up to and including 3.4.x.

By 'current', I mean 'similar in structure and functionality to in-tree
drivers'.

The structure of this driver is more akin to a 2.5 driver (back when
there were separate serial and callout tty drivers).

>  What I have here works 
> with kernels up to 3.4.x. I have not tried anything between 3.4 and 3.8. 
>   As far as building against 3.8, the only issues were the change from 
> *termios to termios and the "structn_tty_data" no longer in an include 
> file so not easily directly accessible.

What is this driver accessing in N_TTY's private data?

> > For both PCI and PCI-e, these drivers should _at a minimum_ be pci
> > drivers that register the tty driver at module init and register _only_
> > the tty devices for that particular PCI device at PCI probe time. Look
> > at the end of synclink_gt.c for how this is supposed to look.
> >
> 
> I'll look at it some more but I have been there.

Specifically, review:
	struct pci_driver
	device_init()
	init_one()
	remove_one()
	sglt_init()
	sglt_exit()

Regards,
Peter Hurley


  reply	other threads:[~2013-04-26 19:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 17:44 Out of tree GPL serial tty driver help? Mark Hounschell
2013-04-25 21:41 ` Peter Hurley
2013-04-26 12:58   ` Mark Hounschell
2013-04-26 13:45     ` Peter Hurley
2013-04-26 14:28       ` Mark Hounschell
2013-04-26 14:35         ` Greg KH
2013-04-26 15:10           ` Mark Hounschell
2013-04-26 15:19             ` Greg KH
2013-04-26 15:39               ` Peter Hurley
2013-04-26 16:03                 ` Greg KH
2013-04-26 17:58                   ` Mark Hounschell
2013-04-26 23:21                     ` Greg KH
2013-04-26 16:37         ` Peter Hurley
2013-04-26 18:17           ` Mark Hounschell
2013-04-26 19:51             ` Peter Hurley [this message]
2013-04-26 20:26               ` Mark Hounschell
2013-04-26 21:49                 ` Peter Hurley

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=1367005866.3971.15.camel@thor.lan \
    --to=peter@hurleysoftware.com \
    --cc=dmarkh@cfl.rr.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=markh@compro.net \
    /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).