From: mentalg@geocities.com
  To  : Tristan Wibberley <twibberley@llamacom.com>
  Date: Thu, 10 Sep 1998 18:21:17 -0400 (EDT)

Re: kgi vs. fbcon

On Fri, 11 Sep 1998, Tristan Wibberley wrote:

> mentalg@geocities.com wrote:
> > 
> > On Thu, 10 Sep 1998, Alexander Larsson wrote:
> > 
> > >  I was thinking a bit about this too. Wouldn't it be possible to add a
> > > /dev/graphic like the old kgi device that used fbcon/kgicon to set modes
> > > etc.  This way people could get the benefits of the kgi way even when
> > > they are using fbcon.
> > 
> > I don't think it needs to be that complex. the /dev/graphic* (or I think
> > /dev/ttyfb*) devices would behave exactly like /dev/fb*, except with the
> > addition of blanking/unmmapping to take away access to the fb device through
> > that device when the associated VC is switched away.
> > 
> > for instance:
> > 
> > /dev/ttyfb1 - basically the same as whatever /dev/fb* device is
> >               associated with /dev/tty1 -- only, with the additional
> 
> That'll be difficult to get accepted (I wouldn't). TTY stands for
> teletype, and a teletype machine doesn't have *any*thing to do with
> framebuffers, so no association can really be made. A tty device *is* a
> teletype or a teletype emulator.

Okay, stupid naming idea on my part.  Let's call it ... eh, I dunno...
/dev/graph* or something.  But the rest of the suggestion still stands.

-=MenTaLguY=-