From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bmckinlay@perle.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 60/80] tty: extract the pty init time special cases
Date: Thu, 29 Jan 2009 19:34:40 +0000 [thread overview]
Message-ID: <20090129193440.2c6efb65@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <OFD0116D1D.5061D2AB-ON8525754D.005C6317-8525754D.00661977@perle.com>
> - any required documentation explaining how the driver works and
> describing
> the API for the master side of the PTY driver ?
The first most useful part would be understand what your pty driver does
and is required that is not in the base one. Just an idea of what extra
APIs it provides would be quite useful. If it is stuff like virtual modem
lines then that is stuff I want to see supported in the base kernel
anyway.
> As mentioned above the Linux kernel has supported "out of tree" PTY type
> TTY
> drivers all the way back to kernel 2.2.x and up to 2.6.27. To do this the
By chance.. as to policies about kernel recompiles, that is between you
and the vendors. Maybe the vendors will add the symbols to their tree for
you ?
Equally look at the positives - if the facilities you need are in the
base kernel your customers won't run into arguments between yourselves
and the base kernel vendor over support.
Alan
next prev parent reply other threads:[~2009-01-29 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 2:16 bmckinlay
2009-01-22 12:40 ` Alan Cox
2009-01-28 20:36 ` bmckinlay
2009-01-28 20:47 ` Alan Cox
2009-01-29 18:30 ` bmckinlay
2009-01-29 19:34 ` Alan Cox [this message]
2009-02-02 15:42 ` bmckinlay
-- strict thread matches above, loose matches on Subject: below --
2008-10-13 9:31 [PATCH 00/80] TTY updates for 2.6.28 Alan Cox
2008-10-13 9:42 ` [PATCH 60/80] tty: extract the pty init time special cases 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=20090129193440.2c6efb65@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bmckinlay@perle.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®