From owner-freebsd-hackers Mon May 17 11:57: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id DA8B6150BB for ; Mon, 17 May 1999 11:55:52 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id UAA58801; Mon, 17 May 1999 20:55:41 +0200 (CEST) (envelope-from des) To: Kazutaka YOKOTA Cc: Dag-Erling Smorgrav , Kelly Yancey , freebsd-hackers@freebsd.org Subject: Re: modex support (again) References: <199905171637.BAA01434@zodiac.mech.utsunomiya-u.ac.jp> From: Dag-Erling Smorgrav Date: 17 May 1999 20:55:40 +0200 In-Reply-To: Kazutaka YOKOTA's message of "Tue, 18 May 1999 01:37:53 +0900" Message-ID: Lines: 23 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA writes: > In that sense, the support for 320x240 mode-X is minimal too. The > driver can set up this mode, but has no knowledge or code to write to > it. It is entirely up to the userland program to update the video > buffer. (And it is true that there is very little use to this mode at > the moment as we haven't seen anybody using it...) I believe the video_info_t etc. structures aren't able to accurately describe how to address mode X. The graphics code in the graphical screen savers and the splash screen decoders is written in such a way that it does not care if the current mode is linear or windowed (a linear frame buffer is a windowed frame buffer with a window size large enough to hold the entire screen). Extending this code to work with mode X is not trivial; you either have to write a separate drawing function for mode X, or put so much magic in your drawing function that it will bog down to something like 3 fps. And you can't just look at your video_info_t and see that mode X is interlaced; you have to *know* that you're running in mode X and that mode X is interlaced. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message