Re: [PATCH v2 2/9] tty_port: allow a port to be opened with a tty that has no file handle

On Thu, Jan 19, 2017 at 9:05 AM, Rob Herring wrote: > On Thu, Jan 19, 2017 at 7:37 AM, Greg Kroah-Hartman > wrote: >> On Mon, Jan 16, 2017 at 04:54:29PM -0600, Rob Herring wrote: >>> From: Alan Cox >>> >>> Let us create tty objects entirely in kernel space. Untested proposal to >>> show why all

Re: [PATCH v2 2/9] tty_port: allow a port to be opened with a tty that has no file handle

On Thu, Jan 19, 2017 at 7:37 AM, Greg Kroah-Hartman wrote: > On Mon, Jan 16, 2017 at 04:54:29PM -0600, Rob Herring wrote: >> From: Alan Cox >> >> Let us create tty objects entirely in kernel space. Untested proposal to >> show why all the ideas around rewriting half the uart stack are not needed.

Re: [PATCH v2 2/9] tty_port: allow a port to be opened with a tty that has no file handle

On Mon, Jan 16, 2017 at 04:54:29PM -0600, Rob Herring wrote: > From: Alan Cox > > Let us create tty objects entirely in kernel space. Untested proposal to > show why all the ideas around rewriting half the uart stack are not needed. > > With this a kernel created non file backed tty object could

Re: [PATCH v2 2/9] tty_port: allow a port to be opened with a tty that has no file handle

On Mon, 16 Jan 2017 16:54:29 -0600 Rob Herring wrote: > From: Alan Cox > > Let us create tty objects entirely in kernel space. Untested proposal to > show why all the ideas around rewriting half the uart stack are not needed. > > With this a kernel created non file backed tty object could be u

[PATCH v2 2/9] tty_port: allow a port to be opened with a tty that has no file handle

From: Alan Cox Let us create tty objects entirely in kernel space. Untested proposal to show why all the ideas around rewriting half the uart stack are not needed. With this a kernel created non file backed tty object could be used to handle data, and set terminal modes. Not all ldiscs can cope