Grx

grx@gnu.de

559 discussions

Re: grx23 under as-2.95
by pavenis＠lanet.lv 09 Sep '99

09 Sep '99

Sorry, pressed send button too early in previous mail) Now about patch. It seems to be Ok. I had to do the same when tried to build Allegro using recent binutils snapshot. Andris On 8 Sep 99, at 22:29, Ian Miller wrote: > Ahem. > > I'm using pretty much up to date binutils 2.95 > right now. I wouldn't recommend it unless it > doesn't matter to you much if your software > doesn't work. That said, they do seem to > work fine. However,... > > as 2.95 interprets a couple of GRX inline > assembler call instructions as > PC-relative and chokes on them. > as 2.81 interpreted them as absolute > calls, and this is evidently what the code > intends. > > The following simple patch, duplicated at > http://www.shelob.force9.co.uk/djgpp/grxasm.dif, > applies the * prefix to the call absolute > operands as the as 2.95 manual requires. > It works for me. > > IF IN DOUBT, DO NOT APPLY THIS PATCH > > Happy hacking, > Ian > -- > Ian Miller, Dorset, UK > > *** src/vdrivers/vesa_pm.orig.c Mon May 11 20:20:28 1998 > --- src/vdrivers/vesa_pm.c Wed Sep 8 21:41:52 1999 > *************** > *** 349,355 **** > static INLINE void PM_banking(short BX, short DX) { > __asm__ volatile ( > " pushal \n" > ! " call %3 \n" > " popal " > : /* no output */ > : "a" (0x4F05), "b" (BX), "d" (DX), > --- 349,355 ---- > static INLINE void PM_banking(short BX, short DX) { > __asm__ volatile ( > " pushal \n" > ! " call *%3 \n" > " popal " > : /* no output */ > : "a" (0x4F05), "b" (BX), "d" (DX), > *************** > *** 362,368 **** > " pushal \n" > " movw %%ax, %%es \n" > " movw $0x4f05, %%ax \n" > ! " call %3 \n" > " popal " > : /* no output */ > : "a" (es), "b" (BX), "d" (DX), > --- 362,368 ---- > " pushal \n" > " movw %%ax, %%es \n" > " movw $0x4f05, %%ax \n" > ! " call *%3 \n" > " popal " > : /* no output */ > : "a" (es), "b" (BX), "d" (DX), > > > > > >

1 0

Re: grx23 under as-2.95
by pavenis＠lanet.lv 09 Sep '99

09 Sep '99

On 8 Sep 99, at 22:29, Ian Miller wrote: > Ahem. > > I'm using pretty much up to date binutils 2.95 > right now. I wouldn't recommend it unless it > doesn't matter to you much if your software > doesn't work. That said, they do seem to > work fine. However,... > > as 2.95 interprets a couple of GRX inline > assembler call instructions as > PC-relative and chokes on them. > as 2.81 interpreted them as absolute > calls, and this is evidently what the code > intends. > > The following simple patch, duplicated at > http://www.shelob.force9.co.uk/djgpp/grxasm.dif, > applies the * prefix to the call absolute > operands as the as 2.95 manual requires. > It works for me. > > IF IN DOUBT, DO NOT APPLY THIS PATCH > > Happy hacking, > Ian > -- > Ian Miller, Dorset, UK > > *** src/vdrivers/vesa_pm.orig.c Mon May 11 20:20:28 1998 > --- src/vdrivers/vesa_pm.c Wed Sep 8 21:41:52 1999 > *************** > *** 349,355 **** > static INLINE void PM_banking(short BX, short DX) { > __asm__ volatile ( > " pushal \n" > ! " call %3 \n" > " popal " > : /* no output */ > : "a" (0x4F05), "b" (BX), "d" (DX), > --- 349,355 ---- > static INLINE void PM_banking(short BX, short DX) { > __asm__ volatile ( > " pushal \n" > ! " call *%3 \n" > " popal " > : /* no output */ > : "a" (0x4F05), "b" (BX), "d" (DX), > *************** > *** 362,368 **** > " pushal \n" > " movw %%ax, %%es \n" > " movw $0x4f05, %%ax \n" > ! " call %3 \n" > " popal " > : /* no output */ > : "a" (es), "b" (BX), "d" (DX), > --- 362,368 ---- > " pushal \n" > " movw %%ax, %%es \n" > " movw $0x4f05, %%ax \n" > ! " call *%3 \n" > " popal " > : /* no output */ > : "a" (es), "b" (BX), "d" (DX), > > > > > >

1 0

Bug report
by Josu Onandia 08 Sep '99

08 Sep '99

Hi, I believe I've found a bug in GRX. Should I post it on this mailing list, or there is someone maintaining the library and I should send it directly to him? Thanks Josu

1 0

Fwd: Re: PowerPC
by Hartmut Schirmer 05 Sep '99

05 Sep '99

Hmm, from my mail logs it looks like this never made it to the list or to Josu. Sorry, Hartmut ---------- Forwarded Message ---------- Subject: Re: PowerPC Date: Fri, 30 Jul 1999 20:27:22 +0200 From: Hartmut Schirmer <hartmut.schirmer(a)arcormail.de> On Fri, 30 Jul 1999, Josu Onandia wrote: >Hi All, > >I suscribed to this list a month ago, and I don't see a lot of mouvement on >the list, so I wonder if GRX is actually being used. If so, perhaps someone >can help me. > >I'm evaluating the possibility of porting GRX to a PowerPC, precisely to a >MPC823, which has its own on-chip graphics system. I don't need all the >possibilities of GRX, with a 8 bits per pixel frame, and off-screen bitmaps >of 1 bit per pixel will be enough. > >Any help or suggestion would be very appreciate. Well, first tweak grx20.h and add #define GRX_VERSION_GCC_MPC823 -1 // Replace GCC by your compilers name, if your stuff gets included // a unique positiv number will be assigned by the GRX maintainers Now add #if defined(__GNUC__) && defined(???) // Add the right stuff here #define GRX_VERSION GRX_VERSION_GCC_MPC823 #endif Check the definition of GrColor a few lines later Now tweak src/include/libgrx.h for your system. If you checked all setting up to /* * global library data structures */ everything should be fine Now try to set up a makefile and leave out the fdrivers, vdrivers, setup and mouse subdirs. If the highlevel parts of GRX compile, try to compile the setup dir. If youŽre still lucky, continue with the ram8.c driver from the fdrivers subdir and the vdrivers/vtable.c file. If everything worked well, you now have a GRX that can do 256 Color graphics in memory. I donŽt think teherŽs currently a test that will check rhis setup. Would be nice if you could submit one ... That was the easy part. YouŽll have to add support the the vdrivers subdir so GRX knows how to setup graphics on your system. When done, add a driver in fdrivers for readpixel and drawpixel. The rest of the functionality can be taken from src/fdrivers/generic at first Try to compile the test subdir and check if things work well. Continue by adding more functions to the frame driver, adding more color modes, mouse and keyboard-support, ... Good luck, Hartmut PS: At first, second and third view, you shouldnŽt try to figure out what all those macros inside of GRX do --- ItŽs a really big mess but very flexible for optimizing GRX. readpixel/drawpixel should work fine with the usual peek and poke macros from mempeek.h

1 0

RE: error in compiling utils/shiftscl.c
by pavenis＠lanet.lv 18 Aug '99

18 Aug '99

On 18 Aug 99, at 3:36, yu_98_98(a)my-deja.com wrote: > > > > I can only guess that You're compiling GRX-2.3 with gcc-2.95. If so > > then I can only say that gcc-2.95 no more permits to specify register > > both in init list (or result list) and clober list of inline > assembler. > > GRX-2.3 have this problem. > > > what u guess is true, I am very appreciate your help. > after unzip the gcc281b.zip, ive succeed in building the GRX 2.3 After fixing invalid inline assembler GRX-2.3 builds also with GCC-2.95. Patch is in attachment. Andris The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or any another MIME-compliant system, you should be able to save it or view it from within your mailer. If you cannot, please ask your system administrator for assistance. ---- File information ----------- File: grx23.diff1 Date: 18 Aug 1999, 14:51 Size: 2651 bytes. Type: Text

