[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1385143571-3571-1-git-send-email-peter@hurleysoftware.com>
Date: Fri, 22 Nov 2013 13:06:07 -0500
From: Peter Hurley <peter@...leysoftware.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jiri Slaby <jslaby@...e.cz>, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org,
Peter Hurley <peter@...leysoftware.com>
Subject: [PATCH staging-next 0/4] fwserial changes for 3.14
**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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists