Index: [thread] [date] [subject] [author]
  From: mentalg@geocities.com
  To  : Tristan Wibberley <twibberley@llamacom.com>
  Date: Fri, 11 Sep 1998 13:55:22 -0400 (EDT)

Re: kgi vs. fbcon

On Fri, 11 Sep 1998, Tristan Wibberley wrote:

> > > > 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.
> 
> But your /dev/graph* is still 'whatever /dev/fb* device is associated
> with /dev/tty1'. That needs to be changed too.

augh. okay, 'whatever /dev/fb* device is associated with VC 1'...

-=MenTaLguY=-

Index: [thread] [date] [subject] [author]