Grx

grx@gnu.de

559 discussions

update 1 for GRX 2.3.4
by Mariano Alvarez Fernandez 28 Feb '01

28 Feb '01

Hi all: This is a prerelease of an update to GRX 2.3.4, it solves the SVGALIB problem and some other bugs. Please test it if you can. http://www.terra.es/personal/malfer/zipfiles/update1.zip

1 1

SVGALIB problem
by Mariano Alvarez Fernandez 26 Feb '01

26 Feb '01

Hi all: I have found the problem, but not solved yet :-( This is the init code in the svgalib.c video driver: ---------------- static int init(char *options) { if(detect()) { char *frame = NULL; vga_modeinfo *mdinfo; GrVideoMode mode,*modep = &modes[1]; GrVideoModeExt ext, *extp = &exts[0]; int mindex; memzero(modep,(sizeof(modes) - sizeof(modes[0]))); for(mindex = G320x200x16; mindex <= GLASTMODE; mindex++) { if(!(vga_hasmode(mindex))) continue; if(!(mdinfo = vga_getmodeinfo(mindex))) continue; if(!(build_video_mode(mdinfo,&mode,&ext))) continue; if(frame == NULL) { #if 0 /* paranoid hack to really make sure... */ long endmem = (long)(sbrk(0)); if((endmem & 0xffffL) != 0) { brk((void *)((endmem + 0xffffL) & ~0xffffL)); } #endif vga_setmode(mindex); if (ext.flags & GR_VMODEF_LINEAR) vga_setlinearaddressing(); frame = (char *)vga_getgraphmem(); vga_setmode(initmode); } mode.mode = mindex; ext.frame = frame; add_video_mode(&mode,&ext,&modep,&extp); } _GrVideoDriverSVGALIB.adapter = isEGA ? GR_EGA : GR_VGA; return(TRUE); } return(FALSE); } -------------------- The problem: GRX needs ext.frame to be set in advance for all video modes. But with Svgalib GRX needs to set the videomode to get the pointer. GRX assumes ext.frame is the same for all modes, but is not true for the newest video cards. I had make a try, setting the videomode (vga_setmode) for every mode and getting the frame pointer. It works, and "demogrx" runs in 16bpp OK. But it takes a lot to start, and probably is not a good idea to set all video modes consecutive. So, any one knows how to get the frame pointer without set the video mode?

3 4

[Fwd: Re: Problem installing grx]
by Mariano Alvarez Fernandez 23 Feb '01

23 Feb '01

-------- Original Message -------- Asunto: Re: Problem installing grx Fecha: Fri, 23 Feb 2001 01:11:41 +0100 De: Mariano Alvarez Fernandez <malfer(a)teleline.es> A: Markus Gerwinski <markus(a)gerwinski.de> Referencias: <20010222230858.A451@plato> Markus Gerwinski escribió: > Hi folks! > > Got an undocumented problem when installing and compiling GRX 2.3.4 for the > linux shell on my computer: When running the demogrx program (as told in the > readme file), it only yielded a segfault. > > I also tried the modetest program from the grx/bin directory, and I got > these results: I noticed the same in my PII 350 with a Vodoo 3 AGP running Linux Mandrake 7.1,color modes other than 4 bpp don't work (change gfaz.c to use 4bpp and demogrx works). I tried previous versions of GRX with the same results. I thougth my graphics card was not supported by svgalib, because demogrx works nicely in my old P75 with a S3 card running Linux Mandrake 6.2. I don't know if it's a svgalib bug with AGP cards or a GRX bug. Really I don't know very much about svgalib.

1 0

Problem installing grx
by Markus Gerwinski 22 Feb '01

22 Feb '01

Hi folks! Got an undocumented problem when installing and compiling GRX 2.3.4 for the linux shell on my computer: When running the demogrx program (as told in the readme file), it only yielded a segfault. I also tried the modetest program from the grx/bin directory, and I got these results: Modes 1 - 2: Completely black and blue, only the top-left rectangle contains structures, the other ones are empty. 3 - 11: Four different-colored rectangles with structures. 12: Segmentation Fault, when called after the others; when called as the first one: "svgalib: mmap error in linear background memory." 13: Like 3 - 11. 14 - 60: Segmentation Fault. 61: Segmentation Fault, when called as the first one. When called after e.g. 62, there are two large (full-screenwidth) blue rectangles at the bottom and in the middle of the screen. 62 - 73: Two large (full-screenwidth) blue rectangles at the bottom and in the middle of the screen. As for my hardware, I'm running an Intel Celeron 433 (64 MB RAM) with an AGP graphics card (8 MB). Any advice how to get GRX running here? Thanks in advance Markus

1 0

bug in grx234s
by Maurice Lombardi 22 Feb '01

22 Feb '01

Hi all, I have just downloaded compiled and tested grx234s.zip from simtelnet I have found a bug in __gr_text_installfont() contained in src/bgi/text1.c which prevents the loading of chr files. Comparing with grx-2.3.1 it is due to an error in an attempt to sanitize the last parameter (char *name) to make it const. In the old version it was modified in the function and pointed after exit to an invalid (freed) location. But one needs an other temporary pointer temp1 to keep the addresss of the origin of the temporary buffer allocated by temp, and pass temp1 to fopen(). After the while loop temp itself points to the end of the buffer ! The error is corrected by the following diff diff -p -N -C3 -r grx234.ori/src/bgi/text1.c grx234/src/bgi/text1.c *** grx234.ori/src/bgi/text1.c Fri Jan 12 14:43:28 2001 --- grx234/src/bgi/text1.c Wed Feb 21 18:23:14 2001 *************** int __gr_text_installfont( int start, in *** 67,72 **** --- 67,73 ---- void *font; int res; char *temp = alloca(strlen(name)+1+4); + char *temp1; #ifdef __linux__ # define CHG_CHAR '\\' *************** int __gr_text_installfont( int start, in *** 79,85 **** if (temp != NULL) { int have_ext = FALSE; strcpy(temp, name); ! name = temp; while (*temp != '\0') { if (*temp == CHG_CHAR) *temp = NEW_CHAR; else *temp = (tolower)(*temp); --- 80,86 ---- if (temp != NULL) { int have_ext = FALSE; strcpy(temp, name); ! temp1 = temp; while (*temp != '\0') { if (*temp == CHG_CHAR) *temp = NEW_CHAR; else *temp = (tolower)(*temp); *************** int __gr_text_installfont( int start, in *** 88,97 **** ++temp; } if (!have_ext) ! strcat(temp, ".chr"); } ! ff = fopen(temp, "rb"); if (ff == NULL) return grFileNotFound; fseek( ff, 0, SEEK_END); --- 89,98 ---- ++temp; } if (!have_ext) ! strcat(temp1, ".chr"); } ! ff = fopen(temp1, "rb"); if (ff == NULL) return grFileNotFound; fseek( ff, 0, SEEK_END); I have also corrected some pascal files: bgi2grx.pas it is necessary to correct the drawpoly and fillpoly declarations: var PolyPoints: array of PointType while being logical in pascal is wrong in an interface to C for an open array: gpc adds some invisible parameter(s) in addition to the address of the beginning of the array, which are not contained in the C parameters. The solution is to use an untyped variable: var PolyPoints I have also made some changes to make this file compile with more recent versions of gpc (change in declaration of external variables, removal of now invalid __soso__ declarations) A diff containing these corrections, some other sanitizations, and makefiles for dj2 in the pascal directories, as well as the above diff can be retrieved at ftp://agnes.dida.physik.uni-essen.de/home/maurice/grx234.diff hope this helps Maurice -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice.Lombardi@ujf-grenoble.fr

2 1

Re: Rules for XOR
by J-P Stacey 22 Feb '01

22 Feb '01

(Apologies for lateness in reply: work has intervened!) On Sun, 18 Feb 2001, Mariano Alvarez Fernandez wrote: )By example in 16 color you have 16 index to colors. If you perform 1 XOR 2 you )obtain index color 3. Now, if you don't have assigned the index color 3 what )color is it?. Te answer is "undefined". A-ha. So as long as I define 2^n colours, everything behaves as expected? Does undefined refer to weird library behaviour, or is there a default behaviour for undefined colours? I don't expect this to be a problem, as I will probably just use EGA emulation for the time being: I just ask for information :) J-P -- 1. Behold the wisdom of MARKET: it is duty of us to serve MARKET, and to buy, and to fight UNION, and it is the duty of the tribes to serve the Number Beast and to serve the Others, the Shareholders.

2 1

Trade Printing Referral Service
by PRINTHOTLINE 18 Feb '01

18 Feb '01

INTRODUCING PRINTHOTLINE Trade printing and graphics referral service. Printing Distributors and Resellers Whether you are a printer that uses other printers for work you do not produce in-house, whether you are a graphic design firm, an advertising agency or a print broker, PRINTHOTLINE will make your job easier. PRINTHOTLINE is created to assist in the outsourcing of printing and graphics services. If you would rather spend your time getting new customers, visit us on www.printhotline.com and let us refer you to qualified trade printing and graphics companies. We realize the importance of establishing relationships with quality vendors and that is why we introduce you to qualified trade printing companies and allow you to work directly with these companies so that you can form long-term relationships with them. Our role is strictly in the referral process, once the project begins, distributor and manufacturer work directly with one another. Trade Printing and Graphics Manufacturers When it comes acquiring new customers, being a trade printing or graphics company can have its difficulties. Having the same avenues of promoting your business, whether through journals or word of mouth, the choices are very limited. For a fraction of advertising in printing journals, PRINTHOTLINE provides an alternative marketing medium. PRINTHOTLINE now has several options through which you can partner with us. Whether you like to pay per job or whether you prefer a flat annual listing fee, we have created our new PRINTHOTLINE partnership arrangements with feedback from trade printing providers from all facets of our industry. If you want continuous leads for new business, chances are we have a partnership option for you. For more information visit www.printhotline.com or call 1-877-447-HOTLINE for additional details.

1 0

Bug catched
by Mariano Alvarez Fernandez 17 Feb '01

17 Feb '01

Hi all. From the GRX 2.3 version GrLoadFont didn'nt worked with BGI fonts. To fix the problem change in fonts/fdv_bgi.h and fonts/fdv_bgi.c lines with: #ifdef BIG_ENDIAN by: #if BYTE_ORDER==BIG_ENDIAN and GrLoadFont will work nicely with Bgi fonts.

2 2

Wish list & ram4 & Win32
by Josu Onandia 14 Feb '01

14 Feb '01

Hi everybody, - For the wish list: A more compact representation of fixed-width fonts. A font definition has a pointer for every character. If the characters have a fixed with, and are contiguous, the pointer table is a waste. And as I have a font with nearly 20,000 characters, then I'm simply not allowed to have 20,000x4 bytes of wasted space. I use a font representation without pointer table, wich I could submit if you find it useful. - I'm started using the Win32 driver from Peter Gerwinski. I'm very pleased with it (thanks Peter). But I'm having some problems with the colors: when I do a bitblt from the screen to memory and then back to screen some colors are lost. Perhaps it's a problem with the palette, I don't know, I'm working on it right now. - The frame driver I've written (I call it ram4n, for 'non-planar') is not an improvement over the standard ram4 driver. Both of them use 4 bits to represent a pixel, but they are different in the physical organization of those 4 bits. -The standard driver has 4 planes (R G B and bright, if I'm not wrong), and a pixel has one bit in each of the planes. For example, to know a pixel's color, you have to read one byte for plane, pick the bit you are interested in, and then reassemble the 4 bits in a GrColor variable. This is a very nonintuitive and slow way of manipulating pixels. It's advantage is that tha VGA hardware is structured that way, and then pixel manipulation becomes very quick (for a video context, not for an in-memory context). - My ram4n driver has only one plane, and the 4 bits of a pixel are contiguous, that is, in every byte there are 2 pixels. To manipulate a pixel you read a byte, change the upper or lower 4 bits, and write it back to memory. Although this organization is unusual in PCs, I've seen it in other graphics systems that are not VGA. In fact I use it in a PowerPC 823. And that's all. Sorry for the verbosity :-) Greetings, Josu

1 0

Wish list
by Mariano Alvarez Fernandez 14 Feb '01

14 Feb '01

Hi. I want to make a GRX wish list for future releases, here are the mines: New targets: - Win32 (I'm working on this) - DirectX (on Windows) - Frame buffer (on Linux) Docs: - Reference guide. - Frame/Video driver desingn. - Font drivers internals. Other: - Driverized input (so Linux targets could be merged) - Better fonts. - Free repacement for bgi fonts. Please add your wishes, or if you can, pick one. Greetings, M.Alvarez

2 2

← Newer
1
...
39
40
41
42
43
44
45
...
56
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

Grx