Re:kgicon questions
I've got the same setup. vesafb works for me up to 1024x768@16bpp and 1280x1024@8bpp From my experimenting with kgicon you have to compile kgicon with a specific monitor configured. Then run: insmod kgicon.o kgicon_bpp=16 kgicon_width=1024 kgicon_height=768 ; con2fbmap 0 number The number is the next free number is in /proc/fb before you insmod the kgicon driver. Unfortunately it hasn't been very stable for me yet, but I am experimenting. With generic monitor you may need to do something like: insmod kgicon.o blah... ; setmon ; con2fbmap I don't know I haven't try it yet. Hope it helps, Tim Reply Separator Subject:kgicon questions Author: [EMAIL PROTECTED] Date: 12/16/99 12:54 PM Hi, I'm trying to get a kgicon fb running. I have a Cyrix MediaGX board with the 5530 chipset. I can get the kernel vesafb to run in 640x480x8 with no problems. If I configure kgicon and build for the GX and try 'insmod kigocon.o' the screen displays a bunch of dots on all virtual consoles. If I configure kgicon and build for VGA and insmod, then con2fbmap, it appears the new fb takes over but only the top 2-3 inches of the display are refreshed. My real goal is to get 1024x768x16, but the vesafb doesn't seem to work quite right with these settings. Any ideas? Thanks Kyle Harris [EMAIL PROTECTED]
Re:kgicon questions
I have done a bit more experimenting and have got kgicon to work semi-normally. compile kgicon with generic monitor driver. then run: insmod kgicon.o ; fbset 0 number number is the same as in the previous email. then you can run setmon and fbset I think. Unfortunately I have not been able to get fbset to work, but that is the topic of another email. Tim Reply Separator Subject:kgicon questions Author: [EMAIL PROTECTED] Date: 12/16/99 12:54 PM Hi, I'm trying to get a kgicon fb running. I have a Cyrix MediaGX board with the 5530 chipset. I can get the kernel vesafb to run in 640x480x8 with no problems. If I configure kgicon and build for the GX and try 'insmod kigocon.o' the screen displays a bunch of dots on all virtual consoles. If I configure kgicon and build for VGA and insmod, then con2fbmap, it appears the new fb takes over but only the top 2-3 inches of the display are refreshed. My real goal is to get 1024x768x16, but the vesafb doesn't seem to work quite right with these settings. Any ideas? Thanks Kyle Harris [EMAIL PROTECTED]
Inserting visuals into other apps.
Hi, I'm trying to start tinking on inserting GGL games into X applications, and if I'm right this would be very easy because you allow parameters in the display-x target. I need two different things, for one side, to call ggi routines from (for example) a GTK application to draw into a GTK DrawingArea, and for another side, I need to call an independent GGL/GGI program changing the environment variable GGI_DISPLAY. I don0t know how I can do the first thing, but for the second one, as it's said at the libggi manpage, I should use "display-x: -inwin window id". It doesn't run at all. -inroot yes, but -inwin not, ggiOpen returns an error code. Anybody can help me, please? -- In the beggining, Turing created the machine... _ /_) \/ / / email: mailto:[EMAIL PROTECTED] / \ / (_/ www : http://programacion.mundivia.es/ryu [ GGL developer ] [ IRCore developer ] [ GPUL member ]
Re: Win32 port.
- Original Message - From: John Fortin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, December 20, 1999 1:23 PM Subject: Re: Win32 port. You need to use mingw32. I needed to stay away from using cygwin1.dll for licensing reasons. However, the snapshot is really old at this point. I have changed it alot, and added gii support, which I am debugging. There are some things to be done. - I have to fix the 8-bit support. - Occasional trapping during initialization. - Verify keyboard mapping... I also need to create an NT version. The current version will only run on win95/98/2K. Is this due to DirectX issues? Are you using features specific to DirectX 6 or higher? (DirectX 7.0 is supported on 2k, right?) I'd likely be working in NT 4.0. Jeff
Re: If i want working GGI dual headed support, what video card shouldi buy?
On Mon, 20 Dec 1999, Firstname Lastname wrote: I'm going to try a differnt approach at this. I'd like to get dual headed GGI support and am willing to buy a video card to do so. What video card should i buy? If only multihead and not new, fast, accelerated multihead is your goal, just get an old PCI Matrox Millenium and an ald ISA VGA card of any type and go MMIO-only on the matrox. You can also easily add a monochrome 8bit card to multihead on any linux system. The kernel supports it already. I've notice that matrox has a dual headed card, which imagine works with itself :), and that the matrox seem to be more supported then the other cards. would that be the card to get? If they've got the docs, and also if someone is willing to write the driver code to make it all work. It won't be a walk in the park, I dare say. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed
Re: Inserting visuals into other apps.
Rubén [EMAIL PROTECTED] writes: I'm trying to start tinking on inserting GGL games into X applications, and if I'm right this would be very easy because you allow parameters in the display-x target. I need two different things, for one side, to call ggi routines from (for example) a GTK application to draw into a GTK DrawingArea, If you can get the window-ID of the GTK DrawingArea you can just open an X or Xlib visual with the apropriate -inwin parameter and draw onto that. Otherwise you'd have to write a special GTK target which uses GTK functions to do the drawing. If GTK supports blitting images from a shared memory segment you can also attach a memory visual to such a segment and draw into that. and for another side, I need to call an independent GGL/GGI program changing the environment variable GGI_DISPLAY. I don0t know how I can do the first thing, but for the second one, as it's said at the libggi manpage, I should use "display-x: -inwin window id". It doesn't run at all. -inroot yes, but -inwin not, ggiOpen returns an error code. Oh, you actually found a documentation bug. The correct usage is "display-x:-inwin=window id", and docs have now been updated accordingly. //Marcus -- ---+ Marcus Sundberg| http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: [EMAIL PROTECTED]
Re: If i want working GGI dual headed support, what video card shouldi buy?
I've notice that matrox has a dual headed card, which imagine works with itself :), and that the matrox seem to be more supported then the other cards. would that be the card to get? If they've got the docs, and also if someone is willing to write the driver code to make it all work. It won't be a walk in the park, I dare say. Their is developement patch that I heard was working pretty good. In fact I'm including a piece of the patch (whats not in matroxfb.c into the next developement kernel release. Go to http://www.linux-fbdev.org and follow the Driver Sites Matrox section.
