linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Peter Hurley <peter@hurleysoftware.com>
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 08:58:09 -0400	[thread overview]
Message-ID: <517A79E1.8060504@compro.net> (raw)
In-Reply-To: <1366926071.3452.17.camel@thor.lan>

On 04/25/2013 05:41 PM, Peter Hurley wrote:
> On Wed, 2013-04-24 at 13:44 -0400, Mark Hounschell wrote:
>> I've been sort of maintaining a couple of Digi International serial port
>> card (XP and AP) drivers for years now because, well, they just won't do
>> it anymore. In any case, I'm moving from a 3.4.x kernel, that works just
>> fine, to a 3.8.8 kernel, that does not. I have code that does something
>> like this:
>>
>>       tty_set_operations(&SerialDriver, &SerialOps);
>>       tty_register_driver(&SerialDriver);
>>       maxminor = NumBoards * 64;
>>       for (i = 0; i < maxminor; i++)
>>           tty_register_device(&SerialDriver, i, NULL);
>
> You're correct in diagnosing the problem to cdevs == NULL.
> You're missing:
>
> 	maxminor = min(num_boards * 64, 256);
> 	serial_driver = alloc_tty_driver(maxminor);
>
> then,
> 	/* Fill in pertinent tty_driver fields, esp. */
> 	serial_driver->flags = TTY_DRIVER_DYNAMIC_DEV;
>
> 	tty_set_operations(serial_driver, &serial_ops);
> 	tty_register_driver(serial_driver);
> 	for (i = 0; i < maxminor; i++)
> 		tty_register_device(serial_driver, i, NULL);
>
>

Thanks for responding Peter.

Earlier in the code they do this:

static struct tty_driver SerialDriver
and things like
SerialDriver.termios = kmalloc((maxminor - 256) * sizeof(TERMIOS *), 
GFP_KERNEL);

So is the above no longer going to work and I _must_ now use 
alloc_tty_driver? If alloc_tty_driver is now a requirement, how much is 
it going to do for me? There are several things like the termios above 
that are manually allocated. How much if any of this is alloc_tty_driver 
going to do for me?

or might this work

static struct tty_driver SerialDriver
.
.
.
  	serial_driver.flags = TTY_DRIVER_DYNAMIC_DEV;

         SerialDriver.cdevs  = kcalloc(maxminor, 
sizeof(SerialDriver.cdevs), GFP_KERNEL);

  	tty_set_operations(&serial_driver, &serial_ops);
  	tty_register_driver(&serial_driver);
  	for (i = 0; i < maxminor; i++)
  		tty_register_device(&serial_driver, i, NULL);

???

>
> PS - Each board supports 64 individual serial ports??

No, this particular card comes in 4, 8, and 16 port flavors. I never did 
understand why they create so many device entries. I just figured they 
had a reason. For a single card, no matter how many ports, they create 
64 normal serial tty entries (tty_dgdm_G0 - tty_dgdm_G63), 64 serial 
printer entries (lp_dgdm_G0 - lp_dgdm_G63), and then 64 serial modem 
entries (cu_dgdm_G0 - cu_dgdm_G63). Don't know why.


Thanks again
Mark

  reply	other threads:[~2013-04-26 12:58 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 [this message]
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
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=517A79E1.8060504@compro.net \
    --to=markh@compro.net \
    --cc=dmarkh@cfl.rr.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    /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).