From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
devel@driverdev.osuosl.org,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] staging: Add firewire-serial driver
Date: Mon, 22 Oct 2012 15:45:05 -0700 [thread overview]
Message-ID: <20121022224505.GD24489@kroah.com> (raw)
In-Reply-To: <1350565015.23730.4.camel@thor>
On Thu, Oct 18, 2012 at 08:56:55AM -0400, Peter Hurley wrote:
> 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
I'd like to get an Ack from Stefan here, before I'll add this to the
staging tree.
thanks,
greg k-h
next prev parent reply other threads:[~2012-10-22 22:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 12:56 [PATCH 0/1] staging: Add firewire-serial driver Peter Hurley
2012-10-22 22:45 ` Greg Kroah-Hartman [this message]
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=20121022224505.GD24489@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=peter@hurleysoftware.com \
--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.