On Mon, 1 Dec 2014 19:51:18 -0600
Felipe Balbi wrote:
> On Tue, Dec 02, 2014 at 01:13:38AM +0200, Aaro Koskinen wrote:
> > Hi,
> >
> > On Mon, Dec 01, 2014 at 02:09:14PM +, One Thousand Gnomes wrote:
> > > > Well the nightmare userspace switch from ttyS to ttyO few years ago is
> > > >
On Mon, 1 Dec 2014 19:51:18 -0600
Felipe Balbi ba...@ti.com wrote:
On Tue, Dec 02, 2014 at 01:13:38AM +0200, Aaro Koskinen wrote:
Hi,
On Mon, Dec 01, 2014 at 02:09:14PM +, One Thousand Gnomes wrote:
Well the nightmare userspace switch from ttyS to ttyO few years ago is
On Tue, Dec 02, 2014 at 01:13:38AM +0200, Aaro Koskinen wrote:
> Hi,
>
> On Mon, Dec 01, 2014 at 02:09:14PM +, One Thousand Gnomes wrote:
> > > Well the nightmare userspace switch from ttyS to ttyO few years ago is
> > > something we want to avoid.. I think the best solution would be to make
Hi,
On Mon, Dec 01, 2014 at 02:09:14PM +, One Thousand Gnomes wrote:
> > Well the nightmare userspace switch from ttyS to ttyO few years ago is
> > something we want to avoid.. I think the best solution would be to make
> > serial-omap.c transparently provide support for ttyO using the new
* Sebastian Andrzej Siewior [141201 09:27]:
> On 12/01/2014 05:38 PM, Tony Lindgren wrote:
> > * One Thousand Gnomes [141201 06:11]:
> >>> Well the nightmare userspace switch from ttyS to ttyO few years ago is
> >>> something we want to avoid.. I think the best solution would be to make
> >>>
On 12/01/2014 05:38 PM, Tony Lindgren wrote:
> * One Thousand Gnomes [141201 06:11]:
>>> Well the nightmare userspace switch from ttyS to ttyO few years ago is
>>> something we want to avoid.. I think the best solution would be to make
>>> serial-omap.c transparently provide support for ttyO
* One Thousand Gnomes [141201 06:11]:
> > Well the nightmare userspace switch from ttyS to ttyO few years ago is
> > something we want to avoid.. I think the best solution would be to make
> > serial-omap.c transparently provide support for ttyO using the new 8250
> > code so both ttyS and ttyO
> Well the nightmare userspace switch from ttyS to ttyO few years ago is
> something we want to avoid.. I think the best solution would be to make
> serial-omap.c transparently provide support for ttyO using the new 8250
> code so both ttyS and ttyO devices would just work. Otherwise it will
> be
Hi,
On Mon, Dec 01, 2014 at 02:09:14PM +, One Thousand Gnomes wrote:
Well the nightmare userspace switch from ttyS to ttyO few years ago is
something we want to avoid.. I think the best solution would be to make
serial-omap.c transparently provide support for ttyO using the new 8250
On Tue, Dec 02, 2014 at 01:13:38AM +0200, Aaro Koskinen wrote:
Hi,
On Mon, Dec 01, 2014 at 02:09:14PM +, One Thousand Gnomes wrote:
Well the nightmare userspace switch from ttyS to ttyO few years ago is
something we want to avoid.. I think the best solution would be to make
Well the nightmare userspace switch from ttyS to ttyO few years ago is
something we want to avoid.. I think the best solution would be to make
serial-omap.c transparently provide support for ttyO using the new 8250
code so both ttyS and ttyO devices would just work. Otherwise it will
be years
* One Thousand Gnomes gno...@lxorguk.ukuu.org.uk [141201 06:11]:
Well the nightmare userspace switch from ttyS to ttyO few years ago is
something we want to avoid.. I think the best solution would be to make
serial-omap.c transparently provide support for ttyO using the new 8250
code so
On 12/01/2014 05:38 PM, Tony Lindgren wrote:
* One Thousand Gnomes gno...@lxorguk.ukuu.org.uk [141201 06:11]:
Well the nightmare userspace switch from ttyS to ttyO few years ago is
something we want to avoid.. I think the best solution would be to make
serial-omap.c transparently provide
* Sebastian Andrzej Siewior bige...@linutronix.de [141201 09:27]:
On 12/01/2014 05:38 PM, Tony Lindgren wrote:
* One Thousand Gnomes gno...@lxorguk.ukuu.org.uk [141201 06:11]:
Well the nightmare userspace switch from ttyS to ttyO few years ago is
something we want to avoid.. I think the
* Sebastian Andrzej Siewior [141129 01:50]:
> * Sebastian Andrzej Siewior | 2014-11-26 23:01:46 [+0100]:
>
> >Technically speaking this is not required. If both are enabled then the
> >Maikefile order says that 8250 one wins, the second is never probed.
> >
> >If we choose to enable 8250_omap
* Sebastian Andrzej Siewior | 2014-11-26 23:01:46 [+0100]:
>Technically speaking this is not required. If both are enabled then the
>Maikefile order says that 8250 one wins, the second is never probed.
>
>If we choose to enable 8250_omap via defconfig then one might get supprised
>that his
* Sebastian Andrzej Siewior | 2014-11-26 23:01:46 [+0100]:
Technically speaking this is not required. If both are enabled then the
Maikefile order says that 8250 one wins, the second is never probed.
If we choose to enable 8250_omap via defconfig then one might get supprised
that his console
* Sebastian Andrzej Siewior bige...@linutronix.de [141129 01:50]:
* Sebastian Andrzej Siewior | 2014-11-26 23:01:46 [+0100]:
Technically speaking this is not required. If both are enabled then the
Maikefile order says that 8250 one wins, the second is never probed.
If we choose to enable
Technically speaking this is not required. If both are enabled then the
Maikefile order says that 8250 one wins, the second is never probed.
If we choose to enable 8250_omap via defconfig then one might get supprised
that his console isn't working anymore since nothing says use ttySx
instead
Technically speaking this is not required. If both are enabled then the
Maikefile order says that 8250 one wins, the second is never probed.
If we choose to enable 8250_omap via defconfig then one might get supprised
that his console isn't working anymore since nothing says use ttySx
instead
20 matches
Mail list logo