Grx

grx@gnu.de

559 discussions

GRX 2.4.7 pre-release 1
by Mariano Alvarez Fernandez 07 Jan '04

07 Jan '04

Hi, I have uploaded a GRX 2.4.7 pre-release. Mostly the new Dinitar's DGA driver. Get it from http://grx.gnu.de/more.html Happy new year, M.Alvarez

2 4

Re: Testing the DGA driver
by Dimitar Zhekov 04 Jan '04

04 Jan '04

MAF> Hi Dimitar. Hi. Long time no hear. MAF> I have retested your new DGA driver in 2.4.7p1 MAF> without the framebuffer: Tnanks. MAF> In my desktop with XFree86 4.2.0 I see a blak MAF> screen only. Does it work with the framebuffer enabled under the same circumstances? What's the video driver? MAF> In my Toshiba with XFree86 4.3.0: MAF> ./xdemogrx and Hey! It seems to work, but returning MAF> to X the screen was cripped to a 640*480 window. I didn't quite understood that. If the entire screen (the one before ./xdemogrx?) is now in a window, then what's on the rest of it, that is, outside that window? Empty? MAF> I managed to run "./xdemogrx 1024 768 24" and it MAF> works, but funny things happen with the input, like MAF> if you have pressed the Return key all the time. I have such a problem, but only when running xfce4. TWM and IceWM are OK - gtk+2 dependency here? Tried to solve it with absolutely no success. All DGA 1/2 examples fail the same way as well, so it's not a vd_xfdga.c error. DGA is unstable, as noted... It'll be replaced in XFree86-5. Anyone else tested that? I can send you the DGA examples. -- E-gards: Jimmy

2 1

Testing the DGA driver
by Mariano Alvarez Fernandez 30 Dec '03

30 Dec '03

Hi Dimitar. I have retested your new DGA driver in 2.4.7p1 without the framebuffer: In my desktop with XFree86 4.2.0 I see a blak screen only. In my Toshiba with XFree86 4.3.0: ./xdemogrx and Hey! It seems to work, but returning to X the screen was cripped to a 640*480 window. I managed to run "./xdemogrx 1024 768 24" and it works, but funny things happen with the input, like if you have pressed the Return key all the time. Greetings, M.Alvarez

1 0

Re: DGA driver v2 fix
by Josu Onandia 15 Dec '03

15 Dec '03

Hi, Interesting comments. Thank you. Josu > -----Mensaje original----- > De: Dimitar Zhekov [SMTP:jimmy@is-vn.bg] > Enviado el: lunes 15 de diciembre de 2003 12:24 > Para: Josu Onandia > CC: grx(a)gnu.de > Asunto: Re: DGA driver v2 fix > > Hi. > > JO> Sorry for my ignorance, > > That's allright, they're too recent. DGA driver v1 has been > included in 246, the rest currently exists only as patches. > > JO> but I haven't heard about DGA, raw driver or psf2. > JO> I use the drivers for Linux framebuffer and for ..., > JO> and I would like to know if those changes affect me. > > They won't, except that you'll be able to use psf2 fonts. > Presently only iso01-12x22, iso02-12x22 and sun12x22 are > psf2 AFAIK. My next terminus font will include 12x24 psf2. > > JO> Could you explain me something about all this? > > DGA is the XFree86 Direct Graphics Access, which operates > with or without [it's own] framebuffer [a memory pointer]. > 246's vd_xfdga.c requires that framebuffer, DGA v2 (to be > included in 247p1?) may operate without it (and w/o 4755). > > As of psf2, that's v2.0 of the Linux Console PC Screen Font > format. Allows arbitary width and height monospaced fonts > (GRX driver does, but as of 2.4.22, the console framebuffer > drivers allow only width = 8, 12 and 16 and height <= 32). > > -- > E-gards: Jimmy >

1 0

Re: DGA driver v2 fix
by Josu Onandia 15 Dec '03

15 Dec '03

