[Prev][Next][Index][Thread]

Re: Linux + SVGALIB





On Thu, 26 Oct 1995, Mat Hostetter wrote:

> >>>>> "Ben" == Ben Lindstrom <mouring@netnet.net> writes:
>     Ben> At least if you can figure out if your are doing massives
>     Ben> amount of screen graphics...lock the VT terminal focus.  =)
> 
> I think your suggestion is a good one, even if it won't work for all
> programs we emulate.  I can lock the vc around where Executor itself
> modifies screen memory.  I wonder if locking the vc when we don't even
> own the vc causes our process to stop until we have regained the vc?
> 
> We do hardward accelerated rect fills under svgalib...I wonder if
> switching vc's after such an operation has been started could cause
> problems.
> 
What mainly the problem seems to be occuring it turns the cursor black.
Which almost gives me the feeling that some section of memory is being
blanked out when you leave a VC.  I don't think it's a SVGALib problem
since Doom and Abuse both work just fine switching in and out of their
VCs.  Maybe the video display is not being saved correctly under vgagl?

I don't know..=)  I'm doing SVGALib work and it's REALLY poorly documented
and I personally wish there was a better solution. (Note: I did see a 
comment about a another SVGA type library that had DOS/Linux support.  I
don't remeber the name of it nor how good it is.)

> I am also concerned that switching vc's to X windows will cause
> problems because Executor still owns the mouse and keyboard devices.
> Hmmm.

I've never had problems with most software VC mouse/keyboard/graphics 
software when switching between X and VC...Had not tried it with Executor.

Oh well..If I'm stuck using Executor under SVGALib in one VC...I can live
with it for a while. =)


References: