*BSD News Article 76055


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!news.vbc.net!samba.rahul.net!rahul.net!a2i!bug.rahul.net!rahul.net!a2i!ddsw1!news.mcs.net!van-bc!news.rmii.com!usenet
From: roell@xinside.com (Thomas Roell)
Newsgroups: comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.x,comp.os.linux.hardware,comp.os.linux.setup,comp.unix.bsd.386bsd.misc,comp.unix.bsd.bsdi.misc,comp.unix.bsd.netbsd.misc,comp.unix.bsd.freebsd.misc,misc.consumers
Subject: Re: Why not buy Matrox Millennium
Date: 13 Aug 1996 09:31:32 -0600
Organization: X Inside Inc.
Lines: 43
Sender: roell@xeno.xinside.com
Message-ID: <8720hb712j.fsf@xeno.xinside.com>
References: <4j21ph$crr@slappy.cs.utexas.edu>
	<873f1tjxf1.fsf@xeno.xinside.com>
	<4uopgf$si4@cantaloupe.srv.cs.cmu.edu>
NNTP-Posting-Host: fog.xinside.com
In-reply-to: jmcc@m5.vi.ri.cmu.edu's message of 13 Aug 1996 02:32:47 GMT
X-Newsreader: Gnus v5.1
Xref: euryale.cc.adfa.oz.au comp.os.linux.development.apps:20302 comp.os.linux.development.system:29679 comp.os.linux.x:37877 comp.os.linux.hardware:47399 comp.os.linux.setup:68474 comp.unix.bsd.386bsd.misc:1038 comp.unix.bsd.bsdi.misc:4600 comp.unix.bsd.netbsd.misc:4385 comp.unix.bsd.freebsd.misc:25404 misc.consumers:94303

In article <4uopgf$si4@cantaloupe.srv.cs.cmu.edu> jmcc@m5.vi.ri.cmu.edu (Jason Mcmullan) writes:

>     * Make sure user has the 'FooBar' chipset like he told me..

That code is alredy in place.

>     * Do the X thang...
>       - VT Switch TIME!
>	 * What size of screen did the user tell me he used? (XxY)
>	 * Set card to that screen mode if possible, 80x25 otherwise
>	 * ioctl(vt_Device,VT_RESIZEX,..) /* See include/linux/vt.h */

I am thinking along this line ;-) However the code the sets a text
mode would really belong into a kernel device driver. LINUX right now
uses a dirty hack to abuse the normal BIOS to set the text mode
initially during the boot phase. 

>     Unless the video support that you have in you loadable modules
>   (vgaSetText, from nm(1)) is inadequite to the task of arbitray 
>   resizing, I would say you're all set to support the diehard
>   115x91 fans...

*smile* You are almost right. vgaSetText() however gets no parameter
passed in the say which textmode is to be restored (actually it is not
vgaSetText(), but XXXSetText() (like et6000SetText()), which then in
turn usually calls vgaSetText() to initialize standard VGA
registers). Adding such a parameter would mean to break binary
compatibility with the loadable modules.


Actually given the upper idea about moving stuff like this into a
kernel driver anyway raises the question for me, why to use a textmode
at all. Why not simply switch into a graphics mode, and draw bitmap
characters directly. Sun SPARC is doing that, all the PowerPCs are
doing that as well ...

- Thomas

-- 
Denver Office               THOMAS ROELL        /\      Das Reh springt hoch,
+1(303)298-7478             X INSIDE INC       /  \/\   das Reh springt weit,
1801 Broadway, Suite 1710                     /    \ \/\     was soll es tun,
Denver, CO 80202          roell@xinside.com  / Oelch! \ \     es hat ja Zeit.