Hi Dimitar, Sorry for my ignorance, but I haven't heard about DGA, raw driver or psf2. Could you explain me something about all this? I use the drivers for Linux framebuffer and for Windows, and I would like to know if those changes affect me. Thank you, Regards Josu Onandia > -----Mensaje original----- > De: Dimitar Zhekov [SMTP:jimmy@is-vn.bg] > Enviado el: viernes 12 de diciembre de 2003 14:13 > Para: grx(a)gnu.de > Asunto: DGA driver v2 fix > > Close the framebuffer if DGA is compiled with framebuffer > support, not without it. Incremential, apply after > xfdga-small-changes and dga-driver-v2. > > -- > E-gards: Jimmy <<Archivo: dga-driver-v2-fix.zip>>

2 1

DGA driver v2 fix
by Dimitar Zhekov 12 Dec '03

12 Dec '03

Close the framebuffer if DGA is compiled with framebuffer support, not without it. Incremential, apply after xfdga-small-changes and dga-driver-v2. -- E-gards: Jimmy

1 0

RAW driver v2
by Dimitar Zhekov 12 Dec '03

12 Dec '03

Version 2 of the raw driver. Support for psf2. Better support for RAW: up to 16x32, assuming width:height 1:2 (the previous code was always assuming width = 8). -- E-gards: Jimmy

1 0

mingw-gpc compilation fails
by Gábor Peintler 28 Nov '03

28 Nov '03

Hi, I tried to compile GRX 2.4.6 with pascal support threough makefile.w32, however, the creation of the executables from pascal sources was not successful. The compiler always said that there an unknown reference to WinMain@16. I used gcc3.2.3+gpc3.2.3. Does somebody have any suggestion? Regards, Gabor Peintler _________________________________________________________ Gabor Peintler University of Szeged, Institute of Physical Chemistry Address: Szeged, P.O.Box 105., H-6701, HUNGARY or Szeged, Rerrich Bela ter. 1., H-6720, HUNGARY E-mail: Peintler(a)Chem.U-Szeged.HU Phone: 36(62)544-613 FAX: 36(62)544-652 _________________________________________________________

2 1

Re: (PATCH) BUG in u_egavga.c - patch problem?
by Eugene Yavorsky 19 Nov '03

19 Nov '03

Hello, Allan! You wrote to "Eugene Yavorsky" <eugene_yavorsky(a)mail.ru> on Tue, 18 Nov 2003 20:16:52 -0500 (EST): AK> vdrivers/u_egavga.c:28: error: for each function it appears in.) AK> vdrivers/u_egavga.c:28: error: parse error before "r" AK> vdrivers/u_egavga.c:29: error: `r' undeclared (first use in this function) AK> make.exe[1]: *** [vdrivers/u_egavga.o] Error 1 AK> make.exe[1]: Leaving directory `c:/djgpp/contrib/grx246/src' AK> make.exe: *** [libs] Error 2 Posted source is not complete u_egavga.c. You must pacth your original u_egavga.c whith posted script; or edit it manually to replace line 82 of original file if(IREG_AX(r) == VESA_SUCCESS) return(TRUE); to if(IREG_AX(r) == VESA_SUCCESS){ _GrViDrvReLoadFonts(); return(TRUE); } And add this function after includes at beginning of file: void _GrViDrvReLoadFonts(void) { GRX_ENTER(); int86Regs r; sttzero(&r); // read font height to load appropriate ROM BIOS font IREG_AX(r) = 0x1130; IREG_BX(r) = 0x0000; int10(&r); IREG_BL(r) = 0x0000; if(IREG_CX(r) == 16) IREG_AX(r) = 0x1114; else if(IREG_CX(r) == 14) IREG_AX(r) = 0x1111; else if(IREG_CX(r) == 8) IREG_AX(r) = 0x1112; else{ DBGPRINTF(DBG_DRIVER, ("Strange font height = %d\n", IREG_CX(r))); GRX_RETURN(); } int10(&r); GRX_LEAVE(); } For your convenience, see attachment. With best regards, Eugene Yavorsky. E-mail: olg_eug(a)mail.i.com.ua

