Re: no serial output when using cdk/ncurses with Fbsplash

[daggs]

> Sent: Thursday, April 02, 2015 at 12:18 PM
> From: "Thomas Dickey" <address@hidden>
> To: daggs <address@hidden>
> Cc: address@hidden
> Subject: Re: no serial output when using cdk/ncurses with Fbsplash
>
> On Thu, Apr 02, 2015 at 07:57:59AM +0200, daggs wrote:
> > 
> > 
> > > Sent: Thursday, April 02, 2015 at 4:02 AM
> > > From: "Thomas Dickey" <address@hidden>
> > > To: daggs <address@hidden>
> > > Cc: address@hidden
> > > Subject: Re: no serial output when using cdk/ncurses with Fbsplash
> > >
> > > On Wed, Apr 01, 2015 at 12:32:07PM +0200, daggs wrote:
> > > > Greetings,
> > > > 
> > > > I have a usb image that boots something called Fbsplash (see: 
> > > > https://wiki.gentoo.org/wiki/Fbsplash).
> > > > this requires booting the system with uvesa enabled.
> > > > part of our gui I cdk based and the usb prints the output to both the 
> > > > screen and serial port for saving.
> > > > 
> > > > if I disable uvesa, I see all the outputs on both the screen and the 
> > > > serial port but if I enable it, I'm missing outputs on serial when we 
> > > > use cdk.
> > > > I've looked into the code of cdk and saw it is done in ncurses, looking 
> > > > at ncurses's code didn't labeled out anything special.
> > > > 
> > > > my only hunch is that ncurses writes directly into the vga buffer when 
> > > > not using uvesa. is that correct?
> > > > when using uvesa, where does ncurses writes to?
> > > 
> > > no - ncurses only knows how to write escape sequences to the terminal...
> > > 
> > > (MinGW port is a different case, but we've not mentioned that so far)
> > > 
> > 
> > so the issue is that in terminal mode stdout is somehow connected into 
> > serial when using ncurses while in uvesa mode it doesn't?
> 
> I suppose so - in any case, ncurses does not know anything about that :-)
> 

after some digging I've found out this has nothing to do with cdk or ncurses, 
it is a bug on our part, thanks for the help.