RE: FW: problems over matrox fb
I'm sorry but that is not real distribution. Simly add -I./.. -Original Message- From: James Simmons [mailto:[EMAIL PROTECTED]] Sent: Saturday, November 06, 1999 22:56 To: Dmitry Semenov Cc: [EMAIL PROTECTED] Subject: Re: FW: problems over matrox fb I just tried to compile wip-0.1. Here is the error I get. make[4]: Entering directory `/home/jsimmons/wip-0.1/wip/fonts' c++ -DHAVE_CONFIG_H -I. -I. -I../.. -g -O2 -c wipmc.cpp wipmc.cpp:19: wip.h: No such file or directory "We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. It made something better, linux :)"
FW: problems over matrox fb
Hi I've just tested vesafb. I've found no problems. So I believe there is a bug inside of some acceleration function(s). The question is where is it, in GGI or matroxfb or my G100 board? If any one has matrox board working with accelerator matroxfb please test ggiDrawBox and ggiDrawLine in 16 bit 1024x768 F2 mode. Write frame should be invisible, read frame is opposite, please use clipping 0, 0, 1027, 768 and draw functions arguments like these -10, 10, 200, 200. Flip it and see results after drawing. I do believe the problem is when using the other settings as well, but these settings have problems exactly at least for my board. I use the May release version of ggi. If this is my mistake please let me know:) Dmitry -Original Message- From: Dmitry Semenov [mailto:[EMAIL PROTECTED]] Sent: Monday, November 01, 1999 2:42 PM To: [EMAIL PROTECTED] Subject: FW: problems over matrox fb I'm sorry to send this message ones more. I still have no any answer. Additional info. I use Matrox G100 with 4meg memory May be is a good idea to add an accelerator functions trigger in GGI interface to give possibility to switch off some accelerator function in case of bad hardware. Best regards. Dmitry -Original Message- From: Dmitry Semenov [mailto:[EMAIL PROTECTED]] Sent: Friday, October 29, 1999 4:17 PM To: [EMAIL PROTECTED] Subject: problems over matrox fb Hi I'm sorry if this is well known problem I use LibGGI 2.0beta2 I've just tested some ggi drawing function over matrox fb. I tested 1024x768 F2 with full screen clipping and also partly screen clipping(something like 10, 0, 1024, 768). I've found that DrawLine and DrawBox(at least) function have problems when first (at least) coordinate X is negative. Sample: ggiDrawLine(-10, 20, 90, 120); ggiDrawBox(-10, 20, 100, 100); line left top end is pointed somewhere else -10, 20 Box disappeared from the screen I have no problem with X target. I never tested vesafb. Best regards, Dmitry
Re: FW: problems over matrox fb
Do you have this piece of code? Could you send it to me so I can compile it and test this problem? "We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true. It made something better, linux :)" On Mon, 1 Nov 1999, Dmitry Semenov wrote: I'm sorry to send this message ones more. I still have no any answer. Additional info. I use Matrox G100 with 4meg memory May be is a good idea to add an accelerator functions trigger in GGI interface to give possibility to switch off some accelerator function in case of bad hardware. Best regards. Dmitry -Original Message- From: Dmitry Semenov [mailto:[EMAIL PROTECTED]] Sent: Friday, October 29, 1999 4:17 PM To: [EMAIL PROTECTED] Subject: problems over matrox fb Hi I'm sorry if this is well known problem I use LibGGI 2.0beta2 I've just tested some ggi drawing function over matrox fb. I tested 1024x768 F2 with full screen clipping and also partly screen clipping(something like 10, 0, 1024, 768). I've found that DrawLine and DrawBox(at least) function have problems when first (at least) coordinate X is negative. Sample: ggiDrawLine(-10, 20, 90, 120); ggiDrawBox(-10, 20, 100, 100); line left top end is pointed somewhere else -10, 20 Box disappeared from the screen I have no problem with X target. I never tested vesafb. Best regards, Dmitry
FW: problems over matrox fb
I'm sorry to send this message ones more. I still have no any answer. Additional info. I use Matrox G100 with 4meg memory May be is a good idea to add an accelerator functions trigger in GGI interface to give possibility to switch off some accelerator function in case of bad hardware. Best regards. Dmitry -Original Message- From: Dmitry Semenov [mailto:[EMAIL PROTECTED]] Sent: Friday, October 29, 1999 4:17 PM To: [EMAIL PROTECTED] Subject: problems over matrox fb Hi I'm sorry if this is well known problem I use LibGGI 2.0beta2 I've just tested some ggi drawing function over matrox fb. I tested 1024x768 F2 with full screen clipping and also partly screen clipping(something like 10, 0, 1024, 768). I've found that DrawLine and DrawBox(at least) function have problems when first (at least) coordinate X is negative. Sample: ggiDrawLine(-10, 20, 90, 120); ggiDrawBox(-10, 20, 100, 100); line left top end is pointed somewhere else -10, 20 Box disappeared from the screen I have no problem with X target. I never tested vesafb. Best regards, Dmitry
Re: FW: problems over matrox fb
Hi ! I've just tested vesafb. I've found no problems. So I believe there is a bug inside of some acceleration function(s). The question is where is it, in GGI or matroxfb or my G100 board? Well basically it is probably the GGI lib that accesses the matroxfb not checking for conditions the G100 chip will not handle gracefully in hardware. You might want to try disabling the matrox acceleration driver in /etc/ggi/targets/fbdev.conf . CU, ANdy -- = Andreas Beck| Email : [EMAIL PROTECTED] =
RE: FW: problems over matrox fb
Ok Thanks, It's not a big problem. Just now I've added support for back buffer additionally to paging mode. GGI default functions work well. Best regards, Dmitry -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, November 05, 1999 2:22 AM To: [EMAIL PROTECTED] Subject: Re: FW: problems over matrox fb Hi ! I've just tested vesafb. I've found no problems. So I believe there is a bug inside of some acceleration function(s). The question is where is it, in GGI or matroxfb or my G100 board? Well basically it is probably the GGI lib that accesses the matroxfb not checking for conditions the G100 chip will not handle gracefully in hardware. You might want to try disabling the matrox acceleration driver in /etc/ggi/targets/fbdev.conf . CU, ANdy -- = Andreas Beck| Email : [EMAIL PROTECTED] =