1 0

(PATCH) BUG in u_egavga.c - Incorrect behaviour when installed DISPLAY.SYS to display non-Latin characters
by Eugene Yavorsky 10 Nov '03

10 Nov '03

Hello, all! SYMPTOMS: When loaded driver DISPLAY.SYS to support fonts with characters from non-latin alphabets, such as Cyrillics, Hebrew, Central European, Baltic etc., after termination of GRX application, localized fonts not loaded and international characters displayed incorrectly until manual reset video mode. This happen always under TESTED SOFTWARE ENVIRONMENT: OPERATING SYSTEMS: MSDOS 7.0, 7.1; MS Windows 95, 98, SE, ME; MS Windows NT, 2000, (XP?) DISPLAY DRIVERS: DISPLAY.SYS from corresponding DOS/Windows installation (or 32-bit analog for NT family) KEYRUS - available to me alternative device driver. CAUSE: Before terminating GRX application, this library always calls setmode() to restore initial videomode, which first invoke corresponding VESA function, instead of INT 10H AH=0, as expected (and supported) by driver. SOLUTION: Forced call to INT 10H to reload ROM fonts (this function superceded by driver DISPLAY.SYS and loads localized fonts). See code below. (P.S. Excuse my terrible English. See my e-mail ;-) ======= begin "diff -c -p u_egavga.c.bak u_egavga.c" *** u_egavga.c.bak Sat Jan 20 03:11:28 2001 --- u_egavga.c Mon Nov 10 20:04:34 2003 *************** *** 22,27 **** --- 22,56 ---- #include "vesa.h" #include "memfill.h" + void _GrViDrvReLoadFonts(void) + { + GRX_ENTER(); + int86Regs r; + sttzero(&r); + + /* read font height to load appropriate ROM BIOS font */ + IREG_AX(r) = 0x1130; + IREG_BX(r) = 0x0000; + int10(&r); + + IREG_BL(r) = 0x0000; + + if(IREG_CX(r) == 16) + IREG_AX(r) = 0x1114; + else if(IREG_CX(r) == 14) + IREG_AX(r) = 0x1111; + else if(IREG_CX(r) == 8) + IREG_AX(r) = 0x1112; + else{ + DBGPRINTF(DBG_DRIVER, ("Strange font height = %d\n", IREG_CX(r))); + GRX_RETURN(); + } + + int10(&r); + + GRX_LEAVE(); + } + int _GrViDrvDetectEGAVGA(void) { Int86Regs r; *************** static int setmode(int mode,int noclear) *** 79,85 **** IREG_AX(r) = VESA_FUNC + VESA_SET_MODE; IREG_BX(r) = (mode & 0x7fff) | (noclear ? 0x8000U : 0); int10(&r); ! if(IREG_AX(r) == VESA_SUCCESS) return(TRUE); IREG_AX(r) = (mode & 0x7f) | (noclear ? 0x80U : 0); int10(&r); return((_GrViDrvGetCurrentEGAVGAmode() == mode) ? TRUE : FALSE); --- 108,117 ---- IREG_AX(r) = VESA_FUNC + VESA_SET_MODE; IREG_BX(r) = (mode & 0x7fff) | (noclear ? 0x8000U : 0); int10(&r); ! if(IREG_AX(r) == VESA_SUCCESS){ ! _GrViDrvReLoadFonts(); ! return(TRUE); ! } IREG_AX(r) = (mode & 0x7f) | (noclear ? 0x80U : 0); int10(&r); return((_GrViDrvGetCurrentEGAVGAmode() == mode) ? TRUE : FALSE); ======= end of "diff -c -p u_egavga.c.bak u_egavga.c" With best regards, Eugene Yavorsky. E-mail: eugene_yavorsky(a)mail.ru

1 0

← Newer
1
...
15
16
17
18
19
20
21
...
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