linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Peter Hurley <peter@hurleysoftware.com>
Subject: [PATCH staging-next 0/4] fwserial changes for 3.14
Date: Fri, 22 Nov 2013 13:06:07 -0500	[thread overview]
Message-ID: <1385143571-3571-1-git-send-email-peter@hurleysoftware.com> (raw)

**This patchset requires 'Halve tty buffer memory consumption' patchset **

Greg,

I have not forgotten fwserial :)

Patches 1 & 2 remove the hacky rx buffering, and instead rely on
configurable tty buffers. [Interestingly, tty buffers were originally
introduced by Alan Cox to replace flip buffers specifically to support
higher throughput serial devices which had mutated special-purpose
rx buffering.]

Patch 3 remedies an ugly (private interface) name.
Patch 4 adds build configuration options which control how many
fwserial devices can exist (per adapter and in total). This is
so some build configurations can minimize resources while still
providing firewire serial console autoconnect (say for a debugging
console or a headless server) while another build configuration
could support many headless server consoles running on a single
machine.

I hope to get the stage 1 console driver into -next in this
cycle as well.

Regards,

Peter Hurley (4):
  staging/fwserial: Rip out rx buffering
  staging/fwserial: Up the tty buffer limit to 128K
  staging/fwserial: Rename data profiling functions
  staging/fwserial: Add Kconfig options for max ports

 drivers/staging/fwserial/Kconfig    |  20 +++++
 drivers/staging/fwserial/fwserial.c | 151 ++++++++++--------------------------
 drivers/staging/fwserial/fwserial.h |  24 +-----
 drivers/tty/tty_buffer.c            |   1 +
 4 files changed, 64 insertions(+), 132 deletions(-)

-- 
1.8.1.2


             reply	other threads:[~2013-11-22 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 18:06 Peter Hurley [this message]
2013-11-22 18:06 ` [PATCH staging-next 1/4] staging/fwserial: Rip out rx buffering Peter Hurley
2013-11-22 18:06 ` [PATCH staging-next 2/4] staging/fwserial: Up the tty buffer limit to 128K Peter Hurley
2013-11-22 18:06 ` [PATCH staging-next 3/4] staging/fwserial: Rename data profiling functions Peter Hurley
2013-11-22 18:06 ` [PATCH staging-next 4/4] staging/fwserial: Add Kconfig options for max ports Peter Hurley
2013-11-25 20:43 ` [PATCH staging-next 0/4] fwserial changes for 3.14 Greg Kroah-Hartman
2013-11-25 21:00   ` Peter Hurley
2013-11-25 21:24     ` Greg Kroah-Hartman

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=1385143571-3571-1-git-send-email-peter@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).