1 0

Crashing on exit
by Menno_Smits/Agsystems/AU%NTSERVER＠agsystems.com.au 06 Aug '99

06 Aug '99

1 0

PowerPC
by Josu Onandia 30 Jul '99

30 Jul '99

Hi All, I suscribed to this list a month ago, and I don't see a lot of mouvement on the list, so I wonder if GRX is actually being used. If so, perhaps someone can help me. I'm evaluating the possibility of porting GRX to a PowerPC, precisely to a MPC823, which has its own on-chip graphics system. I don't need all the possibilities of GRX, with a 8 bits per pixel frame, and off-screen bitmaps of 1 bit per pixel will be enough. Any help or suggestion would be very appreciate. Tanks. > Josu Onandia > Dpto. I+D Software. > e-mail: jonandia(a)fagorautomation.es > > ---------------------------------------------------- > Fagor Automation, S.Coop. > Barrio San Andres, s/n - P.O. Box. 144 > Mondragon 20500 - SPAIN > > http://www.fagorautomation.mcc.es >

2 1

offscreen rendering
by Joachim Euchner 13 Jul '99

13 Jul '99

Hi All, maybe I´m about to demontsrate my stupidty (again). I want to do "off-off-screen" rendering with GRX, huh, what?? Let me explain. It all works almost fine for one time: I do: GrSetDriver("memory gw 640 gh 400 nc 256"); GrSetMode(GR_default_graphics); GrContext* root = GrCurrentContext(); GrSetContext ( root ); root = GrSaveContext( NULL ); /* doing lots of drawing */ /* ... */ /* after a while, probing what has been drawn,(double-loop x,y): */ c = (*GrCurrentFrameDriver()->readpixel)((GrFrame *)(&(root)->gc_frame), ((x)), ((y)) ); /* => leads to all what is fine. */ This all works fine for one level of offscreen-drawing. Now for the bisquit: Beyond that, I would like to generate another GrContext out of the blue, make some drawings on it, off-off-screen, so to speak, and later do something like the following: GrImage img_local = GrImageFromContext(ImageGrContext_out_of_the_blue); GrImageDisplay(x, y, img_local); to smash this image onto my root-GrContext. The bisquit is this "ImageGrContext_out_of_the_blue": When not in offscreen mode (that is, having said GrSetDriver("xwin...")), it all works great when doing: ImageGrContext_out_of_the_blue = GrCreateContext(width,height,NULL,NULL); Mainly because GrCoreFrameMode() (GrDriverInfo->sdriver.rmode) leads to something usable (??). But when being in offscreen-mode, GrCoreFrameMode() yields NULL. This might be alright, but GrCreateFrameContext() depends on a valid mode, thus returning NULL for the whole function, and blocking all what should follow. Later I tried to spoof this function with ImageGrContext_out_of_the_blue = GrCreateFrameContext(19, ....); (19 is the mode I need, it seems), but this leads to SigSegv. later somewhere in the system. Many thanks in advance. greetings, Joe. -- Joachim Euchner, Prozessrechnerverbund-Zentrale Sekr.: MA 073, FSP-PV, Technische Universitaet Berlin Str. d. 17. Juni 136, 10623 Berlin, Deutschland Phone: [(+49|0)30]-314-21701 Fax: ..-21114 Email: joe(a)prz.tu-berlin.de www: www.prz.tu-berlin.de/~joe "We're going up the river about 75 klicks above the Do Lung bridge."

2 2

(no subject)
by Martin Ruskov 07 Jul '99

07 Jul '99

subscribe grx mapto(a)polbox.com ------------- [ REKLAMA / ADVERTISEMENT ] -------------- Uwaga: POPkarta o wartosci 50 zl. GRATIS. Szczegoly: http://www.pop.centertel.pl/pop/promocja.html --------------------------------------------------------

1 0

Fonts in GRX
by Cavit Cahit VURAL 18 Jun '99

18 Jun '99

Hi everybody, I am from TURKEY, ISTANBUL. I need to change some characters in GRX fonts. They are bitmap fonts. Does anyone know any utility to change them easily.

1 0

Jump to page:

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