On Wed, Dec 27, 2006 at 01:11:24AM -0500, Thor Lancelot Simon wrote:
> On Tue, Dec 26, 2006 at 10:02:54PM -0800, Aaron J. Grier wrote:
> > there exist VESA text modes; perhaps this is confusing you?
> 
> Uh, no.  Your strange idea that the limitiations of the code currently
> in the tree somehow represent a design ideal rather than a design
> mistake, on the other hand -- that really _does_ confuse me.

I assume the _FB_ in vesafb stands for framebuffer.

     vesafb -- VESA framebuffer device driver for wscons

apparently I'm not the only one who interprets it this way.

> It is not exactly clear to me why you think (as evinced above) that
> drivers with 'fb' in the name should omit support for character-cell
> modes that are mandatory features of the hardware in question...

how dumb I am to mix up vesafb up with the vesa driver, which provides
both framebuffer and textmode access.

now where can I find this magical vesa driver which supports both
accelerated text and framebuffer modes in the tree?

-- 
  Aaron J. Grier | "Not your ordinary poofy goof." | agrier@poofygoof.com
              "silly brewer, saaz are for pils!"  --  virt