Date: Sun, 8 Oct 1995 22:01:00 +0100 (MET) From: Didier Derny <didier@aida.org> To: Julian Elischer <julian@ref.tfs.com> Cc: joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org Subject: Re: direct acces to the text screen memory Message-ID: <Pine.BSF.3.91.951008215806.240A-100000@aida> In-Reply-To: <199510082038.NAA13827@ref.tfs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Oct 1995, Julian Elischer wrote: > > > > As Didier Derny wrote: > > > > > > Is there any way to write directly in the text screen memory. > > > > > > I'm writing a commodore 8000 emulation and the use of ANSI sequences > > > to write in the screen is extremely slow. > > for this sort of thing it starts to become attractive to run a local frame > buffer in the program and do totoal screen updates every now and then.. > (I guess you could say that this is what curses does..) > > > > There is a way (you could mmap() the frame buffer), but using > > something like curses is strongly recommended instead. This way, your > > emulation will automagically also run inside an xterm or on a serial > > terminal. > > > > -- > > cheers, J"org > > > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > > Never trust an operating system you don't have sources for. ;-) > > > > The Commodore 8032 directly write in the screen memory. I transform the write operation to the screen memory by an optimized ANSI sequences everything works fine but when the Commodore scroll the screen the entire screen update becomes very slow since it rewrite the entire screen. How can I map the text screen ? -- Didier Derny didier@aida.org --- I boycott everything from: new zealand, australia, denmark, england
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.951008215806.240A-100000>