From: Peter Hurley <peter@hurleysoftware.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: [PATCH 0/1] staging: Add firewire-serial driver
Date: Thu, 18 Oct 2012 08:56:55 -0400 [thread overview]
Message-ID: <1350565015.23730.4.camel@thor> (raw)
Please consider this serial driver for review for submission to staging.
The firewire-serial driver implements TTY over IEEE 1394. In its default
configuration, it creates 4 TTY devices and one loopback device per
firewire card (respectively, named fwtty<n>~fwtty<n+3> and fwloop<n>).
Currently, the TTY devices auto-connect to every cabled peer (the TODO
list includes plans for providing a sysfs interface to control virtual
cabling with whitelist/blacklist support per GUID).
Efforts are still ongoing for a companion console driver, with plans to
eventually add early_printk & kgdb support (via additional drivers).
Some issues did arise with both the TTY and Firewire subsystems which
are noted in the TODO file. Please review these workarounds.
Peter Hurley (1):
staging: fwserial: Add TTY-over-Firewire serial driver
drivers/staging/Kconfig | 2 +
drivers/staging/Makefile | 1 +
drivers/staging/fwserial/Kconfig | 9 +
drivers/staging/fwserial/Makefile | 2 +
drivers/staging/fwserial/TODO | 89 ++
drivers/staging/fwserial/dma_fifo.c | 310 ++++
drivers/staging/fwserial/dma_fifo.h | 130 ++
drivers/staging/fwserial/fwserial.c | 2885 +++++++++++++++++++++++++++++++++++
drivers/staging/fwserial/fwserial.h | 355 +++++
9 files changed, 3783 insertions(+)
create mode 100644 drivers/staging/fwserial/Kconfig
create mode 100644 drivers/staging/fwserial/Makefile
create mode 100644 drivers/staging/fwserial/TODO
create mode 100644 drivers/staging/fwserial/dma_fifo.c
create mode 100644 drivers/staging/fwserial/dma_fifo.h
create mode 100644 drivers/staging/fwserial/fwserial.c
create mode 100644 drivers/staging/fwserial/fwserial.h
--
1.7.12.3
next reply other threads:[~2012-10-18 13:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 12:56 Peter Hurley [this message]
2012-10-22 22:45 ` [PATCH 0/1] staging: Add firewire-serial driver Greg Kroah-Hartman
2012-10-23 2:34 ` Peter Hurley
2012-10-23 3:15 ` Greg Kroah-Hartman
2012-10-23 9:51 ` Alan Cox
2012-10-23 16:30 ` Peter Hurley
2012-10-23 18:41 ` Stefan Richter
2012-10-23 18:41 ` Stefan Richter
2012-10-24 13:41 ` Stefan Richter
2012-10-24 15:56 ` Peter Hurley
2012-11-02 12:16 ` [PATCH v2 " Peter Hurley
2012-11-02 12:16 ` [PATCH v2 1/1] staging: fwserial: Add TTY-over-Firewire serial driver Peter Hurley
2012-11-12 23:33 ` Stefan Richter
2012-11-12 23:51 ` Greg Kroah-Hartman
2012-11-13 19:37 ` Peter Hurley
2012-11-13 19:47 ` Greg Kroah-Hartman
2012-11-13 19:14 ` Peter Hurley
2012-11-14 1:25 ` Stefan Richter
2012-11-27 18:33 ` Peter Hurley
2012-11-27 23:58 ` Stefan Richter
2012-11-27 23:58 ` Stefan Richter
2012-11-28 1:00 ` Peter Hurley
2012-11-28 1:00 ` 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=1350565015.23730.4.camel@thor \
--to=peter@hurleysoftware.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.