From owner-freebsd-hackers Sun Oct 8 13:39:13 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA10776 for hackers-outgoing; Sun, 8 Oct 1995 13:39:13 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA10769 for ; Sun, 8 Oct 1995 13:39:08 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id NAA13827; Sun, 8 Oct 1995 13:38:29 -0700 From: Julian Elischer Message-Id: <199510082038.NAA13827@ref.tfs.com> Subject: Re: direct acces to the text screen memory To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 8 Oct 1995 13:38:29 -0700 (PDT) Cc: didier@aida.org, hackers@freebsd.org In-Reply-To: <199510080915.KAA00387@uriah.heep.sax.de> from "J Wunsch" at Oct 8, 95 10:14:59 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 828 Sender: owner-hackers@freebsd.org Precedence: bulk > > 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. ;-) >