> > > /usr/doc/linux/Documentation/fb/vesafb.txt on how to do this.
> > That's a distribution specific path.
No - it's simply a wrong path. Freudian I'd say. It is corrected in CVS.
Noticed it as soon as I got my post back from the list.
> Right. Andy has the RH distribution. I have the SuSE distribution.
> In RH it is in /usr/doc/linux/Documentation/fb/...
> In SuSE it is in /usr/src/linux/Documentation/fb/...
It's always in /usr/src/linux/Documentation/... at least to my knowledge.
> > > 2. It cannot switch modes. This is a VESA limitation, not a driver
> > > limitation.
> > Well, it is not a GGI limitation, but it _is_ a driver limit. I
> > think I even saw a patch to use the VESA real-mode interface to
> > switch modes.
Ouch. That's pretty sick. O.K. - what I meant, is that VESA has no protected
mode interface to switching modes, which would make changing the VESA driver
to be able to switch on the fly a major PITA.
Whoever made that patch: If it works reliably on many cards, he's got much
of what it takes to be a genius as well as much of a masochist.
Should I change the FAQ to be more precise ? The comment I made was meant to
protect the vesafb authors a little, as I can perfectly understand, why
they didn't implement modeswitching.
> Yep. You can switch between differenet VESA-modes under DOS.
Sure. BIOS is fully available there, as you usually are in real or rather
vm86 mode there.
CU, Andy
--
Andreas Beck | Email : <[EMAIL PROTECTED]>
