[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170313222608.pfmv37tw3badlsjw@var.youpi.perso.aquilenet.fr>
Date: Mon, 13 Mar 2017 23:26:08 +0100
From: Samuel Thibault <samuel.thibault@...-lyon.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: okash.khawaja@...il.com, Jiri Slaby <jslaby@...e.com>,
linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
Kirk Reiser <kirk@...sers.ca>,
Chris Brannon <chris@...-brannons.com>,
speakup@...ux-speakup.org
Subject: Re: [patch 0/7] staging: speakup: introduce tty-based comms
Hello,
Greg KH, on mar. 14 mars 2017 06:14:04 +0800, wrote:
> On Mon, Mar 13, 2017 at 10:05:51PM +0000, okash.khawaja@...il.com wrote:
> > This patchset introduces a TTY-based way for the synths to communicate
> > with devices as an alternate for direct serial comms used by the synths
> > at the moment. It then migrates some of the synths to the TTY-based
> > comms. Synths migrated in this patchset are dummy, acntsa, bns and
> > txprt.
>
> What about using the serbus code that is now in the tree?
I guess you mean serdev?
Well, for a start that didn't exist when Okash worked on the TTY part :)
> That should make this a lot easier than your patchset from what I can
> see.
Will serdev support modem line control? We need this for some devices.
How is the serial port chosen with serdev?
Samuel
Powered by blists - more mailing lists