From MAILER-DAEMON Mon Jun 7 15:33:50 1999 Date: Mon, 7 Jun 1999 15:33:50 -0400 (EDT) From: Mail System Internal Data Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA X-IMAP: 0928784030 0000000000 Status: RO This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. From ggiweb@metalab.unc.edu Tue Jun 1 04:30:46 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA00944 for ; Tue, 1 Jun 1999 04:30:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA12884; Tue, 1 Jun 1999 01:21:36 -0700 Resent-Date: Tue, 1 Jun 1999 01:21:36 -0700 Sender: Rodolphe.Ortalo@cert.fr Message-ID: <375397BB.5132@cert.fr> Date: Tue, 01 Jun 1999 10:20:11 +0200 From: Rodolphe Ortalo Organization: ONERA X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.6 sun4m) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Where's the glide target? References: <3752CDF6.84C6EBAA@uumail.de> <3752EDF5.2C792832@stacken.kth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Resent-Message-ID: <"eBLEg3.0.e83.fVvKt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13115 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg wrote: > /usr/local is the default prefix for 99% of all autoconf using packages, > so I absolutely can not see why distribution makers doesn't include > /usr/local/lib in the linker path by default... security strikes back... I guess distribution makers want system administrators to activate _themselves_ the usage of 'self-built' libraries... Adding /usr/local/lib to the default linker path is definitely NOT fool-proof (IMHO). Of course, on home machines, that's mainly an inconvenience... Rodolphe From ggiweb@metalab.unc.edu Tue Jun 1 05:00:02 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA01063 for ; Tue, 1 Jun 1999 05:00:01 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA17511; Tue, 1 Jun 1999 01:51:26 -0700 Resent-Date: Tue, 1 Jun 1999 01:51:26 -0700 Sender: marcus@e.kth.se Message-ID: <37539F07.7C7B15EB@stacken.kth.se> Date: Tue, 01 Jun 1999 08:51:19 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Where's the glide target? References: <3752CDF6.84C6EBAA@uumail.de> <3752EDF5.2C792832@stacken.kth.se> <375397BB.5132@cert.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"LNd6W1.0.MH4.DyvKt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13116 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Rodolphe Ortalo wrote: > > Marcus Sundberg wrote: > > /usr/local is the default prefix for 99% of all autoconf using packages, > > so I absolutely can not see why distribution makers doesn't include > > /usr/local/lib in the linker path by default... > > security strikes back... > I guess distribution makers want system administrators to > activate _themselves_ the usage of 'self-built' libraries... > Adding /usr/local/lib to the default linker path is definitely > NOT fool-proof (IMHO). Sorry, but that's just nonsense and an example of people who can not tell security from obscurity. /usr/lib, /usr/local/bin and /etc are not any "safer" than /usr/local/lib on a standard system. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Tue Jun 1 05:03:18 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA01073 for ; Tue, 1 Jun 1999 05:03:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA17739; Tue, 1 Jun 1999 01:54:44 -0700 Resent-Date: Tue, 1 Jun 1999 01:54:44 -0700 Sender: marcus@e.kth.se Message-ID: <37539FCE.2B388BE0@stacken.kth.se> Date: Tue, 01 Jun 1999 08:54:38 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Where's the glide target? References: <3752CDF6.84C6EBAA@uumail.de> <3752EDF5.2C792832@stacken.kth.se> <37531DB3.DA86F4FA@uumail.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"8Wht22.0.wK4.J_vKt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13117 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ben Bucksch wrote: > > Marcus Sundberg wrote: > > Yes, I did. Can't you patch this, because this is the > standard-procedure? I'll consider that for the next release. > > Only targets for which the requirements (libraries and headers) are met > > are built. Check the output of configure to see why the glide target > > is not built. > > Yes, configure says, it wouldn't build glide. Please check the entire output to see what the results of glide-related checks are. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Tue Jun 1 05:13:56 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA01144 for ; Tue, 1 Jun 1999 05:13:55 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA19036; Tue, 1 Jun 1999 02:05:17 -0700 Resent-Date: Tue, 1 Jun 1999 02:05:17 -0700 Sender: Rodolphe.Ortalo@cert.fr Message-ID: <3753A22F.1E8C@cert.fr> Date: Tue, 01 Jun 1999 11:04:47 +0200 From: Rodolphe Ortalo Organization: ONERA X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.6 sun4m) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Where's the glide target? References: <3752CDF6.84C6EBAA@uumail.de> <3752EDF5.2C792832@stacken.kth.se> <375397BB.5132@cert.fr> <37539F07.7C7B15EB@stacken.kth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Resent-Message-ID: <"XsbbP2.0.6f4.B9wKt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13118 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg wrote: > Sorry, but that's just nonsense and an example of people who can > not tell security from obscurity. > /usr/lib, /usr/local/bin and /etc are not any "safer" than > /usr/local/lib > on a standard system. Yes. But people tend to install things that they compiled themselves inside /usr/local/lib... (Again this is not a generality.) And maybe they do not always check that such libraries are not (for example) writable by someone else (a thing distrib. builders surely do [I hope ;-)] with what they put by themselves in /usr/lib.) So I GUESS distrib. makers tend not to add /usr/local/lib to the default linker path. Anyway, this is just a guess. I do not mean that this is especially 'right' from the security point of view (the real security issue is the installation procedure of shared libraries). But it may be a common habit; and I don't see it so negatively: it is pragmatic and fool-oriented, but it seems reasonable to me. Furthermore, that's a good occasion for novice admin. to learn what /etc/ld.so.conf is for... :-) Rodolphe From ggiweb@metalab.unc.edu Tue Jun 1 07:30:08 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA01943 for ; Tue, 1 Jun 1999 07:30:07 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA12416; Tue, 1 Jun 1999 04:21:30 -0700 Resent-Date: Tue, 1 Jun 1999 04:21:30 -0700 From: becka@rz.uni-duesseldorf.de Message-Id: <199906011120.NAA06692@zeus.rz.uni-duesseldorf.de> Subject: Re: Where's the glide target? In-Reply-To: <37539F07.7C7B15EB@stacken.kth.se> from Marcus Sundberg at "Jun 1, 99 08:51:19 am" To: ggi-develop@eskimo.com Date: Tue, 1 Jun 1999 13:20:17 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"--hRo2.0.k13.r8yKt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13119 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > I guess distribution makers want system administrators to > > activate _themselves_ the usage of 'self-built' libraries... > > Adding /usr/local/lib to the default linker path is definitely > > NOT fool-proof (IMHO). Why is /usr/local/bin in their default paths, then ? Waht ever the reason is - IMHO we should add a check for that in the "make install" procedure at the very end and print a big fat warning in that case. For binary distribs in RPM/DEB/whatever format one should set prefix to /usr anyway, so no problem. We already have that warnings from libtool while installing the rendering libs, but those are scrolled off the screen already, when the installation ends. CU, ANdy -- Andreas Beck | Email : From ggiweb@metalab.unc.edu Tue Jun 1 11:01:22 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA05191 for ; Tue, 1 Jun 1999 11:01:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA30969; Tue, 1 Jun 1999 07:52:19 -0700 Resent-Date: Tue, 1 Jun 1999 07:52:19 -0700 From: Thad Phetteplace Message-Id: <199906012003.PAA12831@dexter.glaci.com> Subject: Pageflip Problem To: ggi-develop@eskimo.com Date: Tue, 1 Jun 1999 15:03:18 -0500 (CDT) In-Reply-To: <19990530235646.D12808@rz.uni-duesseldorf.de> from "Andreas Beck" at May 30, 99 11:56:46 pm Content-Type: text Resent-Message-ID: <"U6fRk2.0.TZ7.VE_Kt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13120 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com This is probably a stupid question, but here goes anyway. I'm having trouble getting page flipping to work. Even the pageflip demo program fails. I think it because there is no /dev/fb* framebuffer on my linux box, thus it is falling back to svgalib or somesuch. I am running kernel 2.0.36. Do I need to upgrade my kernel? Can I just manually add the device? Am I forgetting a step in the GGI install? I've been digging through the available on-line docs but the (probably obvious) answer is not jumping out at me. Other than that the blit work is going well, when I can find time to work on it that is. Later, Thad From ggiweb@metalab.unc.edu Tue Jun 1 18:40:44 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA16058 for ; Tue, 1 Jun 1999 18:40:43 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA12199; Tue, 1 Jun 1999 15:31:14 -0700 Resent-Date: Tue, 1 Jun 1999 15:31:14 -0700 Sender: marcus@e.kth.se Message-ID: <3754541E.2E237665@stacken.kth.se> Date: Tue, 01 Jun 1999 21:43:58 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Win32 binaries References: <3751C94B.3672235B@stacken.kth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"fjFzS3.0.ao2.Ay5Lt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13121 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, Just want to inform you that Suhaib M. Siddiqi has made a binary package of LibGGI for win32 available at http://siddiqi.webjump.com/ in case someone would like to try it. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Tue Jun 1 18:40:50 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA16067 for ; Tue, 1 Jun 1999 18:40:49 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA12202; Tue, 1 Jun 1999 15:31:14 -0700 Resent-Date: Tue, 1 Jun 1999 15:31:14 -0700 Sender: marcus@e.kth.se Message-ID: <37544F4D.4974500E@stacken.kth.se> Date: Tue, 01 Jun 1999 21:23:25 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Pageflip Problem References: <199906012003.PAA12831@dexter.glaci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Qj0Wi.0.Eq2.Fy5Lt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13122 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Thad Phetteplace wrote: > > This is probably a stupid question, but here goes anyway. I'm having trouble > getting page flipping to work. Even the pageflip demo program fails. I think > it because there is no /dev/fb* framebuffer on my linux box, thus it is falling > back to svgalib or somesuch. I am running kernel 2.0.36. Do I need to > upgrade my kernel? Can I just manually add the device? Am I forgetting a > step in the GGI install? I've been digging through the available on-line docs > but the (probably obvious) answer is not jumping out at me. Other than that > the blit work is going well, when I can find time to work on it that is. Pageflipping will work if you have a target which can pageflip. Currently that includes fbdev (with a driver which supports it), glide, X, dga, and when using supported child targets: palemu, trueemu and tile. For info about framebuffer consoles (fbdev) please see /usr/src/linux/Documentation/fb/ and the Framebuffer-HOWTO. But in short, yes you need a 2.2 kernel to use framebuffers on ix86. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Tue Jun 1 18:56:01 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA16414 for ; Tue, 1 Jun 1999 18:56:00 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA22809; Tue, 1 Jun 1999 15:47:18 -0700 Resent-Date: Tue, 1 Jun 1999 15:47:18 -0700 Message-ID: X-Mailer: NailMail 1.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <37531BD8.33EBB884@stacken.kth.se> ECHELON: nuclear,Saddam,CIA,Milosevic,Clinton,dead,Plutonium,KGB,USA,bomb,terror Date: Wed, 02 Jun 1999 00:46:30 +0200 (CEST) Sender: thomas@ffii.org From: Thomas Tanner To: ggi-develop@eskimo.com Subject: Re: 346-day anniversary of seeing the stars ;) Resent-Message-ID: <"G9Qm52.0.5a5.qB6Lt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13123 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On 31-May-99 Marcus Sundberg wrote: >> > Some hints for installation: >> > Libtool doesn't handle the .exe extension on demos properly, >> What exactly does go wrong? > Don't rember excactly now, but I will check it. Basicly the automake > install target fails because libtool can't find the program. > > Btw, is there any reason why an import library for lib*.dll is generated > in every directory where something links agains lib*.dll instead of > doing it once when lib*.dll itself is built?!? Good question. I'll forward this to our libtool/cygwin maintainer. > On a related issue, the -export-symbols option is broken in current > libtool CVS because of this line (around line 2200 in ltmain.sh): > # Prepare the list of exported symbols > if test -z "$export_symbols"; then What's wrong with it? If the "export symbols" file doesn't exist libtool will generate it itself. Thomas Tanner ----------------------------------------- email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de) web: http://home.pages.de/~tanner GGI/Picasso: http://picasso.ffii.org From ggiweb@metalab.unc.edu Tue Jun 1 18:56:08 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA16418 for ; Tue, 1 Jun 1999 18:56:07 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA22852; Tue, 1 Jun 1999 15:47:23 -0700 Resent-Date: Tue, 1 Jun 1999 15:47:23 -0700 Message-ID: X-Mailer: NailMail 1.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <37531919.4D0DCE65@stacken.kth.se> ECHELON: nuclear,Saddam,CIA,Milosevic,Clinton,dead,Plutonium,KGB,USA,bomb,terror Date: Wed, 02 Jun 1999 00:46:31 +0200 (CEST) Sender: thomas@ffii.org From: Thomas Tanner To: ggi-develop@eskimo.com Subject: Re: libgii and libggi2d - can't compile it Resent-Message-ID: <"WOf5q2.0.ga5.vB6Lt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13124 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On 31-May-99 Marcus Sundberg wrote: > To clarify - if you have the libtool.m4 contents in a *.m4, where > * is != acinclude, in the cwd. > 0 ~/src/degas/lib/libggi $) aclocal -I . ... > Due to the above errors no new aclocal.m4 is generated. I see. Have you already reported this bug to automake@gnu.org? >> I recommend to add the contents of libtool.m4 of a >> recent libtool version (1.3.2) to acinclude.m4. > > Yes, it seems like we have to do that unless the automake maintainer > can be convinced to make aclocal work properly... > But it's much more convenient to have a separate libtool.m4 file > and just replace that when upgrading. Certainly, but ... >> Then no one would have to install libtool anymore. > No one have to install libtool now - on the contrary, due to said bug, > it is a requirement to _not_ have libtool installed. ;-) .. `acincluding' does always work, regardless whether libtool is installed or not :) Thomas Tanner ----------------------------------------- email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de) web: http://home.pages.de/~tanner GGI/Picasso: http://picasso.ffii.org From ggiweb@metalab.unc.edu Wed Jun 2 00:14:44 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA22304 for ; Wed, 2 Jun 1999 00:14:42 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA21212; Tue, 1 Jun 1999 21:05:46 -0700 Resent-Date: Tue, 1 Jun 1999 21:05:46 -0700 Date: Tue, 1 Jun 1999 21:05:37 -0700 (PDT) From: "Jon M. Taylor" To: GGI mailing list cc: uwe_maurer@t-online.de Subject: GGIMesa updates/questions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"2YjDH2.0.h75.MsALt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13125 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com New stuff: * ggimesa.conf is now separately installed and opened, instead of .includeing it in libggi.conf, using LibGG appropriately. * gears.c has been updated to use GGI_AUTO and renders directly to the primary display instead of rendering to a display-memory visual and then blitting to the primary visual. * linear_24.so was not implemented correctly. This should be fixed now but I do all my testing at 16bpp so I haven't had a chance to try it out yet. * The new display/ subsystem is in place and integrated into the build/install system. Currently it only contains kgi-savage4.c because there are no other accelerated GGIMesa targets in existence yet. * Misc. internal regorganization/cleanups. Questions: * I cannot seem to get kgi-savage4.so to be used by GGIMesa. ggimesa.conf maps 'display-fbdev-mesa' to the .so correctly (well it is a hack but...), so kgi-savage4.so does get loaded and its ggi_dlinit() function is called properly as well. However, in spite of the fact that display-fbdev-mesa is the last line in ggimesa.conf, ggiGetAPI() apparently insists on loading it _first_, before generic-stubs-mesa and friends. The end result is that the GGIMesa private function pointers, which were initially set correctly by kgi-savage4.so, get reset to the stub routines immediately afterward. No other extension implements both default/ and display/ subsystems, so I have no example to look at in this situation. * GGIMesa still handles the binding-together of GGI contexts (visuals) and Mesa contexts (gl_ctx structs) outside of the LibGGI system, using: GGIMesaCreateContext(), GGIMesaDestroyContext(), GGIMesaSetVisual(), GGIMesaMakeCurrent(), GGIMesaGetCurrentContext(), and GGIMesaSwapBuffers(). now, the first urge I had was to turn all of this inside-out and bind the Mesa context to the LibGGI visual instead of the reverse like it is now. That would enable me to make all those functions go away - context creation and destruction would happen in ggiMesaAttach() and friends, SetVisual() would be handled in an overloaded ggiSetMode() function, and SwapBuffers() should be handled through the normal directbuffer routines anyway. The CurrentContext() stuff is a bit trickier to remove since OpenGL is an immediate mode API and thus there is always one and only one global OpenGL context in existence. That'll have to stay, warts and all.... However, I am not sure if the above is the best course of action. It might be the case that someone will want to be able to allocate a set of Mesa contexts but only one LibGGI visual and switch the context mapping around at runtime. If the Mesa context is implemented as an extension private struct (as all(?) other extensions handle their private contexts), one would need to allocate multiple DB visuals and blit between them, which is what gears.c used to do. Not only is this a large waste of DB memory which is otherwise not needed (the GL contexts holds the world data, all the GGI visual is for is to tell it how and where to render), but it pretty much rules out a LibGGI-based multipipe direct rendering system since you wouldn't be able to render outside of a LibGGI visual context, which would force you to soft-render to the temporary buffers or block, which defeats the whole point of a DRI. Anyway, unless I am presented with or discover a nice clean way to resolve this, I think I am going to leave Uwe's API mostly unchanged. It may not be as clean as the other extensions, but it does work pretty well so far. If anyone who groks LibGGI internals better than I do could take a quick glance at the Mesa CVS code (they have anonCVS), that would be wonderful. It is time for me to go home now.... Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggiweb@metalab.unc.edu Wed Jun 2 01:40:55 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA23423 for ; Wed, 2 Jun 1999 01:40:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA12850; Tue, 1 Jun 1999 22:32:10 -0700 Resent-Date: Tue, 1 Jun 1999 22:32:10 -0700 From: Andrew Apted Message-ID: <19990602125452.15345@ajax.netspace.net.au> Date: Wed, 2 Jun 1999 12:54:52 +1000 To: ggi-develop@eskimo.com Subject: Re: Modifiers ... small problem ... opinions ? Reply-To: ggi-develop@eskimo.com References: <199905310648.IAA15924@zeus.rz.uni-duesseldorf.de> <19990531234549.60313@ajax.netspace.net.au> <3752EB75.EF173FA@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <3752EB75.EF173FA@stacken.kth.se>; from Marcus Sundberg on Mon, May 31, 1999 at 08:05:09PM +0000 Resent-Message-ID: <"67Kpn.0.P83.N7CLt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13126 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus writes: > Andrew Apted wrote: > > > > I can see the problem. Right now I can't think of any reason why the > > modifier (e.g. shift) shouldn't come into effect straight away. The > > more I think about it, the more the current behaviour seems like a bug. > > It's the way X does it and until know we have had no reason to deviate > from that. But now we do. > > > Marcus, what do you think ? > > Well, it was I who suggested the change in reflect the state after > the key event in the first place, so yes I still think it's a good > idea. ;-) Well good, we're agreed :-). Shall I make a patch, or are you (or Andy) happy to do it ? Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggiweb@metalab.unc.edu Wed Jun 2 04:32:29 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA24608 for ; Wed, 2 Jun 1999 04:32:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA09254; Wed, 2 Jun 1999 01:23:19 -0700 Resent-Date: Wed, 2 Jun 1999 01:23:19 -0700 Sender: marcus@e.kth.se Message-ID: <3754E9D7.349241AA@stacken.kth.se> Date: Wed, 02 Jun 1999 08:22:47 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: 346-day anniversary of seeing the stars ;) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"D2EdH3.0.LG2.odELt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13127 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Thomas Tanner wrote: > > On a related issue, the -export-symbols option is broken in current > > libtool CVS because of this line (around line 2200 in ltmain.sh): > > # Prepare the list of exported symbols > > if test -z "$export_symbols"; then > > What's wrong with it? If the "export symbols" file > doesn't exist libtool will generate it itself. Yes, but if it does exist the compilation will fail because $soname-ltdll.c is generated by export_symbols_cmds, which is not evaluated if export_symbols is not empty... //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Wed Jun 2 04:32:47 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA24617 for ; Wed, 2 Jun 1999 04:32:46 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA09330; Wed, 2 Jun 1999 01:24:06 -0700 Resent-Date: Wed, 2 Jun 1999 01:24:06 -0700 Sender: marcus@e.kth.se Message-ID: <3754EA05.58BC701A@stacken.kth.se> Date: Wed, 02 Jun 1999 08:23:33 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"lLu6c1.0.SH2.aeELt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13128 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > * The new display/ subsystem is in place and integrated into the > build/install system. Currently it only contains kgi-savage4.c because > there are no other accelerated GGIMesa targets in existence yet. Hmm, wonder if one could hook up the glide target with GGIMesa and Mesa3DFX... > Questions: > > * I cannot seem to get kgi-savage4.so to be used by GGIMesa. ggimesa.conf > maps 'display-fbdev-mesa' to the .so correctly (well it is a hack but...), so > kgi-savage4.so does get loaded and its ggi_dlinit() function is called > properly as well. However, in spite of the fact that display-fbdev-mesa is > the last line in ggimesa.conf, ggiGetAPI() apparently insists on loading it > _first_, before generic-stubs-mesa and friends. The end result is that the > GGIMesa private function pointers, which were initially set correctly by > kgi-savage4.so, get reset to the stub routines immediately afterward. No > other extension implements both default/ and display/ subsystems, so I > have no example to look at in this situation. After a quick look at things it's obvious that we need to make the API lists more flexible. For example it is desirable to have extensions being able to add APIs which LibGGI itself does not know or need to know about. I propose we make the API list a property of the visual (not the target as now, but the list is still initialized by the target at setmode time) and add a new internal function: _ggiAddAPI(ggi_visual_t vis, const char *api): Also when you look at a target, for example do_setmode() in display/fbdev/mode.c, you'll see that display/fbdev.so actually implements an API which comes after all the generic ones. (I'm refering to the lines: vis->opdraw->setorigin = GGI_fbdev_setorigin; vis->opdraw->setdisplayframe = GGI_fbdev_setdisplayframe; if that isn't clear.) So the complete API list after the fbdev target is loaded on a kgicon driver would look like: display-fbdev generic-stubs generic-color generic-linear-* tgt-fbdev tgt-fbdev-kgicon-generic and when GGIMesa is attached display-fbdev-mesa would detect the presence of a Savage3D and add tgt-fbdev-kgicon-s3-savage3d to the API list. Comments? Andy? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Wed Jun 2 06:42:34 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA25732 for ; Wed, 2 Jun 1999 06:42:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA26411; Wed, 2 Jun 1999 03:33:51 -0700 Resent-Date: Wed, 2 Jun 1999 03:33:51 -0700 Message-ID: <19990602103348.10946.rocketmail@web123.yahoomail.com> Date: Wed, 2 Jun 1999 03:33:48 -0700 (PDT) From: Kien Pham Subject: Sure-fire way to detect GGI. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"CTFoL1.0.wR6.9YGLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13129 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com What's a sure-fire way to detect that GGI is installed and functional on a system? Also, was the issue of the ability to detect a cursor ever resolved? ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Wed Jun 2 06:51:44 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA25806 for ; Wed, 2 Jun 1999 06:51:43 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA28159; Wed, 2 Jun 1999 03:43:08 -0700 Resent-Date: Wed, 2 Jun 1999 03:43:08 -0700 Message-ID: <19990602104458.27918.rocketmail@send205.yahoomail.com> Date: Wed, 2 Jun 1999 03:44:58 -0700 (PDT) From: Kien Pham Subject: GGI and Hurd: Stefan Seeger, what else do you need? To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"G1fgU.0.jt6.wgGLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13130 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi. Tell me what else you need to get GGI on Hurd rolling. I will do the head hunting. I also have about a week of vacation from school to do some fun coding. Again, I don't know much about Hurd, but I'll try anything I can learn in about a week. As for the console code, it's a translator called term. It's very primitive with no color support or much of anything else. GGI has the potential to be the default console on Hurd? :) If you want more specifics, I can write a short summary of the code, but it seems primitive enough that you can jump right in. Also, I can e-mail the translator code to you if you don't want to download the entire Hurd sources. ~K.P. P.S. Rolling rolling rolling. Let's get GGI on Hurd rolling. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Wed Jun 2 08:03:11 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA26246 for ; Wed, 2 Jun 1999 08:03:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA11141; Wed, 2 Jun 1999 04:54:28 -0700 Resent-Date: Wed, 2 Jun 1999 04:54:28 -0700 Date: Wed, 2 Jun 1999 07:42:35 -0400 (EDT) From: Leimy To: ggi-develop@eskimo.com Subject: Documentation for hardware (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"9-Ki93.0.jj2.njHLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13131 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Anyone know of any good sources on the web or otherwise for hardware documentation? Writing a trident driver. Dave From ggiweb@metalab.unc.edu Wed Jun 2 08:46:36 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA26871 for ; Wed, 2 Jun 1999 08:46:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA20059; Wed, 2 Jun 1999 05:37:46 -0700 Resent-Date: Wed, 2 Jun 1999 05:37:46 -0700 From: Steffen Seeger Message-Id: <199906021236.OAA13517@demonti.physik.tu-chemnitz.de> Subject: Re: GGI and Hurd: Stefan Seeger, what else do you need? In-Reply-To: <19990602104458.27918.rocketmail@send205.yahoomail.com> from Kien Pham at "Jun 2, 99 03:44:58 am" To: ggi-develop@eskimo.com Date: Wed, 2 Jun 1999 14:36:39 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"mXUkS1.0.6v4.PMILt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13132 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Hi. Tell me what else you need to get GGI on Hurd rolling. Currently I am downloading the HURD stuff and trying to get it working. If you are seriously going into a KGI-on-HURD port, I suggest you get a Permedia2 based board (they are quiet cheap now). Have you found someone who knows how the issues I asked in my last mail are handled? > P.S. Rolling rolling rolling. Let's get GGI on Hurd rolling. Ok, I will try to get a HURD system running this week. Steffen ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- From ggiweb@metalab.unc.edu Wed Jun 2 16:44:40 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA08140 for ; Wed, 2 Jun 1999 16:44:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA03736; Wed, 2 Jun 1999 13:33:34 -0700 Resent-Date: Wed, 2 Jun 1999 13:33:34 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990602223347.C588@rz.uni-duesseldorf.de> Date: Wed, 2 Jun 1999 22:33:47 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions Mail-Followup-To: ggi-develop@eskimo.com References: <3754EA05.58BC701A@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <3754EA05.58BC701A@stacken.kth.se>; from Marcus Sundberg on Wed, Jun 02, 1999 at 08:23:33AM +0000 Resent-Message-ID: <"nPgmE.0.du.IKPLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13133 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > * I cannot seem to get kgi-savage4.so to be used by GGIMesa. ggimesa.conf > > maps 'display-fbdev-mesa' to the .so correctly (well it is a hack but...), so > > kgi-savage4.so does get loaded and its ggi_dlinit() function is called > > properly as well. However, in spite of the fact that display-fbdev-mesa is > > the last line in ggimesa.conf, ggiGetAPI() apparently insists on loading it > > _first_, before generic-stubs-mesa and friends. The end result is that the > > GGIMesa private function pointers, which were initially set correctly by > > kgi-savage4.so, get reset to the stub routines immediately afterward. No > > other extension implements both default/ and display/ subsystems, so I > > have no example to look at in this situation. > After a quick look at things it's obvious that we need to make the > API lists more flexible. For example it is desirable to have extensions > being able to add APIs which LibGGI itself does not know or need to know > about. ??? The _driver_ should know about the APIs. That is, the _driver_ should export a set of string describing which APIs the card exports. I always wondered, why the heck that code was disabled in the KGI directories: /* We don't need the suggest stuff for kgicon */ #undef NEED_SUGGEST_FEAT You are right, that LibGGI should not need to know. Thus for fbdev,KGI and friend TRTTD is IMHO to reactivate the kgi call for getAPI and have the driver export a list of APIs. It's simply that the driver exports something like : (generic-stubs) - implicit map from LibGGI not exported as it's no real API. generic-linear-8 - _driver_ exports a LFB for linear-8 generic-kgicommand - driver can take KGI-commands. That is, the interfacing code (the display-* lib) should have filled in the kgicommand pointer and the generic-kgi lib should be loaded which will send commands through that interface. Note, that the suidkgi target will use a direct call in the kgicommand pointer, while the fbdev target will use ioctl(). vendor-s3 - this is an S3 board. Load an eventual common accel dirver. vendor-s3-savage3d - it's a savage-3D IMHO mayn of the drivers have been broken in that respect ever since, so it might be a good time to fix it. Shall I set up a "template" for a (IMO) "correct" implementation of that ? (I admit, I didn't do it for the PM driver as well, as it worked without). > I propose we make the API list a property of the visual (not the target > as now, but the list is still initialized by the target at setmode time) > and add a new internal function: > _ggiAddAPI(ggi_visual_t vis, const char *api): Why should one add an API later ? Because the extension might be needed to detect it ? IMHO for the "good" systems, there should be an exported APIlist by the driver. > So the complete API list after the fbdev target is loaded on a kgicon > driver would look like: > display-fbdev > generic-stubs > generic-color > generic-linear-* > tgt-fbdev > tgt-fbdev-kgicon-generic IMHO the fbdev target should query the driver. That's how it was designed, and that's foolprof IMHO. > and when GGIMesa is attached display-fbdev-mesa would detect the > presence of a Savage3D and add tgt-fbdev-kgicon-s3-savage3d to > the API list. > > Comments? Andy? I don't think that's good. The suggest-strings feature was designed to do away with that "and then we try to detect" stuff, which is IMHO very risky business. The card should export what APIs can be used to access it from the very beginning. If the card exports MMIO areas, it is IMHO supposed to tell their format in the list of suggest-strings. CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Wed Jun 2 16:44:47 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA08144 for ; Wed, 2 Jun 1999 16:44:46 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA03742; Wed, 2 Jun 1999 13:33:34 -0700 Resent-Date: Wed, 2 Jun 1999 13:33:34 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990602221241.B588@rz.uni-duesseldorf.de> Date: Wed, 2 Jun 1999 22:12:41 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Sure-fire way to detect GGI. Mail-Followup-To: ggi-develop@eskimo.com References: <19990602103348.10946.rocketmail@web123.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990602103348.10946.rocketmail@web123.yahoomail.com>; from Kien Pham on Wed, Jun 02, 1999 at 03:33:48AM -0700 Resent-Message-ID: <"PE8zb1.0.rv.SKPLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13134 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > What's a sure-fire way to detect that GGI is installed and > functional on a system? That's a tricky question actually. You need to at least check for LibGII and LibGGI being installed in the dynamic linker search path and being of the minimum version your program wants. If you want to compile stuff, you should as well check for the headers. To find mis-installs, checking if the libggi.conf matches the actual place of the render libs might be a good idea. What IMHO can't be tested in a nice way, is that someone set up a working combination of graphics drivers on which to run. You could basically try to detect a few of the systems that are always active (like fbcon, or maybe X, if the user installs from there) and consider them working, if you find them and the lib install is o.k. At least for SVGAlib, I don't think one can safely say that it works, except by launching the program or a stub of it and asking the user if he saw it work right. > Also, was the issue of the ability to detect a cursor ever resolved? ? I don't get you here ... CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Wed Jun 2 17:48:52 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA09850 for ; Wed, 2 Jun 1999 17:48:51 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA31388; Wed, 2 Jun 1999 14:40:03 -0700 Resent-Date: Wed, 2 Jun 1999 14:40:03 -0700 Sender: marcus@e.kth.se Message-ID: <3755A49E.3B734654@stacken.kth.se> Date: Wed, 02 Jun 1999 21:39:42 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions References: <3754EA05.58BC701A@stacken.kth.se> <19990602223347.C588@rz.uni-duesseldorf.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"nL7Bs.0.cf7.iIQLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13135 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck wrote: > ??? The _driver_ should know about the APIs. That is, the _driver_ should > export a set of string describing which APIs the card exports. I always > wondered, why the heck that code was disabled in the KGI directories: > > /* We don't need the suggest stuff for kgicon */ > #undef NEED_SUGGEST_FEAT > > You are right, that LibGGI should not need to know. Thus for fbdev,KGI and > friend TRTTD is IMHO to reactivate the kgi call for getAPI and have the > driver export a list of APIs. Yes, I can agree with that, but then it needs to be fixed a bit. > It's simply that the driver exports something like : > > (generic-stubs) - implicit map from LibGGI not exported as it's no real API. Yes, this is clearly not an exported API. > generic-linear-8 - _driver_ exports a LFB for linear-8 Not an exported API either. An exported _API_ would consist of basicly all the information in the DirectBuffer structure, and for paletted modes the entrire initial palette. Encoding all that into a string and have LibGGI parse it would be really weird IMHO. > generic-kgicommand - driver can take KGI-commands. That is, the interfacing > code (the display-* lib) should have filled in the kgicommand pointer and > the generic-kgi lib should be loaded which will send commands through that > interface. Note, that the suidkgi target will use a direct call in the > kgicommand pointer, while the fbdev target will use ioctl(). > vendor-s3 - this is an S3 board. Load an eventual common accel dirver. > vendor-s3-savage3d - it's a savage-3D Yep, this is ok except that the the latter two would begin with vendor-creative- for Jon's drivers. > > I propose we make the API list a property of the visual (not the target > > as now, but the list is still initialized by the target at setmode time) > > and add a new internal function: > > _ggiAddAPI(ggi_visual_t vis, const char *api): > > Why should one add an API later ? Because the extension might be needed to > detect it ? IMHO for the "good" systems, there should be an exported APIlist > by the driver. Because I don't think you can convince the fbdev people to start using suggest-strings for normal fbdev drivers. ;-) Also, we really need that flexibility for the case where a driver just exports the registers and a newer, but backward compatible card is released. If for example the new card just has a new 3D engine added it would be stupid to have to distribute new KGI drivers (perhapps binary) when all that's needed is a new sublib for LibGGI3D. > > So the complete API list after the fbdev target is loaded on a kgicon > > driver would look like: > > display-fbdev > > generic-stubs > > generic-color > > generic-linear-* > > tgt-fbdev > > tgt-fbdev-kgicon-generic > > IMHO the fbdev target should query the driver. That's how it was designed, > and that's foolprof IMHO. Agreed for the drivers we have control over, but we still need the functionality for other drivers and flexibility. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Wed Jun 2 19:47:50 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA12257 for ; Wed, 2 Jun 1999 19:47:49 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA11589; Wed, 2 Jun 1999 16:37:17 -0700 Resent-Date: Wed, 2 Jun 1999 16:37:17 -0700 Date: Wed, 2 Jun 1999 16:36:52 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions In-Reply-To: <19990602223347.C588@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"L2JGT3.0.4o2.M0SLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13136 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 2 Jun 1999, Andreas Beck wrote: > > > * I cannot seem to get kgi-savage4.so to be used by GGIMesa. ggimesa.conf > > > maps 'display-fbdev-mesa' to the .so correctly (well it is a hack but...), so > > > kgi-savage4.so does get loaded and its ggi_dlinit() function is called > > > properly as well. However, in spite of the fact that display-fbdev-mesa is > > > the last line in ggimesa.conf, ggiGetAPI() apparently insists on loading it > > > _first_, before generic-stubs-mesa and friends. The end result is that the > > > GGIMesa private function pointers, which were initially set correctly by > > > kgi-savage4.so, get reset to the stub routines immediately afterward. No > > > other extension implements both default/ and display/ subsystems, so I > > > have no example to look at in this situation. > > > After a quick look at things it's obvious that we need to make the > > API lists more flexible. For example it is desirable to have extensions > > being able to add APIs which LibGGI itself does not know or need to know > > about. > > ??? The _driver_ should know about the APIs. That is, the _driver_ should > export a set of string describing which APIs the card exports. What for? Since the "API set" exported by the driver will not ever change, it really is just one global driver API and thus there is no point to having the driver care about any of that stuff. Just have the userspace code map an ident string retrieved from the driver to an interface table or caplist or whatever you are using. > I always > wondered, why the heck that code was disabled in the KGI directories: > > /* We don't need the suggest stuff for kgicon */ > #undef NEED_SUGGEST_FEAT Because there's no point to using it other than to know that the driver can map a LibGGI GC, which is a bad thing anyway because there's no reasonable way to support API-specific context handling directly in the driver for all possible userspace APIs. Even the LibGGI GC support should not be hardwired into KGI, IMHO. Contexts are API-specific, not hardware-specific, so it is the API code, not the driver, that should care about them. > You are right, that LibGGI should not need to know. Thus for fbdev,KGI and > friend TRTTD is IMHO to reactivate the kgi call for getAPI and have the > driver export a list of APIs. > > It's simply that the driver exports something like : > > (generic-stubs) - implicit map from LibGGI not exported as it's no real API. > generic-linear-8 - _driver_ exports a LFB for linear-8 > generic-kgicommand - driver can take KGI-commands. That is, the interfacing > code (the display-* lib) should have filled in the kgicommand pointer and > the generic-kgi lib should be loaded which will send commands through that > interface. Note, that the suidkgi target will use a direct call in the > kgicommand pointer, while the fbdev target will use ioctl(). > vendor-s3 - this is an S3 board. Load an eventual common accel dirver. > vendor-s3-savage3d - it's a savage-3D Why is this any better than having one ioctl which asks the driver to return a unique ident string which then is mapped to all those interfaces in userspace? It is certainly worse in that it dramatically reduces the flexibility of the driver-userspace communications pipe. > The card should export what APIs can be used to access > it from the very beginning. The card should export _one_ global API. Device drivers should not have to care about how they are used, they should have to care about abstracting the hardware. If the hardware doesn't change, the exported API will not change, and thus there is no point in allowing for that change within the structure of the driver itself. > If the card exports MMIO areas, it is IMHO supposed to tell their format > in the list of suggest-strings. If the card exports MMIO areas, the driver-specific target code should be aware of that and directly handle the use of those card-specific features appropriately. At the very least, if general-purpose buffer management code is to be used, there still needs to be some device-specific _userspace library code_ which handles the setup and translation between the hardware native interface and other hardware-independent userspace systems. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggiweb@metalab.unc.edu Wed Jun 2 20:02:33 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA12543 for ; Wed, 2 Jun 1999 20:02:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA15512; Wed, 2 Jun 1999 16:52:13 -0700 Resent-Date: Wed, 2 Jun 1999 16:52:13 -0700 Date: Wed, 2 Jun 1999 16:52:04 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions In-Reply-To: <3755A49E.3B734654@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"Yv0V-1.0.1o3.hESLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13137 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 2 Jun 1999, Marcus Sundberg wrote: > Andreas Beck wrote: > > ??? The _driver_ should know about the APIs. That is, the _driver_ should > > export a set of string describing which APIs the card exports. I always > > wondered, why the heck that code was disabled in the KGI directories: > > > > /* We don't need the suggest stuff for kgicon */ > > #undef NEED_SUGGEST_FEAT > > > > You are right, that LibGGI should not need to know. Thus for fbdev,KGI and > > friend TRTTD is IMHO to reactivate the kgi call for getAPI and have the > > driver export a list of APIs. > > Yes, I can agree with that, but then it needs to be fixed a bit. > > > It's simply that the driver exports something like : > > > > (generic-stubs) - implicit map from LibGGI not exported as it's no real API. > > Yes, this is clearly not an exported API. > > > generic-linear-8 - _driver_ exports a LFB for linear-8 > > Not an exported API either. An exported _API_ would consist of basicly > all the information in the DirectBuffer structure, and for paletted > modes > the entrire initial palette. Encoding all that into a string and have > LibGGI > parse it would be really weird IMHO. The exporting of the driver's interface info to userspace isn't the problem. The problem is the idea of supporting multiple predefined interfaces within a static device driver. > > generic-kgicommand - driver can take KGI-commands. That is, the interfacing > > code (the display-* lib) should have filled in the kgicommand pointer and > > the generic-kgi lib should be loaded which will send commands through that > > interface. Note, that the suidkgi target will use a direct call in the > > kgicommand pointer, while the fbdev target will use ioctl(). > > vendor-s3 - this is an S3 board. Load an eventual common accel dirver. > > vendor-s3-savage3d - it's a savage-3D > > Yep, this is ok except that the the latter two would begin with > vendor-creative- for Jon's drivers. What info does the vendor-creative- part provide that an ident string cannot? And the ident string can map back to vendor-s3, generic-kgicommand, or an infinite number of interfaces that haven't been designed yet! And all that can happen without having to go back and rewrite your driver code. You do need a little extra userspace code to handle that mapping, but A) each extension would only have to care about mapping the ident string to _its_ interfaces, and B) you don't need to manage a fixed set of interface strings. > > > I propose we make the API list a property of the visual (not the target > > > as now, but the list is still initialized by the target at setmode time) > > > and add a new internal function: > > > _ggiAddAPI(ggi_visual_t vis, const char *api): > > > > Why should one add an API later ? Because the extension might be needed to > > detect it ? IMHO for the "good" systems, there should be an exported APIlist > > by the driver. > > Because I don't think you can convince the fbdev people to start > using suggest-strings for normal fbdev drivers. ;-) Or Glide, or X, or VNC, or.... > Also, we really need that flexibility for the case where a driver > just exports the registers and a newer, but backward compatible card > is released. If for example the new card just has a new 3D engine added > it would be stupid to have to distribute new KGI drivers (perhapps > binary) > when all that's needed is a new sublib for LibGGI3D. Right. Tying the drivers and the APIs that use them together like that is just not going to work. The intelligence has to come from within the API implementation itself, just as the LibGGI fbdev target and its kgicon helperlib have. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggiweb@metalab.unc.edu Wed Jun 2 20:23:32 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA12859 for ; Wed, 2 Jun 1999 20:23:31 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA22026; Wed, 2 Jun 1999 17:13:08 -0700 Resent-Date: Wed, 2 Jun 1999 17:13:08 -0700 Message-ID: X-Mailer: NailMail 1.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3754E9D7.349241AA@stacken.kth.se> ECHELON: nuclear,Saddam,CIA,Milosevic,Clinton,dead,Plutonium,KGB,USA,bomb,terror Date: Thu, 03 Jun 1999 02:12:51 +0200 (CEST) Sender: thomas@ffii.org From: Thomas Tanner To: ggi-develop@eskimo.com Subject: Re: 346-day anniversary of seeing the stars ;) Resent-Message-ID: <"vkDe3.0.VN5.FYSLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13138 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On 02-Jun-99 Marcus Sundberg wrote: >> > On a related issue, the -export-symbols option is broken in current >> > libtool CVS because of this line (around line 2200 in ltmain.sh): >> > # Prepare the list of exported symbols >> > if test -z "$export_symbols"; then >> What's wrong with it? If the "export symbols" file >> doesn't exist libtool will generate it itself. > Yes, but if it does exist the compilation will fail because > $soname-ltdll.c is generated by export_symbols_cmds, which is not > evaluated if export_symbols is not empty... Thanks. Forwarded. Thomas Tanner ----------------------------------------- email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de) web: http://home.pages.de/~tanner GGI/Picasso: http://picasso.ffii.org From ggiweb@metalab.unc.edu Wed Jun 2 20:29:19 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA12965 for ; Wed, 2 Jun 1999 20:29:18 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA24192; Wed, 2 Jun 1999 17:19:13 -0700 Message-ID: X-Mailer: NailMail 1.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Resent-Date: Wed, 2 Jun 1999 16:22:17 -0700 Resent-Message-Id: <19990602162217.A8330@harlot.rb.ca.us> Resent-From: Daryll Strauss Resent-To: mesa-dev@mesa3d.org ECHELON: nuclear,Saddam,CIA,Milosevic,Clinton,dead,Plutonium,KGB,USA,bomb,terror Date: Thu, 03 Jun 1999 02:18:54 +0200 (CEST) Sender: thomas@ffii.org From: Thomas Tanner To: ggi-develop@eskimo.com Subject: FW: [Mesa-dev] nVidia releases open source driver Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13139 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com -----FW: <19990602162217.A8330@harlot.rb.ca.us>----- Date: Wed, 2 Jun 1999 16:22:17 -0700 Sender: mesa-dev-admin@lists.mesa3d.org From: Daryll Strauss To: mesa-dev@mesa3d.org Subject: [Mesa-dev] nVidia releases open source driver The news hasn't made it to this list yet, so I'll post it. nVidia has released the source to their 2D and 3D driver on their website. This is a driver for Mesa. You can find the details here: http://www.nvidia.com/Products.nsf/htmlmedia/software_drivers.html It will be great to get another line of hardware well supported under Linux! - |Daryll _______________________________________________ Mesa-dev maillist - Mesa-dev@lists.mesa3d.org http://lists.mesa3d.org/mailman/listinfo/mesa-dev --------------End of forwarded message------------------------- Thomas Tanner ----------------------------------------- email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de) web: http://home.pages.de/~tanner GGI/Picasso: http://picasso.ffii.org From ggiweb@metalab.unc.edu Wed Jun 2 21:13:10 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA13628 for ; Wed, 2 Jun 1999 21:13:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id SAA07995; Wed, 2 Jun 1999 18:02:54 -0700 Resent-Date: Wed, 2 Jun 1999 18:02:54 -0700 From: Thad Phetteplace Message-Id: <199906030614.BAA13331@dexter.glaci.com> Subject: Re: FW: [Mesa-dev] nVidia releases open source driver To: ggi-develop@eskimo.com Date: Thu, 3 Jun 1999 01:14:40 -0500 (CDT) In-Reply-To: from "Thomas Tanner" at Jun 3, 99 02:18:54 am Content-Type: text Resent-Message-ID: <"Z8GgM3.0.Ry1.sGTLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13140 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > The news hasn't made it to this list yet, so I'll post it. nVidia has > released the source to their 2D and 3D driver on their website. This is > a driver for Mesa. You can find the details here: > > http://www.nvidia.com/Products.nsf/htmlmedia/software_drivers.html > > It will be great to get another line of hardware well supported under Linux! I was tempted to mention it myself, but decided to leave it up to someone else. :-) I've downloaded the driver source but have not looked at it yet (probably be a few weeks before I get the time). I will now likely run out and buy an nVidia card this weekend, if for no other reason than to support this awesomely cool action on their part (and having kickass 3D on my linux box doesn't hurt either). Glad I dragged my feet on buying a Voodoo card. So I assume we will ransack these drivers and add support into libggi3d? Thad From ggiweb@metalab.unc.edu Thu Jun 3 00:06:12 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA16684 for ; Thu, 3 Jun 1999 00:06:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA31303; Wed, 2 Jun 1999 20:56:02 -0700 Resent-Date: Wed, 2 Jun 1999 20:56:02 -0700 Message-ID: <19990603035559.25745.rocketmail@web601.yahoomail.com> Date: Wed, 2 Jun 1999 20:55:59 -0700 (PDT) From: Kien Pham Subject: Re: Sure-fire way to detect GGI. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"ftnuB2.0.ie7.FpVLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13141 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- Andreas Beck wrote: > > What's a sure-fire way to detect that GGI is installed > and > > functional on a system? > > That's a tricky question actually. You need to at least > check > for LibGII and LibGGI being installed in the dynamic > linker > search path and being of the minimum version your program > wants. > > If you want to compile stuff, you should as well check > for the > headers. > > To find mis-installs, checking if the libggi.conf matches > the > actual place of the render libs might be a good idea. > > What IMHO can't be tested in a nice way, is that someone > set up > a working combination of graphics drivers on which to > run. > > You could basically try to detect a few of the systems > that > are always active (like fbcon, or maybe X, if the user > installs > from there) and consider them working, if you find them > and the > lib install is o.k. > At least for SVGAlib, I don't think one can safely say > that it works, > except by launching the program or a stub of it and > asking the user if > he saw it work right. Woops my fault. I meant to check during runtime from a binary. Couldn't GGI installation procedure put a drivers.lst or something like that in the ggi directory in the include dirs. (Bad hack, I know.) Someone with a more eloquent way should jump right up and tell me. :) > > Also, was the issue of the ability to detect a cursor > ever resolved? A long time ago I asked whether or not I could check for a cursor during runtime in GGI. I need to know whether I need to render it myself(svgalib target) or if I can use a pre-existing one (X11 target). > ? I don't get you here ... > > CU, ANdy > > -- > = Andreas Beck | Email : > = > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Thu Jun 3 03:27:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA19072 for ; Thu, 3 Jun 1999 03:26:58 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA13917; Thu, 3 Jun 1999 00:16:45 -0700 Resent-Date: Thu, 3 Jun 1999 00:16:45 -0700 Message-ID: <19990603071659.242.rocketmail@web135.yahoomail.com> Date: Thu, 3 Jun 1999 00:16:59 -0700 (PDT) From: Kien Pham Subject: How to force evPtrAbsolute to certain values. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"39jB43.0.3P3.PlYLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13142 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Is there an emCommand to force an evAbsolute pointer to a certain value? I.e. start at the middle of the screen or the origin? Also, a simple API to access the cursor for X Windows? Like simple show/hide/set Cursor? ~K.P. ~Fumbling towards coder ecstacy. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Thu Jun 3 03:28:12 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA19092 for ; Thu, 3 Jun 1999 03:28:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA14048; Thu, 3 Jun 1999 00:18:02 -0700 Resent-Date: Thu, 3 Jun 1999 00:18:02 -0700 Sender: marcus@e.kth.se Message-ID: <37562C02.6A969B68@stacken.kth.se> Date: Thu, 03 Jun 1999 07:17:22 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Sure-fire way to detect GGI. References: <19990603035559.25745.rocketmail@web601.yahoomail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"CytU9.0.FR3.fmYLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13143 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Kien Pham wrote: > > he saw it work right. > Woops my fault. I meant to check during runtime from a > binary. Couldn't GGI installation procedure put a > drivers.lst or something like that in the ggi directory in > the include dirs. (Bad hack, I know.) Someone with a more > eloquent way should jump right up and tell me. :) ??? Exactly what is it that you want to achieve? If ggiInit() and ggiOpen() succeeds LibGGI works, if it doesn't LibGGI does not work. If you want to do something else than that you're most probably on a very wrong track. > > > Also, was the issue of the ability to detect a cursor > > ever resolved? > A long time ago I asked whether or not I could check for a > cursor during runtime in GGI. I need to know whether I need > to render it myself(svgalib target) or if I can use a > pre-existing one (X11 target). If you don't use a hardware cursor (which there currently isn't any extension for) you have to draw the cursor yourself, otherwise you are not coding for the LibGGI API. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Thu Jun 3 03:34:59 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA19195 for ; Thu, 3 Jun 1999 03:34:58 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA16531; Thu, 3 Jun 1999 00:24:55 -0700 Resent-Date: Thu, 3 Jun 1999 00:24:55 -0700 Sender: marcus@e.kth.se Message-ID: <37562DBB.216D2D33@stacken.kth.se> Date: Thu, 03 Jun 1999 07:24:43 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: How to force evPtrAbsolute to certain values. References: <19990603071659.242.rocketmail@web135.yahoomail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"pfwDM1.0.z14.5tYLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13144 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Kien Pham wrote: > > Is there an emCommand to force an evAbsolute pointer to a > certain value? I.e. start at the middle of the screen or > the origin? No. How would you move the pen of a drawing tablet in software? > Also, a simple API to access the cursor for X Windows? Like simple show/hide/set Cursor? No, not yet. Wanna write one? ;) //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Thu Jun 3 07:53:40 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA20831 for ; Thu, 3 Jun 1999 07:53:38 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA16951; Thu, 3 Jun 1999 04:43:09 -0700 Resent-Date: Thu, 3 Jun 1999 04:43:09 -0700 Message-ID: <19990603114311.1181.rocketmail@web130.yahoomail.com> Date: Thu, 3 Jun 1999 04:43:11 -0700 (PDT) From: Kien Pham Subject: Re: How to force evPtrAbsolute to certain values. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"ZWKpk2.0.084.4fcLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13145 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- Marcus Sundberg wrote: > Kien Pham wrote: > > > > Is there an emCommand to force an evAbsolute pointer to > a > > certain value? I.e. start at the middle of the screen > or > > the origin? > > No. How would you move the pen of a drawing tablet in > software? Good point, but I thinking along the lines of XWarpPointer or something like that for mice. > Also, a simple API to access the cursor for X Windows? > Like > simple show/hide/set Cursor? > > No, not yet. Wanna write one? ;) Sure. :) > //Marcus > -- > -------------------------------+------------------------------------ > Marcus Sundberg | > http://www.stacken.kth.se/~mackan/ > Royal Institute of Technology | Phone: +46 707 > 295404 > Stockholm, Sweden | E-Mail: > mackan@stacken.kth.se > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Thu Jun 3 07:54:01 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA20838 for ; Thu, 3 Jun 1999 07:54:00 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA17080; Thu, 3 Jun 1999 04:43:59 -0700 Resent-Date: Thu, 3 Jun 1999 04:43:59 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990603125410.B501@rz.uni-duesseldorf.de> Date: Thu, 3 Jun 1999 12:54:10 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions Mail-Followup-To: ggi-develop@eskimo.com References: <19990602223347.C588@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Jon M. Taylor on Wed, Jun 02, 1999 at 04:36:52PM -0700 Resent-Message-ID: <"h-CYt3.0.ZA4.zfcLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13146 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > ??? The _driver_ should know about the APIs. That is, the _driver_ should > > export a set of string describing which APIs the card exports. > > What for? Since the "API set" exported by the driver will not ever > change, it really is just one global driver API and thus there is no > point to having the driver care about any of that stuff. Wrong. Backward compatibility is the idea. If you load a new KGi driver onto an older LibGGI system, a single ID leads to: Drivers say: Savage3d - LibGGI: Doesn't know it. => no accel. The system I proposed will yield: generic-ioctl -> LibGGI knows it. ioctl() accel active. vendor-s3-generic -> LibGGI know S3 cards. It can MMIO accel simple stuff common to all S3s. vendor-s3-savage3d-> LibGGI doesn't know. Tough luck. This enables us to make better use of our layered driver structure for card families. We can place the common code in a generic module that works for the whole family and add specific code in additional libs. This yields less double code being produced. > Just have the userspace code map an ident string retrieved from the > driver to an interface table or caplist or whatever you are using. That would require updating the userspace code at installing a new driver. Look at the tries with acceled XF86fbdev on what that leads to. I don't see the merit of pulling that information out of the driver, as it 1. isn't much. A few 100 bytes of string data. 2. it hints the driver writers at looking, if they can easily support fallback family-APIs. (I don't advocate emulating them, though - that would be a waste of time and space). > Because there's no point to using it other than to know that the > driver can map a LibGGI GC, No. That's precisely what it was _not_ designed for. It was designed for telling the external parts (be it LibGGI or whatever) about all APIs it exports. And these should be multiple , if you want to be reasonably backward compatible. A single "driver-id-string" carries no information for older libs on what the card can do. That is, you must update the userspace code when installing a new kernel driver, to get at least some acceleration. > which is a bad thing anyway because there's no reasonable way to support > API-specific context handling directly in the driver for all possible > userspace APIs. The idea was to have a reserved space in the GC (say bytes 2048-4095) that is card-private and will only be touched by the most specific API lib. > Even the LibGGI GC support should not be hardwired into KGI, IMHO. > Contexts are API-specific, not hardware-specific, so it is the API > code, not the driver, that should care about them. The GC mapping is done for exactly one reason: Having _fast_ communications for GC parameters to kernelspace. If you run from userspace by hitting the card accel, this is no issue. But for ioctl-accel, PingPong and friends, you need to either transfer the whole GC state at each call or have a quick way to access it from kernelspace. > > vendor-s3 - this is an S3 board. Load an eventual common accel dirver. > > vendor-s3-savage3d - it's a savage-3D > Why is this any better than having one ioctl which asks the driver to > return a unique ident string which then is mapped to all those interfaces in > userspace? Because you have to modify that map every time a new driver pops up. > It is certainly worse in that it dramatically reduces the > flexibility of the driver-userspace communications pipe. I what respect ? The very last string in the list is exactly your unique ID string. It's more or less a reasonable extension to what you propose that has the additional capability to work with older userspace driver without changing a line of code in them. > The card should export _one_ global API. Device drivers should not > have to care about how they are used, they should have to care about > abstracting the hardware. If the hardware doesn't change, the exported > API will not change, and thus there is no point in allowing for that > change within the structure of the driver itself. The hardware the driver is for will not change. But there will be hardware that is more-or less compatible with the existing one. > If the card exports MMIO areas, the driver-specific target code > should be aware of that and directly handle the use of those card-specific > features appropriately. At the very least, if general-purpose buffer > management code is to be used, there still needs to be some device-specific > _userspace library code_ which handles the setup and translation between the > hardware native interface and other hardware-independent userspace systems. That _requires_ installing a userspace driver for _ALL_ LibGGI extensions at driver install time. Else all not-installed extension will crawl. The multi-layer setup I propose willuse the fallback capabilities and thus get at least reasonable performance. CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Thu Jun 3 07:54:04 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA20843 for ; Thu, 3 Jun 1999 07:54:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA17117; Thu, 3 Jun 1999 04:44:02 -0700 Resent-Date: Thu, 3 Jun 1999 04:44:02 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990603130851.C501@rz.uni-duesseldorf.de> Date: Thu, 3 Jun 1999 13:08:51 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions Mail-Followup-To: ggi-develop@eskimo.com References: <3755A49E.3B734654@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Jon M. Taylor on Wed, Jun 02, 1999 at 04:52:04PM -0700 Resent-Message-ID: <"b_Vy2.0.BB4.0gcLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13147 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Yep, this is ok except that the the latter two would begin with > > vendor-creative- for Jon's drivers. > What info does the vendor-creative- part provide that an ident string > cannot? And the ident string can map back to vendor-s3, generic-kgicommand, > or an infinite number of interfaces that haven't been designed yet! That makes no sense. The driver must be written to support those interfaces, so not-yet designed interfaces have only a very remote chance to be compatible with an existing driver. > do need a little extra userspace code to handle that mapping, but A) each > extension would only have to care about mapping the ident string to _its_ > interfaces, ??? Why should these interfaces differ ? Interfaces do _NOT_ describe any external interface toward the user, but only the Intraface between the LibGGI(-extension) module and the card driver. It just says something like "to send a command, use kgicommand(...)" or "this card exports an S3-style MMIO area with registers". > B) you don't need to manage a fixed set of interface strings. This is a natural process: When you write a new driver and you see it is 100% compatible to the older one for the functions supported there, plus a few new ones, you just keep exporting the old API-strings and add a new one for the new functions. > > > > _ggiAddAPI(ggi_visual_t vis, const char *api): > > > Why should one add an API later ? Because the extension might > > > be needed to detect it ? > > Because I don't think you can convince the fbdev people to start > > using suggest-strings for normal fbdev drivers. ;-) > Or Glide, or X, or VNC, or.... These can be handled by the LibGGI "display" driver. Though I see reason for the AddAPI call (like the Mesa extension detecting GLX), and we should do that change. Chained list of API-strings ? Modification functions like: _ggiAPIAdd (ggi_visual_t vis, struct API *what_to_add, struct API *after); _ggiAPIDelete(ggi_visual_t vis, struct API *what_to_delete); _ggiAPIGet (ggi_visual_t vis, int number); for convenience ? We will want to count APIAdds in case multiple extension want to add the same API string. CU, Andy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Thu Jun 3 07:54:12 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA20848 for ; Thu, 3 Jun 1999 07:54:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA17163; Thu, 3 Jun 1999 04:44:10 -0700 Resent-Date: Thu, 3 Jun 1999 04:44:10 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990603131802.D501@rz.uni-duesseldorf.de> Date: Thu, 3 Jun 1999 13:18:02 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions Mail-Followup-To: ggi-develop@eskimo.com References: <3754EA05.58BC701A@stacken.kth.se> <19990602223347.C588@rz.uni-duesseldorf.de> <3755A49E.3B734654@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <3755A49E.3B734654@stacken.kth.se>; from Marcus Sundberg on Wed, Jun 02, 1999 at 09:39:42PM +0000 Resent-Message-ID: <"ZhsNl.0.oB4.8gcLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13148 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > (generic-stubs) - implicit map from LibGGI not exported as it's no real API. > Yes, this is clearly not an exported API. > > generic-linear-8 - _driver_ exports a LFB for linear-8 > Not an exported API either. An exported _API_ would consist of basicly > all the information in the DirectBuffer structure, Yes. I'd like to add such a capability anyway. As of now, this is the "best effort" to describe the exported framebuffer. IMHO we should as well be able to export multiple framebuffers, as some cards can export Big/Little endian and such. > and for paletted modes the entrire initial palette. That is handled by the "generic-ramdac" API which I didn't include in the example. > Encoding all that into a string and have LibGGI > parse it would be really weird IMHO. Yes. The idea is that you know the generic layout, which joins all "compatible" libs. linear-15 is IMHO nonsense. The difference to linear-16 is the encoding of the colors which should be queryable in another fashion. > > Why should one add an API later ? > Because I don't think you can convince the fbdev people to start > using suggest-strings for normal fbdev drivers. ;-) > Also, we really need that flexibility for the case where a driver > just exports the registers and a newer, but backward compatible card > is released. If for example the new card just has a new 3D engine added > it would be stupid to have to distribute new KGI drivers (perhapps > binary) when all that's needed is a new sublib for LibGGI3D. Yes - I see. You mean a card that is 100% compatible, but has some extra regs in the already exported space ... O.K. - if they can be queried in a dafe way, that would be doable. Though I'd still recommend to patch the driver to avoid collecting a big bunch of specific tests in the userspace libs. > Agreed for the drivers we have control over, but we still need the > functionality for other drivers and flexibility. Yes. See my proposal for the AddAPI you suggested. Quick addition on that: I think the struct *API should have a *private pointer which can be used to store some extra data (like say the DB layout). It should be assumed to be malloced memory which is free()ed when the API is deleted. CU, Andy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Thu Jun 3 08:00:46 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA20922 for ; Thu, 3 Jun 1999 08:00:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA18448; Thu, 3 Jun 1999 04:50:43 -0700 Resent-Date: Thu, 3 Jun 1999 04:50:43 -0700 Message-ID: <19990603115052.1830.rocketmail@web130.yahoomail.com> Date: Thu, 3 Jun 1999 04:50:52 -0700 (PDT) From: Kien Pham Subject: Re: Sure-fire way to detect GGI. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"GrYmH3.0.vV4.HmcLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13149 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- Marcus Sundberg wrote: > Kien Pham wrote: > > eloquent way should jump right up and tell me. :) > > ??? > Exactly what is it that you want to achieve? > If ggiInit() and ggiOpen() succeeds LibGGI works, if it > doesn't > LibGGI does not work. If you want to do something else > than that > you're most probably on a very wrong track. I'm writing a multiplatform library. I would prefer to use GGI first and then any other library last. If GGI is not installed, won't GGIInit() bomb out the entire program rather than return an error code? I just want a quick way to check that GGI is installed and functional. Forcing everyone who wants to use my library to install GGI is a great idea, but I don't think that's plausible. > > > > Also, was the issue of the ability to detect a > cursor > > > ever resolved? > > A long time ago I asked whether or not I could check > for a > > cursor during runtime in GGI. I need to know whether I > need > > to render it myself(svgalib target) or if I can use a > > pre-existing one (X11 target). > > If you don't use a hardware cursor (which there currently > isn't any > extension for) you have to draw the cursor yourself, > otherwise > you are not coding for the LibGGI API. Yeah. But then I end up with two cursors in X11 target of GGI. > //Marcus > -- > -------------------------------+------------------------------------ > Marcus Sundberg | > http://www.stacken.kth.se/~mackan/ > Royal Institute of Technology | Phone: +46 707 > 295404 > Stockholm, Sweden | E-Mail: > mackan@stacken.kth.se > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Thu Jun 3 08:04:41 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA20959 for ; Thu, 3 Jun 1999 08:04:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA19059; Thu, 3 Jun 1999 04:54:36 -0700 Resent-Date: Thu, 3 Jun 1999 04:54:36 -0700 Message-ID: <19990603115437.20338.rocketmail@web117.yahoomail.com> Date: Thu, 3 Jun 1999 04:54:37 -0700 (PDT) From: Kien Pham Subject: Re: GGI and Hurd: Stefan Seeger, what else do you need? To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"4Igiy1.0.Xf4.wpcLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13150 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- Steffen Seeger wrote: > > > Hi. Tell me what else you need to get GGI on Hurd > rolling. > > Currently I am downloading the HURD stuff and trying to > get it working. > > If you are seriously going into a KGI-on-HURD port, I > suggest you get > a Permedia2 based board (they are quiet cheap now). I wish. I'm a starving student. But I'll do what I can. :) > Have you found someone who knows how the issues I asked > in my last mail > are handled? I've already sent an e-mail to the most visible gnumach guy. I'm awaiting a reply. > P.S. Rolling rolling rolling. Let's get GGI on Hurd > rolling. > > Ok, I will try to get a HURD system running this week. > > Steffen > > ----------------- e-mail: seeger@physik.tu-chemnitz.de > ----------------- > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Thu Jun 3 09:21:18 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA22063 for ; Thu, 3 Jun 1999 09:21:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA03226; Thu, 3 Jun 1999 06:10:57 -0700 Resent-Date: Thu, 3 Jun 1999 06:10:57 -0700 From: Andrew Apted Message-ID: <19990603231545.50441@ajax.netspace.net.au> Date: Thu, 3 Jun 1999 23:15:45 +1000 To: ggi-develop@eskimo.com Subject: Re: How to force evPtrAbsolute to certain values. Reply-To: ggi-develop@eskimo.com References: <19990603114311.1181.rocketmail@web130.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <19990603114311.1181.rocketmail@web130.yahoomail.com>; from Kien Pham on Thu, Jun 03, 1999 at 04:43:11AM -0700 Resent-Message-ID: <"P8PeV2.0.Zn.LxdLt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13151 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Kien Pham writes: > > > Is there an emCommand to force an evAbsolute pointer to > > a > > > certain value? I.e. start at the middle of the screen > > or > > > the origin? > > > > No. How would you move the pen of a drawing tablet in > > software? > Good point, but I thinking along the lines of XWarpPointer > or something like that for mice. You may know this already, but if you want relative events from X then you can press CTRL + ALT + m. This turns off the cursor too. Good for something like Doom (up to a point :->). Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggiweb@metalab.unc.edu Thu Jun 3 09:37:45 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA22450 for ; Thu, 3 Jun 1999 09:37:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA07860; Thu, 3 Jun 1999 06:27:34 -0700 Resent-Date: Thu, 3 Jun 1999 06:27:34 -0700 Message-ID: <19990603132738.19560.rocketmail@web114.yahoomail.com> Date: Thu, 3 Jun 1999 06:27:38 -0700 (PDT) From: Kien Pham Subject: GGI Cursor API proposal. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"Zz-993.0.Uw1.5BeLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13152 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com typedef struct ggi_cursor_t { ggi_visual_t vis; // Visual that the cursor is bound to. void* image; // Must be of the same depth and color format as the corresponding ggi_visual_t; int width, height; int hotx, hoty; // hotspot } ggi_cursor_t; typdef ggi_cursor_t* ggi_cursor_id_t; ggi_cursor_id_t ggiCreateCursor(ggi_cursor_t cursor); int ggiMoveCursor(ggi_cursor_id_t cursor, int x, int y); int ggiHideCursor(ggi_cursor_id_t cursor); int ggiShowCursor(ggi_cursor_id_t cursor); int ggiDeleteCursor(ggi_cursor_id_t cursor); This API allows each visual to have multiple cursors and it allows the cursors to move independently. What else can you want? Systems that do not support hardware cursors can use software emulation. ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Thu Jun 3 09:46:13 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA22579 for ; Thu, 3 Jun 1999 09:46:12 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA09832; Thu, 3 Jun 1999 06:36:04 -0700 Resent-Date: Thu, 3 Jun 1999 06:36:04 -0700 From: Andrew Apted Message-ID: <19990603234101.24615@ajax.netspace.net.au> Date: Thu, 3 Jun 1999 23:41:01 +1000 To: ggi-develop@eskimo.com Subject: Re: Sure-fire way to detect GGI. Reply-To: ggi-develop@eskimo.com References: <19990603115052.1830.rocketmail@web130.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <19990603115052.1830.rocketmail@web130.yahoomail.com>; from Kien Pham on Thu, Jun 03, 1999 at 04:50:52AM -0700 Resent-Message-ID: <"VmewD1.0.GP2.2JeLt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13153 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Kien Pham writes: > I'm writing a multiplatform library. I would prefer to > use GGI first and then any other library last. If GGI is > not installed, won't GGIInit() bomb out the entire program > rather than return an error code? Yes, it won't dynamically link. If you want _runtime_ selection of what API to use, you're gonna need some kind of *plug-in* system. That is possible (CrystalSpace does this), but is something you'll need to think about a lot (it isn't trivial). I'd recommend just using _compiletime_ selection of the API. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggiweb@metalab.unc.edu Thu Jun 3 11:44:40 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA25401 for ; Thu, 3 Jun 1999 11:44:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA16740; Thu, 3 Jun 1999 08:34:14 -0700 Resent-Date: Thu, 3 Jun 1999 08:34:14 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990603165740.B628@rz.uni-duesseldorf.de> Date: Thu, 3 Jun 1999 16:57:40 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Sure-fire way to detect GGI. Mail-Followup-To: ggi-develop@eskimo.com References: <19990603115052.1830.rocketmail@web130.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990603115052.1830.rocketmail@web130.yahoomail.com>; from Kien Pham on Thu, Jun 03, 1999 at 04:50:52AM -0700 Resent-Message-ID: <"lFIqI2.0.844.m1gLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13155 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > If ggiInit() and ggiOpen() succeeds LibGGI works, if it > I'm writing a multiplatform library. I would prefer to > use GGI first and then any other library last. If GGI is > not installed, won't GGIInit() bomb out the entire program > rather than return an error code? The program will not link at loadtime and thus bomb out. LibGGI makes quite some effort to avoid that behaviour for binaries. You will at least need some kind of dynamic loading in place to avoid this problem at runtime. It can more easily be solved at compiletime, where I'd just detect the presence of LibGGI and the includes and assume the user knows what he's doing and sets an override (like ./configure --disable-ggi) , if he knows that LibGGI doesn't work as expected. If you want a runtime check rather, and you don't already have code to do that, I'd rather leave that problem to LibGGI and always use it. > > extension for) you have to draw the cursor yourself, > Yeah. But then I end up with two cursors in X11 target of GGI. Not really. The X cursor is set to a single dot for GGI-on-X. Shouldn't be too noticeable. One might also want to turn on relmouse Ctrl-Alt-M, which will turn off the cursor entirely. CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Thu Jun 3 11:45:29 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA25465 for ; Thu, 3 Jun 1999 11:45:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA16714; Thu, 3 Jun 1999 08:34:11 -0700 Resent-Date: Thu, 3 Jun 1999 08:34:11 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990603165036.A628@rz.uni-duesseldorf.de> Date: Thu, 3 Jun 1999 16:50:36 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGI Cursor API proposal. Mail-Followup-To: ggi-develop@eskimo.com References: <19990603132738.19560.rocketmail@web114.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990603132738.19560.rocketmail@web114.yahoomail.com>; from Kien Pham on Thu, Jun 03, 1999 at 06:27:38AM -0700 Resent-Message-ID: <"TTvxQ3.0.f34.j1gLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13154 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > typedef struct ggi_cursor_t > { > ggi_visual_t vis; // Visual that the cursor is bound to. > void* image; // Must be of the same depth and color format as the corresponding ggi_visual_t; This is _not_ the usual case. Most HW cursor are of a really different format. > int width, height; > int hotx, hoty; // hotspot > } ggi_cursor_t; > ggi_cursor_id_t ggiCreateCursor(ggi_cursor_t cursor); > int ggiMoveCursor(ggi_cursor_id_t cursor, int x, int y); > int ggiHideCursor(ggi_cursor_id_t cursor); > int ggiShowCursor(ggi_cursor_id_t cursor); > int ggiDeleteCursor(ggi_cursor_id_t cursor); This lacks cursor image setup. > This API allows each visual to have multiple cursors and it > allows the cursors to move independently. What else can you > want? The most interesting part is setting up the bitmap. > Systems that do not support hardware cursors can use > software emulation. No. They can't. This has been discussed here several times. Please read up the ML archives on that topic. CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Thu Jun 3 12:01:33 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA25846 for ; Thu, 3 Jun 1999 12:01:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA23421; Thu, 3 Jun 1999 08:51:10 -0700 Resent-Date: Thu, 3 Jun 1999 08:51:10 -0700 Message-ID: <19990603175233.E20961@maxime.u-strasbg.fr> Date: Thu, 3 Jun 1999 17:52:33 +0200 From: Sven LUTHER To: ggi-develop@eskimo.com Subject: Re: Sure-fire way to detect GGI. Reply-To: luther@dpt-info.u-strasbg.fr References: <19990603115052.1830.rocketmail@web130.yahoomail.com> <19990603165740.B628@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <19990603165740.B628@rz.uni-duesseldorf.de>; from Andreas Beck on Thu, Jun 03, 1999 at 04:57:40PM +0200 Resent-Message-ID: <"KWb6o2.0.dj5.hHgLt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13156 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, Jun 03, 1999 at 04:57:40PM +0200, Andreas Beck wrote: > > > If ggiInit() and ggiOpen() succeeds LibGGI works, if it > > > I'm writing a multiplatform library. I would prefer to > > use GGI first and then any other library last. If GGI is > > not installed, won't GGIInit() bomb out the entire program > > rather than return an error code? > > The program will not link at loadtime and thus bomb out. > LibGGI makes quite some effort to avoid that behaviour for binaries. > > You will at least need some kind of dynamic loading in place > to avoid this problem at runtime. what about some libggi_not_there library of some kind, that just provide empty stubs, and a sure way for detecting that it is not the true ggi ? like it was done with svgalib to compile stuff on architecture where svgalib was not supported ? Friendly, Sven LUTHER From ggiweb@metalab.unc.edu Thu Jun 3 15:35:33 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA01260 for ; Thu, 3 Jun 1999 15:35:31 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA04067; Thu, 3 Jun 1999 12:23:47 -0700 Resent-Date: Thu, 3 Jun 1999 12:23:47 -0700 Date: Thu, 3 Jun 1999 12:15:36 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions In-Reply-To: <19990603130851.C501@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"E5vg3.0.9y.vOjLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13157 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 3 Jun 1999, Andreas Beck wrote: > > > Yep, this is ok except that the the latter two would begin with > > > vendor-creative- for Jon's drivers. > > > What info does the vendor-creative- part provide that an ident string > > cannot? And the ident string can map back to vendor-s3, generic-kgicommand, > > or an infinite number of interfaces that haven't been designed yet! > > That makes no sense. The driver must be written to support those interfaces, Not at all. The bridge code that translates the driver's native API into whatever userspace API is being used is contained in that API's kgi-savage4 (or whatever) target code. I thought the whole point of the target system was to be able to keep the kernel components (KGI drivers) as lightweight as possible by this exact system. > so not-yet designed interfaces have only a very remote chance to be > compatible with an existing driver. Right. They all need "driver" libraries to do the API bridging. > > do need a little extra userspace code to handle that mapping, but A) each > > extension would only have to care about mapping the ident string to _its_ > > interfaces, > > ??? Why should these interfaces differ ? Because the APIs in question differ in their needs of the KGI driver, and thus in the most efficient way(s) to represent the KGI driver's state. > Interfaces do _NOT_ describe any external interface toward the user, but > only the Intraface between the LibGGI(-extension) module and the card > driver. Correct, and that will vary from extension to extension. It should be the library's responsibility to do the API bridge, not the driver's. Unless, as I said, we get a KGI-dynamic which can load and unload intraface handler/implementor modules at runtime. If we had a system like that (which I have thought a lot about recently as it would be very useful), your way would be better because the KGI driver could directly export dynamic APIS just as LibGGI does. But wo do not have such a system at the present time, and thus all the interface handling code has to be statically linked into the driver, leading to bloat. > It just says something like "to send a command, use kgicommand(...)" > or "this card exports an S3-style MMIO area with registers". Or: * This card can double/triple-buffer * This card has a z/w-buffer with xxx bits of precision * This card exports x number of tiled apertures, each with a different possible stride/bitdepth/etc * This card can map texture and/or vertex buffers with a wide range of possible parameters * This card has a command fifo which can be mmap()ed to userspace * This card can draw single triangle/strips/fans/quads in hardware ...and this list goes on, and on, and on. And it will continue to grow as new cards with all sorts of wacky types of features hit the market. > > B) you don't need to manage a fixed set of interface strings. > > This is a natural process: > When you write a new driver and you see it is 100% compatible to the older > one for the functions supported there, plus a few new ones, you just keep > exporting the old API-strings and add a new one for the new functions. And in five years you have a hundred strings to support. Drivers should be written, debugged, and then left alone. The userspace code is what is flexible - it should bear the burden of bridging an extension API to the KGI driver. > > > > > _ggiAddAPI(ggi_visual_t vis, const char *api): > > > > Why should one add an API later ? Because the extension might > > > > be needed to detect it ? > > > Because I don't think you can convince the fbdev people to start > > > using suggest-strings for normal fbdev drivers. ;-) > > Or Glide, or X, or VNC, or.... > > These can be handled by the LibGGI "display" driver. > > Though I see reason for the AddAPI call (like the Mesa extension detecting > GLX), and we should do that change. Cool. The rest of this discussion is interesting but this is what is preventing me from getting a working display/ subsystem in GGIMesa so it is kind of urgent right now. > Chained list of API-strings ? Modification functions like: > > _ggiAPIAdd (ggi_visual_t vis, struct API *what_to_add, struct API *after); > _ggiAPIDelete(ggi_visual_t vis, struct API *what_to_delete); > _ggiAPIGet (ggi_visual_t vis, int number); > > for convenience ? > > We will want to count APIAdds in case multiple extension want to add the > same API string. In LibGGI3D, the same interface can have different implementations. How will we handle this? Will it even be possible? Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggiweb@metalab.unc.edu Thu Jun 3 16:46:37 1999 -0400 Status: X-Status: X-Keywords: Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA03204 for ; Thu, 3 Jun 1999 16:46:36 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id NAA13769; Thu, 3 Jun 1999 13:37:20 -0700 (PDT) Resent-Date: Thu, 3 Jun 1999 13:37:20 -0700 (PDT) Sender: marcus@e.kth.se Message-ID: <3756E057.1E4CA213@stacken.kth.se> Date: Thu, 03 Jun 1999 20:06:47 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Sure-fire way to detect GGI. References: <19990603115052.1830.rocketmail@web130.yahoomail.com> <19990603165740.B628@rz.uni-duesseldorf.de> <19990603175233.E20961@maxime.u-strasbg.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"iICR91.0.EB3.OQkLt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13159 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Sven LUTHER wrote: > what about some libggi_not_there library of some kind, that just provide empty > stubs, and a sure way for detecting that it is not the true ggi ? Why in the world would you want that, when you can just as well install the real LibGGI? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Thu Jun 3 18:02:05 1999 -0400 Status: X-Status: X-Keywords: Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA05126 for ; Thu, 3 Jun 1999 18:02:03 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id OAA24243; Thu, 3 Jun 1999 14:49:55 -0700 (PDT) Resent-Date: Thu, 3 Jun 1999 14:49:55 -0700 (PDT) From: Denis Oliver Kropp Reply-To: dok@fischlustig.de Organization: Fischlustig To: ggi-develop@eskimo.com Subject: DGA 2.0 Date: Thu, 3 Jun 1999 23:43:32 +0200 X-Mailer: KMail [version 1.0.22] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99060323464900.09150@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"HlUnn2.0.zr5.EWlLt"@mx2> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13161 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, I use the latest XFree 3.9 from cvs. There is already dga 2.0 support for mystique card, some older dga programs work, but libggi causes this: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 141 (XFree86-VidModeExtension) Minor opcode of failed request: 10 (XF86VidModeSwitchToMode) Value in failed request: 0x26 Serial number of failed request: 24 Current serial number in output stream: 27 Maybe there are other video mode numbers now? btw: I am writing a little test app for DGA 2.0 and instead of a FillRectangle it says, that the DirectMode is not enabled, how to enable it? -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggiweb@metalab.unc.edu Thu Jun 3 18:14:12 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA05355 for ; Thu, 3 Jun 1999 18:14:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA04422; Thu, 3 Jun 1999 15:03:50 -0700 Resent-Date: Thu, 3 Jun 1999 15:03:50 -0700 Sender: marcus@e.kth.se Message-ID: <3756FBAF.56CDBA21@stacken.kth.se> Date: Thu, 03 Jun 1999 22:03:27 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: DGA 2.0 References: <99060323464900.09150@master> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"NZFrM.0.K31.xklLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13163 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > > Hi, > > I use the latest XFree 3.9 from cvs. > There is already dga 2.0 support for mystique card, > some older dga programs work, but libggi causes this: > > X Error of failed request: BadValue (integer parameter out of range for operation) > Major opcode of failed request: 141 (XFree86-VidModeExtension) > Minor opcode of failed request: 10 (XF86VidModeSwitchToMode) > Value in failed request: 0x26 > Serial number of failed request: 24 > Current serial number in output stream: 27 > > Maybe there are other video mode numbers now? No idea. Due to the closed source development model of XFree it is impossible to support, or even speculate about, features in pre- or beta releases of XFree. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Thu Jun 3 22:24:13 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA09702 for ; Thu, 3 Jun 1999 22:24:12 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA07321; Thu, 3 Jun 1999 19:13:46 -0700 Resent-Date: Thu, 3 Jun 1999 19:13:46 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990604012941.A2919@rz.uni-duesseldorf.de> Date: Fri, 4 Jun 1999 01:29:41 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Sure-fire way to detect GGI. Mail-Followup-To: ggi-develop@eskimo.com References: <19990603115052.1830.rocketmail@web130.yahoomail.com> <19990603165740.B628@rz.uni-duesseldorf.de> <19990603175233.E20961@maxime.u-strasbg.fr> <3756E057.1E4CA213@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <3756E057.1E4CA213@stacken.kth.se>; from Marcus Sundberg on Thu, Jun 03, 1999 at 08:06:47PM +0000 Resent-Message-ID: <"hOCDe2.0.Pm1.6PpLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13164 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > what about some libggi_not_there library of some kind, that just provide empty > > stubs, and a sure way for detecting that it is not the true ggi ? > Why in the world would you want that, when you can just as well > install the real LibGGI? Especially as installing LibGGI shouldn't break a single thing and not cause havoc (like SVGAlib could), _IF_ configured properly (e.g. disabled SVGAlib target and other potentially dangerous ones. IMHO you should just bring along or point to LibGGI and tell users to install it. Users happily install GTK+ in a bazillion of versions, so ... CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Thu Jun 3 22:24:18 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA09706 for ; Thu, 3 Jun 1999 22:24:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA07318; Thu, 3 Jun 1999 19:13:46 -0700 Resent-Date: Thu, 3 Jun 1999 19:13:46 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990604020804.B2919@rz.uni-duesseldorf.de> Date: Fri, 4 Jun 1999 02:08:04 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions Mail-Followup-To: ggi-develop@eskimo.com References: <19990603130851.C501@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Jon M. Taylor on Thu, Jun 03, 1999 at 12:15:36PM -0700 Resent-Message-ID: <"Kt8g32.0.3n1.EPpLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13165 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > That makes no sense. The driver must be written to support those interfaces, > Not at all. The bridge code that translates the driver's native API > into whatever userspace API is being used is contained in that API's > kgi-savage4 (or whatever) target code. I thought the whole point of the > target system was to be able to keep the kernel components (KGI drivers) as > lightweight as possible by this exact system. Yes. I think we have a misunderstanding here. See below. > > so not-yet designed interfaces have only a very remote chance to be > > compatible with an existing driver. > Right. They all need "driver" libraries to do the API bridging. Note, that I dislike the term "bridging" as it implies a "glue layer" of some kind. That's not what I am talking about. > > ??? Why should these interfaces differ ? > Because the APIs in question differ in their needs of the KGI driver, > and thus in the most efficient way(s) to represent the KGI driver's state. This has nothing to do with the way the userspace driver communicates with the kernelspace driver. > > Interfaces do _NOT_ describe any external interface toward the user, but > > only the Intraface between the LibGGI(-extension) module and the card > > driver. > Correct, and that will vary from extension to extension. No. The KGI driver exports a mmio region, or has a kgi_command.h style interface or whatever. The suggest-strings I am talking about do _not_ in any way communicate the specifics of the commands/features implemented by that interface. That's the business of interface-internal code, like kgicommand checking the returncode for supported commands. They just tell how to "get through" to the card. > It should be the library's responsibility to do the API bridge, There should not be a bridge, except in the sense that you need to map the user-API to the card API in some way. And that should be done in userspace. Right. Emulating other APIs is useless in deed. _BUT_ we have to tell userspace to what the exported APIs are compatible for quick results and better fallback compatibility. If you have one and only one ID-string, all extensions you don't provide drivers for are screwed and fall back to stubs or linear-* at best. But if you tell userspace: 1. This card has linear FB of type ... 2. This card can do kgicommand style access. 3. This card allows MMIO-access like any S3 >=Virge. 4. this card is a Savage-3D and allows extra commands for 3. This will provide a two-step fallback for all the extensions for which no special Savage-3D renderers exist yet. If the extension has S3 mmio support, great. If it has kgicommand well o.k., if not tough luck. _And_ it gives for much better code-reusability with much less cut/copy/paste (which is a nightmare to maintain). You only need to write the new functions for the savage3d, that were not there in the virge and be done with it. And for the next generation card, you can do the same. If a function differs, you override it. This way, you can "drop in" a new KGI driver into an existing system without having to install something into LibGGI. That decouples KGI and LibGGI development, which is IMHO a good thing, as when distributing binary drivers, you very probably will not be able to make one for all the possible versions of LibGGI floating around. Using a scheme that allows for fallback is much better in that respect, as there is less one _has_ to upgrade. > But wo do not have such a system at the present time, > and thus all the interface handling code has to be statically linked into the > driver, leading to bloat. The interfaces do _not_ need to be "handled", except for the kgicommand interface, which is special, as it does abstract the HW for common functions to allow for a decent basic mode of operation for any card, whether we have the modules for LibGGI or not. > > It just says something like "to send a command, use kgicommand(...)" > > or "this card exports an S3-style MMIO area with registers". > Or: > * This card can double/triple-buffer > * This card has a z/w-buffer with xxx bits of precision > * This card exports x number of tiled apertures, each with a different > possible stride/bitdepth/etc NOOOOO . That's precisely what it does _NOT_ do. This is the interfaces business. The render-lib has to know (due to the very fact that it is loaded, i.e. that the corresponding API string was given), or due to internal probing methods. > ...and this list goes on, and on, and on. And it will continue to grow > as new cards with all sorts of wacky types of features hit the market. This is exactly the reason for the API-_list_. Cards tend to accumulate features. And they tend to be backward-compatible. That's what the API-string give. _Not_ a precise list of features. That's DirectX style, and that's sick. You just tell the Lib which "language" is spoken on the channel and what level of vocabulary you can expect. Not, if any one word within that dictionary is supported or not. > > This is a natural process: > > When you write a new driver and you see it is 100% compatible to the older > > one for the functions supported there, plus a few new ones, you just keep > > exporting the old API-strings and add a new one for the new functions. > And in five years you have a hundred strings to support. Drivers > should be written, debugged, and then left alone. The userspace code is what > is flexible - it should bear the burden of bridging an extension API to the > KGI driver. You do not _ever_ have to touch an old driver. A new driver gets an additional string, if the card is compatible, and if it isn't, which happens from time to time, you strip the incompatible ones. > > Though I see reason for the AddAPI call (like the Mesa extension detecting > > GLX), and we should do that change. > Cool. The rest of this discussion is interesting but this is what is > preventing me from getting a working display/ subsystem in GGIMesa so it is > kind of urgent right now. I do not see any reason for this, if you just want to have a single API added, but if it makes you happy, so am I ... > > We will want to count APIAdds in case multiple extension want to add the > > same API string. > In LibGGI3D, the same interface can have different implementations. > How will we handle this? Will it even be possible? What is the problem with that ? the mapping is still up to the lib/extension itself. So if you have some external data on which to base that decision, it should work. I hope I have cleared up that misunderstanding about API strings. They are not intended as DirectX capability-flags V0.0.1, but as "hey Userspace, I'm a Savage 3D. Huh - you don't know me ... Sniff. O.K. - assume I'm a Virge. Heck, you don't know what that is ? O.K. - just assume im kgicommand capable o.k. ? Ah ... now we can talk.". And when userspace learns, it gets better. Of course such a mapping can be done in a userspace table like: savage3D: fallbacks to virge kgicommand linear* But the driver knows better, as the table might depend on mode or other circumstances like the #define SECURITY_LEVEL at compiletime, which might have inhibited the export of a moderately dangerous MMIO area, and we are talking about around 100 extra bytes max. CU, Andy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Fri Jun 4 01:49:23 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA13022 for ; Fri, 4 Jun 1999 01:49:22 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA01530; Thu, 3 Jun 1999 22:39:11 -0700 Resent-Date: Thu, 3 Jun 1999 22:39:11 -0700 Message-ID: <19990604054550.7672.rocketmail@web121.yahoomail.com> Date: Thu, 3 Jun 1999 22:45:50 -0700 (PDT) From: Kien Pham Subject: Re: GGI Cursor API proposal. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"957xW3.0.WN.xPsLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13166 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- Andreas Beck wrote: > > typedef struct ggi_cursor_t > > { > > ggi_visual_t vis; // Visual that the cursor is bound > to. > > void* image; // Must be of the same depth and color > format as the corresponding ggi_visual_t; > > This is _not_ the usual case. Most HW cursor are of a > really different > format. O.k. If so we can accept plain RGB or YUV bitmaps and do the actual conversion and scaling in ggiCreateCursor(). > > int width, height; > > int hotx, hoty; // hotspot > > } ggi_cursor_t; > > > ggi_cursor_id_t ggiCreateCursor(ggi_cursor_t cursor); > > int ggiMoveCursor(ggi_cursor_id_t cursor, int x, int > y); > > int ggiHideCursor(ggi_cursor_id_t cursor); > > int ggiShowCursor(ggi_cursor_id_t cursor); > > int ggiDeleteCursor(ggi_cursor_id_t cursor); > > This lacks cursor image setup. What kind of setup do you need? I wasn't aiming for a perfect API. Just one that is simple, useable, and can be implemented now. > > This API allows each visual to have multiple cursors > and it > > allows the cursors to move independently. What else can > you > > want? > > The most interesting part is setting up the bitmap. > > > Systems that do not support hardware cursors can use > > software emulation. > > No. They can't. This has been discussed here several > times. Please read up > the ML archives on that topic. If you have a better idea and want to implement it, great. :) I'm just selfishly trying to add features to GGI so I can make my stuff work. :) Software implementation is not a problem even in DirectBuffer when the proper hooks are added to GGI. It will probably be ugly and slow, but it'll work. Or we can add: boolean ggiCursorAvailable() and avoid all that extra code. Whatever the case, help me improve the API or replace it totally with your genious. Something is better than nothing. > CU, ANdy > > -- > = Andreas Beck | Email : > = ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Fri Jun 4 01:55:22 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA13069 for ; Fri, 4 Jun 1999 01:55:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA02637; Thu, 3 Jun 1999 22:45:18 -0700 Resent-Date: Thu, 3 Jun 1999 22:45:18 -0700 Message-ID: <19990604055157.8314.rocketmail@web121.yahoomail.com> Date: Thu, 3 Jun 1999 22:51:57 -0700 (PDT) From: Kien Pham Subject: Re: GGI and Hurd To: OKUJI Yoshinori Cc: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"_dHwx3.0.ue.hVsLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13167 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- OKUJI Yoshinori wrote: > From: Kien Pham > Subject: Re: GGI and Hurd > Date: Wed, 2 Jun 1999 21:16:49 -0700 (PDT) > > > Tell me where to look. > > I assume that you are asking for the information about > GNU Mach > device drivers and virtual memory system. I haven't seen > the > description of the device drivers. So I just investigated > it by > myself. As for the VM, the user interface and the basic > concept are > documented in the OSF Mach manuals, but the internals are > not. > > If you want to understand the GNU Mach internals, I > have to say "You > must read the source code by yourself." However, you > should find it > ugly soon, like me and UCHIYAMA Yasushi, who was working > on SMP > support for GNU Mach. If you have skill and time enough > to rewrite the > basic code from scratch, please discuss that with him, > otherwise > please bear it. > > ---------------------------------------------------------------------- > OKUJI Yoshinori > ^o-o^ > http://duff.kuicr.kyoto-u.ac.jp/~okuji (in English) m > / OK. I've forwarded your message to the GGI mailing list. Do you know of anyone who knows a lot about the internals of mach that I can get a hold of? I'm grasping at straws here. Also, what's Mr. UCHIYAMA Yasushi's e-mail address? Thanks again. ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Fri Jun 4 01:55:55 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA13089 for ; Fri, 4 Jun 1999 01:55:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA02737; Thu, 3 Jun 1999 22:45:46 -0700 Resent-Date: Thu, 3 Jun 1999 22:45:46 -0700 Date: Thu, 3 Jun 1999 22:45:40 -0700 From: "Samuel A. Falvo II" To: ggi-develop@eskimo.com Subject: Re: GGI Cursor API proposal. Message-ID: <19990603224540.A9741@dolphin.openprojects.net> References: <19990604054550.7672.rocketmail@web121.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990604054550.7672.rocketmail@web121.yahoomail.com>; from Kien Pham on Thu, Jun 03, 1999 at 10:45:50PM -0700 Resent-Message-ID: <"Tby2t2.0.Og.8WsLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13168 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, Jun 03, 1999 at 10:45:50PM -0700, Kien Pham wrote: > If you have a better idea and want to implement it, great. > :) I'm just selfishly trying to add features to GGI so I I have an extremely better idea. All mouse cursors are really sprites, so why not make a fast, portable, capable sprite engine? Game developers and OS developers will both thank you for it, I'm sure. ========================================================================== KC5TJA/6 | -| TEAM DOLPHIN |- DM13 | Samuel A. Falvo II QRP-L #1447 | http://www.dolphin.openprojects.net Oceanside, CA |...................................................... From ggiweb@metalab.unc.edu Fri Jun 4 02:17:33 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id CAA13282 for ; Fri, 4 Jun 1999 02:17:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA07677; Thu, 3 Jun 1999 23:07:24 -0700 Resent-Date: Thu, 3 Jun 1999 23:07:24 -0700 Date: Thu, 3 Jun 1999 23:07:25 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: GGIMesa updates/questions In-Reply-To: <19990604020804.B2919@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"ADURz2.0.it1.RqsLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13169 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 4 Jun 1999, Andreas Beck wrote: > > > That makes no sense. The driver must be written to support those interfaces, > > > Not at all. The bridge code that translates the driver's native API > > into whatever userspace API is being used is contained in that API's > > kgi-savage4 (or whatever) target code. I thought the whole point of the > > target system was to be able to keep the kernel components (KGI drivers) as > > lightweight as possible by this exact system. > > Yes. I think we have a misunderstanding here. See below. I think I have figured out why the misunderstanding happened. Also see below |->. > > > Interfaces do _NOT_ describe any external interface toward the user, but > > > only the Intraface between the LibGGI(-extension) module and the card > > > driver. > > > Correct, and that will vary from extension to extension. > > No. The KGI driver exports a mmio region, or has a kgi_command.h style > interface or whatever. Aaahhhh. I see what you are describing, but I would not call it an interface. Communications pipe and/or protocol is what those are. This explains the misunderstanding. > The suggest-strings I am talking about do _not_ in any way communicate the > specifics of the commands/features implemented by that interface. You mean "they do not communicate the specifics of the API which is represented/transmitted by the communications pipe/protocol". > That's the business of interface-internal code, like kgicommand checking the > returncode for supported commands. > > They just tell how to "get through" to the card. Right. A communications channel. Got it. [Rest of long discussion snipped] Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggiweb@metalab.unc.edu Fri Jun 4 02:39:29 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id CAA13427 for ; Fri, 4 Jun 1999 02:39:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA10539; Thu, 3 Jun 1999 23:29:20 -0700 Resent-Date: Thu, 3 Jun 1999 23:29:20 -0700 Sender: marcus@e.kth.se Message-ID: <37577237.72465624@stacken.kth.se> Date: Fri, 04 Jun 1999 06:29:11 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Sure-fire way to detect GGI. References: <19990603115052.1830.rocketmail@web130.yahoomail.com> <19990603165740.B628@rz.uni-duesseldorf.de> <19990603175233.E20961@maxime.u-strasbg.fr> <3756E057.1E4CA213@stacken.kth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"XYwkY1.0.Qa2.-8tLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13170 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg wrote: > > Sven LUTHER wrote: > > what about some libggi_not_there library of some kind, that just provide empty > > stubs, and a sure way for detecting that it is not the true ggi ? > > Why in the world would you want that, when you can just as well > install the real LibGGI? And to clarify - if you just install libggi.so without any sublibs you will effectively have your "empty stub". //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Fri Jun 4 03:43:55 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA13903 for ; Fri, 4 Jun 1999 03:43:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA19716; Fri, 4 Jun 1999 00:33:47 -0700 Resent-Date: Fri, 4 Jun 1999 00:33:47 -0700 From: becka@rz.uni-duesseldorf.de Message-Id: <199906040732.JAA17832@zeus.rz.uni-duesseldorf.de> Subject: Re: GGI Cursor API proposal. In-Reply-To: <19990604054550.7672.rocketmail@web121.yahoomail.com> from Kien Pham at "Jun 3, 99 10:45:50 pm" To: ggi-develop@eskimo.com Date: Fri, 4 Jun 1999 09:32:49 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"RW1fz.0.mp4.N5uLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13171 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi ! > > > void* image; // Must be of the same depth and color > > format as the corresponding ggi_visual_t; > > > > This is _not_ the usual case. Most HW cursor are of a > > really different > > format. > O.k. If so we can accept plain RGB or YUV bitmaps and do > the actual conversion and scaling in ggiCreateCursor(). Even that won't suffice. We will have to be able to set some extra data, like colors that induce a xor/and/or with the underlying bitmap, colors that are transparent etc. Maybe a completed LibGGI2D might help here, as IIRC it has all the hooks and modes needed. > > > ggi_cursor_id_t ggiCreateCursor(ggi_cursor_t cursor); > > > int ggiMoveCursor(ggi_cursor_id_t cursor, int x, int > > y); > > > int ggiHideCursor(ggi_cursor_id_t cursor); > > > int ggiShowCursor(ggi_cursor_id_t cursor); > > > int ggiDeleteCursor(ggi_cursor_id_t cursor); > > > > This lacks cursor image setup. > What kind of setup do you need? I wasn't aiming for a > perfect API. Just one that is simple, useable, and can be > implemented now. I think the best way to set up the cursor image would be, if we can Crossblit it from another visual. That's in the line of the general LibGGI philosophy. I think I have proposed a sprite/bob API a while ago and we've been discussing that between the "hardcore coders" for a while, but then got distracted. We should finally implement it. I'll skim through my mail archives and check with Marcus for a good preliminary API and then we should set up a "stub" extension. > > > Systems that do not support hardware cursors can use > > > software emulation. > > No. They can't. This has been discussed here several > > times. Please read up > > the ML archives on that topic. > If you have a better idea and want to implement it, great. > :) I'm just selfishly trying to add features to GGI so I > can make my stuff work. :) Please don't feel pissed, if I sound arrogant or something. It's just that the subject has been up too many times and noone ever coded something. > Software implementation is not a problem even in DirectBuffer when the > proper hooks are added to GGI. You are right in the sense, that GGI now _has_ hooks for that with the RessourceAcquire code. > It will probably be ugly and slow, but it'll work. As Linus said one day: I don't think we should emulate braindamage. If we make it a general Sprite/Bob API, I'd say we shouldn't try such an emulation anyway, as it will be overly complex and slow. The point is, that if you have no HW-cursor, the application should be told about that, as it can usually better decide on what to do then. Often significant optimizations can be done, if the application handles the cursor, then. With respect to multithreading, we'd have to at least block on sprite operations and all others, if emulated sprites are present, if we tried to emulate, so I'd say we should keep our hands off that. > Or we can add: > boolean ggiCursorAvailable() and avoid all that extra code. Yes. Something along that line makes sense. > Whatever the case, help me improve the API or replace it > totally with your genious. Something is better than nothing. Right you are. And I got the feeling you really want to get that done, so I again apologize, if I sounded harsh. Let's discuss this for the last time now. Let's find a good way to implement it and just do so. I'll dig out the mails about that subject when I get home and forward them to you, so we can have a look at all previous thoughts and find a good solution. CU, ANdy -- Andreas Beck | Email : From ggiweb@metalab.unc.edu Fri Jun 4 06:40:11 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA14958 for ; Fri, 4 Jun 1999 06:40:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA13197; Fri, 4 Jun 1999 03:29:40 -0700 Resent-Date: Fri, 4 Jun 1999 03:29:40 -0700 Message-ID: <19990604102949.22390.rocketmail@web124.yahoomail.com> Date: Fri, 4 Jun 1999 03:29:49 -0700 (PDT) From: Kien Pham Subject: Re: GGI Cursor API proposal. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"fQ2QQ.0.tD3.DgwLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13172 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- "Samuel A. Falvo II" wrote: > On Thu, Jun 03, 1999 at 10:45:50PM -0700, Kien Pham > wrote: > > If you have a better idea and want to implement it, > great. > > :) I'm just selfishly trying to add features to GGI so > I > > I have an extremely better idea. All mouse cursors are > really sprites, so > why not make a fast, portable, capable sprite engine? > Game developers and > OS developers will both thank you for it, I'm sure. Because all I really need is cursors to get my library done. I don't want to over do it with all kinds of fancy stuff. But if you want to step up to it and blow the world's mind by writing one...go right on ahead. :) I'll thank you for it. :) _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Fri Jun 4 07:34:28 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA15276 for ; Fri, 4 Jun 1999 07:34:27 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA22759; Fri, 4 Jun 1999 04:24:25 -0700 Resent-Date: Fri, 4 Jun 1999 04:24:25 -0700 Date: Fri, 4 Jun 1999 13:22:39 +0200 (CEST) From: Jos Hulzink To: GGI Development Subject: Riva TNT: Accellerated Mesa drivers !!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"l_rbV3.0.MZ5.dTxLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13173 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, NVidia has released Mesa drivers for Linux... www.nvidia.com Jos From ggiweb@metalab.unc.edu Fri Jun 4 10:26:13 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA17919 for ; Fri, 4 Jun 1999 10:26:12 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA04855; Fri, 4 Jun 1999 07:15:39 -0700 Resent-Date: Fri, 4 Jun 1999 07:15:39 -0700 Date: Fri, 4 Jun 1999 07:15:26 -0700 From: "Samuel A. Falvo II" To: ggi-develop@eskimo.com Subject: Re: GGI Cursor API proposal. Message-ID: <19990604071526.B10441@dolphin.openprojects.net> References: <19990604102949.22390.rocketmail@web124.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990604102949.22390.rocketmail@web124.yahoomail.com>; from Kien Pham on Fri, Jun 04, 1999 at 03:29:49AM -0700 Resent-Message-ID: <"ptTzq2.0.sA1.3-zLt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13174 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Because all I really need is cursors to get my library > done. I don't want to over do it with all kinds of fancy > stuff. What's so fancy about it? :-) The problems addressed with a "cursor" (more accurately known as a pointer; 'cursor' is really only used in the Windows camp to the best of my knowledge) are precisely the same problems addressed by sprites. Sprite engines, usually to accomodate games, have the single additional facility for detecting "collisions." Otherwise, they've identical feature-sets. ========================================================================== KC5TJA/6 | -| TEAM DOLPHIN |- DM13 | Samuel A. Falvo II QRP-L #1447 | http://www.dolphin.openprojects.net Oceanside, CA |...................................................... From ggiweb@metalab.unc.edu Fri Jun 4 12:42:11 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA20865 for ; Fri, 4 Jun 1999 12:42:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA21806; Fri, 4 Jun 1999 09:31:30 -0700 Resent-Date: Fri, 4 Jun 1999 09:31:30 -0700 Date: Fri, 4 Jun 1999 18:01:15 +0200 (MEST) To: ggi-develop@eskimo.com Subject: Re: libgii and libggi2d - can't compile it In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"zlwOE1.0.HK5.Tz_Lt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13175 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sun, 30 May 1999, Christoph Egger wrote: > > On Sun, 30 May 1999, Marcus Sundberg wrote: > > > Christoph Egger wrote: > > > > > > Hi! > > > > > > I've just downloaded the 990530 ggi-snapshot. > > > > > > I am always compiling GGI with > > > > > > "./autogen.sh && ./configure && make && su -c "make install" > > > > That's impossible because there is no file named autoconf in > > any of the library directories... You mean autogen.sh, right? > > Yes. Sorry. Was a typos mistake. > > > It's not necessary to run autogen.sh when using a snapshot. > > Oh! I didn't know that! Testing with > > ./configure && make && su -c "make install" ... > > Yes, libgii compiles! Thanks! > > > > > > I've installed libtool 1.2f, autoconf 2.13 and automake 1.4! > > > > > > At this snapshot I get this error on compiling libgii: > > > > > > configure.in:128: warning: AC_TRY_RUN called without default to allow cross compiling > > > autoconf: Undefined macros: > > > configure.in:38:AC_LIBTOOL_DLOPEN > > > configure.in:39:AC_LIBTOOL_WIN32_DLL > > > > Due to a braindamaged bug in automake you can't have libtool.m4 > > installed on the system when you run 'aclocal -I .'. > > > > Steve, could you remove $prefix/share/aclocal/libtool.m4 from the > > snapshot generating system, or if that is not possible - install > > your own copy of automake 1.4 in a different location and use that > > for snapshot generation. > > > > > At this snapshot I get this error on compiling libggi2d: > > > > > > make: *** No rule to make target `@MAINTAINER_MODE_TRUE@', needed by `Makefile.in'. > > > > I just added LibGGI2D to the list of directories which is autoconfed > > for snapshots, should work in the next snapshot > > Great! Will test! OK! I've just downloaded the ggi 990604 snapshot. Now I can compile all two libs again! Thanks! Christoph Egger E-Mail: Christoph_Egger@t-online.de From ggiweb@metalab.unc.edu Fri Jun 4 13:44:39 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA22235 for ; Fri, 4 Jun 1999 13:44:36 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA08782; Fri, 4 Jun 1999 10:34:14 -0700 Resent-Date: Fri, 4 Jun 1999 10:34:14 -0700 Date: Fri, 4 Jun 1999 12:35:36 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: mailing list GGI Subject: XGGI and latest GGI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"HvdH-3.0.382.Du0Mt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13176 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I got and installed latest libggi and xggi. Does XGGI now have acceleration for matrox mystique? Is there a FAQ online that says how to set it up?(font paths, keyboard # of keys, monitor, etc) Perhaps an import utility of /etc/X11/XF86Config would be a good idea? thanks! -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Fri Jun 4 14:55:09 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA23681 for ; Fri, 4 Jun 1999 14:55:05 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA06663; Fri, 4 Jun 1999 11:44:45 -0700 Resent-Date: Fri, 4 Jun 1999 11:44:45 -0700 From: Denis Oliver Kropp Reply-To: dok@fischlustig.de Organization: Fischlustig To: ggi-develop@eskimo.com Subject: aalib with 16 bit Date: Fri, 4 Jun 1999 20:17:24 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99060420184701.12241@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"6EkSc3.0.3d1.Pw1Mt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13177 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, how is it possible to use the aalib target with apps using 16 bit target depth? I saw palemu, but don't know how to use it, if it is the right thing to get out of this problem. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggiweb@metalab.unc.edu Fri Jun 4 15:15:33 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA24129 for ; Fri, 4 Jun 1999 15:15:30 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA17475; Fri, 4 Jun 1999 12:05:17 -0700 Resent-Date: Fri, 4 Jun 1999 12:05:17 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990604195439.A517@rz.uni-duesseldorf.de> Date: Fri, 4 Jun 1999 19:54:39 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: XGGI and latest GGI Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from David Cougle on Fri, Jun 04, 1999 at 12:35:36PM -0500 Resent-Message-ID: <"av0Fl1.0.RG4.hD2Mt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13178 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I got and installed latest libggi and xggi. Does XGGI now have > acceleration for matrox mystique? If the unserlying hardware driver has, then yes. What do you use ? SVGAlib ? fbcon from kernel ? kgicon ? > Is there a FAQ online that says how to set it up? ( > font paths, -fp "path" alternatively xset fp "new font path" at runtime > keyboard # of keys, Not needed. Load the country specific keymap and be happy. LibGGI handles that. > monitor, Is as well handled by the underlying display subsystem. If you use kgicon, you have to use setmon, fbcon uses /etc/fb.modes, and SVGAlib probably some entry in /etc/vga/libvga.config . > Perhaps an import utility of /etc/X11/XF86Config would be a good idea? 90% of the stuff there is not needed for an XGGI server. That's because XGGI doesn't incorporate the graphics driver. CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Fri Jun 4 15:30:51 1999 -0400 Status: X-Status: X-Keywords: Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA24468 for ; Fri, 4 Jun 1999 15:30:49 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id MAA28617; Fri, 4 Jun 1999 12:21:02 -0700 (PDT) Resent-Date: Fri, 4 Jun 1999 12:21:02 -0700 (PDT) Date: Fri, 4 Jun 1999 14:18:16 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: XGGI and latest GGI In-Reply-To: <19990604195439.A517@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"4DVqL2.0.Ux6.XR2Mt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13179 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I have fb for matrox in kernel installed, but isn't it better to use kgicon? svgalib is also installed. When will you have acceleration for sis6326? On Fri, 4 Jun 1999, Andreas Beck wrote: > > I got and installed latest libggi and xggi. Does XGGI now have > > acceleration for matrox mystique? > > If the unserlying hardware driver has, then yes. What do you use ? > SVGAlib ? fbcon from kernel ? kgicon ? > > > Is there a FAQ online that says how to set it up? ( > > font paths, > -fp "path" > alternatively xset fp "new font path" at runtime > > > keyboard # of keys, > > Not needed. Load the country specific keymap and be happy. LibGGI handles > that. > > > monitor, > > Is as well handled by the underlying display subsystem. If you use kgicon, > you have to use setmon, fbcon uses /etc/fb.modes, and SVGAlib probably > some entry in /etc/vga/libvga.config . > > > Perhaps an import utility of /etc/X11/XF86Config would be a good idea? > > 90% of the stuff there is not needed for an XGGI server. > That's because XGGI doesn't incorporate the graphics driver. > > CU, ANdy > > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Fri Jun 4 16:48:53 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA26050 for ; Fri, 4 Jun 1999 16:48:52 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA31554; Fri, 4 Jun 1999 13:38:15 -0700 Resent-Date: Fri, 4 Jun 1999 13:38:15 -0700 Sender: marcus@e.kth.se Message-ID: <37583912.120B5A17@stacken.kth.se> Date: Fri, 04 Jun 1999 20:37:38 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: aalib with 16 bit References: <99060420184701.12241@master> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"1boLf2.0.9i7.ja3Mt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13180 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > > Hi, > > how is it possible to use the aalib target with apps using 16 bit target > depth? That is not possible. You can use it with apps using 24 or 32 bit modes though, using the trueemu target. > I saw palemu, but don't know how to use it, if it is the right thing > to get out of this problem. palemu as the name suggests does the opposite - it emulates a paletted mode on a truecolor mode. Trueemu it was you need here, but it only supports 24 and 32 bit modes. You're welcome to improve it ofcourse. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Fri Jun 4 16:51:33 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA26118 for ; Fri, 4 Jun 1999 16:51:30 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA00474; Fri, 4 Jun 1999 13:41:21 -0700 Resent-Date: Fri, 4 Jun 1999 13:41:21 -0700 Sender: marcus@e.kth.se Message-ID: <375839E2.EA20E7B@stacken.kth.se> Date: Fri, 04 Jun 1999 20:41:06 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: XGGI and latest GGI References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"2hR1e2.0.l6.id3Mt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13181 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > > I have fb for matrox in kernel installed, but isn't it better to use > kgicon? svgalib is also installed. The mystique is not accelerated in kgicon, you'll have to use matroxfb for acceleration > When will you have acceleration for sis6326? When someone writes a driver for it. It could be you. ;-) //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Fri Jun 4 16:56:24 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA26216 for ; Fri, 4 Jun 1999 16:56:22 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA02468; Fri, 4 Jun 1999 13:45:54 -0700 Resent-Date: Fri, 4 Jun 1999 13:45:54 -0700 Date: Fri, 4 Jun 1999 15:46:44 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: XGGI and latest GGI In-Reply-To: <375839E2.EA20E7B@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"AvP8x2.0.7c.0i3Mt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13182 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I have matroxfb enabled in kernel. So all I have to is run XGGI and it will use the matroxfb for acceleration in X? On Fri, 4 Jun 1999, Marcus Sundberg wrote: > David Cougle wrote: > > > > I have fb for matrox in kernel installed, but isn't it better to use > > kgicon? svgalib is also installed. > > The mystique is not accelerated in kgicon, you'll have to use matroxfb > for acceleration > > > When will you have acceleration for sis6326? > > When someone writes a driver for it. It could be you. ;-) > > //Marcus > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Fri Jun 4 17:36:25 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA27018 for ; Fri, 4 Jun 1999 17:36:24 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA15723; Fri, 4 Jun 1999 14:26:17 -0700 Resent-Date: Fri, 4 Jun 1999 14:26:17 -0700 Sender: marcus@e.kth.se Message-ID: <3758446F.62317376@stacken.kth.se> Date: Fri, 04 Jun 1999 21:26:07 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: XGGI and latest GGI References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"4sqOF2.0.Qr3.uH4Mt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13183 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > > I have matroxfb enabled in kernel. So all I have to is run XGGI and it > will use the matroxfb for acceleration in X? Yes, that's all. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Fri Jun 4 23:23:46 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA02071 for ; Fri, 4 Jun 1999 23:23:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA26214; Fri, 4 Jun 1999 20:14:27 -0700 Resent-Date: Fri, 4 Jun 1999 20:14:27 -0700 Sender: martine@concentric.net Message-ID: <375897AB.C17D1421@concentric.net> Date: Fri, 04 Jun 1999 20:21:15 -0700 From: Evan Martin X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.8 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Riva TNT: Accellerated Mesa drivers !!! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"ZgeGb2.0.uL6.4O9Mt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13184 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jos Hulzink wrote: > NVidia has released Mesa drivers for Linux... Since I'm an nVidia user, I thought I'd elaborate: nVidia has updated their X server (which supports the NV1, 128, 128ZX, TNT, and TNT2) to support Mesa/GLX on their 3D cards (all of the above except the NV1). I have a RIVA 128, and this is what I see: The updated X server is a bit faster: one of the window moving options in enlightenment no longer takes 5 seconds per frame, because of accellerated pattern fills. I'm not so sure of the 3D support. The instructions tell you to replace libMesaGL.so with their provided libGL.so . I tried running some of the examples included with some GL tutorials, and didn't notice a big difference. A few of them ran, and a few of them segfaulted. The real difference with hardware GL would be speed, of course, but it was hard to see. I couldn't get anything to run double-buffered, because glutCreateWindow() would terminate the program if glutInitDisplayMode() had been called with the GLUT_DOUBLE parameter. This included many of the mesa demos. :\ Also, my initial message that I was writing to this list was lost, because the X server crashed. (These problems are all specific to the nVidia-provided libGL.so: All of these problems didn't occur when I was using the debian libMesaGL.so, which is the software-only version, of course.) I hope my problems are attributable to using binaries. I may try using their patches and compiling mesa, x, and the glx module. -- Evan Martin - txs@concentric.net - http://e.x0r.ml.org From ggiweb@metalab.unc.edu Fri Jun 4 23:56:08 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA02761 for ; Fri, 4 Jun 1999 23:56:07 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA02259; Fri, 4 Jun 1999 20:47:08 -0700 Resent-Date: Fri, 4 Jun 1999 20:47:08 -0700 From: Thad Phetteplace Message-Id: <199906050900.EAA14029@dexter.glaci.com> Subject: Re: Riva TNT: Accellerated Mesa drivers !!! To: ggi-develop@eskimo.com Date: Sat, 5 Jun 1999 04:00:15 -0500 (CDT) In-Reply-To: <375897AB.C17D1421@concentric.net> from "Evan Martin" at Jun 4, 99 08:21:15 pm Content-Type: text Resent-Message-ID: <"8G7u5.0.2Z.xs9Mt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13185 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Since I'm an nVidia user, I thought I'd elaborate: > nVidia has updated their X server (which supports the NV1, 128, 128ZX, > TNT, > and TNT2) to support Mesa/GLX on their 3D cards (all of the above except > the > NV1). I was sort of hoping they offered a non-GLX full screen mesa targed similar to the GLIDE target for Mesa. That would be more useful for game development (IMHO). Still, the GLX support will be useful, and since the source is available, supporting these cards under GGI will be much simplified. Thad From ggiweb@metalab.unc.edu Sat Jun 5 00:33:14 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA03104 for ; Sat, 5 Jun 1999 00:33:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA11149; Fri, 4 Jun 1999 21:24:22 -0700 Resent-Date: Fri, 4 Jun 1999 21:24:22 -0700 Date: Sat, 5 Jun 1999 01:04:09 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Re: GGI Cursor API proposal. In-Reply-To: <19990604071526.B10441@dolphin.openprojects.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"Blnag.0.vj2.pPAMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13186 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 4 Jun 1999, Samuel A. Falvo II wrote: > The problems addressed with a "cursor" (more accurately known as a pointer; > 'cursor' is really only used in the Windows camp to the best of my > knowledge) are precisely the same problems addressed by sprites. Sprite > engines, usually to accomodate games, have the single additional facility > for detecting "collisions." Otherwise, they've identical feature-sets. If we're talking software emulation, it is a bit complicated, as the emulated sprite/cursor must be "undone" before primitives are drawn and redrawn afterwards. Perhaps the easiest way to do this is assume all sprite/cursors are like this, and advise app developers to call a "hide/unhide" function which for hardware sprites/cursors will do nothing. A generic feature/sprite API proposal of mine is out to Marcus and Andy for comments, when we get details banged out to where it looks good to them for the GGI core and/or an extension I'm willing to start coding on it again (my first attempt "ggiAuxBuf" was a bit of a dead end so I abandoned that angle). -- Brian From ggiweb@metalab.unc.edu Sat Jun 5 07:56:39 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA06096 for ; Sat, 5 Jun 1999 07:56:37 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA07450; Sat, 5 Jun 1999 04:47:46 -0700 Resent-Date: Sat, 5 Jun 1999 04:47:46 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990605130410.C508@rz.uni-duesseldorf.de> Date: Sat, 5 Jun 1999 13:04:10 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Riva TNT: Accellerated Mesa drivers !!! Mail-Followup-To: ggi-develop@eskimo.com References: <375897AB.C17D1421@concentric.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <375897AB.C17D1421@concentric.net>; from Evan Martin on Fri, Jun 04, 1999 at 08:21:15PM -0700 Resent-Message-ID: <"FCfRg.0.tp1.SvGMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13187 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > The real difference with hardware GL would be speed, of course, but > it was hard to see. I couldn't get anything to run double-buffered, > because glutCreateWindow() would terminate the program if > glutInitDisplayMode() had been called with the GLUT_DOUBLE parameter. > This included many of the mesa demos. :\ I suppose this is a general problem with running doublebuffered modes within a window in X. Without hardware specifically designed for it (don't know, if the TNT is, though), this can't be done without much overhead. Doublebuffering means that you have two versions of the displayed image and switch between them. Doing so on a fullscreen display is simple. You just change the start address of the vidmem. In a window, this would mean, that you'd have to copy the entire surroundings of the window before flipping. The hardware support I'm talking about is either: - treating the window as a big sprite. You can then change the base address of the sprite memory or write one image into regular vidmem and turn on/off such a sprite to see the second page which comes from sprite memory. - having special bits in the framebuffer that do HW-frameflipping on a per-pixel basis. It's like having a "setup-bitplane" that tells how data for a specific reagion is to be fetched from vidmem. AFAIK that's what allows SGI to have truecolor and palettized displays at the same time. CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Sat Jun 5 12:45:14 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA07995 for ; Sat, 5 Jun 1999 12:45:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA26800; Sat, 5 Jun 1999 09:36:21 -0700 Resent-Date: Sat, 5 Jun 1999 09:36:21 -0700 Sender: wouter@xs4all.nl Message-ID: <37595130.1F73B534@xs4all.nl> Date: Sat, 05 Jun 1999 18:32:48 +0200 From: WHS Organization: robots anonymous X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.34 i586) MIME-Version: 1.0 To: ggi-misc@kludge.org CC: steve@ggi-project.org, ggi-develop@eskimo.com Subject: descent etc [Re: Mouse: Error reading mouse ...] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"t4Y9G.0.QY6.18LMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13188 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com teunis wrote: > > On Thu, 20 May 1999 becka@rz.uni-duesseldorf.de wrote: > > > Hi ! > > > > > BTW - anyone have a working GGI Descent? :) > > > > Sure. Guess where you can find it ... ftp.ggi-project.org. Or on Wouter's > > pages ... > > The ftp.ggi-project.org version doesn't work for me (too old? - it's > asking for pre-DirectBuffer info that's no longer present) > And I can't get to Wouter's page for some reason...(404 - not found) > > Anyone know why? Yes. My e-address changed. direct references to the ggi (lens demo) & descent pages are: http://www.xs4all.nl/~whs/ggi/ggi.html http://www.xs4all.nl/~whs/spellen/descent/descent.html > ps: I definitely -can't- help out on anything in GGI due to depression. If it hasn't > happened already take me out of whereever I am a contact. On the war of > depression versus programming depression won. [sorry bout this] Yes, I had/have this too. I'm taking things very easy and doing very little programming (even on GSI, the next generation ;). Hopefully, my interest picks up again soon so I can finish that obsd port. PS. I'm crospossting to ggi-misc@kludge.org as eskimo doesn't accept posts I make from obsd so I have to advocate the kludge list ;) Wouter GSI (pcm/midi/cd/mixer), GGI, descent, OpenBSD: http://www.xs4all.nl/~whs/ From ggiweb@metalab.unc.edu Sat Jun 5 14:55:55 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA09238 for ; Sat, 5 Jun 1999 14:55:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA04541; Sat, 5 Jun 1999 11:47:07 -0700 Resent-Date: Sat, 5 Jun 1999 11:47:07 -0700 Date: Sat, 5 Jun 1999 13:48:23 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: mailing list GGI Subject: XGGI! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"5b-nR1.0.Q61.d2NMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13189 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ok, I can start XGGI, but mouse does not work, resolution is 640x480, my WM does not start. Isn't there a text file I can store all of this information in or something so that I can just type "XGGI" to start it? I obviously need to store... font path resolution monitor info? mouse info keyboard info(104 key) ?????? -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sat Jun 5 14:57:36 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA09257 for ; Sat, 5 Jun 1999 14:57:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA05041; Sat, 5 Jun 1999 11:48:51 -0700 Resent-Date: Sat, 5 Jun 1999 11:48:51 -0700 Date: Sat, 5 Jun 1999 13:50:25 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: mailing list GGI Subject: also Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"ppOZD2.0.TE1.H4NMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13190 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com location /usr/X11R6/lib/X11/fonts/ you don't need to specify a fontpath. that's from the readme. I DO Have my fonts there and i have to specify a fontpath. -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sat Jun 5 14:57:38 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA09261 for ; Sat, 5 Jun 1999 14:57:37 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA05073; Sat, 5 Jun 1999 11:48:53 -0700 Resent-Date: Sat, 5 Jun 1999 11:48:53 -0700 Message-ID: <06f901beaf84$d32c6b00$d417d7d1@massacre> From: "David Waite" To: References: <375897AB.C17D1421@concentric.net> <19990605130410.C508@rz.uni-duesseldorf.de> Subject: Re: Riva TNT: Accellerated Mesa drivers !!! Date: Sat, 5 Jun 1999 14:54:21 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Resent-Message-ID: <"av7O42.0.0F1.J4NMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13191 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com ----- Original Message ----- From: Andreas Beck > > The real difference with hardware GL would be speed, of course, but > > it was hard to see. I couldn't get anything to run double-buffered, > > because glutCreateWindow() would terminate the program if > > glutInitDisplayMode() had been called with the GLUT_DOUBLE parameter. > > This included many of the mesa demos. :\ > What resolution were you in? I have heard reports that this version of the driver does not work properly in modes other than 15/16 bit (even if you have a TNT, blah). Also, if you are in a resolution too high for your britches (800x600 for Riva 128, 1280x1024 I think for the TNT are the maxes), you won't have enough memory for the card to make both a Z-Buffer and another copy of the window. > Without hardware specifically designed for it (don't know, if the TNT is, > though), this can't be done without much overhead. TNT is DEFINATELY designed for doublebuffering. 3D accells would be near useless without it. > Doublebuffering means that you have two versions of the displayed image > and switch between them. Doing so on a fullscreen display is simple. You > just change the start address of the vidmem. In a window, this would mean, > that you'd have to copy the entire surroundings of the window before > flipping. > > The hardware support I'm talking about is either: > - treating the window as a big sprite. You can then change the base address > of the sprite memory or write one image into regular vidmem and turn on/off > such a sprite to see the second page which comes from sprite memory. > - having special bits in the framebuffer that do HW-frameflipping on a > per-pixel basis. It's like having a "setup-bitplane" that tells how data > for a specific reagion is to be fetched from vidmem. AFAIK that's what > allows SGI to have truecolor and palettized displays at the same time. > > CU, ANdy > > -- > = Andreas Beck | Email : = > From ggiweb@metalab.unc.edu Sat Jun 5 15:04:08 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA09333 for ; Sat, 5 Jun 1999 15:04:07 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA07881; Sat, 5 Jun 1999 11:55:22 -0700 Resent-Date: Sat, 5 Jun 1999 11:55:22 -0700 Message-ID: <3759726C.E525278@t-online.de> Date: Sat, 05 Jun 1999 18:54:36 +0000 X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.9 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Riva TNT: Accellerated Mesa drivers !!! References: <375897AB.C17D1421@concentric.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 0511635709-0001@t-online.de From: Achim_Kaiser@t-online.de (Achim Kaiser) Resent-Message-ID: <"Zx14U3.0.Ew1.LANMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13192 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com No! Evan Martin wrote: > I'm not so sure of the 3D support. > The instructions tell you to replace libMesaGL.so with their provided > libGL.so . I tried running some of the examples included with some > GL tutorials, and didn't notice a big difference. A few of them ran, > and a few of them segfaulted. Make sure, that you delete the old mesa library! Do not use "mv" to make a backup. ldconfig changes the links to the backup file! I have a RivaTNT and I MUST say that I'm impressed. I'm running "bzflag" in 1152x864 with 20 frames/sec. All settings are set to maximum. Without hardware acceleration I get 1 Picture in 3 sec. WOW!!! You are right, not all mesa demos are running. But the most, including "fire". Very nice! Hardware : Pentium II 350MHz 128MB RivaTNT AGP Achim From ggiweb@metalab.unc.edu Sat Jun 5 15:38:51 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA09622 for ; Sat, 5 Jun 1999 15:38:50 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA18196; Sat, 5 Jun 1999 12:30:05 -0700 Resent-Date: Sat, 5 Jun 1999 12:30:05 -0700 Sender: marcus@e.kth.se Message-ID: <37597AB2.6154AA7A@stacken.kth.se> Date: Sat, 05 Jun 1999 19:29:54 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: also References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"uSetk3.0.3S4.xgNMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13193 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > > location /usr/X11R6/lib/X11/fonts/ you don't need to specify a fontpath. > > that's from the readme. > > I DO Have my fonts there and i have to specify a fontpath. This is the default font-path of standard XGGI: /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ What does 'strings XGGI|grep /usr' on your XGGI binary tell you? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Sat Jun 5 15:56:28 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA09766 for ; Sat, 5 Jun 1999 15:56:27 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA22252; Sat, 5 Jun 1999 12:47:31 -0700 Resent-Date: Sat, 5 Jun 1999 12:47:31 -0700 Date: Sat, 5 Jun 1999 14:49:02 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: also In-Reply-To: <37597AB2.6154AA7A@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"bk0yW.0.IR5.GxNMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13194 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com strings XGGI|grep /usr /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ /usr/X11R6/lib/X11/rgb /usr/adm/X%smsgs /usr/X11R6/lib/X11/xserver/SecurityPolicy /usr/X11R6/lib/X11/xkb Could you help me with the other mail? I really would like to use XGGI now that it has acceleration for matrox. I need to specify my resolution, keyboard options(104key), mouse, and whatever else? On Sat, 5 Jun 1999, Marcus Sundberg wrote: > David Cougle wrote: > > > > location /usr/X11R6/lib/X11/fonts/ you don't need to specify a fontpath. > > > > that's from the readme. > > > > I DO Have my fonts there and i have to specify a fontpath. > > This is the default font-path of standard XGGI: > /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ > > What does 'strings XGGI|grep /usr' on your XGGI binary tell you? > > //Marcus > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sat Jun 5 16:13:32 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA09875 for ; Sat, 5 Jun 1999 16:13:30 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA25849; Sat, 5 Jun 1999 13:04:39 -0700 Resent-Date: Sat, 5 Jun 1999 13:04:39 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990605220736.A9306@rz.uni-duesseldorf.de> Date: Sat, 5 Jun 1999 22:07:36 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: XGGI! Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from David Cougle on Sat, Jun 05, 1999 at 01:48:23PM -0500 Resent-Message-ID: <"rhc_V2.0.eJ6.MBOMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13195 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Ok, I can start XGGI, but mouse does not work, You have not configured your mouse for LibGII - right ? Either configure your /etc/vga/libVGA.conf, or set up your ~/.ggi/input/linux-mouse or whatever. Check that your mouse setup is o.k. with inputdump or monitest. When that works, try XGGI. > resolution is 640x480, -modes 1024x768 > my WM does not start. XGGI is an X _SERVER_ not an X startup system like startx. Use a script or change your X symlink, or tell startx to use the XGGI server. If you enter plain X, you get the same effect. > Isn't there a text file I can store all of this information in or > something so that I can just type "XGGI" to start it? How about a script ? I tend to use, though AFAIK it isn't needed anymore. -----------snip---------- #!/bin/bash # DIS=${1:-:0} (export DISPLAY=$DIS ; sleep 3; fvwm2 & sleep 1 ;\ xmodmap /usr/local/lib/ggi/xggikeymaps/xggimap.base ; \ xmodmap /usr/local/lib/ggi/xggikeymaps/xggimap.de_de \ ) & exec XGGI $* -noxfreeemu -----------snip---------- > I obviously need to store... > font path -fp in the script. > resolution -modes in the script > monitor info? XGGI has no business with that. That depends solely on the underlying graphics subsystem. > mouse info > keyboard info(104 key) Same here. Configure LibGII and LibGGI appropriately and be done with it. Regarding keyboard, you of course have to load the appropriate xmodmaps. CU, Andy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Sat Jun 5 16:15:46 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA09882 for ; Sat, 5 Jun 1999 16:15:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA26512; Sat, 5 Jun 1999 13:06:56 -0700 Resent-Date: Sat, 5 Jun 1999 13:06:56 -0700 Sender: marcus@e.kth.se Message-ID: <37598356.478E2469@stacken.kth.se> Date: Sat, 05 Jun 1999 20:06:46 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: XGGI! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"zpJ-R1.0._T6.VDOMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13196 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > > Ok, I can start XGGI, but mouse does not work, Have you configured the mouse for LibGII? > resolution is 640x480, Just set a different one, see below. > my WM does not start. Then you probably haven't started it. No X-server starts a window manager, you need a script or something like xdm or xinit for that. > Isn't there a text file I can store all of this information in or > something so that I can just type "XGGI" to start it? XGGI is just an X-server, if you want to start other programs with a single command you need a script as with any other X-server. > I obviously need to store... > font path Shouldn't be necessary, see my other mail. > resolution Specified on the command line or with normal LibGGI envvars. See doc/env.txt in the LibGGI distribution and the XGGI README. > monitor info? No, that's the job of the graphics driver. > mouse info No, just configure your mouse for LibGII. See doc/inputs.txt in the LibGII distribution. > keyboard info(104 key) As Andy said there's nothing to configure, just load a national keymap unless you want a US keyboard mapping. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Sat Jun 5 16:21:30 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA09927 for ; Sat, 5 Jun 1999 16:21:29 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA27700; Sat, 5 Jun 1999 13:12:43 -0700 Resent-Date: Sat, 5 Jun 1999 13:12:43 -0700 Sender: marcus@e.kth.se Message-ID: <375984B5.574FFB37@stacken.kth.se> Date: Sat, 05 Jun 1999 20:12:37 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: also References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"vgDtx2.0.Vm6.vIOMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13197 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > > strings XGGI|grep /usr > /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ > /usr/X11R6/lib/X11/rgb > /usr/adm/X%smsgs > /usr/X11R6/lib/X11/xserver/SecurityPolicy > /usr/X11R6/lib/X11/xkb That seems really odd, it's the excact same thing as I have here. Not sure why it doesn't find your fonts. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Sat Jun 5 16:28:33 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA09993 for ; Sat, 5 Jun 1999 16:28:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA29268; Sat, 5 Jun 1999 13:19:43 -0700 Resent-Date: Sat, 5 Jun 1999 13:19:43 -0700 Sender: martine@concentric.net Message-ID: <37598803.30B89564@concentric.net> Date: Sat, 05 Jun 1999 13:26:44 -0700 From: Evan Martin X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.8 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Riva TNT: Accellerated Mesa drivers !!! References: <375897AB.C17D1421@concentric.net> <19990605130410.C508@rz.uni-duesseldorf.de> <06f901beaf84$d32c6b00$d417d7d1@massacre> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"dtrXk.0.y87.UPOMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13198 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Waite wrote: > What resolution were you in? I have heard reports that this version of the > driver does not work properly in modes other than 15/16 bit (even if you > have a TNT, blah). Also, if you are in a resolution too high for your > britches (800x600 for Riva 128, 1280x1024 I think for the TNT are the > maxes), you won't have enough memory for the card to make both a Z-Buffer > and another copy of the window. Ah, great! It works at 800x600. What's particularly interesting about that, though, is that 1024xres * 768yres * 2bytesperpixel * 2buffers = 3,145,728 bytes. You'd think it would work on my 4mb video card. I'd guess that other stuff is using some video memory. -- Evan Martin - txs@concentric.net - http://e.x0r.ml.org From ggiweb@metalab.unc.edu Sat Jun 5 16:53:56 1999 -0400 Status: X-Status: X-Keywords: Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA10232 for ; Sat, 5 Jun 1999 16:53:55 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id NAA14821; Sat, 5 Jun 1999 13:45:58 -0700 (PDT) Resent-Date: Sat, 5 Jun 1999 13:45:58 -0700 (PDT) Date: Sat, 5 Jun 1999 15:40:28 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: also In-Reply-To: <375984B5.574FFB37@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"sfwBp3.0.Bd3.anOMt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13199 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com dir /usr/X11R6/lib/X11/fonts/ total 16k drwxr-xr-x 9 root root 1.0k Apr 18 18:32 . drwxr-xr-x 15 root root 1.0k May 18 21:19 .. drwxr-xr-x 2 root root 5.0k May 18 21:19 75dpi drwxr-xr-x 2 root root 1.0k May 18 21:19 PEX drwxr-xr-x 2 root root 1.0k May 18 21:19 Speedo drwxr-xr-x 2 root root 1.0k May 18 21:19 Type1 drwxr-xr-x 2 999 users 3.0k Mar 23 1995 freefont drwxr-xr-x 2 root root 2.0k May 26 15:41 misc drwxr-xr-x 2 999 users 1.0k Mar 23 1995 sharefont On Sat, 5 Jun 1999, Marcus Sundberg wrote: > David Cougle wrote: > > > > strings XGGI|grep /usr > > /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ > > /usr/X11R6/lib/X11/rgb > > /usr/adm/X%smsgs > > /usr/X11R6/lib/X11/xserver/SecurityPolicy > > /usr/X11R6/lib/X11/xkb > > That seems really odd, it's the excact same thing as I have here. > Not sure why it doesn't find your fonts. > > //Marcus > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sat Jun 5 16:53:58 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA10237 for ; Sat, 5 Jun 1999 16:53:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA00302; Sat, 5 Jun 1999 13:45:12 -0700 Resent-Date: Sat, 5 Jun 1999 13:45:12 -0700 Date: Sat, 5 Jun 1999 15:46:21 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: XGGI! In-Reply-To: <37598356.478E2469@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"TBXM81.0.S4.MnOMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13200 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com But I have my .xinitrc setup, that's why it starts up gnome/icewm when I type startx. Am I supposed to be typing XGGI to start it, or somehow start it with startx? How do I configure mouse for libggi? On Sat, 5 Jun 1999, Marcus Sundberg wrote: > David Cougle wrote: > > > > Ok, I can start XGGI, but mouse does not work, > > Have you configured the mouse for LibGII? > > > resolution is 640x480, > > Just set a different one, see below. > > > my WM does not start. > > Then you probably haven't started it. No X-server starts a window > manager, you need a script or something like xdm or xinit for that. > > > Isn't there a text file I can store all of this information in or > > something so that I can just type "XGGI" to start it? > > XGGI is just an X-server, if you want to start other programs with > a single command you need a script as with any other X-server. > > > I obviously need to store... > > font path > > Shouldn't be necessary, see my other mail. > > > resolution > > Specified on the command line or with normal LibGGI envvars. See > doc/env.txt in the LibGGI distribution and the XGGI README. > > > monitor info? > > No, that's the job of the graphics driver. > > > mouse info > > No, just configure your mouse for LibGII. See doc/inputs.txt in > the LibGII distribution. > > > keyboard info(104 key) > > As Andy said there's nothing to configure, just load a national > keymap unless you want a US keyboard mapping. > > //Marcus > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sat Jun 5 17:08:31 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA10376 for ; Sat, 5 Jun 1999 17:08:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA03223; Sat, 5 Jun 1999 13:59:37 -0700 Resent-Date: Sat, 5 Jun 1999 13:59:37 -0700 Date: Sat, 5 Jun 1999 16:01:11 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: XGGI! In-Reply-To: <19990605220736.A9306@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"dDd991.0.wn.s-OMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13201 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I take it neither of you guys hang on the #GGI channel?:) -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sat Jun 5 18:21:23 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA11161 for ; Sat, 5 Jun 1999 18:21:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA27476; Sat, 5 Jun 1999 15:12:28 -0700 Resent-Date: Sat, 5 Jun 1999 15:12:28 -0700 Message-ID: <000d01beafa1$409a44c0$21aa4cd8@massacre> From: "David Waite" To: References: <375897AB.C17D1421@concentric.net> <19990605130410.C508@rz.uni-duesseldorf.de> <06f901beaf84$d32c6b00$d417d7d1@massacre> <37598803.30B89564@concentric.net> Subject: Re: Riva TNT: Accellerated Mesa drivers !!! Date: Sat, 5 Jun 1999 18:17:47 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Resent-Message-ID: <"GURp93.0.yi6.83QMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13202 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com ----- Original Message ----- From: Evan Martin > Ah, great! > It works at 800x600. > What's particularly interesting about that, though, is that > 1024xres * 768yres * 2bytesperpixel * 2buffers = 3,145,728 bytes. > You'd think it would work on my 4mb video card. > I'd guess that other stuff is using some video memory. You are forgetting the 16-bit Z Buffer 1024*768*2*2 for 16 bit double buffer then another 1024*768*2*2 for the 16 bit Z's for both of those. double your number :) -David Waite From ggiweb@metalab.unc.edu Sat Jun 5 18:23:10 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA11183 for ; Sat, 5 Jun 1999 18:23:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA27900; Sat, 5 Jun 1999 15:14:26 -0700 Resent-Date: Sat, 5 Jun 1999 15:14:26 -0700 From: Thad Phetteplace Message-Id: <199906060327.WAA14310@dexter.glaci.com> Subject: Re: Riva TNT: Accellerated Mesa drivers !!! To: ggi-develop@eskimo.com Date: Sat, 5 Jun 1999 22:27:58 -0500 (CDT) In-Reply-To: <37598803.30B89564@concentric.net> from "Evan Martin" at Jun 5, 99 01:26:44 pm Content-Type: text Resent-Message-ID: <"BhtBF1.0.gp6.05QMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13203 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Ah, great! > It works at 800x600. > What's particularly interesting about that, though, is that > 1024xres * 768yres * 2bytesperpixel * 2buffers = 3,145,728 bytes. > You'd think it would work on my 4mb video card. > I'd guess that other stuff is using some video memory. > Yup, that is likely what is happening. For high speed graphical programs, it is not uncommon to use video mem as a scratchpad. Store your images in an off screen visual and then blit them directly to screen, its much faster than crossing the bus from main mem to video mem. Thad From ggiweb@metalab.unc.edu Sat Jun 5 18:32:37 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA11257 for ; Sat, 5 Jun 1999 18:32:36 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA30057; Sat, 5 Jun 1999 15:23:49 -0700 Resent-Date: Sat, 5 Jun 1999 15:23:49 -0700 X-Authentication-Warning: neon.cs.umn.edu: dejong owned process doing -bs Date: Sat, 5 Jun 1999 17:23:42 -0500 From: Moses DeJong To: ggi-develop@eskimo.com Subject: Help, gii compile error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"85Qsg1.0.JL7.qDQMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13204 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I just got this compile error with a fresh degas CVS tree. Has anyone seen this before? I was running on a Solaris 2.5 box with egcs 1.1.1. make[2]: Entering directory `/project/neon/users/mo/degas/build/libgii/demos' gcc -DHAVE_CONFIG_H -I. -I../../../lib/libgii/demos -I.. -I../../../lib/libgii/include -I../include -I.. -I/soft/X11R6.3/include -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -c ../../../lib/libgii/demos/mhub.c /bin/sh ../libtool --mode=link gcc -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -o mhub mhub.o -L../gg/.libs ../gii/libgii.la mkdir .libs gcc -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -o .libs/mhub mhub.o -L/project/neon/users/mo/degas/build/libgii/gg/.libs ../gii/.libs/libgii.so /project/neon/users/mo/degas/build/libgii/gg/.libs/libgg.so -ldl Undefined first referenced symbol in file ggUsleep /project/neon/users/mo/degas/build/libgii/gg/.libs/libgg.so ld: fatal: Symbol referencing errors. No output written to .libs/mhub collect2: ld returned 1 exit status make[2]: *** [mhub] Error 1 make[2]: Leaving directory `/project/neon/users/mo/degas/build/libgii/demos' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/project/neon/users/mo/degas/build/libgii' make: *** [all-recursive-am] Error 2 mo(/project/neon/users/mo/degas/build/libgii)% I hope that helps Mo DeJong dejong at cs.umn.edu From ggiweb@metalab.unc.edu Sat Jun 5 18:39:03 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA11319 for ; Sat, 5 Jun 1999 18:39:01 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA31777; Sat, 5 Jun 1999 15:30:16 -0700 Resent-Date: Sat, 5 Jun 1999 15:30:16 -0700 Message-ID: <000b01beafa3$c08934a0$21aa4cd8@massacre> From: "David Waite" To: References: <199906060327.WAA14310@dexter.glaci.com> Subject: Re: Riva TNT: Accellerated Mesa drivers !!! Date: Sat, 5 Jun 1999 18:35:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Resent-Message-ID: <"LpsL83.0.Em7.sJQMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13205 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com ----- Original Message ----- From: Thad Phetteplace > > Ah, great! > > It works at 800x600. > > What's particularly interesting about that, though, is that > > 1024xres * 768yres * 2bytesperpixel * 2buffers = 3,145,728 bytes. > > You'd think it would work on my 4mb video card. > > I'd guess that other stuff is using some video memory. > > > > Yup, that is likely what is happening. For high speed graphical > programs, it is not uncommon to use video mem as a scratchpad. Store > your images in an off screen visual and then blit them directly > to screen, its much faster than crossing the bus from main mem to > video mem. > Yes, it will use leftover memory for textures. I've pushed it right to the max though -I think if you do not have any memory remaining it will load textures into its chip-internal texcture cache directly from main memory. This is why when you set the res higher you don't get a consistant dropoff with games (As you become fillrate limited) -David Waite > Thad > From ggiweb@metalab.unc.edu Sat Jun 5 22:22:29 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA13395 for ; Sat, 5 Jun 1999 22:22:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA18645; Sat, 5 Jun 1999 19:13:27 -0700 Resent-Date: Sat, 5 Jun 1999 19:13:27 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990606025218.A28853@rz.uni-duesseldorf.de> Date: Sun, 6 Jun 1999 02:52:18 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: also Mail-Followup-To: ggi-develop@eskimo.com References: <375984B5.574FFB37@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <375984B5.574FFB37@stacken.kth.se>; from Marcus Sundberg on Sat, Jun 05, 1999 at 08:12:37PM +0000 Resent-Message-ID: <"oRhfd.0.qY4.2bTMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13206 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > strings XGGI|grep /usr > > /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ > > /usr/X11R6/lib/X11/rgb > > /usr/adm/X%smsgs > > /usr/X11R6/lib/X11/xserver/SecurityPolicy > > /usr/X11R6/lib/X11/xkb > That seems really odd, it's the excact same thing as I have here. > Not sure why it doesn't find your fonts. Hmm - setting -fp helps ? That's real odd. Other than that I think I have seen problems with fonts not beeing accessible to everyone ... checking permissions in the font dirs might be worth a try. CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Sat Jun 5 23:32:45 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA13928 for ; Sat, 5 Jun 1999 23:32:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA02872; Sat, 5 Jun 1999 20:23:22 -0700 Resent-Date: Sat, 5 Jun 1999 20:23:22 -0700 Date: Sat, 5 Jun 1999 22:24:29 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: also In-Reply-To: <19990606025218.A28853@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"GbUsV3.0.Ii.QcUMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13207 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com well, when I do -fp, I basically paste what font paths are listed in XF86Config. On Sun, 6 Jun 1999, Andreas Beck wrote: > > > strings XGGI|grep /usr > > > /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ > > > /usr/X11R6/lib/X11/rgb > > > /usr/adm/X%smsgs > > > /usr/X11R6/lib/X11/xserver/SecurityPolicy > > > /usr/X11R6/lib/X11/xkb > > That seems really odd, it's the excact same thing as I have here. > > Not sure why it doesn't find your fonts. > > Hmm - setting -fp helps ? That's real odd. Other than that I think I have > seen problems with fonts not beeing accessible to everyone ... checking > permissions in the font dirs might be worth a try. > > CU, ANdy > > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sun Jun 6 01:27:05 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA15086 for ; Sun, 6 Jun 1999 01:27:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA25376; Sat, 5 Jun 1999 22:18:02 -0700 Resent-Date: Sat, 5 Jun 1999 22:18:02 -0700 Date: Sun, 6 Jun 1999 01:58:03 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Re: Documentation for hardware (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"DSEDk1.0.hA6.1IWMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13208 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Go to the developers section on the GGI page and get VGADOC 4b. It has specs for the older Tridents. -- Brian From ggiweb@metalab.unc.edu Sun Jun 6 01:36:40 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA15166 for ; Sun, 6 Jun 1999 01:36:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA30395; Sat, 5 Jun 1999 22:27:51 -0700 Resent-Date: Sat, 5 Jun 1999 22:27:51 -0700 Date: Sun, 6 Jun 1999 02:08:08 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Back from Vacation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"85uIY2.0.dQ7.LRWMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13209 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com And yikes do I have a lot of e-mail... :). I'm looking forward to working on the Sprite/Bob/cursor stuff, when Marcus and Andy are ready. I did manage to do a little coding; expect tomorrow a GGI:: Perl5 v01 ALPHA release -- coded at an altitude of 40,000 feet, no less :). I couldn't sit idly by and let Perl5 lag behind Python, given the (friendly) rivalry :). -- Brian From ggiweb@metalab.unc.edu Sun Jun 6 04:08:35 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA16082 for ; Sun, 6 Jun 1999 04:08:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA22124; Sun, 6 Jun 1999 00:57:42 -0700 Resent-Date: Sun, 6 Jun 1999 00:57:42 -0700 Date: Sun, 6 Jun 1999 02:58:08 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: mailing list GGI Subject: XGGI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"zGhdo3.0.RP5.pdYMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13210 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ok, this is the script I had for XGGI #!/bin/bash # DIS=${1:-:0} (export DISPLAY=$DIS ; sleep 3; gnome-session & sleep 1 ;\ xmodmap /usr/local/lib/ggi/xggikeymaps/xggimap.base ; \ ) & exec XGGI $* -noxfreeemu -fp unix/:-1,/usr/X11R6/lib/X11/fonts/freefont,/usr/share/fonts/default/Type1,/usr/share/fonts/default/ghostscript,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/sharefont,/usr/X11R6/lib/X11/fonts/PEX,/wine/abi/fonts -modes 1024x768 It won't work unless I go to 640x480 for modeline, while X works fine with 1024x768. It also doesn't seem to be using many colors, and I cannot move mouse, and I cannot use my win95 keys(104 key keyboard). I thought I set up mouse in vga.conf file, but apparently I did not. I do not have a ~/.ggi dir, but I had the config file. I have a serial logitech mouseman 3 button mouse. And 104 key keyboard MAtrox mystique too. How do I (which I presume I must do) tell XGGI/libgii all of this so it will work correctly? My wm starts fine. Thanks! -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sun Jun 6 04:49:46 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA16255 for ; Sun, 6 Jun 1999 04:49:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA28064; Sun, 6 Jun 1999 01:38:57 -0700 Resent-Date: Sun, 6 Jun 1999 01:38:57 -0700 Message-ID: <19990606083915.3154.rocketmail@web114.yahoomail.com> Date: Sun, 6 Jun 1999 01:39:15 -0700 (PDT) From: Kien Pham Subject: Attn: Stefan Seeger -> Fwd: Re: GGI and Hurd To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"7Rd743.0.xr6.WEZMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13211 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- OKUJI Yoshinori wrote: > To: xengren@yahoo.com > CC: ggi-develop@eskimo.com > Subject: Re: GGI and Hurd > From: OKUJI Yoshinori > Date: Fri, 04 Jun 1999 22:03:34 +0900 > > From: Kien Pham > Subject: Re: GGI and Hurd > Date: Thu, 3 Jun 1999 22:51:57 -0700 (PDT) > > > Do you know of anyone who knows a lot about the > internals of > > mach that I can get a hold of? > > Perhaps I'm the one. And, Thomas Bushnell, BSG > , who is > the maintainer of GNU Mach, should know it thoroughly, > but he seems to > be very busy now. Roland McGrath should > also have > the knowledge. Aymeric Vincent > is > porting GNU Mach to m68k, so he should understand the > implementation > in details. > > > Also, what's Mr. UCHIYAMA Yasushi's e-mail address? > > Sorry, I forgot to write his address. "uch@nop.or.jp" > is his > address. > > Regards, > OKUJI > ---------------------------------------------------------------------- > OKUJI Yoshinori > ^o-o^ > http://duff.kuicr.kyoto-u.ac.jp/~okuji (in English) m > / Well no one seems to jump right out to me wanting to collaberate with you. My interpretation of what they're telling me is "Use the Source, Luke." My week is about up, so I'll have to say adieu till next summer. See you guys in coder heaven. (A LinuxExpo in a galaxy far, far away?) ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggiweb@metalab.unc.edu Sun Jun 6 07:17:43 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA16820 for ; Sun, 6 Jun 1999 07:17:42 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA06170; Sun, 6 Jun 1999 04:08:56 -0700 Resent-Date: Sun, 6 Jun 1999 04:08:56 -0700 Date: Sun, 6 Jun 1999 04:07:30 -0700 From: Joseph Carter To: ggi-develop@eskimo.com Subject: Re: XGGI! Message-ID: <19990606040730.D7232@debian.org> Mail-Followup-To: ggi-develop@eskimo.com References: <19990605220736.A9306@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: multipart/signed; boundary=pQhZXvAqiZgbeUkD; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.4i In-Reply-To: ; from David Cougle on Sat, Jun 05, 1999 at 04:01:11PM -0500 X-Operating-System: Linux icarus2 2.2.6-ac1 Resent-Message-ID: <"d3jJ5.0.1W1.4RbMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13212 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --pQhZXvAqiZgbeUkD Content-Type: text/plain; charset=us-ascii On Sat, Jun 05, 1999 at 04:01:11PM -0500, David Cougle wrote: > I take it neither of you guys hang on the #GGI channel?:) I was hanging out in #ggi on OPN for awhile but nobody else ever stopped by so I figured nobody on the network was terribly interested. I created the channel because the existing one on irc.ggi-project.org was just as dead. =p -- Joseph Carter Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBE The Source Comes First! ------------------------------------------------------------------------- xhost +localhost should only be done by people who would paint their hostname and root password on an interstate overpass. --pQhZXvAqiZgbeUkD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQEVAwUBN1pWbnRYxo9QvaDtAQHGdAf9H64ebxg2eT4jWE3uUuRsh4gKOSeIhN9Z IS5iYuWzbciHLByZOx4va1zkhLBz4YNTG1wSQt+QGbrVPyCc/3qyOEcy35pYMxyn 3HQTqeTHdkNqP2/xEwTv/KfHA9XXzotNwVs1mhVrXSDQiaNyEtp3ns33WS95LUYN SXPOZ+mFTxUbY9LWC+Xnwxoxi5mvdlVexrRH3iIx0CkMaTBYHm8toS+/SsETaPSq SkdR5zXWlx36r9TUbmvUylSBH3rIL0ZjJq7H59c1P5Z9v5tkDcpSJjFdglWzjBZP QGvhBjD0+qCxFyXy47XKppetrvUUTfSwL9aSJLWkLx/zuPfFATxsXg== =ot8s -----END PGP SIGNATURE----- --pQhZXvAqiZgbeUkD-- From ggiweb@metalab.unc.edu Sun Jun 6 08:25:34 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA17126 for ; Sun, 6 Jun 1999 08:25:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA14780; Sun, 6 Jun 1999 05:16:47 -0700 Resent-Date: Sun, 6 Jun 1999 05:16:47 -0700 Sender: core@orb.suntech.fr Message-ID: <375A684E.FD6BEDD1@ggi-project.org> Date: Sun, 06 Jun 1999 14:23:42 +0200 From: Emmanuel Marty Organization: Suntech X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.9 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: XGGI! References: <19990605220736.A9306@rz.uni-duesseldorf.de> <19990606040730.D7232@debian.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"rHheB3.0.ec3.fQcMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13213 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi ! > On Sat, Jun 05, 1999 at 04:01:11PM -0500, David Cougle wrote: > > I take it neither of you guys hang on the #GGI channel?:) > > I was hanging out in #ggi on OPN for awhile but nobody else ever stopped > by so I figured nobody on the network was terribly interested. I created > the channel because the existing one on irc.ggi-project.org was just as > dead. =p Well irc.ggi-project.org is mostly for meetings (that we hadn't had in a long while, though). The ggi-project.org services that I host (nameserver, irc, master cvs repository) are behind a pretty fast link (which is growing 6x in size on june 23rd btw :) and I asked OPN to be linked to them, and they said okay, and then didn't have any news and it was 6 months ago, so I figured they didn't really want a server in France :) But if you want to ask them for a link, it's still waiting for them :) -- Emmanuel From ggiweb@metalab.unc.edu Sun Jun 6 08:26:55 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA17133 for ; Sun, 6 Jun 1999 08:26:55 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA15998; Sun, 6 Jun 1999 05:18:12 -0700 Resent-Date: Sun, 6 Jun 1999 05:18:12 -0700 Sender: core@orb.suntech.fr Message-ID: <375A68A7.D65D8566@ggi-project.org> Date: Sun, 06 Jun 1999 14:25:11 +0200 From: Emmanuel Marty Organization: Suntech X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.9 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: XGGI! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"bePrS1.0.Zv3.2ScMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13214 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > I take it neither of you guys hang on the #GGI channel?:) If you mean the irc.ggi-project.org server it's mostly for team meetings; otherwise you can sometimes find me in #Tunes on openprojects or more often as an op of #linux on lagnet^Wundernet I mean. -- Emmanuel From ggiweb@metalab.unc.edu Sun Jun 6 08:45:27 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA17208 for ; Sun, 6 Jun 1999 08:45:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA18095; Sun, 6 Jun 1999 05:36:40 -0700 Resent-Date: Sun, 6 Jun 1999 05:36:40 -0700 Date: Sun, 6 Jun 1999 05:34:41 -0700 From: Joseph Carter To: lilo@openprojects.net Cc: ggi-develop@eskimo.com Subject: OPN server Message-ID: <19990606053441.A9096@debian.org> Mail-Followup-To: lilo@openprojects.net, ggi-develop@eskimo.com Mime-Version: 1.0 Content-Type: multipart/signed; boundary=kORqDWCi7qDJ0mEj; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.4i X-Operating-System: Linux icarus2 2.2.6-ac1 Resent-Message-ID: <"AzxG53.0.TQ4.NjcMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13215 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --kORqDWCi7qDJ0mEj Content-Type: multipart/mixed; boundary=PNTmBPCT7hxwcZjr --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii hey lilo, this is more your department, not mine.. Appropriate sig, I do suspect. =D -- Joseph Carter Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBE The Source Comes First! ------------------------------------------------------------------------- * lilo hereby declares OPN a virtual pain in the ass :) --PNTmBPCT7hxwcZjr Content-Type: message/rfc822 >From knghtbrd Sun Jun 6 05:30:41 1999 Received: from icarus2.soark.net (mail.novare.net) [127.0.0.1] (root) by icarus2.soark.net with esmtp (Exim 2.11 #1 (Debian)) id 10qc4X-0002MV-00; Sun, 6 Jun 1999 05:30:41 -0700 Received: from master.debian.org (qmailr@master.debian.org [209.41.108.5]) by mail.novare.net (8.8.8/8.8.8/Debian/GNU) with SMTP id HAA03728 for ; Sun, 6 Jun 1999 07:23:55 -0500 Received: (qmail 32757 invoked by uid 1242); 6 Jun 1999 12:23:55 -0000 Delivered-To: knghtbrd@debian.org Received: (qmail 32751 invoked from network); 6 Jun 1999 12:23:55 -0000 Received: from mx1.eskimo.com (204.122.16.48) by master.debian.org with SMTP; 6 Jun 1999 12:23:55 -0000 Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA14766; Sun, 6 Jun 1999 05:16:41 -0700 Resent-Date: Sun, 6 Jun 1999 05:16:41 -0700 Sender: core@orb.suntech.fr Message-ID: <375A684E.FD6BEDD1@ggi-project.org> Date: Sun, 06 Jun 1999 14:23:42 +0200 From: Emmanuel Marty Organization: Suntech X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.9 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: XGGI! References: <19990605220736.A9306@rz.uni-duesseldorf.de> <19990606040730.D7232@debian.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"rHheB3.0.ec3.fQcMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13213 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com X-UIDL: 569d98430a92b3af8b7fb94958b1ddb5 Resent-Bcc: Hi ! > On Sat, Jun 05, 1999 at 04:01:11PM -0500, David Cougle wrote: > > I take it neither of you guys hang on the #GGI channel?:) > > I was hanging out in #ggi on OPN for awhile but nobody else ever stopped > by so I figured nobody on the network was terribly interested. I created > the channel because the existing one on irc.ggi-project.org was just as > dead. =p Well irc.ggi-project.org is mostly for meetings (that we hadn't had in a long while, though). The ggi-project.org services that I host (nameserver, irc, master cvs repository) are behind a pretty fast link (which is growing 6x in size on june 23rd btw :) and I asked OPN to be linked to them, and they said okay, and then didn't have any news and it was 6 months ago, so I figured they didn't really want a server in France :) But if you want to ask them for a link, it's still waiting for them :) -- Emmanuel --PNTmBPCT7hxwcZjr-- --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQEVAwUBN1pq3HRYxo9QvaDtAQGuDwf9EjGlZiOivSwzOlvs4aMby5J0OwUtiMUr NrfiYcGQFe03kH4gYsVHg/KJr8qQDgRBpmmVK9FHjgT5oSE889eAVRYHrKRHLqcE 76dnu4uWBuCvTP4cvPHcAg28LzM5RseBON0jFLyOw7G7vJm60dnBDWLYdce08trY QBcYiezSMB1IXVVHr7CYmbNcdoU/MIUsDmDPcTiFyjW7x6xxu4x00MqSb3HwNBQ1 2TRr2hta21IGMXf20lvrJNRS6+wvUayz4grdTb0ZteZRZXQwQS23ShUw2io3OPrh u5povY6eowwF2YX2p5glQOTLCG5EgcWedhBpUBeGVnjScqotMXvLTQ== =eIUl -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj-- From ggiweb@metalab.unc.edu Sun Jun 6 10:31:05 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA17953 for ; Sun, 6 Jun 1999 10:31:04 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA00525; Sun, 6 Jun 1999 07:22:19 -0700 Resent-Date: Sun, 6 Jun 1999 07:22:19 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990606152406.D502@rz.uni-duesseldorf.de> Date: Sun, 6 Jun 1999 15:24:06 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: XGGI Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from David Cougle on Sun, Jun 06, 1999 at 02:58:08AM -0500 Resent-Message-ID: <"QMmFR.0.g7.NGeMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13218 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > exec XGGI $* -noxfreeemu ... -modes 1024x768 > It won't work unless I go to 640x480 for modeline, while X works fine with > 1024x768. You are using the kernel included fbdev - right ? Not kgicon ? fbdev is not capable to generate modelines on the fly as kgicon. For fbdev, you have to generate the mode table in /etc/fb.modes. You use fbset to generate these. > It also doesn't seem to be using many colors, I suppose it defaults to 8 bit depth. 1024x768[C16/16] should help. > and I cannot move mouse, Configure it. > and I cannot use my win95 keys(104 key keyboard). ? That's odd. In WindowMaker I can use the complete keyboard. The W95 keys are mapped to a mod? modifier anf "menu". I can easily map them to some arbitrary WM function. > I thought I set up mouse in vga.conf file, but apparently I did not. Check the entry against your XF86config. > I have a serial logitech mouseman 3 button mouse. Make a file ~/.ggi/input/mouse or $prefix/etc/ggi/input/mouse and enter -----snip----- mouse mman mdev /dev/cua? -----snap----- Try varying the protocol, as Logi mice talk several protocols depending on the exact version. Test it with inputdump. > And 104 key keyboard That should work out of the box. Which version of LibGGI/XGGI do you have installed ? Beta 2.1 should have fixed the Windows-keys problem. CU, Andy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Sun Jun 6 10:31:05 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA17957 for ; Sun, 6 Jun 1999 10:31:04 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA00533; Sun, 6 Jun 1999 07:22:20 -0700 Resent-Date: Sun, 6 Jun 1999 07:22:20 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990606150735.B502@rz.uni-duesseldorf.de> Date: Sun, 6 Jun 1999 15:07:35 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: XGGI! Mail-Followup-To: ggi-develop@eskimo.com References: <19990605220736.A9306@rz.uni-duesseldorf.de> <19990606040730.D7232@debian.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990606040730.D7232@debian.org>; from Joseph Carter on Sun, Jun 06, 1999 at 04:07:30AM -0700 Resent-Message-ID: <"brXZ-2.0.u6.KGeMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13216 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > I take it neither of you guys hang on the #GGI channel?:) > the existing one on irc.ggi-project.org was just as dead. Seems like that's what everyone did - look in, find noone, hang around a little, then quit. O.K. - if there is demand for it, we could try to populate it. I'll try to remember hanging out there when I feel a bit bored in the office. CU, Andy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Sun Jun 6 10:31:05 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA17958 for ; Sun, 6 Jun 1999 10:31:04 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA00528; Sun, 6 Jun 1999 07:22:19 -0700 Resent-Date: Sun, 6 Jun 1999 07:22:19 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990606151231.C502@rz.uni-duesseldorf.de> Date: Sun, 6 Jun 1999 15:12:31 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: XGGI! Mail-Followup-To: ggi-develop@eskimo.com References: <37598356.478E2469@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from David Cougle on Sat, Jun 05, 1999 at 03:46:21PM -0500 Resent-Message-ID: <"b3jwM.0.G7.MGeMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13217 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > But I have my .xinitrc setup, that's why it starts up gnome/icewm when I > type startx. > Am I supposed to be typing XGGI to start it, or somehow start it with > startx? Yes. Try either changing your "X" link to point to XGGI or using startx -- /usr/local/bin/XGGI :0 -whatever_options_you_need Setting up an xserverrc is also an option. > How do I configure mouse for libggi? >From lib/libgii/doc/inputs.txt: we first try to read ~/.ggi/input/linux-mouse and then $prefix/etc/ggi/input/linux-mouse. In the first file found we look for the following entries: mouse mdev If none of the files are found we first try to autodetect the mouse, and as a last resort we try parsing /etc/vga/libvga.config to find out the necessary info. CU, ANdy -- = Andreas Beck | Email : = From ggiweb@metalab.unc.edu Sun Jun 6 11:25:50 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA18462 for ; Sun, 6 Jun 1999 11:25:49 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA10368; Sun, 6 Jun 1999 08:17:04 -0700 Resent-Date: Sun, 6 Jun 1999 08:17:04 -0700 Date: Sun, 6 Jun 1999 08:16:58 -0700 From: Joseph Carter To: ggi-develop@eskimo.com Subject: Re: XGGI! Message-ID: <19990606081658.A21122@debian.org> Mail-Followup-To: ggi-develop@eskimo.com References: <19990605220736.A9306@rz.uni-duesseldorf.de> <19990606040730.D7232@debian.org> <19990606150735.B502@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="jI8keyz6grp/JLjh"; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.4i In-Reply-To: <19990606150735.B502@rz.uni-duesseldorf.de>; from Andreas Beck on Sun, Jun 06, 1999 at 03:07:35PM +0200 X-Operating-System: Linux icarus2 2.2.6-ac1 Resent-Message-ID: <"fxS9E1.0.lX2.k3fMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13219 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii On Sun, Jun 06, 1999 at 03:07:35PM +0200, Andreas Beck wrote: > > > I take it neither of you guys hang on the #GGI channel?:) > > the existing one on irc.ggi-project.org was just as dead. > > Seems like that's what everyone did - look in, find noone, hang around a > little, then quit. > > O.K. - if there is demand for it, we could try to populate it. I'll try to > remember hanging out there when I feel a bit bored in the office. I hung out there for a week and a half => I think an irc channel would be very useful. There are lots of problems and buglets that could get fixed a lot easier if there was a more interactive way to address them. I also see a need for people to be able to find answers to common questions (infobot anyone?) And we all know we need another place for mostly off-topic discussions and arguments that don't add to the number of bytes in people's mailboxes... => -- Joseph Carter Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBE The Source Comes First! ------------------------------------------------------------------------- hmm, lunch does sound like a good idea would taste like a good idea too --jI8keyz6grp/JLjh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQEVAwUBN1qQ53RYxo9QvaDtAQE4mQf/RQeUqs0MJKXMCiQTgHeVZWtmJRV+Dq8A 9O22P8QSzSMwQpAJRsyM3jqhkhkg+xoeVPsBgwW02Fj1wwFbORXMP9hLJ7AbTnDm Ei/RetXAaMTjDNZrs/26QMaC9l/URZ03vLV/hD8CCj/i7zQqkE2q8hC2rICidPGl 8P1qzVROCIOkgRshqObQuhKfUX4x4ikykSbKKU5ku7AULPYR4DkK00yoxCjpTb3+ Z2OrqRpynIVr6RxI8QISg99oFhTMEXVPcnz98OvpZFl9XGbr44HlIbMiLk0euisW nhLMeMmyguZPkvm7dW5JxrM9+KpbDvxtKHyfAeaxwZP1Wm0POT+YAA== =60yL -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From ggiweb@metalab.unc.edu Sun Jun 6 13:04:34 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA19118 for ; Sun, 6 Jun 1999 13:04:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA29115; Sun, 6 Jun 1999 09:55:41 -0700 Resent-Date: Sun, 6 Jun 1999 09:55:41 -0700 Date: Sun, 6 Jun 1999 11:57:21 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: XGGI! In-Reply-To: <19990606151231.C502@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"PxQMq1.0.g67.8WgMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13220 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com The thing is, all I have is a linux-mouse.so(a library). Here is my libvga.conf # Configuration file for svgalib. Default location is /etc/vga. # Other config file locations: ~/.svgalibrc # where SVGALIB_CONFIG_FILE points # Lines starting with '#' are ignored. # Have a deep look at README.config to see what can do here (especially # for mach32). # Mouse type: # mouse Microsoft # Microsoft # mouse MouseSystems # Mouse Systems mouse MMSeries # Logitech MM Series # mouse Logitech # Logitech protocol (old, newer mice use Microsoft protocol) # mouse Busmouse # Bus mouse # mouse PS2 # PS/2 mouse # mouse MouseMan # Logitech MouseMan # mouse Spaceball # Spacetec Spaceball # mouse IntelliMouse # Microsoft IntelliMouse or Logitech MouseMan+ on serial port # mouse IMPS2 # Microsoft IntelliMouse or Logitech MouseMan+ on PS/2 port # mouse none # None #mouse Microsoft # Mouse/keyboard customisation by 101 (Attila Lendvai). If you have any good # ideas you can reach me at 101@kempelen.inf.bme.hu # mouse_accel_type normal # No acceleration while delta is less then # threshold but delta is multiplied by # mouse_accel_mult if more. Originally done by # Mike Chapman mike@paranoia.com mouse_accel_type power # The acceleration factor is a power function # of delta until it reaches m_accel_mult. It # starts from the coordinate # [1, 1 + m_accel_offset] and goes to # [m_accel_thresh, m_accel_mult]. If delta # is bigger then m_accel_thresh it is a plain # constant (m_accel_mult). It is the f(delta) # function with which the delta itself will be # multiplied. m_accel_offset is 1 by default, # so for delta = 1 the accelerated delta will # remain 1 (You don't lose resolution). The # starting point of the f(delta) function # might be moved along the Y axis up/down with # m_accel_offset thus defining the initial # minimum acceleration (for delta = 1). # Basically it's like the normal mode but the # acceleration factor grows as you move your # mouse faster and faster, not just turns in # and out. Threshold is the point from where # the f(delta) function gets linear. # This is the one I use for *uaking... =) # mouse_accel_type off # No comment... mouse_accel_mult 60 # This is the number with which delta will # be multiplied. Basically it's the number # that defines how big the acceleration will # be mouse_accel_thresh 4 # This is the threshold. See description by # power mouse_accel_power 0.8 # This is the second parameter of the power # function used in power mode. Used only by # the power mode mouse_accel_offset 30 # This is the offset of the starting point # on the Y axis. With this you can define the # number that will multiply delta = 1 so it's # the initial acceleration. # mouse_accel_maxdelta 600 # This is an upper limit for delta after # the acceleration was applied # mouse_maxdelta 30 # This is an upper limit for the delta # before the acceleration. With this one you # can limit the biggest valid delta that # comes from the mouse. # mouse_force # Force parameters even if they seem strange # By default svgalib prints an error if any # of the numbers are somhow out of the # reasonable limit, (Like a negative mult :) # and uses the default that's in vgamouse.h # Usually /dev/mouse will be a link to the mouse device. # However, esp. with the Spacetec Spaceball you may # want to specify a different device for svgalib to use # mdev /dev/ttyS0 # mouse is at /dev/ttyS0 # Some multiprotocol mice will need one of the following: # setRTS # set the RTS wire. # clearRTS # clear the RTS wire. # leaveRTS # leave the RTS wire alone (default) (Wire is usually set) # setDTR # set the DTR wire. # clearDTR # clear the DTR wire. # leaveDTR # leave the DTR wire alone (default) (Wire is usually set) # On mice such as the Microsoft IntelliMouse and Logitech MouseMan+, turning # the wheel rotates the mouse around the X axis. mouse_wheel_steps controls # how many steps make up a full 360-degree turn and thus how much rotation # occurs with each step. The default is 18 steps (20 degrees per step), the # real-world value for the IntelliMouse. Adjust it to match your mouse or to # suit your preferences; a negative number reverses the direction and zero # disables rotation. mouse_wheel_steps 18 # For MS IntelliMouse (default) # mouse_wheel_steps 24 # For Logitech FirstMouse+ # mouse_wheel_steps -18 # Reverses direction # mouse_wheel_steps 0 # Disables rotation # mouse_fake_kbd_event sends a fake keyboard event to the program when the # wheel on a Microsoft IntelliMouse, Logitech MouseMan+, or similar wheel # mouse is turned. This can be useful for programs that do not recognize the # Z axis, but only works with some programs that use raw keyboard. # The format is: # # mouse_fake_kbd_event upscancode downscancode # # The up and down scancodes are the scancodes of the keys to simulate when # the wheel is turned up and down, respectively. # # Scancodes can be specified numerically or symbolically; the symbolic names # are determined by the keymap (see below), if no keymap is loaded the default # is the standard US QWERTY keyboard with the following names available: # letters (a-z), numbers (zero-nine), function keys (F1-F12), the keypad # numbers (KP_0-KP_9) and other keys (KP_Multiply, KP_Subtract, KP_Add, # KP_Period, KP_Enter, and KP_Divide), and the following - minus, equal, # Delete, Tab, bracketleft, bracketright, Return, Control, semicolon, # apostrophe, grave, Shift, backslash, comma, period, slash, Shift, Alt, space, # Caps_Lock, Num_Lock, Scroll_Lock, Last_Console, less, Control_backslash, # AltGr, Break, Find, Up, Prior, Left, Right, Select, Down, Next, Insert, # and Remove. # # Note that this option has no effect unless the IntelliMouse or IMPS2 mouse # type is used (see above). Also note that the simulated keypresses are # instantaneous, so they cannot be used for functions that require a key to # be held down for a certain length of time. # This example simulates a press of the left bracket ([) when the wheel is # turned up and a press of the right bracket (]) when the wheel is turned # down (good for selecting items in Quake II): # mouse_fake_kbd_event bracketleft bracketright # Keyboard config: # kbd_keymap allows you to use an alternate keyboard layout with programs that # use raw keyboard support by translating scancodes from the desired layout to # their equivalents in the layout expected by the program. This option has no # affect on programs that do not use raw keyboard. # # Keymap files to convert between any two arbitrary keyboard layouts can be # generated with the svgakeymap utility, but there are limitations to the # translations that can be performed. Read the file README.keymap in the # svgalib documentation directory for more in-depth information. # # You must specify the full path to the keymap file; it is recommended that # keymaps be kept in the same directory as libvga.config, normally /etc/vga. # The keymap specified in the configuration file can be overriden by setting # the environment variable SVGALIB_KEYMAP to point to another keymap file; # this can be useful for setting keymaps on a per-program basis. # # This example will use the provided US-Dvorak to US-QWERTY map to allow a # Dvorak keyboard layout to be used with a program that expects a standard US # QWERTY keyboard, for instance Quake: # kbd_keymap /etc/vga/dvorak-us.keymap # There is a potential security risk in allowing users to remap keyboard # scancodes at will; with this option enabled only keymap files owned by # root can be used. Normally you should leave this on, but if you have a # single-user box or you really trust your users you may find it convenient # to run without it and allow users to load arbitrary keymaps. kbd_only_root_keymaps # kbd_fake_mouse_event, as it says, sends a fake mouse event to the program. # The format is: kbd_fake_mouse_event scancode [flag(s)] command [argument] # Scancode is a raw scancode or a descriptive name, the same as with fake # keyboard events (see above). If you use keymap conversion, specify # scancodes for the keyboard layout the program will receive. # Flags: down - trigger event when the key is pressed (default) # up - the opposite # both - trigger in both case, if pressed/released # repeat - repeat events if the key is kept pressed (off by default) # commands: delta[xyz] - send a fake delta event as if you have moved your # mouse. If the parameter is 'off' / 'on' it will turn # off/on the respective mouse axis (requires a # parameter, of course) # button[123] - send a fake event that the mouse button is pressed # or released that's given by the parameter. # ('pressed' or 'released') # Here are some examples: # This is one I use in *uake: it turns around, looks down a bit and when the # key is released it does the opposite, so it gets back to the starting state. # With this one and the help of a rocket you can fly though the whole map :) # (Scancode 28 is enter) # kbd_fake_mouse_event 28 both deltax 8182 down deltay -1500 up deltay 1500 # This one will switch off the y axis of the mouse while the key (right ctrl) # is kept pressed. # kbd_fake_mouse_event 97 down deltay off up deltay on # This one is the same as if you were pressing the left mouse button. (But # if you move your mouse then the button state will reset even if you keep # right ctrl down...) # kbd_fake_mouse_event 97 down button1 pressed up button1 released # Monitor type: # Only one range can be specified for the moment. Format: # HorizSync min_kHz max_kHz # VertRefresh min_Hz max_Hz # Typical Horizontal sync ranges # (Consult your monitor manual for Vertical sync ranges) # # 31.5 - 31.5 kHz (Standard VGA monitor, 640x480 @ 60 Hz) # 31.5 - 35.1 kHz (Old SVGA monitor, 800x600 @ 56 Hz) # 31.5 - 35.5 kHz (Low-end SVGA, 8514, 1024x768 @ 43 Hz interlaced) # 31.5 - 37.9 kHz (SVGA monitor, 800x600 @ 60 Hz, 640x480 @ 72 Hz) # 31.5 - 48.3 kHz (SVGA non-interlaced, 800x600 @ 72 Hz, 1024x768 @ 60 Hz) # 31.5 - 56.0 kHz (high frequency, 1024x768 @ 70 Hz) # 31.5 - ???? kHz (1024x768 @ 72 Hz) # 31.5 - 64.3 kHz (1280x1024 @ 60 Hz) HorizSync 31.5 35.5 VertRefresh 50 90 # Montitor timings # # These are prefered over the default timings (if monitor and chipset # can handle them). Not all drivers use them at the moment, and Mach32 # has its own syntax (see below). # The format is identical to the one used by XFree86, but the label # following the modeline keyword is ignored by svgalib. # # Here some examples: # modeline "640x480@100" 43 640 664 780 848 480 483 490 504 # modeline "800x600@73" 50 800 856 976 1024 600 637 643 666 # modeline "1024x768@75" 85 1024 1048 1376 1400 768 771 780 806 # It seems there is a need for a 512x384 mode, this timing was donated # by Simon Hosie : (it is 39kHz horz by 79Hz vert) # Modeline "512x384@79" 25.175 512 522 598 646 384 428 436 494 # Here's a 400x300 Modeline (created by svidtune). Note that for # doublescan modes, the Vertical values are half the real one (so XFree86 # modelines can be used). # Modeline "400x300@72" 25.000 400 440 504 520 300 319 322 333 doublescan # The following modes are defined in svgalib, but have no timings in # timing.c, so you'll have to add a modeline in order to use them: # 1280x720, 1360x768, 1800x1012, 1920x1080, 1920x1440, 2048x1152 # and 2048x1536 # Mach32 timings: # e.g. Setup a 320x200 mode for the mach32: #define 320x200x32K 320x200x64K 320x200x16M 320x200x16M32 # 16 320 392 464 552 200 245 265 310 # These are REQUIRED for above mode, please edit to suit your monitor. # (No, I won't pay for a new one) # HorizSync 29 65 # VertRefresh 42 93.5 # Chipset type: # # Use one of the following force chipset type. # Autodetects if no chipset is specified. # If a chipset driver gives trouble, try forcing VGA. # chipset VGA # Standard VGA # chipset EGA # EGA # chipset ET3000 # Tseng ET3000 # chipset ET4000 # Tseng ET4000 # chipset Cirrus # Cirrus Logic GD542x # chipset TVGA # Trident TVGA8900/9000 # chipset Oak # Oak Technologies 037/067/077 # chipset S3 # S3 chipsets # chipset GVGA6400 # Genoa 6400 # chipset ARK # ARK Logic # chipset ATI # old ATI VGA # chipset Mach32 # ATI Mach32 # chipset ALI # ALI2301 # chipset Mach64 # ATI Mach64 # chipset ET6000 # Tseng ET6000 # chipset APM # Alliance Technology AT 24/25/3D # chipset NV3 # nVidia Riva 128 # chipset VESA # nicely behaved Vesa Bioses # chipset MX # MX86251 (some Voodoo Rush boards) # chipset PARADISE # WD90C31 # EGA Color/mono mode: # Required if chipset is EGA. # # Use one of the following digits to force color/mono: # monotext # Card is in monochrome emulation mode # colortext # Card is in color emulation mode colortext # RAMDAC support: # Some chipsets (e.g. S3 and ARK) allows specifying a RAMDAC type. # If your RAMDAC is not autodetected, you can try specifying it. # Do NOT specify a RAMDAC if you card uses the S3 Trio chipset # (the RAMDAC is built in). # Ramdac Sierra32K # Ramdac SC15025 # Ramdac SDAC # S3 SDAC # Ramdac GenDAC # S3 GenDAC # Ramdac ATT20C490 # AT&T 20C490, 491, 492 (and compatibles) # Ramdac ATT20C498 # AT&T 20C498 # Ramdac IBMRGB52x # IBM RGB524, 526, 528 (and compatibles) # Dotclocks: # Some chipsets needs a list of dot clocks for optimum operation. Some # includes or supports a programmable clock chip. You'll need to specify # them here. # Fixed clocks example: # (The following is just an example, get the values for your card from # you XF86Config) # Clocks 25.175 28.3 40 70 50 75 36 44.9 0 118 77 31.5 110 65 72 93.5 # Programmable clockchip example: # Clockchip ICD2061A # The only one supported right now # VesaText # Helps the VESA driver with text mode restoration # problems. # VesaSave 14 # changing value might help text mode restoring # problems with VESA driver. On Sun, 6 Jun 1999, Andreas Beck wrote: > > But I have my .xinitrc setup, that's why it starts up gnome/icewm when I > > type startx. > > Am I supposed to be typing XGGI to start it, or somehow start it with > > startx? > > Yes. Try either changing your "X" link to point to XGGI or using > startx -- /usr/local/bin/XGGI :0 -whatever_options_you_need > > Setting up an xserverrc is also an option. > > > How do I configure mouse for libggi? > > >From lib/libgii/doc/inputs.txt: > > we first try to read ~/.ggi/input/linux-mouse and then > $prefix/etc/ggi/input/linux-mouse. In the first file found > we look for the following entries: > mouse > mdev > If none of the files are found we first try to autodetect > the mouse, and as a last resort we try parsing > /etc/vga/libvga.config to find out the necessary info. > > CU, ANdy > > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sun Jun 6 13:20:04 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA19275 for ; Sun, 6 Jun 1999 13:20:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA31450; Sun, 6 Jun 1999 10:09:18 -0700 Resent-Date: Sun, 6 Jun 1999 10:09:18 -0700 Date: Sun, 6 Jun 1999 12:11:04 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: XGGI In-Reply-To: <19990606152406.D502@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"fu4dn2.0.9h7.zigMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13221 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Yes, I'm using fbdev, does kgicon work better, and with matrox mystique? I apparently don't have the program "fbset"? On Sun, 6 Jun 1999, Andreas Beck wrote: > > exec XGGI $* -noxfreeemu ... -modes 1024x768 > > > It won't work unless I go to 640x480 for modeline, while X works fine with > > 1024x768. > > You are using the kernel included fbdev - right ? Not kgicon ? > > fbdev is not capable to generate modelines on the fly as kgicon. > For fbdev, you have to generate the mode table in /etc/fb.modes. > You use fbset to generate these. > > > It also doesn't seem to be using many colors, > > I suppose it defaults to 8 bit depth. 1024x768[C16/16] should help. > > > and I cannot move mouse, > > Configure it. > > > and I cannot use my win95 keys(104 key keyboard). > > ? That's odd. In WindowMaker I can use the complete keyboard. The W95 keys > are mapped to a mod? modifier anf "menu". I can easily map them to some > arbitrary WM function. > > > I thought I set up mouse in vga.conf file, but apparently I did not. > > Check the entry against your XF86config. > > > I have a serial logitech mouseman 3 button mouse. > > Make a file ~/.ggi/input/mouse or $prefix/etc/ggi/input/mouse and enter > -----snip----- > mouse mman > mdev /dev/cua? > -----snap----- > > Try varying the protocol, as Logi mice talk several protocols depending on > the exact version. Test it with inputdump. > > > And 104 key keyboard > > That should work out of the box. Which version of LibGGI/XGGI do you have > installed ? Beta 2.1 should have fixed the Windows-keys problem. > > CU, Andy > > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sun Jun 6 13:35:27 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA19418 for ; Sun, 6 Jun 1999 13:35:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA03502; Sun, 6 Jun 1999 10:26:33 -0700 Resent-Date: Sun, 6 Jun 1999 10:26:33 -0700 Date: Sun, 6 Jun 1999 12:28:22 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: mailing list GGI Subject: whoa! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"M1Ptt.0.Ms.8zgMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13222 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Even though I haven't gotten XGGI working correctly, I did run gtop inside of it and it uses a whopping 10 megs less of memory than standard X! Please help me get this baby working!:) -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sun Jun 6 13:35:58 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA19434 for ; Sun, 6 Jun 1999 13:35:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA03849; Sun, 6 Jun 1999 10:27:14 -0700 Resent-Date: Sun, 6 Jun 1999 10:27:14 -0700 Date: Sun, 6 Jun 1999 12:29:02 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: mailing list GGI Subject: sorry Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"7GsNg.0.lx.mzgMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13224 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Me again, I'm on emmanuel's #tunes channel on irc.linux.org if anyone who knows how to solve this problem gets a chance to log on, might be easier that way. -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sun Jun 6 13:38:48 1999 -0400 Status: X-Status: X-Keywords: Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA19480 for ; Sun, 6 Jun 1999 13:38:47 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id KAA17980; Sun, 6 Jun 1999 10:29:30 -0700 (PDT) Resent-Date: Sun, 6 Jun 1999 10:29:30 -0700 (PDT) Date: Sun, 6 Jun 1999 12:23:55 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: mailing list GGI Subject: no luck with XGGI! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"nqyLl3.0.TN4.2_gMt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13223 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com $ cat ~/.ggi/mouse mouse mman mdev /dev/ttyS0 no mouse. still no 104 keys, despite having XGGI load the keymap. -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sun Jun 6 16:02:20 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA21156 for ; Sun, 6 Jun 1999 16:02:19 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA07035; Sun, 6 Jun 1999 12:53:27 -0700 Resent-Date: Sun, 6 Jun 1999 12:53:27 -0700 Date: Sun, 6 Jun 1999 14:59:35 -0400 From: tentacle tentacle boat To: ggi-develop@eskimo.com Subject: Nvidia Riva kgi driver Message-ID: <19990606145935.A10155@greenbytes.greenbytes.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Resent-Message-ID: <"fl99h3.0.gj1.o6jMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13225 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello i am trying to install the nvidia kgicon driver, from the 06/06 snapshot everything builds fine, but when i goto load the module i get this Could't find a nVidia Riva card on the PCI/AGP bus Failed to detect a card or resources was busy error: kgim_chipset_init failed error: init_kgi() failed, bailing out.... ./kgicon.o: init_module: Device or resource busy i have a Creative Labs TNT2 Ultra AGP card anyone know what might be causing this?, or is the nvidia driver not even worth using yet?, aswell in the chipsets dir i saw the there was a define for MTRR support on the card, is this commented out for any particular reason? thanks john From ggiweb@metalab.unc.edu Sun Jun 6 16:04:59 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA21180 for ; Sun, 6 Jun 1999 16:04:58 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA07293; Sun, 6 Jun 1999 12:56:05 -0700 Resent-Date: Sun, 6 Jun 1999 12:56:05 -0700 Date: Sun, 6 Jun 1999 15:55:54 -0400 (EDT) From: Steve Cheng Sender: steve@sephiroth To: GGI Mailing List Subject: On giiEventSelect... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"CI7Q71.0.in1.K9jMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13226 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Looking at the prototype it's obvious that giiEventSelect is giiEventPoll + select(2). I know three things: it updates the timeout (which the system select(2) might not do) and does not use errno, and of course also checks for events. Are there any more gotchas, or something else I should say for the documentation? The code is really confusing. -- Steve Cheng email: steve@ggi-project.org www: From ggiweb@metalab.unc.edu Sun Jun 6 16:11:45 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA21262 for ; Sun, 6 Jun 1999 16:11:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA08299; Sun, 6 Jun 1999 13:02:58 -0700 Resent-Date: Sun, 6 Jun 1999 13:02:58 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: Nvidia Riva kgi driver Date: Sun, 6 Jun 1999 22:02:57 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <19990606145935.A10155@greenbytes.greenbytes.cx> MIME-Version: 1.0 Message-Id: <99060622041000.00668@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"gKN7r.0.K12.mFjMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13227 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com tentacle tentacle boat´s crap from Son, 06 Jun 1999: > Hello > > i am trying to install the nvidia kgicon driver, from the 06/06 > snapshot everything builds fine, but when i goto load the module > i get this > > Could't find a nVidia Riva card on the PCI/AGP bus > Failed to detect a card or resources was busy > error: kgim_chipset_init failed > error: init_kgi() failed, bailing out.... > ./kgicon.o: init_module: Device or resource busy > > i have a Creative Labs TNT2 Ultra AGP card The problem is that the driver only supports tnt1, maybe it works with tnt2, but it does not detect the pci device. the tnt2 has an other device id. if you are familiar with coding you could hack the detection. > > anyone know what might be causing this?, or is the nvidia driver not > even worth using yet?, aswell in the chipsets dir i saw the there > was a define for MTRR support on the card, is this commented out > for any particular reason? > > thanks > > john -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggiweb@metalab.unc.edu Sun Jun 6 16:33:05 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA21458 for ; Sun, 6 Jun 1999 16:33:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA14295; Sun, 6 Jun 1999 13:24:17 -0700 Resent-Date: Sun, 6 Jun 1999 13:24:17 -0700 Sender: e94_msu@e.kth.se Message-ID: <375AD8EA.564DC1E2@stacken.kth.se> Date: Sun, 06 Jun 1999 22:24:10 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Help, gii compile error References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"_8_QU3.0.1V3.mZjMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13228 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Moses DeJong wrote: > > I just got this compile error with a fresh degas CVS tree. Has anyone > seen this before? I was running on a Solaris 2.5 box with egcs 1.1.1. > > make[2]: Entering directory `/project/neon/users/mo/degas/build/libgii/demos' > gcc -DHAVE_CONFIG_H -I. -I../../../lib/libgii/demos -I.. -I../../../lib/libgii/include -I../include -I.. -I/soft/X11R6.3/include -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -c ../../../lib/libgii/demos/mhub.c > /bin/sh ../libtool --mode=link gcc -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -o mhub mhub.o -L../gg/.libs ../gii/libgii.la > mkdir .libs > gcc -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -o .libs/mhub mhub.o -L/project/neon/users/mo/degas/build/libgii/gg/.libs ../gii/.libs/libgii.so /project/neon/users/mo/degas/build/libgii/gg/.libs/libgg.so -ldl > Undefined first referenced > symbol in file > ggUsleep /project/neon/users/mo/degas/build/libgii/gg/.libs/libgg.so > ld: fatal: Symbol referencing errors. No output written to .libs/mhub > collect2: ld returned 1 exit status > make[2]: *** [mhub] Error 1 > make[2]: Leaving directory `/project/neon/users/mo/degas/build/libgii/demos' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/project/neon/users/mo/degas/build/libgii' > make: *** [all-recursive-am] Error 2 > mo(/project/neon/users/mo/degas/build/libgii)% Oh, stupid typo I never noticed because of the conditional compiling. Please change ggUsleep into ggUSleep. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Sun Jun 6 16:59:58 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA22122 for ; Sun, 6 Jun 1999 16:59:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA22344; Sun, 6 Jun 1999 13:49:44 -0700 Resent-Date: Sun, 6 Jun 1999 13:49:44 -0700 Sender: e94_msu@e.kth.se Message-ID: <375ADEE0.735F3D69@stacken.kth.se> Date: Sun, 06 Jun 1999 22:49:36 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: no luck with XGGI! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"1leeF.0.gS5.cxjMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13229 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > > $ cat ~/.ggi/mouse > mouse mman > mdev /dev/ttyS0 > > no mouse. Ehum, the file is ~/.ggi/input/linux-mouse, not ~/.ggi/mouse. ;) > still no 104 keys, despite having XGGI load the keymap. What do you mean "104 keys"? Exactly what is it that doesn't work? The Win* keys? Any other keys? Please run inputdump --long 2>eventlog and press the non-working keys a few times each. Then post the eventlog file together with info of exactly which keys you pressed and in which order. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Sun Jun 6 17:16:56 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA22292 for ; Sun, 6 Jun 1999 17:16:55 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA30543; Sun, 6 Jun 1999 14:05:14 -0700 Resent-Date: Sun, 6 Jun 1999 14:05:14 -0700 Sender: e94_msu@e.kth.se Message-ID: <375AE283.1DD75D6D@stacken.kth.se> Date: Sun, 06 Jun 1999 23:05:07 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: On giiEventSelect... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"MlU7B3.0.1T7.8AkMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13230 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Steve Cheng wrote: > > Looking at the prototype it's obvious that giiEventSelect is > giiEventPoll + select(2). > I know three things: it updates the timeout (which the system select(2) > might not do) Yes. > and does not use errno, On the contrary - it does a great effort to ensure that the errno from a failing select() call is valid when giiEventSelect() returns. > and of course also checks for events. > Are there any more gotchas, or something else I should say for the > documentation? The code is really confusing. giiEventSelect(), as opposed to all other LibGII functions, is not available unless the system have a select() call - not even as a stub. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Sun Jun 6 17:24:28 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA22352 for ; Sun, 6 Jun 1999 17:24:27 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA32743; Sun, 6 Jun 1999 14:10:41 -0700 Resent-Date: Sun, 6 Jun 1999 14:10:41 -0700 Sender: e94_msu@e.kth.se Message-ID: <375AE3C1.9E84746D@stacken.kth.se> Date: Sun, 06 Jun 1999 23:10:25 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: XGGI References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"v0ols1.0.J_7.GFkMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13231 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > > Yes, I'm using fbdev, does kgicon work better, and with matrox mystique? With kgicon you don't have to make up mode specs for /etc/fb.modes, but you also will not have acceleration for Matrox Mystique. > I apparently don't have the program "fbset"? If you get a GGI CVS snapshot you will find it in degas/kgicon/util/fbset/ //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Sun Jun 6 17:34:34 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA22478 for ; Sun, 6 Jun 1999 17:34:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA00993; Sun, 6 Jun 1999 14:16:49 -0700 Resent-Date: Sun, 6 Jun 1999 14:16:49 -0700 Date: Sun, 6 Jun 1999 16:18:33 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: XGGI In-Reply-To: <375AE3C1.9E84746D@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"EyQZ42.0.AF._KkMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13232 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com When will kgicon have acceleration for matrox mystique? On Sun, 6 Jun 1999, Marcus Sundberg wrote: > David Cougle wrote: > > > > Yes, I'm using fbdev, does kgicon work better, and with matrox mystique? > > With kgicon you don't have to make up mode specs for /etc/fb.modes, > but you also will not have acceleration for Matrox Mystique. > > > I apparently don't have the program "fbset"? > > If you get a GGI CVS snapshot you will find it in > degas/kgicon/util/fbset/ > > //Marcus > can I get it via ftp? I have latest GGI(not snapshot, though) -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggiweb@metalab.unc.edu Sun Jun 6 17:39:10 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA22518 for ; Sun, 6 Jun 1999 17:39:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA02962; Sun, 6 Jun 1999 14:27:44 -0700 Resent-Date: Sun, 6 Jun 1999 14:27:44 -0700 To: ggi-develop@eskimo.com Subject: Re: OPN server References: <19990606053441.A9096@debian.org> From: Tijs van Bakel Date: 06 Jun 1999 23:28:08 +0200 In-Reply-To: Joseph Carter's message of "Sun, 6 Jun 1999 05:34:41 -0700" Message-ID: Lines: 31 X-Mailer: Gnus v5.5/Emacs 20.3 Resent-Message-ID: <"M7m-c3.0.1k.FVkMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13233 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Joseph Carter writes: > Hi ! > > > On Sat, Jun 05, 1999 at 04:01:11PM -0500, David Cougle wrote: > > > I take it neither of you guys hang on the #GGI channel?:) > > > > I was hanging out in #ggi on OPN for awhile but nobody else ever stopped > > by so I figured nobody on the network was terribly interested. I created > > the channel because the existing one on irc.ggi-project.org was just as > > dead. =p > > Well irc.ggi-project.org is mostly for meetings (that we hadn't had in > a long while, though). > > The ggi-project.org services that I host (nameserver, irc, master > cvs repository) are behind a pretty fast link (which is growing 6x in > size on june 23rd btw :) and I asked OPN to be linked to them, and they > said okay, and then didn't have any news and it was 6 months ago, so > I figured they didn't really want a server in France :) But if you > want to ask them for a link, it's still waiting for them :) > > -- > Emmanuel We're having a demo channel at #demoscene on OPN. It's for GPL based demos only, no game talk, no non-Free demos. -- Tijs van Bakel, a.k.a. Smoke of C.R.A.P. , http://www.casema.net/~smoke/crap.html From ggiweb@metalab.unc.edu Sun Jun 6 17:44:27 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA22556 for ; Sun, 6 Jun 1999 17:44:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA04153; Sun, 6 Jun 1999 14:33:49 -0700 Resent-Date: Sun, 6 Jun 1999 14:33:49 -0700 Sender: e94_msu@e.kth.se Message-ID: <375AE936.9BAF8C16@stacken.kth.se> Date: Sun, 06 Jun 1999 23:33:42 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: XGGI References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"LFuvA2.0.a01.yakMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13234 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > > When will kgicon have acceleration for matrox mystique? Don't know. Most of the kgicon drivers doesn't have any maintainer. > > > I apparently don't have the program "fbset"? > > > > If you get a GGI CVS snapshot you will find it in > > degas/kgicon/util/fbset/ > > can I get it via ftp? Sure: ftp://ftp.ggi-project.org/pub/ggi/ggi-snapshots/ //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Sun Jun 6 21:36:21 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA25393 for ; Sun, 6 Jun 1999 21:36:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id SAA01317; Sun, 6 Jun 1999 18:27:23 -0700 Resent-Date: Sun, 6 Jun 1999 18:27:23 -0700 Date: Sun, 6 Jun 1999 20:33:28 -0400 From: tentacle tentacle boat To: ggi-develop@eskimo.com Subject: Re: Nvidia Riva kgi driver Message-ID: <19990606203328.A10392@greenbytes.greenbytes.cx> References: <19990606145935.A10155@greenbytes.greenbytes.cx> <99060622041000.00668@master> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.1i In-Reply-To: <99060622041000.00668@master>; from Denis Oliver Kropp on Sun, Jun 06, 1999 at 10:02:57PM +0200 Resent-Message-ID: <"xqBsZ1.0.IK.r_nMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13235 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sun, Jun 06, 1999 at 10:02:57PM +0200, Denis Oliver Kropp wrote: > tentacle tentacle boat´s crap from Son, 06 Jun 1999: > > Hello > > > > i am trying to install the nvidia kgicon driver, from the 06/06 > > snapshot everything builds fine, but when i goto load the module > > i get this > > > > Could't find a nVidia Riva card on the PCI/AGP bus > > Failed to detect a card or resources was busy > > error: kgim_chipset_init failed > > error: init_kgi() failed, bailing out.... > > ./kgicon.o: init_module: Device or resource busy > > > > i have a Creative Labs TNT2 Ultra AGP card > > The problem is that the driver only supports tnt1, > maybe it works with tnt2, but it does not detect the pci device. > the tnt2 has an other device id. > if you are familiar with coding you could hack the detection. > I could do this, if you pointed to me in the right direction :) which file should i be looking at ? john From ggiweb@metalab.unc.edu Sun Jun 6 21:53:33 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA25577 for ; Sun, 6 Jun 1999 21:53:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id SAA05689; Sun, 6 Jun 1999 18:44:43 -0700 Resent-Date: Sun, 6 Jun 1999 18:44:43 -0700 Date: Sun, 6 Jun 1999 20:50:59 -0400 From: tentacle tentacle boat To: ggi-develop@eskimo.com Subject: kgicon TNT2 diff Message-ID: <19990606205059.A10419@greenbytes.greenbytes.cx> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=HlL+5n6rz5pIUxbD X-Mailer: Mutt 0.95.1i Resent-Message-ID: <"8wEgi3.0.bO1.AGoMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13236 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Hello this diff lets the nvidia riva kgi driver detect tnt2 ultras i patched this from someone elses house, and installed the module on my own computer, so i don't know how my screen will look but it loaded and detected the nvidia tnt2 ultra john --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=tnt2-diff 2c2 < //#define NVRIVA_ENABLE_MTRR --- > // #define NVRIVA_ENABLE_MTRR 42a43 > #define NVTNT2_ID 0x0029 /* RIVA TNT2 */ 315c316,317 < else if ( (dev = pci_find_device(NVIDIA_VENDOR, NV4_ID, dev)) ) --- > else if ( (dev = pci_find_device(NVIDIA_VENDOR, NV4_ID, dev)) \ > || (dev = pci_find_device(NVIDIA_VENDOR, NVTNT2_ID, dev)) ) --HlL+5n6rz5pIUxbD-- From ggiweb@metalab.unc.edu Mon Jun 7 01:11:55 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA28779 for ; Mon, 7 Jun 1999 01:11:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA25516; Sun, 6 Jun 1999 22:02:46 -0700 Resent-Date: Sun, 6 Jun 1999 22:02:46 -0700 Date: Mon, 7 Jun 1999 01:43:14 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: GGI:: v0.1 (Perl5 XS module) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"7bz7s2.0.eD6.c9rMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13237 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com The first ALPHA release is at: http://www.calyx.com/~bri/projects/GGI/ggi-perl/ggi-perl-0.1.tar.gz Lots of missing things still -- no palette or color ops, no events, and it has about as much syntactical sugar as a diet soda. But what's there already should not be changing any, so it's stable enough to write with. Enjoy, -- Brian From ggiweb@metalab.unc.edu Mon Jun 7 07:28:06 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA01178 for ; Mon, 7 Jun 1999 07:28:05 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA10289; Mon, 7 Jun 1999 04:18:44 -0700 Resent-Date: Mon, 7 Jun 1999 04:18:44 -0700 Date: Mon, 7 Jun 1999 12:18:21 +0100 From: Tristan Wibberley To: ggi-develop@eskimo.com Subject: Re: GGI Cursor API proposal. Message-ID: <19990607121821.A5194@ps.cus.umist.ac.uk> References: <19990603132738.19560.rocketmail@web114.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990603132738.19560.rocketmail@web114.yahoomail.com>; from Kien Pham on Thu, Jun 03, 1999 at 06:27:38AM -0700 Resent-Message-ID: <"ljxIX.0.NW2.AgwMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13238 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, Jun 03, 1999 at 06:27:38AM -0700, Kien Pham wrote: > Systems that do not support hardware cursors can use > software emulation. You cannot efficiently emulate hardware cursor behaviour. Instead, you need to define a wider scope of the behaviour, which the hardware cursor is an acceptable implementation. See the way that windows does it (a good way). When you have a cursor displayed and you want to draw to the framebuffer, you must tell LibGGICursor that it should soft-disable cursor (ie, a software implementation is turned-off, hardware is not), and tell it to re-enable when it is finished. eg, ggiCursorOn( vis, cursor ); /* various stuff */ ggiCursorSoftOff( vis, cursor ); /* framebuffer operations on the part of the framebuffer which has the cursor */ ggiCursorSoftOn( vis, cursor ); /* various stuff */ ggiCursorOff( vis, cursor ); Although, I think a standard softlocking call should be provided by the core libGGI, where extensions which are performing software emulation which needs to be temporarily disabled when drawing operations are being done register themselves and what part of the visual they care about. Then any drawing operation which acts on that part soft-disables that hardware emulation, and re-enables it after - the programmer can have soft-dis/re-enable calls for operating on the framebuffer. -- Tristan Wibberley From ggiweb@metalab.unc.edu Mon Jun 7 07:37:27 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA01218 for ; Mon, 7 Jun 1999 07:37:27 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA12353; Mon, 7 Jun 1999 04:28:29 -0700 Resent-Date: Mon, 7 Jun 1999 04:28:29 -0700 From: Steffen Seeger Message-Id: <199906071127.NAA09348@demonti.physik.tu-chemnitz.de> Subject: kgi-0.9-990607 To: ggi-kgi@kludge.org (KGI mailing list) Date: Mon, 7 Jun 1999 13:27:38 +0200 (CEST) Cc: ggi-develop@eskimo.com (GGI GGI) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"bmWN4.0.m03.RpwMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13239 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello everyone, the kgi-0.9-990607 snapshot is available from http://www.tu-chemnitz.de/~sse If you like to test it, please fetch the whole tar,gz and extract it into a fresh kgi-0.9 tree. Directory structures have changed, so to have a consistent version you need to extract it into an new tree. What's new? - somewhat self-consistent drivers are included. Please look at kgi-0.9/drivers/ and subdirectories: chipset/3Dlabs clock/3Dlabs ramdac/3Dlabs monitor/ I have done a complete overhaul (again), in order to prepare us for UDI later on. The benefit of this all is, that we can (in theory) support statically linked systems multiheaded now. This driver tree is still not operational, as the card and system driver is missing. I hope to get this working. Anyhow, the drivers themselves are consistent and have the structure/coding techniques __final__ for kgi-0.9. Anyone who wants to write a kgi-0.9 driver, please go ahead and start to look at the PERMEDIA sample driver. - to build the sample driver, install as stated in README.install and the go to the directory drivers/graphic and type 'make' What's not new? - the keyboard driver patches are still not in. Sorry, but the driver stuff has eaten up all my development time. What can you help with? - Send me Monitor spec files for your monitors. (Fill out the monitor/new-monitor) template and send it to me. - How about automating this process, e.g. through a nice Web-form? - If you want to write/port a KGI driver, make yourself familiar with the current code and let me know what you want to work on. - ask if you don't understand things in there. Greetings, Steffen ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- From ggiweb@metalab.unc.edu Mon Jun 7 07:37:58 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA01226 for ; Mon, 7 Jun 1999 07:37:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA12484; Mon, 7 Jun 1999 04:29:00 -0700 Resent-Date: Mon, 7 Jun 1999 04:29:00 -0700 Sender: marcus@e.kth.se Message-ID: <375BACE1.47ABF906@stacken.kth.se> Date: Mon, 07 Jun 1999 11:28:33 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: GGI Cursor API proposal. References: <19990603132738.19560.rocketmail@web114.yahoomail.com> <19990607121821.A5194@ps.cus.umist.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"may193.0.l23.wpwMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13240 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Tristan Wibberley wrote: > Although, I think a standard softlocking call should be provided by > the core libGGI, where extensions which are performing software > emulation which needs to be temporarily disabled when drawing > operations are being done No extension should ever do such emulation. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Mon Jun 7 07:53:46 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA01377 for ; Mon, 7 Jun 1999 07:53:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA14162; Mon, 7 Jun 1999 04:44:53 -0700 Resent-Date: Mon, 7 Jun 1999 04:44:53 -0700 From: Steffen Seeger Message-Id: <199906071144.NAA09397@demonti.physik.tu-chemnitz.de> Subject: KGI-0.9 driver interface released To: ggi-develop@eskimo.com (GGI GGI), ggi-kgi@kludge.org (KGI mailing list) Date: Mon, 7 Jun 1999 13:44:28 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Lptnd.0.1T3.q2xMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13241 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello, this is just to announce (separately from the kgi-0.9-990607 snapshot) that the KGI-0.9 driver internal interface is far enough for driver developers to start writing their code. There is still no fully operational sample driver yet, but people can start to polish their headers/code to 0.9 style. Also, anyone who wants to - enhance the configuration scheme - add monitor spec files is very welcome. Greetings, Steffen ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- ------------- The GGI Project: http://www.ggi-project.org ------------- ----------------- http: http://www.tu-chemnitz.de/~sse ----------------- From ggiweb@metalab.unc.edu Mon Jun 7 08:49:18 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA01917 for ; Mon, 7 Jun 1999 08:49:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA21713; Mon, 7 Jun 1999 05:36:45 -0700 Message-ID: X-Mailer: NailMail 1.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Resent-Date: Sun, 06 Jun 1999 22:33:51 +0200 Resent-Message-Id: Resent-From: Axys Resent-To: tanner@ggi-project.org ECHELON: nuclear,Saddam,CIA,Milosevic,Clinton,dead,Plutonium,KGB,USA,bomb,terror Date: Mon, 07 Jun 1999 14:36:08 +0200 (CEST) Sender: thomas@ffii.org From: Thomas Tanner To: ggi-develop@eskimo.com Subject: FW: Help, i can't compil my prog. Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13242 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com -----FW: ----- Date: Sun, 06 Jun 1999 22:33:51 +0200 From: Axys To: tanner@ggi-project.org Subject: Help, i can't compil my prog. Hello, I hope that i send this e-mail at the good address... (sorry, I'am french and i have a very bad english) my problem is: I write (and copy in the LibGGI API Manual) this program: #include #include #include #include int main(int argc, char **argv) { ggi_visual_t vis; ggi_mode mode; int i; unsigned char *fbptr[2]; int stride[2]; int numbufs; mode.frames = 2; /* Double-buffering */ mode.visible.x = 640; mode.visible.y = 480; mode.virt.x = GGI_AUTO; mode.virt.y = GGI_AUTO; mode.graphtype = GT_16BIT; mode.dpp.x = mode.dpp.y = GGI_AUTO; if (ggiInit() != 0) { fprintf(stderr, "unable to initialize libggi, exiting.\n"); exit(1); } vis = ggiOpen(NULL); if (!vis) { ggiPanic("Couldn't open default visual!\n"); } if (ggiSetMode(vis, &mode)) { ggiPanic("Cannot set 640*480 16bit mode\n"); } numbufs = ggiDBGetNumBuffers(vis); for (i=0; itype & GGI_DB_SIMPLE_PLB)) { fprintf(sterr, "Error: non-standart display buffer\n"); } } /* main code here */ ggiClose(vis); ggiExit(); } My probleme is when I execute this program, there is an error: error in loading shared libraries: libggi.so.2: cannot open shared object file: no such file or directory. The libggi.so.2 exist in the /usr/local/lib, it's a link to libggi.so.2.0.0. When I execute the demos send with GGIlib, they works perfectly... voila, if you could understand my english and help me. (I'm beginer in language C). Thank's Friendly, Fred. --------------End of forwarded message------------------------- Thomas Tanner ----------------------------------------- email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de) web: http://home.pages.de/~tanner GGI/Picasso: http://picasso.ffii.org From ggiweb@metalab.unc.edu Mon Jun 7 09:03:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA02070 for ; Mon, 7 Jun 1999 09:02:59 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA25174; Mon, 7 Jun 1999 05:48:28 -0700 Resent-Date: Mon, 7 Jun 1999 05:48:28 -0700 Sender: marcus@e.kth.se Message-ID: <375BBF83.3E0445C4@stacken.kth.se> Date: Mon, 07 Jun 1999 12:48:03 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: Axys CC: ggi-develop@eskimo.com Subject: Re: FW: Help, i can't compil my prog. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"FmqNQ3.0.796.R-xMt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13243 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Thomas Tanner wrote: > > -----FW: ----- > > Date: Sun, 06 Jun 1999 22:33:51 +0200 > From: Axys > To: tanner@ggi-project.org > Subject: Help, i can't compil my prog. > > Hello, > > I hope that i send this e-mail at the good address... > > (sorry, I'am french and i have a very bad english) > > my problem is: > > I write (and copy in the LibGGI API Manual) this program: > > #include > #include > #include > #include > > int main(int argc, char **argv) > { > ggi_visual_t vis; > ggi_mode mode; > int i; > unsigned char *fbptr[2]; > int stride[2]; > int numbufs; > > mode.frames = 2; /* Double-buffering */ > mode.visible.x = 640; > mode.visible.y = 480; > mode.virt.x = GGI_AUTO; > mode.virt.y = GGI_AUTO; > mode.graphtype = GT_16BIT; > mode.dpp.x = mode.dpp.y = GGI_AUTO; > > if (ggiInit() != 0) > { > fprintf(stderr, "unable to initialize libggi, exiting.\n"); > exit(1); > } > > vis = ggiOpen(NULL); > > if (!vis) > { > ggiPanic("Couldn't open default visual!\n"); > } > > if (ggiSetMode(vis, &mode)) > { > ggiPanic("Cannot set 640*480 16bit mode\n"); > } > numbufs = ggiDBGetNumBuffers(vis); > for (i=0; i { > ggi_directbuffer *db; > db=ggiDBGetBuffer(vis, i); > if (!(db->type & GGI_DB_SIMPLE_PLB)) > { > fprintf(sterr, "Error: non-standart display buffer\n"); > } > } > > /* main code here */ > > ggiClose(vis); > ggiExit(); > } > > My probleme is when I execute this program, there is an error: > error in loading shared libraries: libggi.so.2: cannot open shared object > file: no such file or directory. > > The libggi.so.2 exist in the /usr/local/lib, it's a link to > libggi.so.2.0.0. When I execute the demos send with GGIlib, they works > perfectly... Add the line: /usr/local/lib to the file /etc/ld.so.conf //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggiweb@metalab.unc.edu Mon Jun 7 10:03:35 1999 -0400 Status: X-Status: X-Keywords: Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA03153 for ; Mon, 7 Jun 1999 10:03:34 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id GAA28493; Mon, 7 Jun 1999 06:52:14 -0700 (PDT) Resent-Date: Mon, 7 Jun 1999 06:52:14 -0700 (PDT) Sender: Rodolphe.Ortalo@cert.fr Message-ID: <375BC151.7FA@cert.fr> Date: Mon, 07 Jun 1999 14:55:45 +0200 From: Rodolphe Ortalo Organization: ONERA X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.6 sun4m) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: FW: Help, i can't compil my prog. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Resent-Message-ID: <"AM2h91.0.py6.vvyMt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13244 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Date: Sun, 06 Jun 1999 22:33:51 +0200 > From: Axys > To: tanner@ggi-project.org > Subject: Help, i can't compil my prog. > (sorry, I'am french and i have a very bad english) So do I. > My probleme is when I execute this program, there is an error: > error in loading shared libraries: libggi.so.2: cannot open shared object > file: no such file or directory. > The libggi.so.2 exist in the /usr/local/lib, it's a link to > libggi.so.2.0.0. When I execute the demos send with GGIlib, they works > perfectly... export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/local/lib before running your program should help you (or more precisely the dynamic linker) to find the library. Rodolphe PS: En plus, tu peux aussi ajouter le nom de repertoire '/usr/local/lib' dans le fichier de configuration de l'editeur de lien dynamique: /etc/ld.so.conf pour ne pas avoir a refaire la manipulation et pour que ld.so trouve tout seul la librairie. PPS: Even those that don't understand French should have understood what I say above. ;-)) From ggi-develop-request@eskimo.com Mon Jun 7 17:39:44 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA16336 for ; Mon, 7 Jun 1999 17:39:43 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA31408; Mon, 7 Jun 1999 14:25:58 -0700 Resent-Date: Mon, 7 Jun 1999 14:25:58 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990607032609.C2043@rz.uni-duesseldorf.de> Date: Mon, 7 Jun 1999 03:26:09 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: XGGI! Mail-Followup-To: ggi-develop@eskimo.com References: <19990606151231.C502@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from David Cougle on Sun, Jun 06, 1999 at 11:57:21AM -0500 Resent-Message-ID: <"miAkH3.0.Gg7.WZ3Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13246 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David Cougle wrote: > The thing is, all I have is a linux-mouse.so(a library). > # mouse Microsoft # Microsoft > # mouse MouseSystems # Mouse Systems > mouse MMSeries # Logitech MM Series Are you sure, that this is the correct entry ? I.e. does Mouse work right in SVGAlib ? I had a lot of Logitech mice, and most of them ran either as Microsoft or Mousesystem mice (or PS/2 for the busmouse), but none yet as MMSeries or Logitech or MouseMan. > # mdev /dev/ttyS0 # mouse is at /dev/ttyS0 It might be a good idea to set that explicitly. I take it your mouse works fine in X. Please send me the relevant section of your /etc/XF86Config (Section Pointer) and I'll send you an appropriate /~.ggi/input/mouse entry. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 7 17:39:56 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA16344 for ; Mon, 7 Jun 1999 17:39:55 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA31413; Mon, 7 Jun 1999 14:26:00 -0700 Resent-Date: Mon, 7 Jun 1999 14:26:00 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990607032025.B2043@rz.uni-duesseldorf.de> Date: Mon, 7 Jun 1999 03:20:25 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: no luck with XGGI! Mail-Followup-To: ggi-develop@eskimo.com References: <375ADEE0.735F3D69@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <375ADEE0.735F3D69@stacken.kth.se>; from Marcus Sundberg on Sun, Jun 06, 1999 at 10:49:36PM +0200 Resent-Message-ID: <"I6C1o2.0.wf7.TZ3Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13245 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > still no 104 keys, despite having XGGI load the keymap. > What do you mean "104 keys"? > Exactly what is it that doesn't work? The Win* keys? Win keys work fine here. they map to Meta_L, Meta_R and Menu. You may need to reconfigure either the keymap or your Client, if standard X setup maps those differently. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 7 18:07:44 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA16930 for ; Mon, 7 Jun 1999 18:07:41 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id OAA23434; Mon, 7 Jun 1999 14:54:27 -0700 (PDT) Resent-Date: Mon, 7 Jun 1999 14:54:27 -0700 (PDT) X-Authentication-Warning: sandra.lysator.liu.se: altic owned process doing -bs Date: Mon, 7 Jun 1999 23:47:12 +0200 (MET DST) From: =?iso-8859-1?Q?Peter_=C5strand?= To: ggi-develop@eskimo.com Subject: Monitor-definition Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mx2.eskimo.com id OAA23371 Resent-Message-ID: <"Dtfff.0.Rj5.rz3Nt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13247 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I have an HP A1097C fixed-frequency monitor connected to an Matrox Millenium I (capable of sync-on-green, which I use). It works great with XFree86, and it would be even greater if it worked with KGIcon as well. But .../kgicon/kgi/monitor/monosync doesn't include my monitor. I've tried to add it, but got confused by htiming[HTIMINGS] and vtiming[VTIMINGS]. Is there a simple way to convert XF86 modelines to these entries? Or how can I otherwise find this information? ------------------------------------------------------------------------------- Peter Åstrand , http://www.lysator.liu.se/~altic Master of Science student in Computer Science and Engineering ------------------------------------------------------------------------------- From ggi-develop-request@eskimo.com Mon Jun 7 18:32:40 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA17419 for ; Mon, 7 Jun 1999 18:32:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA21657; Mon, 7 Jun 1999 15:19:46 -0700 Resent-Date: Mon, 7 Jun 1999 15:19:46 -0700 Date: Mon, 7 Jun 1999 15:18:21 -0700 From: Joseph Carter To: ggi-develop@eskimo.com Subject: Re: Monitor-definition Message-ID: <19990607151821.A9402@debian.org> Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary=DocE+STaALJfprDB; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.4i In-Reply-To: =?iso-8859-1?Q?=3CPine=2EGSO=2E4=2E00=2E9906072344420=2E8389-100000=40sa?= =?iso-8859-1?Q?ndra=2Elysator=2Eliu=2Ese=3E=3B_from_Peter_=C5strand_on_M?= =?iso-8859-1?Q?on=2C_Jun_07=2C_1999_at_11:47:12PM_+0200?= X-Operating-System: Linux icarus2 2.2.6-ac1 Resent-Message-ID: <"B5Osb1.0.-H5.1M4Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13248 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --DocE+STaALJfprDB Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On Mon, Jun 07, 1999 at 11:47:12PM +0200, Peter =C5strand wrote: > I have an HP A1097C fixed-frequency monitor connected to an Matrox > Millenium I (capable of sync-on-green, which I use). It works great with > XFree86, and it would be even greater if it worked with KGIcon as well. > But .../kgicon/kgi/monitor/monosync doesn't include my monitor. I've tried > to add it, but got confused by htiming[HTIMINGS] and vtiming[VTIMINGS]. Is > there a simple way to convert XF86 modelines to these entries? Or how can > I otherwise find this information? Since when is the millennium capible of sync on green?? That would have seriously saved my bacon some time ago if it could have been done! I have a script for converting XF86 modelines into fb.modes entries, but I'm not sure that's what you need. -- Joseph Carter Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBE The Source Comes First! ------------------------------------------------------------------------- Studies prove that research causes cancer in 43% of laboratory rats knghtbrd- yeah, but 78% of those statistics are off by 52%... --DocE+STaALJfprDB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQEVAwUBN1xFKXRYxo9QvaDtAQEUbAf/YEivs/KVs7taifuDWxICDZqN1p0CWszL y+S9D6hbdD2OaxkpEbwPzbYPSLWaPtRb6tDBvYZAc48v+XFUTp5OA4AYDn9T97ZT mZaB96Jx0rzs4G4vJ9z0DroqStIjNLXtRTvKILrEetMn6UKXmx4YzIMaRw7Ekk6s 2EIIdSZYIeN0qyaq0AB/T1uCv8/SHeTk1WawRa6M2TC9Sy/i9th+GFO4+JkMZjJm z2rjLyTLdvtfkmrymsHPTdP8BPNb5uEZ6JoBSA3iUUubmSy0YE/fIeqmSwLVsgAR CNTEkw807Ge5pWsbYUi+PVo+xeyirv82P3GKlUj8NqwtaJddpgUwlg== =a9c5 -----END PGP SIGNATURE----- --DocE+STaALJfprDB-- From ggi-develop-request@eskimo.com Mon Jun 7 18:46:37 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA17719 for ; Mon, 7 Jun 1999 18:46:36 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id PAA26134; Mon, 7 Jun 1999 15:35:44 -0700 (PDT) Resent-Date: Mon, 7 Jun 1999 15:35:44 -0700 (PDT) X-Authentication-Warning: sandra.lysator.liu.se: altic owned process doing -bs Date: Tue, 8 Jun 1999 00:28:02 +0200 (MET DST) From: =?iso-8859-1?Q?Peter_=C5strand?= To: Joseph Carter cc: ggi-develop@eskimo.com Subject: Re: Monitor-definition In-Reply-To: <19990607151821.A9402@debian.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mx2.eskimo.com id PAA26087 Resent-Message-ID: <"7yd502.0.rN6.7a4Nt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13249 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Since when is the millennium capible of sync on green?? That would have > seriously saved my bacon some time ago if it could have been done! All Millenium and even Mystique cards are (I am told) capable of sync-on-green. But I had a _lot_ of trouble before I got this information. If i remember correctly, I saw it by accident on http://www.xfree86.org/3.3.3.1/MGA3.html > I have a script for converting XF86 modelines into fb.modes entries, but > I'm not sure that's what you need. Neither am I :-) Is it the one included in degas, modeline2fb by Patrick Reynolds? ------------------------------------------------------------------------------- Peter Åstrand , http://www.lysator.liu.se/~altic Master of Science student in Computer Science and Engineering ------------------------------------------------------------------------------- From ggi-develop-request@eskimo.com Mon Jun 7 18:50:41 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA17794 for ; Mon, 7 Jun 1999 18:50:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA30418; Mon, 7 Jun 1999 15:38:41 -0700 Resent-Date: Mon, 7 Jun 1999 15:38:41 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990607235537.D500@rz.uni-duesseldorf.de> Date: Mon, 7 Jun 1999 23:55:37 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: kgicon TNT2 diff Mail-Followup-To: ggi-develop@eskimo.com References: <19990606205059.A10419@greenbytes.greenbytes.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990606205059.A10419@greenbytes.greenbytes.cx>; from tentacle tentacle boat on Sun, Jun 06, 1999 at 08:50:59PM -0400 Resent-Message-ID: <"g4dEv.0.xQ7.ld4Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13250 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > this diff lets the nvidia riva kgi driver detect tnt2 ultras > i patched this from someone elses house, and installed the module > on my own computer, so i don't know how my screen will look > but it loaded and detected the nvidia tnt2 ultra Please be careful with such tests. Graphics hardware is one of the few things you can actually damage physically by wrong programming. Monitors are pretty safe by now, but the RAMDACs are often not secured against overclocking. Other than that, I'm pretty interested in the results of the experiment. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 7 18:52:32 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA17828 for ; Mon, 7 Jun 1999 18:52:31 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA31469; Mon, 7 Jun 1999 15:40:55 -0700 Resent-Date: Mon, 7 Jun 1999 15:40:55 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990608004346.A661@rz.uni-duesseldorf.de> Date: Tue, 8 Jun 1999 00:43:46 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGI:: v0.1 (Perl5 XS module) Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Brian S. Julin on Mon, Jun 07, 1999 at 01:43:14AM -0400 Resent-Message-ID: <"gxOI6.0.Oh7.rf4Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13251 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > http://www.calyx.com/~bri/projects/GGI/ggi-perl/ggi-perl-0.1.tar.gz O.K. - up on FTP now as well. wrappers/perl . -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 7 18:57:03 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA17886 for ; Mon, 7 Jun 1999 18:57:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA00253; Mon, 7 Jun 1999 15:45:28 -0700 Resent-Date: Mon, 7 Jun 1999 15:45:28 -0700 Date: Mon, 7 Jun 1999 17:47:11 -0500 (CDT) From: David Cougle X-Sender: lunarbard@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: XGGI! In-Reply-To: <19990607032609.C2043@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"4Bthr2.0.U3.7k4Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13252 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Section "Pointer" Protocol "MouseMan" Device "/dev/mouse" On Mon, 7 Jun 1999, Andreas Beck wrote: > David Cougle wrote: > > The thing is, all I have is a linux-mouse.so(a library). > > > # mouse Microsoft # Microsoft > > # mouse MouseSystems # Mouse Systems > > mouse MMSeries # Logitech MM Series > > Are you sure, that this is the correct entry ? I.e. does Mouse work right in > SVGAlib ? > > I had a lot of Logitech mice, and most of them ran either as Microsoft or > Mousesystem mice (or PS/2 for the busmouse), but none yet as MMSeries or > Logitech or MouseMan. > > > # mdev /dev/ttyS0 # mouse is at /dev/ttyS0 > > It might be a good idea to set that explicitly. > > I take it your mouse works fine in X. Please send me the relevant section of > your /etc/XF86Config (Section Pointer) and I'll send you an appropriate > /~.ggi/input/mouse entry. > > CU, ANdy > > -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From ggi-develop-request@eskimo.com Mon Jun 7 19:50:40 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA18796 for ; Mon, 7 Jun 1999 19:50:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA16894; Mon, 7 Jun 1999 16:36:37 -0700 Resent-Date: Mon, 7 Jun 1999 16:36:37 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990608013936.A1049@rz.uni-duesseldorf.de> Date: Tue, 8 Jun 1999 01:39:36 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Monitor-definition Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: =?iso-8859-1?Q?=3CPine=2EGSO=2E4=2E00=2E9906072344420=2E8389-100000=40sa?= =?iso-8859-1?Q?ndra=2Elysator=2Eliu=2Ese=3E=3B_from_Peter_=C5strand_on_M?= =?iso-8859-1?Q?on=2C_Jun_07=2C_1999_at_11:47:12PM_+0200?= Resent-Message-ID: <"Q1Djb1.0.m74.5U5Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13253 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I have an HP A1097C fixed-frequency monitor connected to an Matrox > Millenium I (capable of sync-on-green, which I use). It works great with > XFree86, and it would be even greater if it worked with KGIcon as well. > But .../kgicon/kgi/monitor/monosync doesn't include my monitor. I've tried > to add it, but got confused by htiming[HTIMINGS] and vtiming[VTIMINGS]. Is > there a simple way to convert XF86 modelines to these entries? Yes - look: #ifdef __VGA__ /* VGA From: Steffen Seeger, [Seeger@physik.tu-chemnitz.de] ** Date: 21 Nov 95 ** Note: normally VGA monitors have a bandwidth of 30 MHz. But as this ** would only allow for 640 pixel horizontally the bandwidth is set to ** 32 MHz, which will make 800 pixel modes possible (e.g. 100x50 textmode). */ #define MON_VERSION "0.00 ALPHA" static struct kgi_monitor monitor = { "standard", /* manufacturer */ "14\" VGA", /* model */ GM_ALL, /* supported modes */ 0, /* special capabilities */ { 800, 480 }, /* maximum resolution */ NULL, /* Private data hook */ { 240, 180 }, /* picture size [mm] */ VGA_COLOR, /* VGA color monitor */ SYNC_NORMAL, /* normal syncing, VESA */ { 25000000, 32000000 }, /* pixel clock range */ { 31100, 31900 }, /* hfreq range */ { 50, 70 } /* vfreq range */ }; ** That should be no problem for you to fill in - right ? #define HTIMINGS 1 #define VTIMINGS 3 ** Just the number of different timings that work. Probably both 1 for a ** "true" monosync monitor. static struct kgi_timing htiming[HTIMINGS] = /* horizontal timing in ns, descending hfreq */ {/* width bstart sstart send bend total dummy */ { 25422, 25422, 27011, 30824, 31142, 31778, 0 } /* 31.468 kHz */ }; static struct kgi_timing vtiming[VTIMINGS] = /* vertical timing in lines */ { /* width bstart sstart send bend total polarity & htiming */ { 480, 488, 489, 491, 516, 524, HNEG | VNEG | 0 }, /* 60 Hz */ { 400, 407, 412, 414, 442, 449, HNEG | VPOS | 0 }, /* 70 Hz */ { 350, 356, 387, 389, 443, 449, HPOS | VNEG | 0 } /* 70 Hz */ }; #endif /* __VGA__ */ ** Let's look at the XF86 modeline to understand that: # 640x400 @ 70 Hz, 31.5 kHz hsync Modeline "640x400" 25.175 640 664 760 800 400 409 411 450 # 640x480 @ 60 Hz, 31.5 kHz hsync Modeline "640x480" 25.175 640 664 760 800 480 491 493 525 First of all, note, that the VTIMINGS are almost the same. It's just that GGI also handles blank-start and -end separately. You can use some arbitrary value between width and syncstart or syncend and total respectively. That is, a XF86 Modeline is in GGI terms: Modeline "640x480" 25.175 640 664 760 800 width sstart send total The X timing is handled differently. the reason is, that the monitor can't "see" the pixelclock. It just sees a given horizontal frequency. For that reason, we give horizontal timing in nanoseconds (a 1/1 000 000 000th of a second) instead of pixels. So let's convert the 640x480 Entry to a GGI style entry: One pixel takes 1/pixclock seconds. Pixclock is given in MHz, so 1 pixel = 1/25.175 Mhz = 0.03972 microseconds = 39.72 nanoseconds. => width = 640*39.72ns = 25422ns => sstart= 664*39.72ns = 26375ns => send = 664*39.72ns = 30189ns => total = 800*39.72ns = 31778ns O.K. - you see that people have different ideas of where exactly to put the SYNC pulse, but you get the idea. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 7 19:52:12 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA18817 for ; Mon, 7 Jun 1999 19:52:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA18053; Mon, 7 Jun 1999 16:40:51 -0700 Resent-Date: Mon, 7 Jun 1999 16:40:51 -0700 Date: Mon, 7 Jun 1999 16:40:37 -0700 From: Joseph Carter To: =?iso-8859-1?Q?Peter_=C5strand?= Cc: ggi-develop@eskimo.com Subject: Re: Monitor-definition Message-ID: <19990607164037.B9696@debian.org> Mail-Followup-To: =?iso-8859-1?Q?Peter_=C5strand?= , ggi-develop@eskimo.com References: <19990607151821.A9402@debian.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary=qlTNgmc+xy1dBmNv; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.4i In-Reply-To: =?iso-8859-1?Q?=3CPine=2EGSO=2E4=2E00=2E9906080021570=2E8673-100000=40sa?= =?iso-8859-1?Q?ndra=2Elysator=2Eliu=2Ese=3E=3B_from_Peter_=C5strand_on_T?= =?iso-8859-1?Q?ue=2C_Jun_08=2C_1999_at_12:28:02AM_+0200?= X-Operating-System: Linux icarus2 2.2.6-ac1 Resent-Message-ID: <"VOqOr2.0.jP4.1Y5Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13254 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --qlTNgmc+xy1dBmNv Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Jun 08, 1999 at 12:28:02AM +0200, Peter =C5strand wrote: >=20 > > Since when is the millennium capible of sync on green?? That would have > > seriously saved my bacon some time ago if it could have been done! >=20 > All Millenium and even Mystique cards are (I am told) capable of > sync-on-green. But I had a _lot_ of trouble before I got this information. > If i remember correctly, I saw it by accident on > http://www.xfree86.org/3.3.3.1/MGA3.html Will have a look, thanks. > > I have a script for converting XF86 modelines into fb.modes entries, but > > I'm not sure that's what you need. >=20 > Neither am I :-) Is it the one included in degas, modeline2fb by Patrick > Reynolds? Yes, that's the one. -- Joseph Carter Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBE The Source Comes First! ------------------------------------------------------------------------- =2E.. Where was Stac Electronics when Microsoft invented Doublespace? Where were Xerox and Apple when Microsoft invented the GUI? Where was Apple's QuickTime when Microsoft invented Video for Windows? Where was Spyglass Inc.'s Mosaic when Microsoft invented Internet Explorer? Where was Sun when Microsoft invented Java? --qlTNgmc+xy1dBmNv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQEVAwUBN1xYcXRYxo9QvaDtAQE6NAgAkIlcM1cnFVvNV42QvUYHzo+7r6kslbuN wy3yGowZ2KoTWRYPHIr/9PvCKghgNYqF84UHqd/4ecfbQs4sxv809uAcx63koIL0 kOluQL6Bn3/Op714suI6xCO8qjGgb34x+NlqJN9zzpG/Jt75ZF7c7xqaEb/LWDhJ t2yVlU3FKVymNf6NnEotixw3QipIy/v4F/LE+kPN/2+HFiTy2vApnXhRpNsEyJXd AyCWTsy6hewPyK6JbI9tZ8nOu+CFx6X4nVo514ziLW1hK2D2zh4XU9rsyFz27yKI KL2TeHtVkIanwY2jsVgivNOzu/wj0Ds/ecxtDXSGowQnDf3ZN+/Wxw== =crJd -----END PGP SIGNATURE----- --qlTNgmc+xy1dBmNv-- From ggi-develop-request@eskimo.com Mon Jun 7 22:58:24 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA21570 for ; Mon, 7 Jun 1999 22:58:23 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA17708; Mon, 7 Jun 1999 19:46:34 -0700 Resent-Date: Mon, 7 Jun 1999 19:46:34 -0700 Date: Mon, 7 Jun 1999 22:47:00 -0400 From: tentacle tentacle boat To: ggi-develop@eskimo.com Subject: Re: kgicon TNT2 diff Message-ID: <19990607224700.A11694@greenbytes.greenbytes.cx> References: <19990606205059.A10419@greenbytes.greenbytes.cx> <19990607235537.D500@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990607235537.D500@rz.uni-duesseldorf.de>; from Andreas Beck on Mon, Jun 07, 1999 at 11:55:37PM +0200 Resent-Message-ID: <"lMqYz1.0.RK4.8G8Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13255 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Well, the TNT and the TNT2 2D is pretty much the same, this experiment worked fine, the white lines that come up on TNT cards came up, but if i run super probe before, the driver works perfectly.. well as far as i can tell :) john On Mon, Jun 07, 1999 at 11:55:37PM +0200, Andreas Beck wrote: > > this diff lets the nvidia riva kgi driver detect tnt2 ultras > > i patched this from someone elses house, and installed the module > > on my own computer, so i don't know how my screen will look > > but it loaded and detected the nvidia tnt2 ultra > > Please be careful with such tests. Graphics hardware is one of the few > things you can actually damage physically by wrong programming. > Monitors are pretty safe by now, but the RAMDACs are often not secured > against overclocking. > > Other than that, I'm pretty interested in the results of the experiment. > > CU, ANdy > > -- > = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 8 00:42:39 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA22979 for ; Tue, 8 Jun 1999 00:42:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA13847; Mon, 7 Jun 1999 21:27:31 -0700 Resent-Date: Mon, 7 Jun 1999 21:27:31 -0700 Date: Mon, 7 Jun 1999 21:27:21 -0700 (PDT) From: "Jon M. Taylor" To: KGI mailing list cc: GGI mailing list Subject: Linux memory-mapping problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"_XcRv2.0.9O3.hk9Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13256 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I'm having a very strange linux kernel related problem and I'm hoping that someone here (Marcus in particular) might have some insight. If not I'll ask elsewhere. The problem is that I cannot use remap_page_range() to implement the mmap() function on a file so that I can map auxiliary hardware buffers (z-buffer, textures, etc) into userspace. I have tried implementing this alternate mmap() system as an extension of fbcon-kgi.c's kgifb_mmap() as well as implementing it as a separate function, but no matter what contortions I put the code through I always see the same behavior. The exact behavior is that my mmap() handler returns a valid pointer to userspace but then dies with a 'bogus page' error when the supposedly remapped memory range is accessed in userspace. All I do in my KGI driver is define some kgi_mem_regions which span the appropriate address ranges (exactly like the LFB region is handled in every KGI driver), and then read them out of the driver private data in fbcon-kgi.c and pass them to the new aux-buffer mapping code I'm currently writing. The kgi_mem_regions have been claim_region()ed properly and can be accessed from within the driver as well as by mmap() of /dev/mem. I shouldn't need to ioremap() the regions again, since they have already been remapped by mem_claim_region(). Everything is set up appropriately, but I can't make the damn mmap() process work! Even if I replace my mmap() handler with an _exact copy_ of kgifb_mmap(), it still gives the same error! That last is really weirding me out, because kgifb_mmap() works fine in its current implementation. I can show the affected code to anyone who is willing to help me with this, since it does not involve anything proprietary. In fact, most of it does not involve the Savage4 KGI driver at all, just fbcon-kgi.c. I really want to get this (probably stupid) problem fixed so I can finish implementing this new dynamic proc-based auxiliary buffer management system and release it. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Tue Jun 8 08:13:55 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA26951 for ; Tue, 8 Jun 1999 08:13:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA29364; Tue, 8 Jun 1999 04:59:55 -0700 Resent-Date: Tue, 8 Jun 1999 04:59:55 -0700 Date: Tue, 8 Jun 1999 07:47:05 -0400 (EDT) From: Leimy To: ggi-develop@eskimo.com Subject: Re: Question (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"nkEl12.0.O87.RMGNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13257 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Check this out. I actually got a response from Jaton about my graphics card not that it was any good. Dear Customer: We appreciate your enthusiastic support for our products. However, the Video-67 with the Trident 9680 chipset is supported by Linux already, so you do not need to write any driver for it. There are many GUI shell program available. You may simply enter the Graphics Chipset Trident 9685 or 9680/9660 and default Clock and RAMDAC Chip (there is no seperate clock or RAMDAC chip) and configure the monitor properly with your shell program. Thank you. Perry Li Jaton Corp. Technical Support wrote: > his email address is > Leimy > > Leimy wrote: > > > I want to write a video driver for my Video 67P card for Linux. Is > > there > > any way to get information about the low level stuff on my card? > > > > Dave From ggi-develop-request@eskimo.com Tue Jun 8 10:03:41 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA29236 for ; Tue, 8 Jun 1999 10:03:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA27250; Tue, 8 Jun 1999 06:44:42 -0700 Resent-Date: Tue, 8 Jun 1999 06:44:42 -0700 Sender: flo@sendnix.tele.net Message-ID: <375D1F72.85E2DFF1@vol.at> Date: Tue, 08 Jun 1999 15:49:38 +0200 From: Scandella Florian X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.2.9 i686) MIME-Version: 1.0 To: "ggi-develop@eskimo.com" Subject: kgi-0.9 Bugs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"NHBAh.0.ae6.4vHNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13258 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I have tested kgi at home. I have an 2.2.9 kernel, Matrox Millenium I, serial MS compatible Logitech mouse and a PS/2 keyboard. *First it doesn't detect my /dev/ttyS0 #> setserial /dev/ttyS0 kgi.c:kgi_register_device:291: no display to attach device (dpy 3, dev 63) console.c:console_open:1443: failed: could not register output ( many times ) But when I first search for /dev/ttyS1 #> setserial /dev/ttyS1 ttyS01 at 0x02f8 (irq = 3) is a 16550A #> setserial /dev/ttyS0 ttyS00 at 0x03f8 (irq = 4) is a 16550A Serial drivers are build as modules. *Mc starts only one time ( start mc, end mc,reset console, start mc, mc doesn't start ) *I can switch console with M-[F1,F2,...] , also in X. *On installing kgi I had to copy ( symlink ) the include dirs ( kgi-0.9/lib/ggi/include, kgi-0.9/kgi/Linux/include/[kgi,kii] ) and the source directory ( kgi-0.9/kgi/Linux/src -> linux/driver/kgi ). How does GGI use kgi with the boot driver ? ( for VGA modi ? ) *Sorry for bad english Flo -- Scandella Florian scandella@vol.at Austria From ggi-develop-request@eskimo.com Tue Jun 8 12:40:48 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA03007 for ; Tue, 8 Jun 1999 12:40:47 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA09865; Tue, 8 Jun 1999 09:26:44 -0700 Resent-Date: Tue, 8 Jun 1999 09:26:44 -0700 Message-ID: <19990608162708.4919.rocketmail@web126.yahoomail.com> Date: Tue, 8 Jun 1999 09:27:08 -0700 (PDT) From: Kien Pham Subject: What's the num option to ggiGetAPI()? To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"WsZzt2.0.XO2.0HKNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13259 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com What is the num option that is passed to ggiGetAPI() supposed to be? ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggi-develop-request@eskimo.com Tue Jun 8 15:56:41 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA07377 for ; Tue, 8 Jun 1999 15:56:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA26514; Tue, 8 Jun 1999 12:44:33 -0700 Resent-Date: Tue, 8 Jun 1999 12:44:33 -0700 Date: Tue, 8 Jun 1999 15:24:43 -0400 (EDT) From: "Brian S. Julin" To: Scandella Florian cc: "ggi-develop@eskimo.com" , ggi-kgi@kludge.org Subject: Re: kgi-0.9 Bugs In-Reply-To: <375D1F72.85E2DFF1@vol.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"KAO1C2.0.eT6.RANNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13260 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 8 Jun 1999, Scandella Florian wrote: > *First it doesn't detect my /dev/ttyS0 KGI has currently nothing to do with rs232 ports, unless Steffen added support recently, which I doubt he has since he hasn't been working on input code lately. This is indicative of a rather funky smelling bug. > *I can switch console with M-[F1,F2,...] , also in X. "Feature", not bug. It will stay this way until parameters are added to allow the system administrator to decide what keys cannot be taken away from the console system. > *On installing kgi I had to copy ( symlink ) the include dirs ( > kgi-0.9/lib/ggi/include, kgi-0.9/kgi/Linux/include/[kgi,kii] ) and the > source directory ( kgi-0.9/kgi/Linux/src -> linux/driver/kgi ). If you had to link these by hand, then the kernel patch probably failed, find linux/ -name \*.rej and fix the failed hunks. > How does GGI use kgi with the boot driver ? ( for VGA modi ? ) It doesn't. The boot driver is just a console system. You need a full driver for GGI. -- Brian From ggi-develop-request@eskimo.com Tue Jun 8 16:39:12 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA08356 for ; Tue, 8 Jun 1999 16:39:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA22820; Tue, 8 Jun 1999 13:27:53 -0700 Resent-Date: Tue, 8 Jun 1999 13:27:53 -0700 Date: Tue, 8 Jun 1999 17:09:20 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: At the risk of being preachy Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"yJn5r.0.Ha5.8pNNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13261 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I just got done finishing my backlog of e-mail from various lists, and since I bothered to actually read some threads which I wasn't really interested, I couldn't help but notice from this detached perspective that while (for the most part) people are very polite, in quite a number of the exchanges people were missing each other's points because they were underestimating the person they were talking to. Maybe it's just the language barrier, being the diversity on every list I am subscribed to has increased so much over the past year or so, but I think we could do all afford a little more pondering before answering questions or arguments as to what the other person meant before jumping to the conclusion that they "do not understand" some basic concept because often they do, just their point is stated a little bit obscurely or in the wrong terms. Yes we have a lot of newbies here now, but even a good portion of the newbies are fairly literate in the subject matter. I don't know why I bothered to post this comment, especially to this, one of the better lists, but it just struck me as a trend that we would be better off without. -- Brian From ggi-develop-request@eskimo.com Tue Jun 8 18:08:26 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA10270 for ; Tue, 8 Jun 1999 18:08:25 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA10324; Tue, 8 Jun 1999 14:55:52 -0700 Resent-Date: Tue, 8 Jun 1999 14:55:52 -0700 Sender: marcus@e.kth.se Message-ID: <375D9157.3101850B@stacken.kth.se> Date: Tue, 08 Jun 1999 21:55:35 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: What's the num option to ggiGetAPI()? References: <19990608162708.4919.rocketmail@web126.yahoomail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"wmE4i1.0.VW2.Y5PNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13262 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Kien Pham wrote: > > What is the num option that is passed to ggiGetAPI() > supposed to be? It's the number of the API. You start at 0 and when you get a negative return code you know there are no more APIs. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 8 18:19:34 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA10566 for ; Tue, 8 Jun 1999 18:19:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA14464; Tue, 8 Jun 1999 15:07:32 -0700 Resent-Date: Tue, 8 Jun 1999 15:07:32 -0700 Sender: marcus@e.kth.se Message-ID: <375D9417.3CC4BA6E@stacken.kth.se> Date: Tue, 08 Jun 1999 22:07:19 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Linux memory-mapping problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"GIvIU2.0.hX3.YGPNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13263 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > > I'm having a very strange linux kernel related problem and I'm hoping > that someone here (Marcus in particular) might have some insight. If not > I'll ask elsewhere. The problem is that I cannot use remap_page_range() to > implement the mmap() function on a file so that I can map auxiliary hardware > buffers (z-buffer, textures, etc) into userspace. I have tried implementing > this alternate mmap() system as an extension of fbcon-kgi.c's kgifb_mmap() as > well as implementing it as a separate function, but no matter what > contortions I put the code through I always see the same behavior. Unfortunately I have no idea about this. I still haven't figured out why the GC mapping doesn't work when don't using USE_VMOPS... //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 8 20:42:49 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA13300 for ; Tue, 8 Jun 1999 20:42:48 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA05363; Tue, 8 Jun 1999 17:30:48 -0700 Resent-Date: Tue, 8 Jun 1999 17:30:48 -0700 Date: Tue, 8 Jun 1999 17:30:39 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com cc: Steffen Seeger Subject: Re: Linux memory-mapping problem In-Reply-To: <375D9417.3CC4BA6E@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"Gi4iU3.0.DJ1.sMRNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13264 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 8 Jun 1999, Marcus Sundberg wrote: > Jon M. Taylor wrote: > > > > I'm having a very strange linux kernel related problem and I'm hoping > > that someone here (Marcus in particular) might have some insight. If not > > I'll ask elsewhere. The problem is that I cannot use remap_page_range() to > > implement the mmap() function on a file so that I can map auxiliary hardware > > buffers (z-buffer, textures, etc) into userspace. I have tried implementing > > this alternate mmap() system as an extension of fbcon-kgi.c's kgifb_mmap() as > > well as implementing it as a separate function, but no matter what > > contortions I put the code through I always see the same behavior. > > Unfortunately I have no idea about this. I still haven't figured out why > the GC mapping doesn't work when don't using USE_VMOPS... OK, I have (mostly) fixed my problem, which was caused by using the MAP_PRIVATE flag in the mmap() call, which causes the kernel to implement a shared copy-on-write mapping over the region in question. Obviously this cannot work for a region which is mapped to a physical I/O address space. Using the MAP_SHARED flag instead fixed the problem. Marcus, I think that your GC mapping also falls victim to this because you use _get_free_page() to allocate the GC, which also maps directly to a physical I/O region. I notice that your nopage() handler manually increments the page useage count - a similar manual page-by-page PTE constructor is necessary for multiple-page mappings, which can be seen by examining drivers/video/sbusfb.c and drivers/char/bttv.c. Now, it is obviously not acceptable to allow userspace to trigger that 'bogus page' error in the kernel, so I will have to think about how to gracefully fail when userspace code uses the MAP_PRIVATE flag. I may just lock the aux-buffers on a per-process basis, since it is unlikely that separate processes will ever be hitting the LFB and the aux-buffers at the same time.... Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Tue Jun 8 22:26:54 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA14447 for ; Tue, 8 Jun 1999 22:26:53 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA12794; Tue, 8 Jun 1999 19:13:35 -0700 Resent-Date: Tue, 8 Jun 1999 19:13:35 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990609004754.D523@rz.uni-duesseldorf.de> Date: Wed, 9 Jun 1999 00:47:54 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: kgicon TNT2 diff Mail-Followup-To: ggi-develop@eskimo.com References: <19990606205059.A10419@greenbytes.greenbytes.cx> <19990607235537.D500@rz.uni-duesseldorf.de> <19990607224700.A11694@greenbytes.greenbytes.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990607224700.A11694@greenbytes.greenbytes.cx>; from tentacle tentacle boat on Mon, Jun 07, 1999 at 10:47:00PM -0400 Resent-Message-ID: <"TIiu21.0.X73.DtSNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13265 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Well, the TNT and the TNT2 2D is pretty much the same, this experiment worked > fine, the white lines that come up on TNT cards came up, but if i run super > probe before, the driver works perfectly.. well as far as i can tell :) O.K. - if you have a minute, it would be nice, if you could have a look at the TNT driver and make it dump the whole card state when it gets loaded (you sure look like being enough of a kernel hacker to do that ... :-). If you can reproduce the effect of loading with & without SuperProbe, this should give a clue about what goes wrong without SuperProbe and making a patch for that. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 8 22:27:07 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA14452 for ; Tue, 8 Jun 1999 22:27:06 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA12835; Tue, 8 Jun 1999 19:13:37 -0700 Resent-Date: Tue, 8 Jun 1999 19:13:37 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990609005638.E523@rz.uni-duesseldorf.de> Date: Wed, 9 Jun 1999 00:56:38 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: XGGI! Mail-Followup-To: ggi-develop@eskimo.com References: <19990607032609.C2043@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from David Cougle on Mon, Jun 07, 1999 at 05:47:11PM -0500 Resent-Message-ID: <"IyQ7W2.0.-73.FtSNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13266 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > I take it your mouse works fine in X. Please send me the relevant section > > of your /etc/XF86Config (Section Pointer) and I'll send you an appropriate > > /~.ggi/input/mouse entry. > Section "Pointer" > Protocol "MouseMan" > Device "/dev/mouse" ------ execute this --------- #!/bin/sh mkdir ~/.ggi mkdir ~/.ggi/input cat >~/.ggi/input/linux-mouse < = From ggi-develop-request@eskimo.com Tue Jun 8 22:28:41 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA14457 for ; Tue, 8 Jun 1999 22:28:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA12880; Tue, 8 Jun 1999 19:13:40 -0700 Resent-Date: Tue, 8 Jun 1999 19:13:40 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990609003305.A523@rz.uni-duesseldorf.de> Date: Wed, 9 Jun 1999 00:33:05 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: What's the num option to ggiGetAPI()? Mail-Followup-To: ggi-develop@eskimo.com References: <19990608162708.4919.rocketmail@web126.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990608162708.4919.rocketmail@web126.yahoomail.com>; from Kien Pham on Tue, Jun 08, 1999 at 09:27:08AM -0700 Resent-Message-ID: <"Oaot-1.0.j83.ItSNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13267 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > What is the num option that is passed to ggiGetAPI() > supposed to be? It's an enumerator for the API. Basically it's the number of the API from the list you want to query. It is usually only used in extensions, where one uses a loop like for(i=0; ggiGetAPI(vis, i, api, args) == 0; i++) { ... } To load the extension's idea of rendering helpers for the current target/mode. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Wed Jun 9 07:19:35 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA19607 for ; Wed, 9 Jun 1999 07:19:34 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA06371; Wed, 9 Jun 1999 04:06:24 -0700 Resent-Date: Wed, 9 Jun 1999 04:06:24 -0700 Date: Wed, 9 Jun 1999 12:06:03 +0100 From: Tristan Wibberley To: ggi-develop@eskimo.com Subject: ggiDrawHLine and ggiDrawVLine bugs? Message-ID: <19990609120603.A4665@ps.cus.umist.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Resent-Message-ID: <"oiBAV1.0.CZ1.ggaNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13268 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com The display-x and display-xlib targets seem to behave differently when doing either ggiDrawHLine or ggiDrawVLine, with display-xlib drawing lines one pixel longer. * display-x draws lines from the starting pixel up to, but not including the starting pixel + length. * display-xlib draws lines from the starting pixel up to, *and* including the staing pixel + length. (ie, it's one pixel longer than one would expect). start start+length + + display-x ################ display-xlib ################# Should: XDrawLine(priv->xwin.x.display, priv->xwin.window, priv->xwin.x.gc, x, y, x+w, y); in display/Xlib/hline.c be: XDrawLine(priv->xwin.x.display, priv->xwin.window, priv->xwin.x.gc, x, y, x+w-1, y); Since the Xlib call takes start point and end point, not the point where the line starts and number of pixels on the line. Is this actually happening? Am I imagining it? Is anything else affected by differences in behaviour between LibGGI and Xlib? -- Tristan Wibberley From ggi-develop-request@eskimo.com Wed Jun 9 15:13:25 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA00951 for ; Wed, 9 Jun 1999 15:13:24 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA18936; Wed, 9 Jun 1999 11:59:47 -0700 Resent-Date: Wed, 9 Jun 1999 11:59:47 -0700 Date: Wed, 9 Jun 1999 15:00:04 -0400 From: tentacle tentacle boat To: ggi-develop@eskimo.com Subject: Re: kgicon TNT2 diff Message-ID: <19990609150004.A14587@greenbytes.greenbytes.cx> References: <19990606205059.A10419@greenbytes.greenbytes.cx> <19990607235537.D500@rz.uni-duesseldorf.de> <19990607224700.A11694@greenbytes.greenbytes.cx> <19990609004754.D523@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990609004754.D523@rz.uni-duesseldorf.de>; from Andreas Beck on Wed, Jun 09, 1999 at 12:47:54AM +0200 Resent-Message-ID: <"n--Qy.0.Wc4.6chNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13269 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, Jun 09, 1999 at 12:47:54AM +0200, Andreas Beck wrote: > > Well, the TNT and the TNT2 2D is pretty much the same, this experiment worked > > fine, the white lines that come up on TNT cards came up, but if i run super > > probe before, the driver works perfectly.. well as far as i can tell :) > > O.K. - if you have a minute, it would be nice, if you could have a look at > the TNT driver and make it dump the whole card state when it gets loaded > (you sure look like being enough of a kernel hacker to do that ... :-). > > If you can reproduce the effect of loading with & without SuperProbe, this > should give a clue about what goes wrong without SuperProbe and making > a patch for that. > Well, i modified the save_state function, and made it printf(); the state before the driver is loaded, it won't load because the kernel doesn't have the printf() function ;).. how do i print text to my console from within the module? john From ggi-develop-request@eskimo.com Wed Jun 9 17:15:06 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA04157 for ; Wed, 9 Jun 1999 17:15:05 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA02790; Wed, 9 Jun 1999 14:03:44 -0700 Resent-Date: Wed, 9 Jun 1999 14:03:44 -0700 From: "David L. Bilbey" Message-Id: <199906092103.RAA03419@colossus.csl.mtu.edu> Subject: Game SDKs To: ggi-develop@eskimo.com Date: Wed, 9 Jun 1999 17:03:25 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"r8PkO3.0.Gg.iQjNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13270 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Which Game SDKs currently support the GGI target? Which plan to? I would like to write a game for GGI, but I don't want to reinvent the (Game SDK) wheel. Bilbey -- "I wish somebody would invent a fruit that had no seeds, tasted delicious, and would scream when you ate it." --Jack Handey From ggi-develop-request@eskimo.com Wed Jun 9 17:27:55 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA04430 for ; Wed, 9 Jun 1999 17:27:53 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA09328; Wed, 9 Jun 1999 14:16:12 -0700 Resent-Date: Wed, 9 Jun 1999 14:16:12 -0700 Message-ID: <000d01beb2c5$ba09d2e0$7884d4d1@dave> From: "David Waite" To: References: <19990606205059.A10419@greenbytes.greenbytes.cx> <19990607235537.D500@rz.uni-duesseldorf.de> <19990607224700.A11694@greenbytes.greenbytes.cx> <19990609004754.D523@rz.uni-duesseldorf.de> <19990609150004.A14587@greenbytes.greenbytes.cx> Subject: Re: kgicon TNT2 diff Date: Wed, 9 Jun 1999 17:16:22 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Resent-Message-ID: <"Gwkh_2.0.XH2.QcjNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13271 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Well, i modified the save_state function, and made it printf(); > the state before the driver is loaded, it won't load because the > kernel doesn't have the printf() function ;).. how do i print > text to my console from within the module? printk? :) the 'registers dump' is very useful, it helped a lot when trying to figure out the S3 968 stuff (tracked it down to undocumented registers) -David Waite From ggi-develop-request@eskimo.com Wed Jun 9 22:26:08 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA09185 for ; Wed, 9 Jun 1999 22:26:07 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA03009; Wed, 9 Jun 1999 19:13:57 -0700 Resent-Date: Wed, 9 Jun 1999 19:13:57 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990610003800.A1344@rz.uni-duesseldorf.de> Date: Thu, 10 Jun 1999 00:38:00 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Game SDKs Mail-Followup-To: ggi-develop@eskimo.com References: <199906092103.RAA03419@colossus.csl.mtu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <199906092103.RAA03419@colossus.csl.mtu.edu>; from David L. Bilbey on Wed, Jun 09, 1999 at 05:03:25PM -0400 Resent-Message-ID: <"Mkw6x1.0.bk.WznNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13272 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Which Game SDKs currently support the GGI target? Which plan to? I would > like to write a game for GGI, but I don't want to reinvent the (Game SDK) > wheel. AFAIK the ClanLib people are working on a port ... any status updates ? I'd like to run Pingus :-) ... CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Wed Jun 9 23:02:47 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA09636 for ; Wed, 9 Jun 1999 23:02:46 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA20473; Wed, 9 Jun 1999 19:51:16 -0700 Resent-Date: Wed, 9 Jun 1999 19:51:16 -0700 Date: Wed, 9 Jun 1999 19:50:41 -0700 (PDT) From: "Jon M. Taylor" To: GGI mailing list cc: tanner@ffii.org Subject: Massive GGIMesa update Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"HFENA1.0.d_4.YWoNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13273 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com First, all GGIMesa development has been moved to the experimental-1 Mesa CVS branch because that branch has been autoconfed by Thomas Tanner. This has resulted in such a dramatic improvement in my ability to make GGIMesa work like other GGI extension libs that I cannot do without it. In the three days since I switched to the experimental-1 branch, I have been able to implement essentially every GGIMesa feature I wanted. Thomas, you are a saint. You saved my life. Anyway, the new stuff is as follows: * Everything has been autoconf'ed as previously mentioned. All the hardcoded defaults should be gone, and all libs are built with libtool. * The display/ subsystem is up and running, finally. The only display target right now is display-fbdev-mesa, which is just a shell that loads the APIs (generic-stubs-mesa, generic-linear-xx-mesa, etc) properly. The lack of proper API management within the display target is the reason why I was having that problem with the generic APIs overloading the Savage4 accelerated API, and that is fixed too. * The default/ subsystem has been overhauled and extended. The generic-* APIs are pretty much unchanged, but a new genkgi API has been added which more or less serves the same function as the LibGGI genkgi API - to handle the KGIcon API as an extension of the fbdev target. Under genkgi we also have another level of extension, the 3D accelerated driver targets. Currently savage4/ is the only one, but it should be a snap to add targets for any other 3D accelerated KGI driver. Card-specific acceleration helperlibs can also be attached directly underneath the fbdev target itself, as the LibGGI fbdev target does for the fbdev MGA drivers. I just have a little cleanup work to do, and I'll be pretty much done with the GGIMesa upgrade. If the autconf stuff makes it into the stable tree for Mesa 3.1, so will all the new GGIMesa stuff. If not, I'll distribute tarballs/binaries myself to anyone who wants them until the next stable Mesa release comes out. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Thu Jun 10 01:22:38 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA11284 for ; Thu, 10 Jun 1999 01:22:37 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA30588; Wed, 9 Jun 1999 22:12:09 -0700 Resent-Date: Wed, 9 Jun 1999 22:12:09 -0700 Date: Thu, 10 Jun 1999 13:24:27 +0800 From: Steven Wong To: ggi-develop@eskimo.com Subject: Re: Game SDKs Message-ID: <19990610132427.A516@smarty.phoenixdown.net.au> Mail-Followup-To: ggi-develop@eskimo.com References: <199906092103.RAA03419@colossus.csl.mtu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199906092103.RAA03419@colossus.csl.mtu.edu>; from David L. Bilbey on Wed, Jun 09, 1999 at 05:03:25PM -0400 Resent-Message-ID: <"5C-Z92.0.dT7.caqNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13274 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, Jun 09, 1999 at 05:03:25PM -0400, David L. Bilbey wrote: > Which Game SDKs currently support the GGI target? Which plan to? I would > like to write a game for GGI, but I don't want to reinvent the (Game SDK) > wheel. > > Bilbey > > -- > "I wish somebody would invent a fruit that had no seeds, tasted delicious, > and would scream when you ate it." --Jack Handey As far as I know, there are no game libraries which have support for GGI. I only know of ones which *plan* to. As already stated, that includes Clanlib (http://www.clanlib.org/). There's also SDL (Simple DirectMedia Layer) which is a bit more low-level, last time I heard. You can check SDL out at the address: http://www.devolution.com/~slouken/SDL/. Again, SDL doesn't have GGI support (and nor does Clanlib last time I checked)... but both are intending to integrate it soon. After all, a game library isn't a game library at all without GGI :> -- .. Steven Wong (alias NoEscape) .. .. .. : E-Mail: swong@opera.iinet.net.au : HTTP: www.iinet.net.au/~swong/ : From ggi-develop-request@eskimo.com Thu Jun 10 04:32:06 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA12791 for ; Thu, 10 Jun 1999 04:32:05 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA07635; Thu, 10 Jun 1999 01:18:50 -0700 Resent-Date: Thu, 10 Jun 1999 01:18:50 -0700 Sender: jul@reliam.teaser.fr Message-ID: <375F9180.572B28EB@easter-eggs.fr> Date: Thu, 10 Jun 1999 12:20:48 +0200 From: Julien Tayon Organization: Easter-eggs X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.1 i686) X-Accept-Language: fr, en MIME-Version: 1.0 To: GGI developp , ggi kgi Subject: kgicon crash Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"yg12Y.0.-s1.cJtNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13275 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, I am actually trying to have a Colorgraphic Evolution card work. The problem is that KGIcon works as long I install the module with the option kgi_bpp=13 (hardware text mode) using fbset -depth X (with X!=13) will definitively crash the system, (sometimes corrupting the filesystem, or halting the machine) I would like to know how to resolve this problem / write a proper driver for my card. Here is joined a description of the box I am working on: Box's CPU: intel PIII distribution taste: debian distrib' flavor: slink kernel taste:2.2.1 kernel flavor: fb support and the different video mode loaded. Graphic taste: This PCI card consist of a PCI bridge and 4 CL-GD-5480 processor. At boot time linux sees the 1st chip of the card and works (under X) fine with it. It is compatible from VGA mode 3-0 It is compatible with the CL-GD-5446 each chip as 4MB under X it does not support 32-8-1 bpp mode it only supports 15-16-24 bpp mode the fbcon works fine since it diplays a penguin when I enable it. I red the cirrus doc in the readme.542X saying the this had been tested for a 5446 and worked fine. So I had the detect card utility recognize my card as a CL 542X, I From ggi-develop-request@eskimo.com Thu Jun 10 08:17:03 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA14224 for ; Thu, 10 Jun 1999 08:17:02 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA06611; Thu, 10 Jun 1999 05:05:50 -0700 Resent-Date: Thu, 10 Jun 1999 05:05:50 -0700 Date: Thu, 10 Jun 1999 07:53:18 -0400 (EDT) From: Leimy To: ggi-develop@eskimo.com Subject: Re: Game SDKs In-Reply-To: <19990610003800.A1344@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"50wlK2.0.nc1.KewNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13276 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com ClanBomber has a ggi selection at runtime. I beleive that they have support for GGI built in already. You need to have the developers sources for it though... dave > > Which Game SDKs currently support the GGI target? Which plan to? I would > > like to write a game for GGI, but I don't want to reinvent the (Game SDK) > > wheel. > > AFAIK the ClanLib people are working on a port ... any status updates ? > > I'd like to run Pingus :-) ... > > CU, Andy > > -- > = Andreas Beck | Email : = > > From ggi-develop-request@eskimo.com Thu Jun 10 08:23:36 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA14291 for ; Thu, 10 Jun 1999 08:23:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA07110; Thu, 10 Jun 1999 05:08:47 -0700 Resent-Date: Thu, 10 Jun 1999 05:08:47 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: Game SDKs Date: Thu, 10 Jun 1999 14:07:13 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <199906092103.RAA03419@colossus.csl.mtu.edu> MIME-Version: 1.0 Message-Id: <99061014101302.01278@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"R1iwn3.0.tk1.EhwNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13277 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David L. Bilbey´s crap from Mit, 09 Jun 1999: > Which Game SDKs currently support the GGI target? Which plan to? I would > like to write a game for GGI, but I don't want to reinvent the (Game SDK) > wheel. ClanLib supports GGI, bit depth and resolution is hardwired, but you can use it with DirectBuffer and non DirectBuffer targets. It runs very fast on a Voodoo card with mtrrs. Very slow on Xlib, because the only accelerated function we use right now is ggiDrawBox, but others will follow. What is the best hardware/software configuration to take advantage of these functions? Follow the links below, keep the great GGI work! -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Thu Jun 10 08:25:35 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA14320 for ; Thu, 10 Jun 1999 08:25:34 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA08335; Thu, 10 Jun 1999 05:14:24 -0700 Resent-Date: Thu, 10 Jun 1999 05:14:24 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: Game SDKs Date: Thu, 10 Jun 1999 14:15:09 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <19990610003800.A1344@rz.uni-duesseldorf.de> MIME-Version: 1.0 Message-Id: <99061014154603.01278@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"lXA0f3.0.w12.VmwNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13278 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck´s crap from Don, 10 Jun 1999: > > Which Game SDKs currently support the GGI target? Which plan to? I would > > like to write a game for GGI, but I don't want to reinvent the (Game SDK) > > wheel. > > AFAIK the ClanLib people are working on a port ... any status updates ? I implemented the mouse class, you can play pingus now on all targets supporting pingus´ resolution and 16 bit. > > I'd like to run Pingus :-) ... > > CU, Andy > > -- > = Andreas Beck | Email : = -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Thu Jun 10 10:48:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA17208 for ; Thu, 10 Jun 1999 10:48:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA24859; Thu, 10 Jun 1999 07:36:43 -0700 Resent-Date: Thu, 10 Jun 1999 07:36:43 -0700 X-envelope-info: Date: Thu, 10 Jun 1999 07:37:04 -0700 From: Aaron Van Couwenberghe To: ggi-develop@eskimo.com Subject: Re: Massive GGIMesa update Message-ID: <19990610073704.B301@awac.local.net> Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Jon M. Taylor on Wed, Jun 09, 1999 at 07:50:41PM -0700 Sender: Resent-Message-ID: <"n6aao3.0.-36.uryNt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13279 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, Jun 09, 1999 at 07:50:41PM -0700, Jon M. Taylor wrote: > First, all GGIMesa development has been moved to the experimental-1 > Mesa CVS branch because that branch has been autoconfed by Thomas Tanner. > This has resulted in such a dramatic improvement in my ability to make > GGIMesa work like other GGI extension libs that I cannot do without it. In > the three days since I switched to the experimental-1 branch, I have been > able to implement essentially every GGIMesa feature I wanted. Thomas, you > are a saint. You saved my life. Awesome. Anyway, I'm going to check out the CVS sources today and attempt to build some packages. If everything works, I'll upload them to master. -- ..Aaron Van Couwenberghe... ..vanco@sonic.net.. ..aaronv@debian.org.... Berlin: http://www.berlin-consortium.org Debian GNU/Linux: http://www.debian.org There are three kinds of people: those who can count, and those who can't. From ggi-develop-request@eskimo.com Thu Jun 10 12:56:14 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA20824 for ; Thu, 10 Jun 1999 12:56:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA18318; Thu, 10 Jun 1999 09:44:58 -0700 Resent-Date: Thu, 10 Jun 1999 09:44:58 -0700 From: Justin Cormack Message-Id: <199906101643.RAA32175@lobster.doc.ic.ac.uk> Subject: Re: Game SDKs To: ggi-develop@eskimo.com Date: Thu, 10 Jun 1999 17:43:39 +0100 (BST) In-Reply-To: <19990610132427.A516@smarty.phoenixdown.net.au> from "Steven Wong" at Jun 10, 1999 01:24:27 PM X-Mailer: ELM [version 2.5 PL0pre8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"3H5bt.0.CT4.6k-Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13280 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > On Wed, Jun 09, 1999 at 05:03:25PM -0400, David L. Bilbey wrote: > > Which Game SDKs currently support the GGI target? Which plan to? I would > > like to write a game for GGI, but I don't want to reinvent the (Game SDK) > > wheel. > > > > Bilbey > > > > -- > > "I wish somebody would invent a fruit that had no seeds, tasted delicious, > > and would scream when you ate it." --Jack Handey > > As far as I know, there are no game libraries which have support for GGI. I > only know of ones which *plan* to. As already stated, that includes Clanlib > (http://www.clanlib.org/). There's also SDL (Simple DirectMedia Layer) > which is a bit more low-level, last time I heard. You can check SDL out at > the address: http://www.devolution.com/~slouken/SDL/. Crystal space does have ggi support (if you want a 3D API) http://crystal.linuxgames.com/ It looks nice - having trouble building it though (egcs versions...) Justin From ggi-develop-request@eskimo.com Thu Jun 10 13:10:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA21036 for ; Thu, 10 Jun 1999 13:10:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA24826; Thu, 10 Jun 1999 09:59:26 -0700 Resent-Date: Thu, 10 Jun 1999 09:59:26 -0700 From: "David L. Bilbey" Message-Id: <199906101659.MAA12941@colossus.csl.mtu.edu> Subject: Re: Game SDKs To: ggi-develop@eskimo.com Date: Thu, 10 Jun 1999 12:59:17 -0400 (EDT) In-Reply-To: <199906101643.RAA32175@lobster.doc.ic.ac.uk> from "Justin Cormack" at Jun 10, 99 05:43:39 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"4JvJm.0.d36.jx-Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13281 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Thanks for the help everyone. It looks like I'm going to go with ClanLib after all. The latest version, which supports GGI according to the web site, was released today. Bilbey > > > > > On Wed, Jun 09, 1999 at 05:03:25PM -0400, David L. Bilbey wrote: > > > Which Game SDKs currently support the GGI target? Which plan to? I would > > > like to write a game for GGI, but I don't want to reinvent the (Game SDK) > > > wheel. > > > > > As far as I know, there are no game libraries which have support for GGI. I > > only know of ones which *plan* to. As already stated, that includes Clanlib > > (http://www.clanlib.org/). There's also SDL (Simple DirectMedia Layer) > > which is a bit more low-level, last time I heard. You can check SDL out at > > the address: http://www.devolution.com/~slouken/SDL/. > > Crystal space does have ggi support (if you want a 3D API) > > http://crystal.linuxgames.com/ -- "When I think of all the arguments Marta and I have had, I realize how silly most of them were. And it makes me wonder why she wanted to argue over such stupid things. I think I'll go ask her." --Jack Handey From ggi-develop-request@eskimo.com Thu Jun 10 14:09:33 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA22631 for ; Thu, 10 Jun 1999 14:09:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA22629; Thu, 10 Jun 1999 10:58:28 -0700 Resent-Date: Thu, 10 Jun 1999 10:58:28 -0700 Sender: e94_msu@e.kth.se Message-ID: <375FFCB6.8AB2A11A@stacken.kth.se> Date: Thu, 10 Jun 1999 19:58:14 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Game SDKs References: <199906092103.RAA03419@colossus.csl.mtu.edu> <99061014101302.01278@master> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"R8LTm1.0.9X5.1p_Nt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13282 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > > David L. Bilbey´s crap from Mit, 09 Jun 1999: > > Which Game SDKs currently support the GGI target? Which plan to? I would > > like to write a game for GGI, but I don't want to reinvent the (Game SDK) > > wheel. > > ClanLib supports GGI, bit depth and resolution is hardwired, but > you can use it with DirectBuffer and non DirectBuffer targets. > It runs very fast on a Voodoo card with mtrrs. > Very slow on Xlib, because the only accelerated function we use > right now is ggiDrawBox, but others will follow. > > What is the best hardware/software configuration to take advantage > of these functions? Best performance for LibGGI is currently without competition achieved with matroxfb and the fbdev target. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Thu Jun 10 17:40:53 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA28645 for ; Thu, 10 Jun 1999 17:40:51 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA21871; Thu, 10 Jun 1999 14:28:20 -0700 Resent-Date: Thu, 10 Jun 1999 14:28:20 -0700 Date: Thu, 10 Jun 1999 14:27:59 -0700 (PDT) From: "Jon M. Taylor" To: GGI mailing list Subject: generic-kgi renaming request Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"iSaOd2.0.dI5.Zt2Ot"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13283 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com GGIMesa's fbdev target piggybacks on top of LibGGI's fbdev target, and so does GGIMesa's genkgi helper on top of LibGGI's genkgi helper. The API names get a -mesa tacked on to them so that the piggybacking process takes place automatically. Very nice, very clean. There's only one problem: The LibGGI fbdev target uses "generic-kgicon" as its API name to use when loading the genkgi helper. However, unlike the LibGGI genkgi helper, the GGIMesa genkgi helper implements card-specific acceleration APIs, and as such we get things like tgt-fbdev-kgicon-generic-savage4-mesa which is confusing, as "kgicon-generic" implies the use of the KGIcon framework but no hardware accels. Can the fbdev API name for the genkgi helper be changed to just "kgicon" so I can use tgt-fbdev-kgicon-generic-mesa tgt-fbdev-kgicon-savage4-mesa ? Not a big deal either way, just a matter of namespace cleanliness. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Thu Jun 10 18:28:29 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA29965 for ; Thu, 10 Jun 1999 18:28:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA03328; Thu, 10 Jun 1999 15:17:07 -0700 Resent-Date: Thu, 10 Jun 1999 15:17:07 -0700 Sender: marcus@e.kth.se Message-ID: <37602EF7.5B68E304@stacken.kth.se> Date: Thu, 10 Jun 1999 21:32:39 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: ggiDrawHLine and ggiDrawVLine bugs? References: <19990609120603.A4665@ps.cus.umist.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"usb7v.0.jp.Wb3Ot"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13284 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Tristan Wibberley wrote: > > The display-x and display-xlib targets seem to behave differently when doing either > ggiDrawHLine or ggiDrawVLine, with display-xlib drawing lines one pixel longer. > > * display-x draws lines from the starting pixel up to, but not > including the starting pixel + length. > * display-xlib draws lines from the starting pixel up to, *and* > including the staing pixel + length. (ie, it's one pixel longer > than one would expect). > > start start+length > + + > display-x ################ > display-xlib ################# > > Should: > > XDrawLine(priv->xwin.x.display, priv->xwin.window, priv->xwin.x.gc, > x, y, x+w, y); > > in display/Xlib/hline.c be: > > XDrawLine(priv->xwin.x.display, priv->xwin.window, priv->xwin.x.gc, > x, y, x+w-1, y); > > Since the Xlib call takes start point and end point, not the point where > the line starts and number of pixels on the line. > > Is this actually happening? Am I imagining it? Is anything else affected > by differences in behaviour between LibGGI and Xlib? Just plain old bugs in the xlib target. ;) Thanks for finding those! Probably some leftovers from when I was messing with the clipping code a long time ago. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Thu Jun 10 22:28:01 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA04589 for ; Thu, 10 Jun 1999 22:28:00 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA31099; Thu, 10 Jun 1999 19:13:30 -0700 Resent-Date: Thu, 10 Jun 1999 19:13:30 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990611004209.C526@rz.uni-duesseldorf.de> Date: Fri, 11 Jun 1999 00:42:09 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: generic-kgi renaming request Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Jon M. Taylor on Thu, Jun 10, 1999 at 02:27:59PM -0700 Resent-Message-ID: <"euYUL3.0.Ab7.737Ot"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13285 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > There's only one problem: The LibGGI fbdev target uses > "generic-kgicon" as its API name to use when loading the genkgi helper. > However, unlike the LibGGI genkgi helper, the GGIMesa genkgi helper > implements card-specific acceleration APIs, and as such we get things like > tgt-fbdev-kgicon-generic-savage4-mesa I'll take care of that when I have some time (after the 22nd). I'll then as well get the suikgi target up again and make that stuff something like generic-kgicommand. Your card-specific stuff should usually be loaded by the "vendor" section. I'll take care of reimplementing that functionality. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Thu Jun 10 23:34:58 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA05784 for ; Thu, 10 Jun 1999 23:34:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA04918; Thu, 10 Jun 1999 20:22:47 -0700 Resent-Date: Thu, 10 Jun 1999 20:22:47 -0700 Sender: smaug@seqserv.seqnet.net Message-ID: <37607178.6B39F494@seqnet.net> Date: Thu, 10 Jun 1999 20:16:24 -0600 From: Sengan Baring-Gould X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.30 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: UDI-KGI status? References: <199904230922.LAA03634@shubashi.physik.tu-chemnitz.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"ubiAz.0.BC1.348Ot"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13286 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Steffen Seeger wrote: > Hello everybody, > > The responses: > Mark Evenson, mevenson@cup.hp.com wrote: > > I took a quick glance at the GGI web page, and it looks like the GGI > > work dovetails very well with what we're doing in UDI. We would like > > to include a display hardware driver specification in UDI, and would > > welcome working with you and your group to make that happen. > > Kurt Gollhardt, kdg@sco.com wrote: > > This is very good news! I had not been aware of the GGI project, but > > there has been a lot of interest in the idea of a standardized graphics > > driver interface that's come up in conjunction with UDI. I look forward > > to working with the GGI project to bring these technologies together. Hi Steffan/everybody else. I was wondering what's happened on this front (if anything) Thanks, Sengan From ggi-develop-request@eskimo.com Thu Jun 10 23:48:39 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA06107 for ; Thu, 10 Jun 1999 23:48:38 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA11112; Thu, 10 Jun 1999 20:35:47 -0700 Resent-Date: Thu, 10 Jun 1999 20:35:47 -0700 Date: Thu, 10 Jun 1999 20:35:42 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: generic-kgi renaming request In-Reply-To: <19990611004209.C526@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"39e_2.0.Qj2.IG8Ot"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13287 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 11 Jun 1999, Andreas Beck wrote: > > There's only one problem: The LibGGI fbdev target uses > > "generic-kgicon" as its API name to use when loading the genkgi helper. > > However, unlike the LibGGI genkgi helper, the GGIMesa genkgi helper > > implements card-specific acceleration APIs, and as such we get things like > > tgt-fbdev-kgicon-generic-savage4-mesa > > I'll take care of that when I have some time (after the 22nd). I'll then as > well get the suikgi target up again and make that stuff something like > generic-kgicommand. Don't worry about it, I worked around it by explicitly detecting the presence of a Savage4 in the mesa-genkgi dlinit() function. The mesa-genkgi getapi() function now only has one case to handle now - if a supported accel is detected, it loads the appropriate library. Otherwise it does nothing, since all the generic-* helpers have already been loaded by display-fbdev-mesa. > Your card-specific stuff should usually be loaded by the "vendor" section. > I'll take care of reimplementing that functionality. That would be cool. A separate vendor section would make the distribution of the mesa-fbdev-kgicon- libraries completely separable from GGIMesa as a whole. But, that will mean that _all_ the sublibs that load a .conf file will need to use ggLoadConfig() and friends on their own - currently, only the top-level extension code itself handles its own .conf file. All targets, helpers, etc which belong to that extension .include their .conf files into the top-level .conf (ggimesa.conf, etc). Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 11 00:49:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA06796 for ; Fri, 11 Jun 1999 00:49:15 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA08332; Thu, 10 Jun 1999 21:36:14 -0700 Resent-Date: Thu, 10 Jun 1999 21:36:14 -0700 Date: Thu, 10 Jun 1999 21:36:03 -0700 (PDT) From: "Jon M. Taylor" To: GGI mailing list Subject: Even yet still more GGIMesa updates Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"KXDTh.0.g12.u89Ot"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13288 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com New stuff: * GenKGI helper autodetects the presence of an accelerated KGI driver (Savage4 only for now) and loads the appropriate helper. * The fbdev now target piggybacks its accel-handling on top of the underlying LibGGI fbdev target's accel handling. * Huge directory-layout reorg. GGIMesa's directory structure now mimics that of LibGGI almost 100%. The only major difference is that LibGGI installs its sublib .conf files into the top-level etc/ggi/display directory, while GGIMesa puts everything but ggimesa.conf into etc/ggi/mesa/[display]. Everything should be nice and clean and in its proper place now. * Tons of misc bugfixes. This will probably be the last major GGIMesa structural update for a while. I have what I need to continue my Savage4 work without needing any ugly hacks that would affect other GGIMesa users/developers, the whole thing should be LibGGI 2.0 compliant, and all major features are in place. The only loose ends I see right now are: * The sublibs which use a .conf file should use LibGG to parse it themselves instead of .include'ing the .conf file in the top-level extension library's .conf file. I'm going to put this one on the shelf until Andy reimplements the vendor/ subsystem. * The GGIMesa genkgi helper is hardwired to autodetect the presence of a Savage4 only, no other KGI 3D accelerated drivers are probed for. If a Savage4 is not detected, the genkgi helper does nothing and generic-* libs are used. The KGI acceleration detection is an ugly hack and will need to be replaced with a general-purpose suggest-string parser at which point there are some other 3D accelerated KGI drivers in existence. Until then, this one goes on the shelf as well. * The GGIGLUT situation is a real mess. GLUT is (C) by Mark Kilgard, and although it is open-source, it is NOT redistributable with modifications. It isn't even in Mesa's CVS tree right now |-<. Based on this, I have doubts about the legality of GGIGLUT, because it must be linked to the rest of GLUT in order to function. Some talk about forming a free-GLUT project has been seen on the mesa-dev list, and of course GGI would be the best platform to base it upon, but since that would be a huge amount of work and QuakeIII doesn't use GLUT anyway, someone else will have to take this one on. In the meantime, building of ggiglut.c has been disabled in the Mesa automake system and will remain disabled until the situation is resolved. * A good chunk of Uwe's original GGIMesa code remains in some form, and that code is LGPLed. Since Mesa 3.1 is moving to a X-style license, this is technically a violation of the LPGL. I haven't had any luck in contacting Uwe, so I guess I will just not worry about it unless and until he complains. Enjoy the new GGIMesa, folx. Up next: The first Savage4 KGI/Mesa driver beta! I can't say exactly when this will be released, but it shouldn't be too much longer, now that all the necessary GGIMesa cleanups have been taken care of and I have a killer development environment to work within. Soon, all the world will know the true power of GGI.... Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 11 05:33:34 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA09028 for ; Fri, 11 Jun 1999 05:33:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA31591; Fri, 11 Jun 1999 02:19:52 -0700 Resent-Date: Fri, 11 Jun 1999 02:19:52 -0700 Date: Fri, 11 Jun 1999 02:26:59 -0700 (MST) From: teunis X-Sender: teunis@sigil.mauve.computersupportcentre.com To: Aaron Van Couwenberghe cc: ggi-develop@eskimo.com Subject: Re: Massive GGIMesa update In-Reply-To: <19990610073704.B301@awac.local.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"-exrc3.0.Gj7.gIDOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13289 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 10 Jun 1999, Aaron Van Couwenberghe wrote: > On Wed, Jun 09, 1999 at 07:50:41PM -0700, Jon M. Taylor wrote: > > First, all GGIMesa development has been moved to the experimental-1 > > Mesa CVS branch because that branch has been autoconfed by Thomas Tanner. > > This has resulted in such a dramatic improvement in my ability to make > > GGIMesa work like other GGI extension libs that I cannot do without it. In > > the three days since I switched to the experimental-1 branch, I have been > > able to implement essentially every GGIMesa feature I wanted. Thomas, you > > are a saint. You saved my life. > > Awesome. Anyway, I'm going to check out the CVS sources today and attempt > to build some packages. If everything works, I'll upload them to master. Okay fine. How do I check out the experimental-1 branch? I'm working on a bit of a package with Mesa/GGI and I'm finding bugs.. *sigh*.... Could be anything but I'm willing to check.... Anyone else got a 3DS reader that works? Mine's quite unstable so far.. I'm thinking of attacking VRML/2 next if I can't get 3D Studio files working 100%.... (anyone have a converter that dumps 3DS to VRML/2? :) Yes I'm working on a browser for GGI. Status: *grr*. Reads -some- 3DS files okay. Meshes need work. Collision detecting needs programming. Thinking of adding Visual Basic and/or Javascript but not sure yet. Definitely will go VRML/2 and HTTP/HTML-4 once system's stable. Multithreaded and prone to crashes still. Eats memory like it was written by microsoft (but thanks to a garbage collecter it -will- return it :) Incidentally, anyone know why ggiClose() exception-faults? The bit is: Program received signal SIGSEGV, Segmentation fault. 0x4032e5ba in giiClose (inp=0x4481bf24) at gii.c:702 702 _giiInputFree(curr->prev); I'm guessing there's a pointer prob here somewhere... but I haven't really studied the GII code all that much. yet. G'day, eh? :) - Teunis From ggi-develop-request@eskimo.com Fri Jun 11 08:21:38 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA10464 for ; Fri, 11 Jun 1999 08:21:38 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id FAA29225; Fri, 11 Jun 1999 05:07:33 -0700 (PDT) Resent-Date: Fri, 11 Jun 1999 05:07:33 -0700 (PDT) Date: Fri, 11 Jun 1999 07:52:35 -0400 (EDT) From: Leimy To: ggi-develop@eskimo.com Subject: Re: Game SDKs In-Reply-To: <375FFCB6.8AB2A11A@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"k63AV.0.y77.DlFOt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13290 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com My favorite Game SDK to this day is Allegro for DOS. There is a windows and Xwin port out there somewhere. It would be excellent to see a GGI port. Only because GGI is much faster than Xwin stuff. Anyway that is just a dream... From ggi-develop-request@eskimo.com Fri Jun 11 10:24:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA12859 for ; Fri, 11 Jun 1999 10:24:00 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA10369; Fri, 11 Jun 1999 07:09:28 -0700 Resent-Date: Fri, 11 Jun 1999 07:09:28 -0700 From: "David L. Bilbey" Message-Id: <199906111408.KAA29893@colossus.csl.mtu.edu> Subject: Re: Game SDKs To: ggi-develop@eskimo.com Date: Fri, 11 Jun 1999 10:08:54 -0400 (EDT) In-Reply-To: from "Leimy" at Jun 11, 99 07:52:35 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Zch3c2.0.5X2.DYHOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13291 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Actually, if you take a look at the Work in Progress section of the Allegro homepage, you'll see that it will probably be done. bilbey > > My favorite Game SDK to this day is Allegro for DOS. There is a windows > and Xwin port out there somewhere. It would be excellent to see a GGI > port. Only because GGI is much faster than Xwin stuff. > > > Anyway that is just a dream... > > -- "Probably the saddest thing you'll ever see is a mosquito sucking on a mummy. Forget it, little friend." --Jack Handey From ggi-develop-request@eskimo.com Fri Jun 11 10:29:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA12988 for ; Fri, 11 Jun 1999 10:29:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA10372; Fri, 11 Jun 1999 07:09:28 -0700 Resent-Date: Fri, 11 Jun 1999 07:09:28 -0700 X-envelope-info: Date: Fri, 11 Jun 1999 07:08:50 -0700 From: Aaron Van Couwenberghe To: ggi-develop@eskimo.com Subject: Re: Even yet still more GGIMesa updates Message-ID: <19990611070850.E556@awac.local.net> Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Jon M. Taylor on Thu, Jun 10, 1999 at 09:36:03PM -0700 Sender: Resent-Message-ID: <"AQxhI.0.kX2.NYHOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13292 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon - I can't upload Mesa CVS packages to master until the license issues have been resolved. When a license is illegal, we can't legally distribute the software ;) So, eh, for now these will eventually filter back to my homespace at my ISP. I'll let the list know when it happens. -- ..Aaron Van Couwenberghe... ..vanco@sonic.net.. ..aaronv@debian.org.... Berlin: http://www.berlin-consortium.org Debian GNU/Linux: http://www.debian.org There are three kinds of people: those who can count, and those who can't. From ggi-develop-request@eskimo.com Fri Jun 11 12:56:00 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA16732 for ; Fri, 11 Jun 1999 12:55:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA10397; Fri, 11 Jun 1999 09:40:15 -0700 Resent-Date: Fri, 11 Jun 1999 09:40:15 -0700 From: becka@rz.uni-duesseldorf.de Message-Id: <199906111639.SAA01999@zeus.rz.uni-duesseldorf.de> Subject: Re: Segfault in ggiClose() In-Reply-To: from teunis at "Jun 11, 99 02:26:59 am" To: ggi-develop@eskimo.com Date: Fri, 11 Jun 1999 18:39:05 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"_tSh51.0.5Y2.flJOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13293 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Incidentally, anyone know why ggiClose() exception-faults? > The bit is: > Program received signal SIGSEGV, Segmentation fault. > 0x4032e5ba in giiClose (inp=0x4481bf24) at gii.c:702 > 702 _giiInputFree(curr->prev); That's weird. There was a Bug in that area a while ago and it was fixed ... did it reappear ... ? What target ? CU, ANdy -- Andreas Beck | Email : From ggi-develop-request@eskimo.com Fri Jun 11 15:29:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA20737 for ; Fri, 11 Jun 1999 15:29:01 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA07259; Fri, 11 Jun 1999 12:17:56 -0700 Resent-Date: Fri, 11 Jun 1999 12:17:56 -0700 Date: Fri, 11 Jun 1999 12:24:40 -0700 (MST) From: teunis X-Sender: teunis@sigil.mauve.computersupportcentre.com To: ggi-develop@eskimo.com Subject: Re: Segfault in ggiClose() In-Reply-To: <199906111639.SAA01999@zeus.rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"fWsxK.0.1n1.W3MOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13294 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 11 Jun 1999 becka@rz.uni-duesseldorf.de wrote: > > > Incidentally, anyone know why ggiClose() exception-faults? > > The bit is: > > Program received signal SIGSEGV, Segmentation fault. > > 0x4032e5ba in giiClose (inp=0x4481bf24) at gii.c:702 > > 702 _giiInputFree(curr->prev); > > That's weird. There was a Bug in that area a while ago and it was fixed ... > did it reappear ... ? What target ? fbdev! I'm using Mesa/GGI if that affects anything... Incidentally, it doesn't occur in normal GGI proggies - could it be a prob with the Mesa extension? G'day, eh? :) - Teunis From ggi-develop-request@eskimo.com Fri Jun 11 15:37:23 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA20946 for ; Fri, 11 Jun 1999 15:37:22 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA10713; Fri, 11 Jun 1999 12:26:25 -0700 Resent-Date: Fri, 11 Jun 1999 12:26:25 -0700 Date: Fri, 11 Jun 1999 12:26:19 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: Even yet still more GGIMesa updates In-Reply-To: <19990611070850.E556@awac.local.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"TXkmo.0.4d2.WBMOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13295 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 11 Jun 1999, Aaron Van Couwenberghe wrote: > Jon - > > I can't upload Mesa CVS packages to master until the license issues > have been resolved. When a license is illegal, we can't legally distribute > the software ;) Sure. I'll try to get it all resolved ASAP. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 11 15:40:03 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA21028 for ; Fri, 11 Jun 1999 15:40:02 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA11547; Fri, 11 Jun 1999 12:28:34 -0700 Resent-Date: Fri, 11 Jun 1999 12:28:34 -0700 Date: Fri, 11 Jun 1999 12:28:30 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: Segfault in ggiClose() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"GL5sB3.0.Bq2.WDMOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13296 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 11 Jun 1999, teunis wrote: > On Fri, 11 Jun 1999 becka@rz.uni-duesseldorf.de wrote: > > > > > > Incidentally, anyone know why ggiClose() exception-faults? > > > The bit is: > > > Program received signal SIGSEGV, Segmentation fault. > > > 0x4032e5ba in giiClose (inp=0x4481bf24) at gii.c:702 > > > 702 _giiInputFree(curr->prev); > > > > That's weird. There was a Bug in that area a while ago and it was fixed ... > > did it reappear ... ? What target ? > > fbdev! > I'm using Mesa/GGI if that affects anything... Yes, it is probably a GGIMesa bug. > Incidentally, it doesn't occur in normal GGI proggies - could it be a prob > with the Mesa extension? I'm not seeing it here. Make sure you are using the latest LibGGI, LibGII and GGIMesa sources from CVS. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 11 15:40:44 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA21036 for ; Fri, 11 Jun 1999 15:40:41 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA11839; Fri, 11 Jun 1999 12:29:36 -0700 Resent-Date: Fri, 11 Jun 1999 12:29:36 -0700 Date: Fri, 11 Jun 1999 12:29:32 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: Massive GGIMesa update In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"lfFuQ.0.ju2.UEMOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13297 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 11 Jun 1999, teunis wrote: > On Thu, 10 Jun 1999, Aaron Van Couwenberghe wrote: > > > On Wed, Jun 09, 1999 at 07:50:41PM -0700, Jon M. Taylor wrote: > > > First, all GGIMesa development has been moved to the experimental-1 > > > Mesa CVS branch because that branch has been autoconfed by Thomas Tanner. > > > This has resulted in such a dramatic improvement in my ability to make > > > GGIMesa work like other GGI extension libs that I cannot do without it. In > > > the three days since I switched to the experimental-1 branch, I have been > > > able to implement essentially every GGIMesa feature I wanted. Thomas, you > > > are a saint. You saved my life. > > > > Awesome. Anyway, I'm going to check out the CVS sources today and attempt > > to build some packages. If everything works, I'll upload them to master. > > Okay fine. How do I check out the experimental-1 branch? Use the standard AnonCVS instructions, but add the 'rexperimental-1' flag to all cvs commands. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 11 15:55:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA21405 for ; Fri, 11 Jun 1999 15:55:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA16807; Fri, 11 Jun 1999 12:42:25 -0700 Resent-Date: Fri, 11 Jun 1999 12:42:25 -0700 Date: Fri, 11 Jun 1999 12:49:54 -0700 (MST) From: teunis X-Sender: teunis@sigil.mauve.computersupportcentre.com To: ggi-develop@eskimo.com Subject: Re: Segfault in ggiClose() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"mI_rp3.0.I64.VQMOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13298 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 11 Jun 1999, Jon M. Taylor wrote: > On Fri, 11 Jun 1999, teunis wrote: > > > On Fri, 11 Jun 1999 becka@rz.uni-duesseldorf.de wrote: > > > > > > > > > Incidentally, anyone know why ggiClose() exception-faults? > > > > The bit is: > > > > Program received signal SIGSEGV, Segmentation fault. > > > > 0x4032e5ba in giiClose (inp=0x4481bf24) at gii.c:702 > > > > 702 _giiInputFree(curr->prev); > > > > > > That's weird. There was a Bug in that area a while ago and it was fixed ... > > > did it reappear ... ? What target ? > > > > fbdev! > > I'm using Mesa/GGI if that affects anything... > > Yes, it is probably a GGIMesa bug. > > > Incidentally, it doesn't occur in normal GGI proggies - could it be a prob > > with the Mesa extension? > > I'm not seeing it here. Make sure you are using the latest LibGGI, > LibGII and GGIMesa sources from CVS. It's gone :) Latest GGIMesa CVS (main branch I have -no- idea how to access experimental-1 branch. Just found email on how to DL autoconf-branch so I'll try that next :) [have to patch main branch up quite a bit just to compile..] G'day, eh? :) - Teunis From ggi-develop-request@eskimo.com Fri Jun 11 16:48:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA22633 for ; Fri, 11 Jun 1999 16:48:25 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA00846; Fri, 11 Jun 1999 13:37:27 -0700 Resent-Date: Fri, 11 Jun 1999 13:37:27 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990611224053.A10974@rz.uni-duesseldorf.de> Date: Fri, 11 Jun 1999 22:40:53 +0200 From: Andreas Beck To: mailing list GGI Subject: ftp site perms fixed. Mail-Followup-To: mailing list GGI Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 Resent-Message-ID: <"SSKgu.0.uC.4ENOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13299 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com O.K. - I hopefully fixed the permission problems a few people encountered. Sorry - it was my fault. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Fri Jun 11 18:34:13 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA24718 for ; Fri, 11 Jun 1999 18:34:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA29706; Fri, 11 Jun 1999 15:22:22 -0700 Resent-Date: Fri, 11 Jun 1999 15:22:22 -0700 Sender: marcus@e.kth.se Message-ID: <37618BFC.54F94699@stacken.kth.se> Date: Fri, 11 Jun 1999 22:21:48 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Massive GGIMesa update References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"r_khI3.0.aC7.8mOOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13300 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com teunis wrote: > Incidentally, anyone know why ggiClose() exception-faults? > The bit is: > Program received signal SIGSEGV, Segmentation fault. > 0x4032e5ba in giiClose (inp=0x4481bf24) at gii.c:702 > 702 _giiInputFree(curr->prev); If you post the code causing that together with the GGI_DEBUG=255 output and a backtrace it may be possible to fix the problem. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Fri Jun 11 20:34:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA26403 for ; Fri, 11 Jun 1999 20:34:00 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA02735; Fri, 11 Jun 1999 17:22:48 -0700 Resent-Date: Fri, 11 Jun 1999 17:22:48 -0700 Date: Fri, 11 Jun 1999 20:21:23 -0400 (EDT) From: James Simmons X-Sender: jsimmons@elmwood.afterfive.com To: ggi-develop Subject: Re: [linux-fbdev] fbdev and video DMA'ing (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"RWOBi3.0.Vg.MXQOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13301 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I have been getting positive response on this. Possible kernel handling of accels. On Thu, 10 Jun 1999, Jeff Garzik wrote: > On Thu, 10 Jun 1999, James Simmons wrote: > > On Fri, 4 Jun 1999, Jeff Garzik wrote: > > > > > Everyone seems to be in general agreement that the only addition the > > > kernel needs, in order to support 3D, is a generic DMA hook into > > > userspace. > > > > I disagree. Personally I think no 3d stuff should go into fb. It should be > > its own driver. > > >From what I understand about the Precision Insight work, all that is > needed from the kernel is a hook to allow access to DMA from userspace. > The X server will take care of the rest, talking directly with the card > when it needs to. > This is true if the X servers from Precision Insight are going to be the only ones using the acceleration engines on cards. What about MESA? MESA-GGI mmaps the MMIO of /dev/fb and uses it. What if you do this from X windows, especially the ones from Precision, which will also try to use the accel engine at the same time as MESA. Also what about TNT and Creative cards which are going with writing their own drivers for MESA instead of going with Precision Insight. How are MESA and X going to tell each other on how when they are going to use the accel engine. > Given that, in order to keep them from stepping on each other, the DMA > driver and the framebuffer driver should know about each other. What > if, for example, matroxfb uses screen RAM (left unused by the fb) for > some caching. If the X server wants that same area of memory for > something else, you have problems. Thats right. Also you will have problems when you try to write to the framebuffer and use the accel engine. For alot of cards its use one or the other at a time. Yes /dev/fb will have to work with something to regulate the accel engine. I believe that /dev/gfx would be the best solution. This way you could regulate the accel engine between applications. Having each application seeing what other applications are using the accel engine is going to be a major preformance hit. Plus if they don't your going to lock up the machine. A good example of this is XF86_SVGA with maxtorfb. One out of ten times it locks my machine and even SAK doesn't work. I know its the X server trying to write to the framebuffer as well as the accel engine. This is in the same program. What do you think would happen when its a external program that does this? > I just think that if the X server is going to be DMA'ing to my video > card, my video driver should know about it at least. Agree. It needs to know about any hardware accel access as well. But put this in the hands of another driver instaed of /dev/fb. From ggi-develop-request@eskimo.com Sat Jun 12 09:18:54 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA02440 for ; Sat, 12 Jun 1999 09:18:53 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA04663; Sat, 12 Jun 1999 06:07:00 -0700 Resent-Date: Sat, 12 Jun 1999 06:07:00 -0700 Message-ID: <19990612133542.A5872@sbbs.se> Date: Sat, 12 Jun 1999 13:35:42 +0200 From: =?iso-8859-1?Q?Jonas_Borgstr=F6m?= To: ggi-develop@eskimo.com Subject: ANNOUNCE - URBAN 1.5.0 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93i X-Operating-System: Linux bengburken 2.2.5 Resent-Message-ID: <"81eq13.0.W81.ijbOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13302 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, all! This is off topic, but, I have ported a dos game I've been working on to Linux/libggi. It is a nice shoot-'em-up game for linux and dos. ***** Warning, this game contains lots of blood and gore. ***** :) You will find it at http://urban.home.dhs.org It's GPL of cource. Just download and play! / Jonas -- -------------------------------------------------------- Jonas Borgström U.R.B.A.N http://urban.home.dhs.org ZipCracker http://www.c5.org/zipcracker GGI-Project http://www.ggi-project.org -------------------------------------------------------- From ggi-develop-request@eskimo.com Sun Jun 13 07:23:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA11434 for ; Sun, 13 Jun 1999 07:23:00 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA08797; Sun, 13 Jun 1999 04:07:27 -0700 Resent-Date: Sun, 13 Jun 1999 04:07:27 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: KGI-0.9 driver interface released Date: Sun, 13 Jun 1999 13:06:32 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <199906071144.NAA09397@demonti.physik.tu-chemnitz.de> MIME-Version: 1.0 Message-Id: <99061313082101.21964@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"A8f5w2.0.C52.O3vOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13303 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Steffen Seeger´s crap from Mon, 07 Jun 1999: > Hello, > > this is just to announce (separately from the kgi-0.9-990607 snapshot) I downloaded it, but there are only patches for kernel 2.2.4 or below. I use 2.3.6, would be nice to have working patches. When I got this working I want to start rewriting the TNT driver. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Sun Jun 13 08:15:54 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA11737 for ; Sun, 13 Jun 1999 08:15:53 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA19575; Sun, 13 Jun 1999 05:04:24 -0700 Resent-Date: Sun, 13 Jun 1999 05:04:24 -0700 Date: Sun, 13 Jun 1999 14:04:17 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: GGI Problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"KBLTl2.0.bn4.6vvOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13304 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi. I'm done with my exams now, so I'm going to start bothering you all again :) I have: libggi-2.0b2.1 libgii-0.6 svgalib4ggi-0.6 Matrox Millenium I /etc/fb0 kernel 2.2.9 homemade /etc/fb.modes I'm trying to run an SVGALib program using the GGI SVGALib wrapper. It didn't work, and I was getting some strange errors, so I tried with GGI_DEBUG=255... The following things I had some trouble with: I'm getting a couple of lines saying eg: LibGGI: display-fbdev: setmode 80x30#80x30F1[0x1001004] LibGGI: display-fbdev: cannot get timing from /etc/fb.modes. Just hoping it works. I'm assuming this means it is checking what mode it is in to save it until the running program is done. But I thought I was running 640x480x8? Anyway, the above says a couple of times, but one time I'm getting LibGGI: display-fbdev: checkmode 0x0#0x0F0[0x1001004] LibGGI: display-fbdev: result 0 80x30#80x30F1[0x1001004] LibGGI: display-fbdev: setmode 80x30#80x30F1[0x1001004] LibGGI: display-fbdev: cannot get timing from /etc/fb.modes. Just hoping it works. display-fbdev: FBIOPUT_VSCREENINFO: Invalid argument LibGGI: Failed to set mode: [T4/16] LibGGI: ggiSetMode: done! What is mode [T4/16]? Also, I'm getting something like: LibGGI: ggiCheckMode(0x81915f8, 0xbfffe868) called LibGGI: display-fbdev: checkmode 320x200#320x200F1[0x4000808] LibGGI: display-fbdev: result 0 320x200#320x200F1[0x4000808] LibGGI: display-fbdev: setmode 320x200#320x200F1[0x4000808] LibGGI: display-fbdev: virtual doesn't match for timing. Hope this doesn't matter. Now, I'm suspecting that this has something to do with the modes I've been setting in /etc/fb.modes. For some reason, I can't seem to be able to make the virtual and the physical screen-size the same. I'm setting eg. 'fbset -g 320 200 320 200 8 -t etc...', but the virtual turns out to be 640x200 anyway. Is this a known thing? I've had some trouble with this before, with the virtual size eating up the memory from the screen-resolution I want. Finally I'm getting: LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8] Terminating on signal 11 LibGGI: display-fbdev: GGIdlcleanup start. What happened here? TIA :) Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Sun Jun 13 08:43:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA11842 for ; Sun, 13 Jun 1999 08:43:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA21171; Sun, 13 Jun 1999 05:30:52 -0700 Resent-Date: Sun, 13 Jun 1999 05:30:52 -0700 Date: Sun, 13 Jun 1999 14:30:47 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: palemu target? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"0VIW42.0.bA5.wHwOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13305 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi. I tried running an svgalib-program in X with GGI_DISPLAY=palemu. That resulted in: LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8] Segmentation fault (core dumped) Of course, for all I know this could be the program dying for some reason. Is it? :) Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Sun Jun 13 09:27:29 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA12080 for ; Sun, 13 Jun 1999 09:27:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA27319; Sun, 13 Jun 1999 06:15:00 -0700 Resent-Date: Sun, 13 Jun 1999 06:15:00 -0700 From: Andrew Apted Message-ID: <19990613232012.45862@ajax.netspace.net.au> Date: Sun, 13 Jun 1999 23:20:12 +1000 To: ggi-develop@eskimo.com Subject: Re: GGI Problems Reply-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Ketil Froyn on Sun, Jun 13, 1999 at 02:04:17PM +0200 Resent-Message-ID: <"ymppW2.0.dg6.JxwOt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13306 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn writes: > LibGGI: display-fbdev: checkmode 0x0#0x0F0[0x1001004] > LibGGI: display-fbdev: result 0 80x30#80x30F1[0x1001004] > LibGGI: display-fbdev: setmode 80x30#80x30F1[0x1001004] > LibGGI: display-fbdev: cannot get timing from /etc/fb.modes. Just hoping > it works. > display-fbdev: FBIOPUT_VSCREENINFO: Invalid argument > LibGGI: Failed to set mode: [T4/16] > LibGGI: ggiSetMode: done! > > What is mode [T4/16]? Text mode (4 bits of color, 16 bit "pixels"). Normal fbdev drivers in the kernel can't do text modes, because there is no API for setting different types of modes (only different bit depths). [For KGICON, we use a massive hack where bpp=13 means text mode]. What's the program ? > Finally I'm getting: > LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8] > Terminating on signal 11 > LibGGI: display-fbdev: GGIdlcleanup start. > > What happened here? Something bad :). Most likely either the svgalib-wrapper or the program in question tried to draw outside the mmap'ed framebuffer. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Sun Jun 13 09:28:46 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA12085 for ; Sun, 13 Jun 1999 09:28:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA27957; Sun, 13 Jun 1999 06:17:26 -0700 Resent-Date: Sun, 13 Jun 1999 06:17:26 -0700 From: Andrew Apted Message-ID: <19990613232239.40350@ajax.netspace.net.au> Date: Sun, 13 Jun 1999 23:22:39 +1000 To: ggi-develop@eskimo.com Subject: Re: palemu target? Reply-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Ketil Froyn on Sun, Jun 13, 1999 at 02:30:47PM +0200 Resent-Message-ID: <"3Hn5K2.0.Zq6.azwOt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13307 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn writes: > I tried running an svgalib-program in X with GGI_DISPLAY=palemu. That > resulted in: > LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8] > Segmentation fault (core dumped) > > Of course, for all I know this could be the program dying for some reason. > Is it? :) I hope not :). Please try running some normal libggi demos with GGI_DISPLAY=palemu and see if they work. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Sun Jun 13 11:37:39 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA13175 for ; Sun, 13 Jun 1999 11:37:38 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA16890; Sun, 13 Jun 1999 08:26:52 -0700 Resent-Date: Sun, 13 Jun 1999 08:26:52 -0700 From: Steffen Seeger Message-Id: <199906131526.RAA31471@demonti.physik.tu-chemnitz.de> Subject: Re: UDI-KGI status? In-Reply-To: <37607178.6B39F494@seqnet.net> from Sengan Baring-Gould at "Jun 10, 99 08:16:24 pm" To: ggi-develop@eskimo.com Date: Sun, 13 Jun 1999 17:26:34 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"_I98n3.0.Y74.rsyOt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13308 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Steffen Seeger wrote: > > > Hello everybody, > > > > The responses: > > Mark Evenson, mevenson@cup.hp.com wrote: > > > I took a quick glance at the GGI web page, and it looks like the GGI > > > work dovetails very well with what we're doing in UDI. We would like > > > to include a display hardware driver specification in UDI, and would > > > welcome working with you and your group to make that happen. > > > > Kurt Gollhardt, kdg@sco.com wrote: > > > This is very good news! I had not been aware of the GGI project, but > > > there has been a lot of interest in the idea of a standardized graphics > > > driver interface that's come up in conjunction with UDI. I look forward > > > to working with the GGI project to bring these technologies together. > > Hi Steffan/everybody else. > > I was wondering what's happened on this front (if anything) > > Thanks, > > Sengan A lot. I am participating in the UDI phone conferences and stay in close contact with the UDI people. I have restructured the drivers to allow for a hopefully easy merge later, adopting the UDI driver model as good as possible. The drivers in the last KGI snapshot is the result of this. Also, the UDI people are checking the particular needs of performant graphics hardware driver can be satisfied with the UDI-1.0 spec. So, it's going on, but not really code to show yet, except for the driver released from my side. Steffen ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- ------------- The GGI Project: http://www.ggi-project.org ------------- From ggi-develop-request@eskimo.com Sun Jun 13 12:57:24 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA13785 for ; Sun, 13 Jun 1999 12:57:23 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA08705; Sun, 13 Jun 1999 09:46:17 -0700 Resent-Date: Sun, 13 Jun 1999 09:46:17 -0700 Date: Sun, 13 Jun 1999 18:46:09 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: palemu target? In-Reply-To: <19990613232239.40350@ajax.netspace.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"9ju_c1.0.p72.N1-Ot"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13309 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sun, 13 Jun 1999, Andrew Apted wrote: > > Of course, for all I know this could be the program dying for some reason. > > Is it? :) > I hope not :). Please try running some normal libggi demos with > GGI_DISPLAY=palemu and see if they work. No, that didn't work. The program needs 8 bpp, and my X server is 16. Of course, I could try my X server in 8... I'll try :) Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Sun Jun 13 12:59:51 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA13805 for ; Sun, 13 Jun 1999 12:59:50 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA09520; Sun, 13 Jun 1999 09:48:55 -0700 Resent-Date: Sun, 13 Jun 1999 09:48:55 -0700 Date: Sun, 13 Jun 1999 18:48:33 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: GGI Problems In-Reply-To: <19990613232012.45862@ajax.netspace.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"rOXt73.0.WK2.r3-Ot"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13310 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sun, 13 Jun 1999, Andrew Apted wrote: > > What is mode [T4/16]? > Text mode (4 bits of color, 16 bit "pixels"). Normal fbdev drivers in > the kernel can't do text modes, because there is no API for setting > different types of modes (only different bit depths). [For KGICON, we > use a massive hack where bpp=13 means text mode]. > What's the program ? The program is a SNES emulator :) It really sucks in a window under X (gotta be fullscreen) :> > > Finally I'm getting: > > LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8] > > Terminating on signal 11 > > LibGGI: display-fbdev: GGIdlcleanup start. > > What happened here? > Something bad :). Most likely either the svgalib-wrapper or the program > in question tried to draw outside the mmap'ed framebuffer. So it wasn't just that it failed trying to set the mode? Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Sun Jun 13 16:51:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA16017 for ; Sun, 13 Jun 1999 16:51:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA06711; Sun, 13 Jun 1999 13:39:17 -0700 Resent-Date: Sun, 13 Jun 1999 13:39:17 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990613211303.B1309@rz.uni-duesseldorf.de> Date: Sun, 13 Jun 1999 21:13:03 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGI Problems Mail-Followup-To: ggi-develop@eskimo.com References: <19990613232012.45862@ajax.netspace.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Ketil Froyn on Sun, Jun 13, 1999 at 06:48:33PM +0200 Resent-Message-ID: <"IqRFG2.0.Td1.mR1Pt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13311 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > The program is a SNES emulator :) It really sucks in a window under X > (gotta be fullscreen) :> Tried using it under DGA ? Humm - no, if it's the problem I think it is, that won't help ... > > > LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8] > > > Terminating on signal 11 > > > LibGGI: display-fbdev: GGIdlcleanup start. > So it wasn't just that it failed trying to set the mode? Don't think so. LibGGI would have placed more complaints there I'd say. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sun Jun 13 16:51:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA16034 for ; Sun, 13 Jun 1999 16:51:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA06676; Sun, 13 Jun 1999 13:39:16 -0700 Resent-Date: Sun, 13 Jun 1999 13:39:16 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990613210712.A1309@rz.uni-duesseldorf.de> Date: Sun, 13 Jun 1999 21:07:12 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGI Problems Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Ketil Froyn on Sun, Jun 13, 1999 at 02:04:17PM +0200 Resent-Message-ID: <"lr_PM1.0.ud1.oR1Pt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13312 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi ! > I have: > libggi-2.0b2.1 > libgii-0.6 > svgalib4ggi-0.6 > Matrox Millenium I > /etc/fb0 > kernel 2.2.9 > homemade /etc/fb.modes GREAT !!! Finally someone who gives a complete summary of his setup ! > I'm trying to run an SVGALib program using the GGI SVGALib wrapper. It > didn't work, and I was getting some strange errors, so I tried with > GGI_DEBUG=255... The following things I had some trouble with: > I'm getting a couple of lines saying eg: > LibGGI: display-fbdev: setmode 80x30#80x30F1[0x1001004] > LibGGI: display-fbdev: cannot get timing from /etc/fb.modes. Just hoping > it works. > > I'm assuming this means it is checking what mode it is in to save it until > the running program is done. But I thought I was running 640x480x8? > Anyway, the above says a couple of times, but one time I'm getting That is very probably SVGAlib doing some strange check about the previous resolution. It probably doesn't believe it is started from a graphics mode. 640x480 at a font size of 8x16 gives 80x30 BTW. > LibGGI: display-fbdev: checkmode 0x0#0x0F0[0x1001004] > LibGGI: display-fbdev: result 0 80x30#80x30F1[0x1001004] > LibGGI: display-fbdev: setmode 80x30#80x30F1[0x1001004] > LibGGI: display-fbdev: cannot get timing from /etc/fb.modes. Just hoping > it works. > display-fbdev: FBIOPUT_VSCREENINFO: Invalid argument > LibGGI: Failed to set mode: [T4/16] > LibGGI: ggiSetMode: done! > What is mode [T4/16]? Andrew already answered that. IBM-style Textmode. > LibGGI: ggiCheckMode(0x81915f8, 0xbfffe868) called > LibGGI: display-fbdev: checkmode 320x200#320x200F1[0x4000808] > LibGGI: display-fbdev: result 0 320x200#320x200F1[0x4000808] > LibGGI: display-fbdev: setmode 320x200#320x200F1[0x4000808] > LibGGI: display-fbdev: virtual doesn't match for timing. Hope this doesn't > matter. > Now, I'm suspecting that this has something to do with the modes I've been > setting in /etc/fb.modes. For some reason, I can't seem to be able to make > the virtual and the physical screen-size the same. I'm setting eg. > 'fbset -g 320 200 320 200 8 -t etc...', but the virtual turns out to be > 640x200 anyway. Is this a known thing? I suppose it is a problem with the Matrox accel engine. Many current cards do not support 320x200 anymore when they have been taken out of VGA-compatibility mode. You can often still make a 320x200 picture, as the timing logic is usually separate from the accel logic, but you need to use a higher virtual size. > LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8] > Terminating on signal 11 > LibGGI: display-fbdev: GGIdlcleanup start. I suppose "something" believes it has set 320x200 with a virtual width of 320 and thus only maps 64k of vidmem. However the real virtual is 640 which "something else" then uses and thus hits unmapped memory. We'll need some extra info to figure that out. An strace dump would help, as would a GDB backtrace of the fault. Also try, if it works on other display targets, like e.g. X (or, as your other mail suggests this might be problematic) memory. Those should not suffer from the 320x200 not quite possible effect. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sun Jun 13 18:57:06 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA17661 for ; Sun, 13 Jun 1999 18:57:05 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA02046; Sun, 13 Jun 1999 15:43:49 -0700 Resent-Date: Sun, 13 Jun 1999 15:43:49 -0700 Date: Mon, 14 Jun 1999 00:43:44 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: GGI Problems In-Reply-To: <19990613210712.A1309@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"wtCbf2.0.mV.ZG3Pt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13313 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ach, the stupid program does an iopl(), and dies anyway when I run as root. Never mind, sorry to have bothered you :) I'll try to find a working svgalib program next time. :) PS: I don't have too much of a clue, but I'm assuming this doesn't have anything to do with ggi: (from strace when the program was run as root) ... gettimeofday({929313350, 245374}, NULL) = 0 gettimeofday({929313350, 245707}, NULL) = 0 gettimeofday({929313350, 246039}, NULL) = 0 --- SIGALRM (Alarm clock) --- ioctl(-1, SNDCTL_DSP_GETOSPACE, 0xbfffeb8c) = -1 EBADF (Bad file descriptor) sigreturn() = ? (mask now []) --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Sun Jun 13 20:53:29 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA18430 for ; Sun, 13 Jun 1999 20:53:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA01012; Sun, 13 Jun 1999 17:40:55 -0700 Resent-Date: Sun, 13 Jun 1999 17:40:55 -0700 Date: Sun, 13 Jun 1999 20:40:52 -0400 (EDT) From: Garrett Robert Banuk To: ggi-develop@eskimo.com Subject: GGI won't configure Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"PEchg1.0.YF.M-4Pt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13314 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com No matter what I do to configure GGI I always get this message at the end of configuring. LibGII is not properly installed on the system. You need LibGII for building LibGGI. Please compile LibGII first. I did all the default things to install GII configure/make/make install I checked the dynamic linkers search path and everything. Has this happened to anyone else? Im using SuSe6.1 btw From ggi-develop-request@eskimo.com Mon Jun 14 02:36:54 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id CAA21329 for ; Mon, 14 Jun 1999 02:36:53 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA30550; Sun, 13 Jun 1999 23:22:34 -0700 Resent-Date: Sun, 13 Jun 1999 23:22:34 -0700 Sender: marcus@e.kth.se Message-ID: <37649F9C.238BAACD@stacken.kth.se> Date: Mon, 14 Jun 1999 06:22:20 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: palemu target? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"COdun1.0.bS7.Y-9Pt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13315 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn wrote: > > Hi. > I tried running an svgalib-program in X with GGI_DISPLAY=palemu. That > resulted in: > LibGGI SVGAlib-wrapper: 320x200.V320x200.F1.D1x1.[P8/8] > Segmentation fault (core dumped) Why would you want to use palemu with the SVGAlib wrapper? Use GSW_MODEEMU and GSW_PAGEEMU instead. In any case SVGAlib mode 320x200x256 requires a DirectBuffer which the *emu targets doesn't provide. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Mon Jun 14 02:37:33 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id CAA21334 for ; Mon, 14 Jun 1999 02:37:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA30693; Sun, 13 Jun 1999 23:24:01 -0700 Resent-Date: Sun, 13 Jun 1999 23:24:01 -0700 Sender: marcus@e.kth.se Message-ID: <37649FF9.782C6EB7@stacken.kth.se> Date: Mon, 14 Jun 1999 06:23:53 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: GGI won't configure References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"H9Yj82.0.MV7.__9Pt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13316 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett Robert Banuk wrote: > > No matter what I do to configure GGI I always get this message at the end > of configuring. > > LibGII is not properly installed on the system. You need LibGII for > building LibGGI. Please compile LibGII first. > > I did all the default things to install GII configure/make/make install I > checked the dynamic linkers search path and everything. Has this > happened to anyone else? Im using SuSe6.1 btw Did you remove config.cache between your configure retries? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Mon Jun 14 02:45:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id CAA21376 for ; Mon, 14 Jun 1999 02:45:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA32350; Sun, 13 Jun 1999 23:33:10 -0700 Resent-Date: Sun, 13 Jun 1999 23:33:10 -0700 Sender: marcus@e.kth.se Message-ID: <3764A220.7C09AA48@stacken.kth.se> Date: Mon, 14 Jun 1999 06:33:04 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: GGI Problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"tM3982.0.Fv7.b8APt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13317 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn wrote: > > Ach, the stupid program does an iopl(), and dies anyway when I run as > root. Never mind, sorry to have bothered you :) I'll try to find a working > svgalib program next time. :) > > PS: I don't have too much of a clue, but I'm assuming this doesn't have > anything to do with ggi: > (from strace when the program was run as root) > ... > gettimeofday({929313350, 245374}, NULL) = 0 > gettimeofday({929313350, 245707}, NULL) = 0 > gettimeofday({929313350, 246039}, NULL) = 0 > --- SIGALRM (Alarm clock) --- > ioctl(-1, SNDCTL_DSP_GETOSPACE, 0xbfffeb8c) = -1 EBADF (Bad file descriptor) > sigreturn() = ? (mask now []) > --- SIGSEGV (Segmentation fault) --- > +++ killed by SIGSEGV +++ Nope it doesn't (have anything to do with ggi). This is what happens when people don't check their return codes. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Mon Jun 14 03:52:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA21740 for ; Mon, 14 Jun 1999 03:52:23 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA11705; Mon, 14 Jun 1999 00:39:21 -0700 Resent-Date: Mon, 14 Jun 1999 00:39:21 -0700 From: Garrett B To: ggi-develop@eskimo.com Subject: Re: GGI won't configure Date: Mon, 14 Jun 1999 03:11:41 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99061403375600.06518@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"y4luf3.0.Ws2.a6BPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13318 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Well I deleted the configure.cache file and GGI doesn't seem to report the error any more when I configure it. Now when I try to run the cube3d demo, it starts up with the blinking square with the text in the center saying what the controls are. But it doesn't go anywhere past there and I have to kill it. Any idea whats wrong? From ggi-develop-request@eskimo.com Mon Jun 14 04:11:40 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA21867 for ; Mon, 14 Jun 1999 04:11:37 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id BAA17239; Mon, 14 Jun 1999 01:00:16 -0700 (PDT) Resent-Date: Mon, 14 Jun 1999 01:00:16 -0700 (PDT) From: Steffen Seeger Message-Id: <199906140755.JAA01826@demonti.physik.tu-chemnitz.de> Subject: Re: KGI-0.9 driver interface released In-Reply-To: <99061313082101.21964@master> from Denis Oliver Kropp at "Jun 13, 99 01:06:32 pm" To: ggi-develop@eskimo.com Date: Mon, 14 Jun 1999 09:55:04 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"dQ7p82.0.lC4.TPBPt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13319 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Steffen Seeger´s crap from Mon, 07 Jun 1999: > > Hello, > > > > this is just to announce (separately from the kgi-0.9-990607 snapshot) > > I downloaded it, but there are only patches for kernel 2.2.4 or below. > I use 2.3.6, would be nice to have working patches. I will not support 2.3 kernels in the forseeable future, simply because I don't have the time to do it. 2.2 is stable enough, and there are no significant enhancements (yet) to prefer 2.3 over 2.2. If you want to do it, go ahead, I won't stop you. > When I got this working I want to start rewriting the TNT driver. Why do you need 2.3 for that? Steffen ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- From ggi-develop-request@eskimo.com Mon Jun 14 05:04:24 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA22156 for ; Mon, 14 Jun 1999 05:04:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA29978; Mon, 14 Jun 1999 01:49:19 -0700 Resent-Date: Mon, 14 Jun 1999 01:49:19 -0700 Date: Mon, 14 Jun 1999 10:48:59 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: palemu target? In-Reply-To: <37649F9C.238BAACD@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"NmjoX1.0.CK7.98CPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13320 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Mon, 14 Jun 1999, Marcus Sundberg wrote: > Why would you want to use palemu with the SVGAlib wrapper? > Use GSW_MODEEMU and GSW_PAGEEMU instead. > In any case SVGAlib mode 320x200x256 requires a DirectBuffer which > the *emu targets doesn't provide. Erm... Was I supposed to figure that out all by myself? :D Anyway, thanks. Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Mon Jun 14 05:41:29 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA22353 for ; Mon, 14 Jun 1999 05:41:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA04059; Mon, 14 Jun 1999 02:27:27 -0700 Resent-Date: Mon, 14 Jun 1999 02:27:27 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: KGI-0.9 driver interface released Date: Mon, 14 Jun 1999 11:22:20 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <199906140755.JAA01826@demonti.physik.tu-chemnitz.de> MIME-Version: 1.0 Message-Id: <99061411275401.10435@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"kQ02E1.0.A_.zhCPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13321 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Steffen Seeger´s crap from Mon, 14 Jun 1999: > I will not support 2.3 kernels in the forseeable future, simply because I don't > have the time to do it. 2.2 is stable enough, and there are no significant > enhancements (yet) to prefer 2.3 over 2.2. You are right, but are the PIIX enhancements already in 2.2? > If you want to do it, go ahead, I won't stop you. I tried the 2.2.4 patch it stops at keyboard.h hunk #10. I don´t know much about the kernel inside. > > When I got this working I want to start rewriting the TNT driver. > > Why do you need 2.3 for that? Ask my insane brain that always wants to sit on the bleeding edge ;.) Ok, then I have to ask: Can I use the 2.2.4 patch for the 2.2.9? Btw: I have a Matrox Mystique next to my TNT. I added FBIO_ACCEL_COPYBOX and FBIO_ACCEL_FILLRECT to fb.h, implemented it in matroxfb.c and it worked, but nobody wants that ;-( -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Mon Jun 14 10:02:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA25423 for ; Mon, 14 Jun 1999 10:02:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA19633; Mon, 14 Jun 1999 06:44:57 -0700 Resent-Date: Mon, 14 Jun 1999 06:44:57 -0700 From: Andrew Apted Message-ID: <19990614184430.15575@ajax.netspace.net.au> Date: Mon, 14 Jun 1999 18:44:30 +1000 To: ggi-develop@eskimo.com Subject: Re: palemu target? Reply-To: ggi-develop@eskimo.com References: <19990613232239.40350@ajax.netspace.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Ketil Froyn on Sun, Jun 13, 1999 at 06:46:09PM +0200 Resent-Message-ID: <"khf843.0.8o4._SGPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13323 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn writes: > No, that didn't work. The program needs 8 bpp, and my X server is 16. Of > course, I could try my X server in 8... I'll try :) Oh yeah, I forget to mention that palemu & trueemu don't provide a DirectBuffer, so any program that must have direct access to a framebuffer won't work (perhaps the svgalib-wrapper needs that ? I don't know). Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Mon Jun 14 10:10:00 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA25562 for ; Mon, 14 Jun 1999 10:09:58 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA19627; Mon, 14 Jun 1999 06:44:53 -0700 Resent-Date: Mon, 14 Jun 1999 06:44:53 -0700 From: Andrew Apted Message-ID: <19990614183817.03191@ajax.netspace.net.au> Date: Mon, 14 Jun 1999 18:38:17 +1000 To: ggi-develop@eskimo.com Subject: Re: palemu target? Reply-To: ggi-develop@eskimo.com References: <19990613232239.40350@ajax.netspace.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Ketil Froyn on Sun, Jun 13, 1999 at 06:46:09PM +0200 Resent-Message-ID: <"9dCbY1.0.Mn4.ySGPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13322 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn writes: > On Sun, 13 Jun 1999, Andrew Apted wrote: > > > > Of course, for all I know this could be the program dying for some reason. > > > Is it? :) > > I hope not :). Please try running some normal libggi demos with > > GGI_DISPLAY=palemu and see if they work. > > No, that didn't work. The program needs 8 bpp, and my X server is 16. It works here (e.g. programs/demo/flying_ggis with GGI_DISPLAY=palemu, on an XGGI running in 16 bit mode). programs/demo/demo mostly works too, but I've noticed it hangs sometimes. Here's the back trace after I kill -11 it: | (gdb) bt | #0 0x400e30eb in sched_yield () | #1 0x400e0de4 in pthread_mutex_trylock () | #2 0x4001637c in ggTryLock (lock=0x80505c0) at dlptlock.c:87 | #3 0x400fa09a in GGI_X_flush (vis=0x804ec28, x=0, y=0, w=640, h=480, tryflag=0) | at mode.c:133 | #4 0x40010af2 in _ggiInternFlush (vis=0x804ec28, x=0, y=0, w=640, h=480, | tryflag=0) at stubs.c:88 | #5 0x400ee59c in GGI_palemu_flush (vis=0x804e4b0, x=0, y=0, w=640, h=480, | tryflag=0) at mode.c:427 | #6 0x40010af2 in _ggiInternFlush (vis=0x804e4b0, x=0, y=0, w=640, h=480, | tryflag=0) at stubs.c:88 | #7 0x400f596c in _GGI_mansync_handler (unused=27) at child.c:94 | #8 0xbffed834 in ?? () | #9 0x400162fc in ggLock (lock=0x80505c0) at dlptlock.c:72 | #10 0x401a5b2a in GII_xwin_eventpoll (inp=0x8050910, arg=0x0) at input.c:160 | #11 0x4001cfdc in _giiPollall (inp=0x8050910, mask=160, arg=0x0) at gii.c:553 | #12 0x4001de80 in giiEventPoll (inp=0x8050910, mask=160, timeout=0xbffedc68) | at unix.c:162 | #13 0x4000d129 in ggiKbhit (vis=0x804e4b0) at events.c:80 | #14 0x8049c04 in main (argc=0, argv=0xbffffd64) at demo.c:623 | #15 0x8048ebb in ___crt_dummy__ () I don't see the hang on the console. Marcus, could that be a bug in the GII X input driver, or something else ? [maybe just my crumbling libc5 system ? :-))] Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Mon Jun 14 10:30:03 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA25902 for ; Mon, 14 Jun 1999 10:30:01 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA26398; Mon, 14 Jun 1999 07:16:01 -0700 Resent-Date: Mon, 14 Jun 1999 07:16:01 -0700 Date: Mon, 14 Jun 1999 16:15:38 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: palemu target? In-Reply-To: <19990614183817.03191@ajax.netspace.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"5U4492.0.7S6.VwGPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13324 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Mon, 14 Jun 1999, Andrew Apted wrote: > Ketil Froyn writes: > > > I hope not :). Please try running some normal libggi demos with > > > GGI_DISPLAY=palemu and see if they work. > > No, that didn't work. The program needs 8 bpp, and my X server is 16. > It works here (e.g. programs/demo/flying_ggis with GGI_DISPLAY=palemu, > on an XGGI running in 16 bit mode). programs/demo/demo mostly works Sorry, I screwed up again. The demos probably work fine, I have run another SVGAlib app under X using palemu. (It was APOLLO, can be found on freshmeat, a console game). The one that didn't work was the SNES emulator that I had all the problems with. :) Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Mon Jun 14 11:54:12 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA27688 for ; Mon, 14 Jun 1999 11:54:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA29449; Mon, 14 Jun 1999 08:42:30 -0700 Resent-Date: Mon, 14 Jun 1999 08:42:30 -0700 Date: Mon, 14 Jun 1999 11:40:50 -0400 (EDT) From: James Simmons X-Sender: jsimmons@elmwood.afterfive.com To: ggi-develop@eskimo.com Subject: Re: KGI-0.9 driver interface released In-Reply-To: <99061411275401.10435@master> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"4nbVl1.0.dB7.ZBIPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13325 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Btw: I have a Matrox Mystique next to my TNT. I added FBIO_ACCEL_COPYBOX > and FBIO_ACCEL_FILLRECT to fb.h, implemented it in matroxfb.c and > it worked, but nobody wants that ;-( My patch that will be going into 2.3.x will soon have those two accels available. From ggi-develop-request@eskimo.com Mon Jun 14 14:53:15 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA01874 for ; Mon, 14 Jun 1999 14:53:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA10912; Mon, 14 Jun 1999 11:40:03 -0700 Resent-Date: Mon, 14 Jun 1999 11:40:03 -0700 Sender: e94_msu@e.kth.se Message-ID: <37654C71.92254886@stacken.kth.se> Date: Mon, 14 Jun 1999 20:39:45 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: KGI-0.9 driver interface released References: <199906140755.JAA01826@demonti.physik.tu-chemnitz.de> <99061411275401.10435@master> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"IKFSE2.0.Bg2.0oKPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13326 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > Btw: I have a Matrox Mystique next to my TNT. I added FBIO_ACCEL_COPYBOX > and FBIO_ACCEL_FILLRECT to fb.h, implemented it in matroxfb.c and > it worked, but nobody wants that ;-( Just as well - accels via one-op-per-ioctl() sucks anyway. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Mon Jun 14 15:15:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA02396 for ; Mon, 14 Jun 1999 15:15:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA23000; Mon, 14 Jun 1999 12:03:10 -0700 Resent-Date: Mon, 14 Jun 1999 12:03:10 -0700 Sender: e94_msu@e.kth.se Message-ID: <376551CD.E529873D@stacken.kth.se> Date: Mon, 14 Jun 1999 21:02:38 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: palemu target? References: <19990613232239.40350@ajax.netspace.net.au> <19990614183817.03191@ajax.netspace.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"X05k6.0.-c5.i7LPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13327 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andrew Apted wrote: > programs/demo/demo mostly works > too, but I've noticed it hangs sometimes. Here's the back trace after I > kill -11 it: > > | (gdb) bt > | #0 0x400e30eb in sched_yield () > | #1 0x400e0de4 in pthread_mutex_trylock () > | #2 0x4001637c in ggTryLock (lock=0x80505c0) at dlptlock.c:87 > | #3 0x400fa09a in GGI_X_flush (vis=0x804ec28, x=0, y=0, w=640, h=480, tryflag=0) > | at mode.c:133 > | #4 0x40010af2 in _ggiInternFlush (vis=0x804ec28, x=0, y=0, w=640, h=480, > | tryflag=0) at stubs.c:88 > | #5 0x400ee59c in GGI_palemu_flush (vis=0x804e4b0, x=0, y=0, w=640, h=480, > | tryflag=0) at mode.c:427 > | #6 0x40010af2 in _ggiInternFlush (vis=0x804e4b0, x=0, y=0, w=640, h=480, > | tryflag=0) at stubs.c:88 > | #7 0x400f596c in _GGI_mansync_handler (unused=27) at child.c:94 > | #8 0xbffed834 in ?? () > | #9 0x400162fc in ggLock (lock=0x80505c0) at dlptlock.c:72 > | #10 0x401a5b2a in GII_xwin_eventpoll (inp=0x8050910, arg=0x0) at input.c:160 > | #11 0x4001cfdc in _giiPollall (inp=0x8050910, mask=160, arg=0x0) at gii.c:553 > | #12 0x4001de80 in giiEventPoll (inp=0x8050910, mask=160, timeout=0xbffedc68) > | at unix.c:162 > | #13 0x4000d129 in ggiKbhit (vis=0x804e4b0) at events.c:80 > | #14 0x8049c04 in main (argc=0, argv=0xbffffd64) at demo.c:623 > | #15 0x8048ebb in ___crt_dummy__ () > > I don't see the hang on the console. That's natural, as trylock isn't called by any of the console targets. > Marcus, could that be a bug in the > GII X input driver, or something else ? [maybe just my crumbling libc5 > system ? :-))] Looks like a libc5 bug/obscurity to me. sched_yield() doesn't even take any parameters, so it shouldn't hang becaue of the caller. Try upgrading to current CVS LibGG as it doesn't use libpthread for locking anymore. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Mon Jun 14 15:18:25 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA02450 for ; Mon, 14 Jun 1999 15:18:24 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA24524; Mon, 14 Jun 1999 12:06:52 -0700 Resent-Date: Mon, 14 Jun 1999 12:06:52 -0700 Sender: e94_msu@e.kth.se Message-ID: <376552BC.60DADD68@stacken.kth.se> Date: Mon, 14 Jun 1999 21:06:36 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: GGI won't configure References: <99061403375600.06518@mongoose> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"TrA6i.0.X-5.BBLPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13328 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B wrote: > > Well I deleted the configure.cache file and GGI doesn't seem to report the > error any more when I configure it. Now when I try to run the cube3d demo, it > starts up with the blinking square with the text in the center saying what the > controls are. But it doesn't go anywhere past there and I have to kill it. Any > idea whats wrong? What command line did you use to start cube3d and the applications running on it? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Mon Jun 14 15:23:32 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA02531 for ; Mon, 14 Jun 1999 15:23:27 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id MAA17479; Mon, 14 Jun 1999 12:12:12 -0700 (PDT) Resent-Date: Mon, 14 Jun 1999 12:12:12 -0700 (PDT) Sender: e94_msu@e.kth.se Message-ID: <3765527F.E6242B6F@stacken.kth.se> Date: Mon, 14 Jun 1999 21:05:35 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: palemu target? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"3EAWz3.0.mD4.oCLPt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13329 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn wrote: > > On Mon, 14 Jun 1999, Marcus Sundberg wrote: > > > Why would you want to use palemu with the SVGAlib wrapper? > > Use GSW_MODEEMU and GSW_PAGEEMU instead. > > In any case SVGAlib mode 320x200x256 requires a DirectBuffer which > > the *emu targets doesn't provide. > > Erm... Was I supposed to figure that out all by myself? :D Well, the SVGAlib wrapper README states: GSW_MODEEMU - Tries to emulate modes which are not available. This is recommended as most SVGAlib applications makes quite a lot of assumptions when it comes to mode setting. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Mon Jun 14 19:27:30 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA06652 for ; Mon, 14 Jun 1999 19:27:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA16535; Mon, 14 Jun 1999 16:14:47 -0700 Resent-Date: Mon, 14 Jun 1999 16:14:47 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990615011745.A517@rz.uni-duesseldorf.de> Date: Tue, 15 Jun 1999 01:17:45 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGI won't configure Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Garrett Robert Banuk on Sun, Jun 13, 1999 at 08:40:52PM -0400 Resent-Message-ID: <"b-c--.0.t14.UpOPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13330 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > No matter what I do to configure GGI I always get this message at the end > of configuring. > LibGII is not properly installed on the system. You need LibGII for > building LibGGI. Please compile LibGII first. > I did all the default things to install GII configure/make/make install I > checked the dynamic linkers search path and everything. Has this Check that it isn't just a cached value. Remove config.cache . CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 14 19:55:58 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA06980 for ; Mon, 14 Jun 1999 19:55:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA24047; Mon, 14 Jun 1999 16:42:57 -0700 Resent-Date: Mon, 14 Jun 1999 16:42:57 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: GGI won't configure Date: Mon, 14 Jun 1999 19:42:06 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <376552BC.60DADD68@stacken.kth.se> MIME-Version: 1.0 Message-Id: <99061419425201.00201@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"T62Z93.0.St5.0EPPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13331 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Mon, 14 Jun 1999, Marcus Sundberg wrote: > Garrett B wrote: > > > > Well I deleted the configure.cache file and GGI doesn't seem to report the > > error any more when I configure it. Now when I try to run the cube3d demo, it > > starts up with the blinking square with the text in the center saying what the > > controls are. But it doesn't go anywhere past there and I have to kill it. Any > > idea whats wrong? > > What command line did you use to start cube3d and the applications > running on it? I tried running it in xwindows. What command line should I use to run it? From ggi-develop-request@eskimo.com Mon Jun 14 21:51:46 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA08758 for ; Mon, 14 Jun 1999 21:51:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id SAA02666; Mon, 14 Jun 1999 18:38:43 -0700 Resent-Date: Mon, 14 Jun 1999 18:38:43 -0700 From: Andrew Apted Message-ID: <19990615114336.04958@ajax.netspace.net.au> Date: Tue, 15 Jun 1999 11:43:36 +1000 To: ggi-develop@eskimo.com Subject: Re: palemu target? Reply-To: ggi-develop@eskimo.com References: <19990613232239.40350@ajax.netspace.net.au> <19990614183817.03191@ajax.netspace.net.au> <376551CD.E529873D@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <376551CD.E529873D@stacken.kth.se>; from Marcus Sundberg on Mon, Jun 14, 1999 at 09:02:38PM +0200 Resent-Message-ID: <"lXFxw2.0.ie.RwQPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13332 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus writes: > Andrew Apted wrote: > > | #13 0x4000d129 in ggiKbhit (vis=0x804e4b0) at events.c:80 > > | #14 0x8049c04 in main (argc=0, argv=0xbffffd64) at demo.c:623 > > | #15 0x8048ebb in ___crt_dummy__ () > > > > I don't see the hang on the console. > > That's natural, as trylock isn't called by any of the console targets. Ah yes. > > Marcus, could that be a bug in the > > GII X input driver, or something else ? [maybe just my crumbling libc5 > > system ? :-))] > > Looks like a libc5 bug/obscurity to me. sched_yield() doesn't even > take any parameters, so it shouldn't hang becaue of the caller. Yeah, I reckon that too. No big worries. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Mon Jun 14 22:25:25 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA09355 for ; Mon, 14 Jun 1999 22:25:23 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA13305; Mon, 14 Jun 1999 19:13:08 -0700 Resent-Date: Mon, 14 Jun 1999 19:13:08 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990615012422.A531@rz.uni-duesseldorf.de> Date: Tue, 15 Jun 1999 01:24:22 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: GGI won't configure Mail-Followup-To: ggi-develop@eskimo.com References: <99061403375600.06518@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99061403375600.06518@mongoose>; from Garrett B on Mon, Jun 14, 1999 at 03:11:41AM -0500 Resent-Message-ID: <"T1qvp2.0.gF3.pQRPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13333 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Well I deleted the configure.cache file and GGI doesn't seem to report the > error any more when I configure it. Now when I try to run the cube3d demo, it > starts up with the blinking square with the text in the center saying what the > controls are. But it doesn't go anywhere past there and I have to kill it. Any > idea whats wrong? Read the manpage. You have to start the apps for the cube sides. '#' 'q' will get you out, though. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 14 22:25:49 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA09367 for ; Mon, 14 Jun 1999 22:25:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA13612; Mon, 14 Jun 1999 19:13:43 -0700 Resent-Date: Mon, 14 Jun 1999 19:13:43 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990615013529.C531@rz.uni-duesseldorf.de> Date: Tue, 15 Jun 1999 01:35:29 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: KGI-0.9 driver interface released Mail-Followup-To: ggi-develop@eskimo.com References: <199906140755.JAA01826@demonti.physik.tu-chemnitz.de> <99061411275401.10435@master> <37654C71.92254886@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <37654C71.92254886@stacken.kth.se>; from Marcus Sundberg on Mon, Jun 14, 1999 at 08:39:45PM +0200 Resent-Message-ID: <"Y4U7I3.0.EK3.KRRPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13334 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Btw: I have a Matrox Mystique next to my TNT. I added FBIO_ACCEL_COPYBOX > > and FBIO_ACCEL_FILLRECT to fb.h, implemented it in matroxfb.c and > > it worked, but nobody wants that ;-( > Just as well - accels via one-op-per-ioctl() sucks anyway. Well - at least nine times better than nothing :-). But sure, there are better ways ... CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 15 01:26:47 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA12156 for ; Tue, 15 Jun 1999 01:26:46 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA05434; Mon, 14 Jun 1999 21:59:57 -0700 Resent-Date: Mon, 14 Jun 1999 21:59:57 -0700 From: mongoose@ms241739.users.mindspring.com Date: Tue, 15 Jun 1999 00:58:18 -0400 (EDT) Reply-To: "Terry 'Mongoose' Hendrix" To: ggi-develop@eskimo.com Subject: First ggi project, need help In-Reply-To: <19990615013529.C531@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"vy4QS2.0.eK1.CtTPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13336 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Greetings to the list, I'm working on a NeXt toolkit for ggi. This is my frist real gfx programming project, I'm much better at network and threaded code. =/ I wondering why my ggi visual is blinking. You see I decompress a jpeg and load it on the visual. After loading, I write pixel by pixel out the the visual. Then, I BoxGet that image into a buffer. To draw the image agian I do BoxPut on the buffer. I draw a "desktop" then draw other images like my "docks" over that... then after all the artifacts are drawn I call a Flush(). I'm redrawing all the images by PutBox each loop to clear old artifacts like the pointer off. How can it get it to stop blinking? It blinks mostly on the top with one flush per loop. If I remove the flush or add more it blinks worse. In allegro ( I done the project in dos a long time ago ) I called vsync(). I really don't understand all this bliting and buffer types. Also how is the best way to impelement transparences and animation? I can't use my ggi buffered images for these without drawing pixel by pixel. ( slow ) Point me to something or give me suggestions please. =) FYI the ggi api docs weren't very helpful for me. The only reason I was able to do it in Allegro was due to "plain talk" api docs. The code is all C++, with only the libjpeg called as extern C. This makes it slower I feel but it shouldn't make it blink due to slow function calls. thanks, Terry --------------------------------------------------- BotShop http://www.planetquake.com/botshop Personal http://www.westga.edu.com/~stu7440 Alita is running linux 2.2.9 w/ DoS fix --------------------------------------------------- From ggi-develop-request@eskimo.com Tue Jun 15 01:31:20 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA12222 for ; Tue, 15 Jun 1999 01:31:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA05147; Mon, 14 Jun 1999 21:59:21 -0700 Resent-Date: Mon, 14 Jun 1999 21:59:21 -0700 Date: Mon, 14 Jun 1999 21:59:06 -0700 (PDT) From: "Jon M. Taylor" To: KGI mailing list cc: GGI mailing list Subject: KGIcon 0.9 pre-alpha released Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"T6WrX.0.wF1.YsTPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13335 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com (no, it does absolutely nothing useful yet in case you were wondering....) The time has come. I am finding that I have to hack fbcon-kgi.c more and more heavily in order to make it work properly with my Savage4 KGI driver, and thus I decided that it was time to separate fbcon-kgi.c and the KGI drivers so others could benefit from my KGIcon infrastructure work and so I would not have to lug around all of fbcon-kgi.c with the KGI driver DDK I am currently putting together. fbcon-kgi.c needs to act like sound_core.c does - as a dynamic management framework to which separate KGI driver modules can be dynamically loaded/bound at runtime. After looking at Steffen's latest sources I decided that the separation of fbcon-kgi.c and its associated KGI drivers would be much more easily handled within the framework of the KGI-0.9 API. So I spent most of today hacking together a build tree and I just finally got the whole thing to build and insert properly, which is enough for today. Most of fbcon-kgi.c is #if 0'ed out right now, and all it does is insert itself and sit there. I hope to have a more-or-less fully functional system by the end of the week if not earlier. The current (mostly useless) sources can be downloaded from: http://gaia.ecs.csus.edu/~taylorj/kgicon-0.9.tar.gz I will use my Savage4 here at work and my CL5462 2D card at home as initial KGI-0.9 API porting examples. Hopefully everyone will be able to look at the CL546x code and see clearly what needs to be done to port the other Dali drivers. KGI-0.9 is quite different in some aspects from the KGI that most of us are familiar with, so expect a bit of a learning curve (I am still confused in some areas...). Nevertheless, the new KGI API is so much better than KGI-Dali that its use is basically a necessity IMHO. In KGI-0.9, the familiar chipset/clockchip/accel/etc modules are still defined, but now instead of being hardwired into the API these modules are predefined instances of a generic KGI_SUBSYSTEM class (not an OOP 'class', ICYWW). Therefore, fbcon-kgi.c has both an easier and more difficult job now. It is easier in that, once loaded, fbcon-kgi.c just sits around and waits for other KGI_SUBSYSTEM-exporting modules to be loaded and hook themselves into fbcon-kgi.c's management framework. All the special-case handling that fbcon-kgi.c does now (initializing chipset/ramdac/etc, mapping the GC/MMIO region, setting up the sysctl interface for the monitor driver, etc) will thankfully be EOLed. All that the new fbcon-kgi.c needs to do is be able to map generic objects which it gets from the KGI driver(s) in a predefined set of ways, and handle driver-specific abstracted commands - __MUCH__ cleaner and more powerful. However, the job of bridging the fbdev API and the KGI API just got a lot harder. KGI-0.9's internal mode/display/context/etc representational systems have been reworked so that they can more accurately represent the state of video hardware and associated data structs. Instead of predefined mode types like GT_32BIT, we now have 'dot ports' (software ramdacs, basically) which define the methods by which the buffer data is serialized into a pixel stream. Instead of colors, alpha values, ASCII/Unicode characters, etc with which to interpret our pixel data, we have KGI_A_* 'attribute' types which can be anything. Instead of io_regions and mem_regions, GCs, accel ping-pong buffers, etc we have KGI_RT_* 'resource types'. Etc etc etc. Good stuff, all of it. However, we still have to implement the very different fbcon/fbdev interface on top of all this. The translation between the KGI/Dali representational system and the fbcon/fbdev system already takes up around half of the existing fbcon-kgi.c code, and I expect that percentage to rise. Nothing much we can do about it, but it will take a lot of time and gruntwork to make it all work cleanly. That is another reason I am releasing kgicon-0.9 when it is still so broken - so the code can be available for public hacking and maybe some kind souls will send me some patches.... What will (might?) change: ========================== * The KGI core will now be a logically separate kernelspace entity, able to export and implement its own communication channels and APIs through /proc. This means that we can stop doing any KGI communications through /dev/fb. No more GC/MMIO mapping hacks using the mmap() offset parameter as a map-type flag - each will have its own mapping(s) handled properly through /proc/kgi. This will break the LibGGI genkgi target and perhaps the fbdev target as well. * The mondrivers will probably be loaded separately at runtime before the actual video hardware drivers, so they cannot assume the existence of the other driver subsystems. * The ability to logically divide up the total functionality of a piece of video hardware into any set of KGI_SUBSYSTEMs will mean that the LibGGI code can no longer assume the existence of any particular subsystem interfaces, only the top-level KGI interface. For example, my Savage4 driver will (eventually at least) consist of the following separate KGI_SUBSYSTEMs: * Chipset (chipset+clockchip+ramdac) * 2D accel driver * 3D accel driver * DDC helper * I2C helper * STREAMS helper * XAA API implementation helper * D3D immediate mode API helper * ...many others... LibGGI needs to be aware of all of this and be able to intelligently navigate it as it currently does with its own userspace DLs. Now, these changes are huge and will not happen overnight. But they will happen eventually. We need to start discussing how we should approach this. Steffen, I am sorry to report that I felt it necessary to make some changes to your header files (no changes to the essence of the KGI 0.9 API itself, of course). Some of them are minor, like making all preprocessor #defines uppercased to minimize namespace clashing. However, there is one major change that I made which I do not think you will approve of but I which I strongly feel is necessary: the removal of the ggi* namespace and the conversion of all its members to the kgi* namespace. The ggi* namespace belongs to LibGGI, and while it may be legitimate for some LibGGI userspace code to use the kgi* namespace, the reverse should never be done. The KGI API must be able to stand on its own if it is to be truly portable. Anyway, that's where things stand right now. I would like to see kgicon 0.9 go into CVS as the standard kgicon as soon as it is reasonably stable and at least one of the existing open-source KGI drivers get ported. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Tue Jun 15 02:06:16 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id CAA12539 for ; Tue, 15 Jun 1999 02:06:15 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA19870; Mon, 14 Jun 1999 22:48:15 -0700 Resent-Date: Mon, 14 Jun 1999 22:48:15 -0700 X-envelope-info: Date: Mon, 14 Jun 1999 22:49:01 -0700 From: Aaron Van Couwenberghe To: GGI Development Subject: What is KGICON? Message-ID: <19990614224901.A26449@awac.local.net> Mail-Followup-To: GGI Development Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: Resent-Message-ID: <"_HbLI3.0.Gs4.UaUPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13337 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I know what KGI, SUIDKGI, etc are, but what purpose does KGICon serve? A compatibility layer between FBCON and KGI? If so, what exactly does it do? Sorry for the clueless question. If you feel inclined, just point me to the proper documentation. -- ..Aaron Van Couwenberghe... ..vanco@sonic.net.. ..aaronv@debian.org.... Berlin: http://www.berlin-consortium.org Debian GNU/Linux: http://www.debian.org There are three kinds of people: those who can count, and those who can't. From ggi-develop-request@eskimo.com Tue Jun 15 03:21:56 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA13513 for ; Tue, 15 Jun 1999 03:21:55 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA31427; Mon, 14 Jun 1999 23:34:12 -0700 Resent-Date: Mon, 14 Jun 1999 23:34:12 -0700 Date: Mon, 14 Jun 1999 23:34:06 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: What is KGICON? In-Reply-To: <19990614224901.A26449@awac.local.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"x2xim.0.mg7.YFVPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13338 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Mon, 14 Jun 1999, Aaron Van Couwenberghe wrote: > I know what KGI, SUIDKGI, etc are, but what purpose does KGICon serve? A > compatibility layer between FBCON and KGI? A glue/bridge layer is a more accurate term, but yeah that's basically it. It lets you turn compile KGI drivers into fbdev driver modules. > If so, what exactly does it do? It implements the KGI video device driver API but uses the fbdev interface to export KGI's framebuffers (/dev/fb*) and the kgicommand interface (ioctls on /dev/fb*). The "real" KGI is a kernel patchset which has a boot-time display minidriver, handles events, implements a new kernel console handling system, implements extensions to the existing kernel mmap() system which provide for userspace page fault handlers, _and_ exports the KGI video device driver API. KGIcon is a good way to maintain and develop the KGI driver API and allow for KGI driver development to continue until the final "real" KGI is ready to go into the kernel. > Sorry for the clueless question. If you feel inclined, just point me to the > proper documentation. The proper documentation consists mostly of the KGI and fbdev/fbmem/fbcon .h files which define their respective APIs. The rest is ad hoc glue logic, mostly. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Tue Jun 15 07:31:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA15292 for ; Tue, 15 Jun 1999 07:31:01 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA21611; Tue, 15 Jun 1999 04:08:00 -0700 Resent-Date: Tue, 15 Jun 1999 04:08:00 -0700 Sender: marcus@e.kth.se Message-ID: <3766257F.2F458755@stacken.kth.se> Date: Tue, 15 Jun 1999 10:05:51 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com CC: mongoose@wpi.edu Subject: Re: GGI won't configure References: <376552BC.60DADD68@stacken.kth.se> <99061419425201.00201@mongoose> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Xno6A.0.qG5.bFZPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13339 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B wrote: > > On Mon, 14 Jun 1999, Marcus Sundberg wrote: > > Garrett B wrote: > > > > > > Well I deleted the configure.cache file and GGI doesn't seem to report the > > > error any more when I configure it. Now when I try to run the cube3d demo, it > > > starts up with the blinking square with the text in the center saying what the > > > controls are. But it doesn't go anywhere past there and I have to kill it. Any > > > idea whats wrong? > > > > What command line did you use to start cube3d and the applications > > running on it? > > I tried running it in xwindows. What command line should I use to run it? See 'cube3d -h' or 'man cube3d' //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 15 07:35:41 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA15326 for ; Tue, 15 Jun 1999 07:35:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA23498; Tue, 15 Jun 1999 04:18:16 -0700 Resent-Date: Tue, 15 Jun 1999 04:18:16 -0700 From: Steffen Seeger Message-Id: <199906151117.NAA31223@demonti.physik.tu-chemnitz.de> Subject: Re: KGIcon 0.9 pre-alpha released In-Reply-To: from "Jon M. Taylor" at "Jun 14, 99 09:59:06 pm" To: taylorj@gaia.ecs.csus.edu (Jon M. Taylor) Date: Tue, 15 Jun 1999 13:17:07 +0200 (CEST) Cc: ggi-kgi@kludge.org, ggi-develop@eskimo.com X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"OSpTS3.0.qk5.sPZPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13340 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello Jon, > After looking at Steffen's latest sources I decided that the > separation of fbcon-kgi.c and its associated KGI drivers would be much more > easily handled within the framework of the KGI-0.9 API. So I spent most of > today hacking together a build tree and I just finally got the whole thing to > build and insert properly, which is enough for today. Most of fbcon-kgi.c is > #if 0'ed out right now, and all it does is insert itself and sit there. I > hope to have a more-or-less fully functional system by the end of the week if > not earlier. The current (mostly useless) sources can be downloaded from: > > http://gaia.ecs.csus.edu/~taylorj/kgicon-0.9.tar.gz > > I will use my Savage4 here at work and my CL5462 2D card at home as > initial KGI-0.9 API porting examples. Hopefully everyone will be able to > look at the CL546x code and see clearly what needs to be done to port the > other Dali drivers. KGI-0.9 is quite different in some aspects from the KGI > that most of us are familiar with, so expect a bit of a learning curve (I am > still confused in some areas...). I have just sent an overview article that is intended to give a basic idea of the new structure. If anyone is unclear about something, please ask, I will try to explain what my intentions were. > In KGI-0.9, the familiar chipset/clockchip/accel/etc modules are > still defined, but now instead of being hardwired into the API these modules > are predefined instances of a generic KGI_SUBSYSTEM class (not an OOP > 'class', ICYWW). ICYWW??? This is the basic idea. I want to add the common intra-module API functions as well to the kgim_ structs. These so it becomes quite like OOP in the end. The benefit is that we only need to have the various init_module() functions public. > Therefore, fbcon-kgi.c has both an easier and more > difficult job now. It is easier in that, once loaded, fbcon-kgi.c just sits > around and waits for other KGI_SUBSYSTEM-exporting modules to be loaded and > hook themselves into fbcon-kgi.c's management framework. All the > special-case handling that fbcon-kgi.c does now (initializing > chipset/ramdac/etc, mapping the GC/MMIO region, setting up the sysctl > interface for the monitor driver, etc) will thankfully be EOLed. All that > the new fbcon-kgi.c needs to do is be able to map generic objects which it > gets from the KGI driver(s) in a predefined set of ways, and handle > driver-specific abstracted commands - __MUCH__ cleaner and more powerful. If possible, kgicon should not make assumptions about the internals of drivers. The reason is that the KGI-driver modules are taylored to the most common -- but nontheless particular -- hardware model. So, ideally kgicon would just do minimal management, provide the environment (display registration) and do the bridging to fbcon. > Good stuff, all of it. However, we still have to implement the very > different fbcon/fbdev interface on top of all this. The translation between > the KGI/Dali representational system and the fbcon/fbdev system already takes > up around half of the existing fbcon-kgi.c code, and I expect that percentage > to rise. Nothing much we can do about it, but it will take a lot of time and > gruntwork to make it all work cleanly. That is another reason I am releasing > kgicon-0.9 when it is still so broken - so the code can be available for > public hacking and maybe some kind souls will send me some patches.... I will try to keep an eye on it and do testing with the drivers I have. > What will (might?) change: > ========================== > > * The KGI core will now be a logically separate kernelspace entity, able to > export and implement its own communication channels and APIs through /proc. > This means that we can stop doing any KGI communications through /dev/fb. No > more GC/MMIO mapping hacks using the mmap() offset parameter as a map-type > flag - each will have its own mapping(s) handled properly through /proc/kgi. > This will break the LibGGI genkgi target and perhaps the fbdev target as > well. If possible (and if you agree in terms of copyright) I would like to use this technology for KGI-0.9 as well. This could allow us to have the same userspace environment for true KGI and KGICON. > * The mondrivers will probably be loaded separately at runtime before the > actual video hardware drivers, so they cannot assume the existence of the > other driver subsystems. All driver modules can now be loaded separately. To make a particular card driver out of it, I wanted to use a simple binding module, that gets loaded last; calling the appropriate _init_module() functions. This should even allow to link all subdrivers statically and do the binding with /proc... I have to think about this in detail. > * The ability to logically divide up the total functionality of a piece of > video hardware into any set of KGI_SUBSYSTEMs will mean that the LibGGI code > can no longer assume the existence of any particular subsystem interfaces, > only the top-level KGI interface. For example, my Savage4 driver will > (eventually at least) consist of the following separate KGI_SUBSYSTEMs: > > * Chipset (chipset+clockchip+ramdac) > * 2D accel driver > * 3D accel driver > * DDC helper > * I2C helper > * STREAMS helper > * XAA API implementation helper > * D3D immediate mode API helper > * ...many others... Right. But some of these may be implemented as userspace library modules. The in-kernel part should just coordinate the hardware access and provide virtualization. The libraries in the kgi-0.9/lib directory are an early study of this. Ideally applications would go through a libKGI that does the neccessary communication with the low-level drivers. > LibGGI needs to be aware of all of this and be able to intelligently navigate > it as it currently does with its own userspace DLs. We should probably separate this into a libKGI, but I am not yet sure about this. libKGI should do all the stuff neccessary to establish the mapping to particular resources. > Steffen, I am sorry to report that I felt it necessary to make some > changes to your header files (no changes to the essence of the KGI 0.9 API > itself, of course). Some of them are minor, like making all preprocessor > #defines uppercased to minimize namespace clashing. However, there is one > major change that I made which I do not think you will approve of but I which > I strongly feel is necessary: the removal of the ggi* namespace and the > conversion of all its members to the kgi* namespace. The ggi* namespace > belongs to LibGGI, and while it may be legitimate for some LibGGI userspace > code to use the kgi* namespace, the reverse should never be done. The KGI > API must be able to stand on its own if it is to be truly portable. Just checking: GGI namespace/references are used * in the portability layer (__ggi_sys_). Actually it should be __sys, but that might give clashes with the system in general. I am fine with __kgi_sys. * for error codes. (historical reasons) * in the word 'debugging' (interestingly :-) So, as this is only internal to KGI/not yet used, I am fine with that cleanup. You could save me the time to redo the changes by sending a diff of the changes against the original tree. Thanks. Steffen ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- From ggi-develop-request@eskimo.com Tue Jun 15 15:22:34 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA24978 for ; Tue, 15 Jun 1999 15:22:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA16866; Tue, 15 Jun 1999 12:08:13 -0700 Resent-Date: Tue, 15 Jun 1999 12:08:13 -0700 Date: Tue, 15 Jun 1999 12:07:58 -0700 (PDT) From: "Jon M. Taylor" To: Steffen Seeger cc: ggi-kgi@kludge.org, ggi-develop@eskimo.com Subject: Re: KGIcon 0.9 pre-alpha released In-Reply-To: <199906151117.NAA31223@demonti.physik.tu-chemnitz.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"VQw-D1.0.s64.NIgPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13341 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 15 Jun 1999, Steffen Seeger wrote: > Hello Jon, > > > In KGI-0.9, the familiar chipset/clockchip/accel/etc modules are > > still defined, but now instead of being hardwired into the API these modules > > are predefined instances of a generic KGI_SUBSYSTEM class (not an OOP > > 'class', ICYWW). > > ICYWW??? In Case You Were Wondering |->. I've used that one like four times in nine years on the net, but it does come in handy sometimes. > This is the basic idea. I want to add the common intra-module > API functions as well to the kgim_ structs. These so it > becomes quite like OOP in the end. The benefit is that we only need > to have the various init_module() functions public. Yes. I forsee a nice COM layer developing. > > Therefore, fbcon-kgi.c has both an easier and more > > difficult job now. It is easier in that, once loaded, fbcon-kgi.c just sits > > around and waits for other KGI_SUBSYSTEM-exporting modules to be loaded and > > hook themselves into fbcon-kgi.c's management framework. All the > > special-case handling that fbcon-kgi.c does now (initializing > > chipset/ramdac/etc, mapping the GC/MMIO region, setting up the sysctl > > interface for the monitor driver, etc) will thankfully be EOLed. All that > > the new fbcon-kgi.c needs to do is be able to map generic objects which it > > gets from the KGI driver(s) in a predefined set of ways, and handle > > driver-specific abstracted commands - __MUCH__ cleaner and more powerful. > > If possible, kgicon should not make assumptions about the internals > of drivers. It has to, at least to some degree. It has to be able to interpret the top-level kgi_mode in order to properly implement the fbdev interface. > The reason is that the KGI-driver modules are taylored to > the most common -- but nontheless particular -- hardware model. > > So, ideally kgicon would just do minimal management, provide the environment > (display registration) and do the bridging to fbcon. Yes, but some assumptions will have to be made somewhere IMHO. Hopefully they will be small and clean. > > What will (might?) change: > > ========================== > > > > * The KGI core will now be a logically separate kernelspace entity, able to > > export and implement its own communication channels and APIs through /proc. > > This means that we can stop doing any KGI communications through /dev/fb. No > > more GC/MMIO mapping hacks using the mmap() offset parameter as a map-type > > flag - each will have its own mapping(s) handled properly through /proc/kgi. > > This will break the LibGGI genkgi target and perhaps the fbdev target as > > well. > > If possible (and if you agree in terms of copyright) I would like to use this > technology for KGI-0.9 as well. This could allow us to have the same > userspace environment for true KGI and KGICON. Sure! Creative has agreed to let me release non-proprietary code under X-style licenses, so as long as the (C) Creative Labs remains on any substantial portion of the code it should be fine. > > * The mondrivers will probably be loaded separately at runtime before the > > actual video hardware drivers, so they cannot assume the existence of the > > other driver subsystems. > > All driver modules can now be loaded separately. To make a particular card > driver out of it, I wanted to use a simple binding module, that gets > loaded last; calling the appropriate _init_module() functions. Isn't that 'module' the KGI/KGIcon modesetting framework itself? > This should even allow to link all subdrivers statically and do the binding > with /proc... I have to think about this in detail. Yes, we need to plan this out. In fact the binding probably _will_ be static for the first Savage4 KGI driver beta. > > * The ability to logically divide up the total functionality of a piece of > > video hardware into any set of KGI_SUBSYSTEMs will mean that the LibGGI code > > can no longer assume the existence of any particular subsystem interfaces, > > only the top-level KGI interface. For example, my Savage4 driver will > > (eventually at least) consist of the following separate KGI_SUBSYSTEMs: > > > > * Chipset (chipset+clockchip+ramdac) > > * 2D accel driver > > * 3D accel driver > > * DDC helper > > * I2C helper > > * STREAMS helper > > * XAA API implementation helper > > * D3D immediate mode API helper > > * ...many others... > > Right. But some of these may be implemented as userspace library modules. Sure. The question of user vs. kernel is always present, and you just have to ask if the code really needs kernelspace features to work well. But at least we have a more flexible choice now.... > The in-kernel part should just coordinate the hardware access and provide > virtualization. Also things like: * Provide IRQ/pagefault handling to usersapce * Implement interfaces which can benefit from kernelspace features (IRQ hooking, critical sections, etc). * Manage consoles/multiheading/events > The libraries in the kgi-0.9/lib directory are an early > study of this. Ideally applications would go through a libKGI that does > the neccessary communication with the low-level drivers. Yes. If the LibGGI targets would use a LibKGI instead of a helperlib, LibGGI could still make full use of KGI, portably, _and_ applications could also use the KGIcommand interface directly when possible for maximum speed for games, etc. > > LibGGI needs to be aware of all of this and be able to intelligently navigate > > it as it currently does with its own userspace DLs. > > We should probably separate this into a libKGI, but I am not yet sure > about this. libKGI should do all the stuff neccessary to establish the > mapping to particular resources. Yes. > > Steffen, I am sorry to report that I felt it necessary to make some > > changes to your header files (no changes to the essence of the KGI 0.9 API > > itself, of course). Some of them are minor, like making all preprocessor > > #defines uppercased to minimize namespace clashing. However, there is one > > major change that I made which I do not think you will approve of but I which > > I strongly feel is necessary: the removal of the ggi* namespace and the > > conversion of all its members to the kgi* namespace. The ggi* namespace > > belongs to LibGGI, and while it may be legitimate for some LibGGI userspace > > code to use the kgi* namespace, the reverse should never be done. The KGI > > API must be able to stand on its own if it is to be truly portable. > > Just checking: GGI namespace/references are used > > * in the portability layer (__ggi_sys_). Actually it should be __sys, but > that might give clashes with the system in general. I am fine with > __kgi_sys. > > * for error codes. (historical reasons) > > * in the word 'debugging' (interestingly :-) > > So, as this is only internal to KGI/not yet used, I am fine with that cleanup. Great! > You could save me the time to redo the changes by sending a diff of the changes > against the original tree. Thanks. I will do that today. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Tue Jun 15 18:34:03 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA00130 for ; Tue, 15 Jun 1999 18:34:02 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA26464; Tue, 15 Jun 1999 15:22:01 -0700 Resent-Date: Tue, 15 Jun 1999 15:22:01 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990615074657.A512@rz.uni-duesseldorf.de> Date: Tue, 15 Jun 1999 07:46:57 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: palemu target? Mail-Followup-To: ggi-develop@eskimo.com References: <19990613232239.40350@ajax.netspace.net.au> <19990614183817.03191@ajax.netspace.net.au> <376551CD.E529873D@stacken.kth.se> <19990615114336.04958@ajax.netspace.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990615114336.04958@ajax.netspace.net.au>; from Andrew Apted on Tue, Jun 15, 1999 at 11:43:36AM +1000 Resent-Message-ID: <"SxwDu.0.zS6.58jPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13342 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andrew Apted wrote: > > > GII X input driver, or something else ? [maybe just my crumbling libc5 > > > system ? :-))] > > Looks like a libc5 bug/obscurity to me. sched_yield() doesn't even > > take any parameters, so it shouldn't hang becaue of the caller. > Yeah, I reckon that too. No big worries. Does it really hang in sched-yield, or is it rather in a tight loop that calls it over and over ? Maybe try decreasing GGI_MANSYNC_FPS. Helped for me in a couple of cases. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 15 18:58:14 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA00638 for ; Tue, 15 Jun 1999 18:58:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA05061; Tue, 15 Jun 1999 15:45:33 -0700 Resent-Date: Tue, 15 Jun 1999 15:45:33 -0700 Date: Tue, 15 Jun 1999 22:44:29 GMT Message-Id: <199906152244.WAA01029@platinum.math.arizona.edu> From: "Robert S. Maier" To: tanner@ffii.org Cc: ggi-develop@eskimo.com Subject: libxmi-0.0 released Phase-of-Moon: Waxing Crescent (7% of Full) Organization: Mathematics Department, University of Arizona Resent-Message-ID: <"Zmsyn2.0.jE1.BUjPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13343 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Thomas and other libGGI2D people, this is to let you know that I have released version 0.0 of libxmi, which is the standalone version of the X11 vector graphics code. libxmi-0.0 is at ftp://platinum.math.arizona.edu/ftp/pub/libxmi.tar.gz (about 210kB, gzipped). I hope that you can look at it, and send me your impressions; also perhaps you may find it useful in libGGI2D. The libxmi API is a bit unusual, and I am willing to change it. The libxmi drawing functions (miDrawLines, miFillPolygon, miDrawArcs, etc.) are based on those of X11 (XDrawLines, XFillPolygon, XDrawArcs, etc.). But they draw graphics to an in-core abstraction, a `miPaintedSet'. After pixels are selected and painted in a miPaintedSet, the painted set is rendered to a miCanvas. At this second stage of the graphics pipeline, sophisticated pixel merging algorithms, e.g., alpha compositing and Microsoft's ROP3 operations, can be applied. Textures are supported. libxmi, unlike X11, supports multicolored dashes. No matter whether you're doing conventional on/off dashing or double-dashing, you may now specify an array of colors, from which the colors of the `on' dashes will be cyclically selected. The array may be arbitrarily long. I have not implemented any form of antialiasing yet, but I am thinking about it. Best regards, Robert -- Robert S. Maier | Internet: rsm@math.arizona.edu Dept. of Math. | Univ. of Arizona | FAX: +1 520 621 8322 Tucson, AZ 85721 | Voice: +1 520 621 6892 (department) U.S.A. | +1 520 621 2617 (office) Maintainer of the GNU plotting utilities package (see http://www.gnu.org/software/plotutils/plotutils.html ). From ggi-develop-request@eskimo.com Tue Jun 15 19:24:00 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA01099 for ; Tue, 15 Jun 1999 19:23:59 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA16263; Tue, 15 Jun 1999 16:11:07 -0700 Resent-Date: Tue, 15 Jun 1999 16:11:07 -0700 Sender: marcus@e.kth.se Message-ID: <3766DD7A.C8FC002@stacken.kth.se> Date: Tue, 15 Jun 1999 23:10:50 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-kgi@kludge.org CC: ggi-develop@eskimo.com Subject: Re: KGIcon 0.9 pre-alpha released References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"oOygn1.0.pz3.9sjPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13344 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > > The libraries in the kgi-0.9/lib directory are an early > > study of this. Ideally applications would go through a libKGI that does > > the neccessary communication with the low-level drivers. > > Yes. If the LibGGI targets would use a LibKGI instead of a > helperlib, LibGGI could still make full use of KGI, portably, _and_ > applications could also use the KGIcommand interface directly when possible > for maximum speed for games, etc. LibGGI was designed to be what you refer to as LibKGI. If there is _any_ reason for _any_ application to use LibKGI directly this means LibGGI needs to be fixed - even if it means rewriting every single line of code from scratch. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 15 21:41:30 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA01386 for ; Tue, 15 Jun 1999 21:41:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id SAA32245; Tue, 15 Jun 1999 18:27:34 -0700 Resent-Date: Tue, 15 Jun 1999 18:27:34 -0700 Date: Tue, 15 Jun 1999 22:12:24 -0400 (EDT) From: "Brian S. Julin" To: =?iso-8859-1?Q?Peter_=C5strand?= cc: Joseph Carter , ggi-develop@eskimo.com Subject: Mystique does SoG ICYWW In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mx1.eskimo.com id SAA32211 Resent-Message-ID: <"IbvUn1.0.Zt7.4slPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13345 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 8 Jun 1999, [iso-8859-1] Peter Åstrand wrote: > All Millenium and even Mystique cards are (I am told) capable of > sync-on-green. But I had a _lot_ of trouble before I got this information. > If i remember correctly, I saw it by accident on > http://www.xfree86.org/3.3.3.1/MGA3.html I'm pleased to verify that the Mystique does SoG. You need XFree86 > 3.3.3 to do it, but it works. Whoohoo! now I don't have to "get around" to buying/making an SoG adaptor. (Spending $20 on a Mystique was a lot cheaper, too :). -- Brian From ggi-develop-request@eskimo.com Tue Jun 15 22:18:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA02052 for ; Tue, 15 Jun 1999 22:18:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA10504; Tue, 15 Jun 1999 19:03:31 -0700 Resent-Date: Tue, 15 Jun 1999 19:03:31 -0700 Date: Tue, 15 Jun 1999 22:48:23 -0400 (EDT) From: "Brian S. Julin" To: ggi-kgi@kludge.org cc: ggi-develop@eskimo.com Subject: Re: KGIcon 0.9 pre-alpha released In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"JPGsG1.0.wZ2.oNmPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13346 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 15 Jun 1999, Jon M. Taylor wrote: > > This should even allow to link all subdrivers statically and do the binding > > with /proc... I have to think about this in detail. > > Yes, we need to plan this out. In fact the binding probably _will_ > be static for the first Savage4 KGI driver beta. It's very encouraging seeing "the grand scheme" coalesce again, especially when it's our two best kernel hackers talking. :) Unfortunately, I've lost my notes from when I was trying to do this using evstacks. Never got far, but I wish I could find the file that described the interface I was striving towards. One of the best features of this idea (IMO) was that you could potentially throw more than one monitor driver into the fray for PCs that switch monitors regularly, such that you could make your apps only use modes that work on all monitors. This also ties in sweetly with adding sprite/BOB/texture support to libGGI (or an extension thereof). Maybe Marcus and Andy could prioritize banging out the specs for this so that after I get done moving an obscene amount of large heavy objects into, out of, and around my apartment I can tear into it? -- Brian S. Julin "I love it when a plan comes together." -- That white haired boss-type-guy on the A-Team, whetever his name was. From ggi-develop-request@eskimo.com Tue Jun 15 23:16:49 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA03104 for ; Tue, 15 Jun 1999 23:16:48 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA32447; Tue, 15 Jun 1999 20:01:30 -0700 Resent-Date: Tue, 15 Jun 1999 20:01:30 -0700 From: Andrew Apted Message-ID: <19990616130641.60869@ajax.netspace.net.au> Date: Wed, 16 Jun 1999 13:06:41 +1000 To: ggi-develop@eskimo.com Subject: Re: First ggi project, need help Reply-To: ggi-develop@eskimo.com References: <19990615013529.C531@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from mongoose@ms241739.users.mindspring.com on Tue, Jun 15, 1999 at 12:58:18AM -0400 Resent-Message-ID: <"M8ADJ.0.iw7.8EnPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13347 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com mongoose@ms241739.users.mindspring.com writes: > How can it get it to stop blinking? It blinks mostly on the top with one > flush per loop. If I remove the flush or add more it blinks worse. > > In allegro ( I done the project in dos a long time ago ) I called vsync(). > I really don't understand all this bliting and buffer types. LibGGI does have a vsync like function, it is called something like WaitRayPos() and it is in the Misc extension. Nothing much implements though, so it probably won't help you much. Better is doing double buffering. When you set the ggi mode, request 2 frames, and use ggiSetDrawingFrame & ggiSetWriteFrame functions to flip between them (always drawing in the non-visible frame). When that doesn't work (sometimes 2 frames aren't available), your only other option is to draw everything into a memory buffer, and then ggiCrossBlit it to the real screen every frame. > Also how is the best way to impelement transparences and animation? > I can't use my ggi buffered images for these without drawing pixel by > pixel. ( slow ) Currently there is no LibGGI extensions for Sprites, but as far as I know it is being worked on. The only fast way right now is to get a DirectBuffer and do it yourself (easier might be: GetBox the affected area, modify the buffer directly, then PutBox it back). Hope that helps. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Wed Jun 16 06:13:09 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA07151 for ; Wed, 16 Jun 1999 06:13:08 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA03615; Wed, 16 Jun 1999 03:01:22 -0700 Resent-Date: Wed, 16 Jun 1999 03:01:22 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: libGGI on matroxfb with Mystique Date: Wed, 16 Jun 1999 12:02:06 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99061612035601.02005@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"KSTsL.0.Cu.jNtPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13348 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Wow, I started writing a benchmark program for ClanLib. The first test is filled rectangles: within 5 seconds 800x600x16 X 326 Xlib 75 fbdev 23576 <------------ What is this? Is it hardware accelerated? -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Wed Jun 16 06:39:25 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA07249 for ; Wed, 16 Jun 1999 06:39:24 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA06369; Wed, 16 Jun 1999 03:26:34 -0700 Resent-Date: Wed, 16 Jun 1999 03:26:34 -0700 Date: Wed, 16 Jun 1999 12:26:28 +0200 From: Erik Thiele To: ggi-develop@eskimo.com Subject: ggi rox Message-ID: <19990616122628.A9105@vulcain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Resent-Message-ID: <"2HIYQ3.0.JZ1.PltPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13349 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com hi. i just needed some graphical output to visualize the output of my numerical differential equation approximation simulation ;))) in the past i used DOS+borland+bgi for this. but since GGI i can now finally do this on linux too ! it is so easy. thanks for the great library cu erik -- EMAIL: erikyyy@studbox.uni-stuttgart.de \\\\ thieleek@tick.informatik.uni-stuttgart.de o `QQ'_ IRC: erikyyy / __8 WWW: http://wwwcip.rus.uni-stuttgart.de/~inf24628/ ' ` http://tick.informatik.uni-stuttgart.de/~thieleek/ From ggi-develop-request@eskimo.com Wed Jun 16 06:50:15 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA08015 for ; Wed, 16 Jun 1999 06:50:14 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA08063; Wed, 16 Jun 1999 03:38:55 -0700 Resent-Date: Wed, 16 Jun 1999 03:38:55 -0700 Sender: marcus@e.kth.se Message-ID: <37677EB7.6D0AC83C@stacken.kth.se> Date: Wed, 16 Jun 1999 10:38:47 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique References: <99061612035601.02005@master> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"mseKN1.0.jz1.-wtPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13350 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > > Wow, > > I started writing a benchmark program for ClanLib. > The first test is filled rectangles: > within 5 seconds 800x600x16 > X 326 > Xlib 75 > fbdev 23576 <------------ > > What is this? Is it hardware accelerated? Yes, as of LibGGI 2.0beta2.1 matroxfb is hardware accelerated. But the results are strange - unless you use very small boxes Xlib should be _much_ faster than X on a Matrox card. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 16 12:12:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA13749 for ; Wed, 16 Jun 1999 12:12:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA30906; Wed, 16 Jun 1999 08:56:26 -0700 Resent-Date: Wed, 16 Jun 1999 08:56:26 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Professional graphics Date: Wed, 16 Jun 1999 11:54:35 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99061611560700.21793@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"Y5Ic3.0.xT7.NayPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13351 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com What do proffessional companies use to do graphics for games in linux? Like for example Lokis? Do they use a specific library, or do they just use X? -Mongoose WPI student majoring in Computer Science and an over obsessed game fanatic. From ggi-develop-request@eskimo.com Wed Jun 16 12:55:37 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA14764 for ; Wed, 16 Jun 1999 12:55:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA12421; Wed, 16 Jun 1999 09:40:00 -0700 Resent-Date: Wed, 16 Jun 1999 09:40:00 -0700 From: mongoose@ms241739.users.mindspring.com Date: Wed, 16 Jun 1999 12:32:59 -0400 (EDT) Reply-To: "Terry 'Mongoose' Hendrix" To: Garrett B cc: ggi-develop@eskimo.com Subject: Re: Professional graphics In-Reply-To: <99061611560700.21793@mongoose> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"mRRnC2.0.o13.VDzPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13352 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 16 Jun 1999, Garrett B wrote: > What do proffessional companies use to do graphics for games in linux? Like >for example Lokis? Do they use a specific library, or do they just use X? I have wondered myself, gimp + blender is a pretty good package. However they may be using sgi or even *gasp photoshop on win32 for the gfx designers. I've never seen Lokis, sorry. You can use the developemnt kits for the graphics formats if you want. =) Oh, btw - I *love your nickname. =) later, Terry ( the other Mongoose ) --------------------------------------------------- | BotShop http://www.planetquake.com/botshop | | Personal http://www.westga.edu.com/~stu7440 | | | | Alita is running linux 2.2.9 w/ DoS fix | From ggi-develop-request@eskimo.com Wed Jun 16 13:05:08 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA14987 for ; Wed, 16 Jun 1999 13:05:07 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA18590; Wed, 16 Jun 1999 09:51:27 -0700 Resent-Date: Wed, 16 Jun 1999 09:51:27 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: Professional graphics Date: Wed, 16 Jun 1999 12:50:59 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: MIME-Version: 1.0 Message-Id: <99061612503300.22039@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"ctRnL.0.DY4.EOzPt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13353 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 16 Jun 1999, you wrote: > On Wed, 16 Jun 1999, Garrett B wrote: > > > What do proffessional companies use to do graphics for games in linux? Like > >for example Lokis? Do they use a specific library, or do they just use X? > > I have wondered myself, gimp + blender is a pretty good package. However > they may be using sgi or even *gasp photoshop on win32 for the gfx > designers. I've never seen Lokis, sorry. You can use the developemnt kits > for the graphics formats if you want. =) > > Oh, btw - I *love your nickname. =) Well what I meant before was graphics API's. Not GIMP type graphic programs to make .jpegs and stuff, I mean for programming and accessing the graphic hardware on the machine. Although browsing the Lokis (http://www.lokisoft.com/) tech support site I found this interesting little section, --From lokis In what environment does the game run? Does it run in X or from the console with SVGALIB? The Linux version ships with support for X11r6. We may support SVGALIB in the future and possibly GGI and MGL as well. If so, a free upgrade will be available for download. --end lokis So im guessing X11r6 is just a basic X-windows programming library? Heh and ya, when I saw your name in the email address I was wondering how my address got changed. =) From ggi-develop-request@eskimo.com Wed Jun 16 13:31:47 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA15711 for ; Wed, 16 Jun 1999 13:31:46 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA28845; Wed, 16 Jun 1999 10:17:09 -0700 Resent-Date: Wed, 16 Jun 1999 10:17:09 -0700 Sender: flo@sendnix.TELE.NET Message-ID: <376831C0.EE16CD3D@vol.at> Date: Wed, 16 Jun 1999 19:22:40 -0400 From: Scandella Florian X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.2.10 i686) MIME-Version: 1.0 To: "ggi-develop@eskimo.com" Subject: Re: Professional graphics References: <99061612503300.22039@mongoose> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Ua9bd3.0.Q27.JmzPt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13354 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B wrote: > So im guessing X11r6 is just a basic X-windows programming library? > > Heh and ya, when I saw your name in the email address I was wondering how my > address got changed. =) They are useing SDL ( Simple Directmedia Layer ). I think one of Loki has written it. http://www.devolution.com/~slouken/SDL/ Flo -- Scandella Florian scandella@vol.at Austria From ggi-develop-request@eskimo.com Wed Jun 16 13:56:19 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA16382 for ; Wed, 16 Jun 1999 13:56:18 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA06756; Wed, 16 Jun 1999 10:42:38 -0700 Resent-Date: Wed, 16 Jun 1999 10:42:38 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: Professional graphics Date: Wed, 16 Jun 1999 13:40:08 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <99061619173002.00258@starbase42> MIME-Version: 1.0 Message-Id: <99061613423700.22295@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"eIkbR1.0.Kf1.D8-Pt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13355 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 16 Jun 1999, you wrote: > Nope. X11R6 = X version 11 release 6. The guys at Loki are using SDL (the > Simple Direct media Layer) for interfacing with X. That's probably because > their head programmer (Sam Latinga, IIRC) authored that library (also, it > supported Win32 before GGI did, so it may be closer to the way DirectX works). > AFAIK, SDL includes support for sound and input devices. > Personally, I prefer libggi, though :) Theres so many different Graphics API's to choose from for linux. Its kinda confusing as to what to use. I guess Ill be using GGI for now though. From ggi-develop-request@eskimo.com Wed Jun 16 14:32:54 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA17262 for ; Wed, 16 Jun 1999 14:32:52 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA23237; Wed, 16 Jun 1999 11:19:24 -0700 Resent-Date: Wed, 16 Jun 1999 11:19:24 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: Professional graphics Date: Wed, 16 Jun 1999 14:19:04 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <99061620154903.00258@starbase42> MIME-Version: 1.0 Message-Id: <99061614185000.22469@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"dSR3x2.0.rg5.gg-Pt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13356 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 16 Jun 1999, you wrote: > Hi, > > > Theres so many different Graphics API's to choose from for linux. Its > > kinda confusing as to what to use. I guess Ill be using GGI for now though. > > Well, AFAIK there are the following graphics APIs available: > > SVGAlib: Evil (requires root suid to work), works only on some Intel-based > gnu-linux systems. > X/Xlib: Not exactly comfortable to program for. > XFree/DGA: Probably similar to normal X programming, but faster (I suppose ;-) > FBCon: Limited availability and mode switching, but it should be rather easy to > use (and fast (more or less)) > MDL: ? > Glide: Proprietary. 'nuff said ;-) > SDL: Currently does only Xlib and XFree/DGA. GGI support is planned, but I > haven't seen any code yet. SDL also includes some sound, input, and event > support. > GGI: Is the fastest broad-range solution available. Also, it has an API that I > personally like. Does SVGAlib, AALib, X, XLib, Glide, fbcon, and XFree/DGA. Did you mean MGL up there? Thats the scitech cross platform graphics library http://www.scitechsoft.com/devprod.html That looks like a fairly good library although I've never heard much about it. From ggi-develop-request@eskimo.com Wed Jun 16 15:28:07 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA18677 for ; Wed, 16 Jun 1999 15:28:05 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA14551; Wed, 16 Jun 1999 12:14:21 -0700 Resent-Date: Wed, 16 Jun 1999 12:14:21 -0700 Date: Wed, 16 Jun 1999 12:14:13 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique In-Reply-To: <37677EB7.6D0AC83C@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"8bUfH3.0._Y3.BU_Pt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13357 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 16 Jun 1999, Marcus Sundberg wrote: > Denis Oliver Kropp wrote: > > > > Wow, > > > > I started writing a benchmark program for ClanLib. > > The first test is filled rectangles: > > within 5 seconds 800x600x16 > > X 326 > > Xlib 75 > > fbdev 23576 <------------ > > > > What is this? Is it hardware accelerated? > > Yes, as of LibGGI 2.0beta2.1 matroxfb is hardware accelerated. > > But the results are strange - unless you use very small boxes > Xlib should be _much_ faster than X on a Matrox card. Is it because LibGGI uses async accels for the matroxfb target? Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Wed Jun 16 15:29:52 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA18724 for ; Wed, 16 Jun 1999 15:29:51 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA16746; Wed, 16 Jun 1999 12:18:35 -0700 Resent-Date: Wed, 16 Jun 1999 12:18:35 -0700 Date: Wed, 16 Jun 1999 12:18:27 -0700 (PDT) From: "Jon M. Taylor" To: "Brian S. Julin" cc: ggi-kgi@kludge.org, ggi-develop@eskimo.com Subject: Re: KGIcon 0.9 pre-alpha released In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"LRka43.0.G54.9Y_Pt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13358 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 15 Jun 1999, Brian S. Julin wrote: > On Tue, 15 Jun 1999, Jon M. Taylor wrote: > > > This should even allow to link all subdrivers statically and do the binding > > > with /proc... I have to think about this in detail. > > > > Yes, we need to plan this out. In fact the binding probably _will_ > > be static for the first Savage4 KGI driver beta. > > It's very encouraging seeing "the grand scheme" coalesce again, especially when > it's our two best kernel hackers talking. :) Unfortunately, I've lost my > notes from when I was trying to do this using evstacks. Never got far, but I > wish I could find the file that described the interface I was striving towards. > > One of the best features of this idea (IMO) was that you could potentially > throw more than one monitor driver into the fray for PCs that switch monitors > regularly, such that you could make your apps only use modes that work > on all monitors. Yes, this would be easily doable. > This also ties in sweetly with adding sprite/BOB/texture support to > libGGI (or an extension thereof). Maybe Marcus and Andy could prioritize > banging out the specs for this so that after I get done moving an > obscene amount of large heavy objects into, out of, and around my apartment I > can tear into it? I don't see the connection. Won't all the sprite/bob stuff be in userspace, unless the hardware supports them (Amiga, SVGA HW cursors, etc)? > -- > Brian S. Julin > "I love it when a plan comes together." > -- That white haired boss-type-guy on the A-Team, whetever his name was. John "Hannibal" Smith. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Wed Jun 16 16:09:51 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA19582 for ; Wed, 16 Jun 1999 16:09:50 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA30838; Wed, 16 Jun 1999 12:58:05 -0700 Resent-Date: Wed, 16 Jun 1999 12:58:05 -0700 Date: Wed, 16 Jun 1999 15:45:10 -0400 (EDT) From: Leimy To: ggi-develop@eskimo.com Subject: driver info. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"eUhbR.0.cX7.B70Qt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13359 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Well I have almost gone nuts looking for documentation for the Trident Chipset. None of what I have found is readable to me so I suppose I will have to throw in the towel. I really want to do something substantial this summer as far as linux programming goes. I am going to a computer show this weekend and will probably pick up a new graphics card there. I need to know though of the two which I should get. RIVA TNT or 3DFX? So far 3dFX controls the Windows market. But I see theTNT cards are holding their own. Documentation-wise TNT seems to be the way to go. Any suggestions especially relating to compatibility with this project would be greatly appreciated. Thanks Dave Leimbach From ggi-develop-request@eskimo.com Wed Jun 16 16:17:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA19720 for ; Wed, 16 Jun 1999 16:17:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA01663; Wed, 16 Jun 1999 13:06:03 -0700 Resent-Date: Wed, 16 Jun 1999 13:06:03 -0700 Sender: marcus@e.kth.se Message-ID: <376803A4.4F1AF5DC@stacken.kth.se> Date: Wed, 16 Jun 1999 20:05:56 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"reAEn2.0.iP.gE0Qt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13360 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > > On Wed, 16 Jun 1999, Marcus Sundberg wrote: > > > Denis Oliver Kropp wrote: > > > > > > Wow, > > > > > > I started writing a benchmark program for ClanLib. > > > The first test is filled rectangles: > > > within 5 seconds 800x600x16 > > > X 326 > > > Xlib 75 > > > fbdev 23576 <------------ > > > > > > What is this? Is it hardware accelerated? > > > > Yes, as of LibGGI 2.0beta2.1 matroxfb is hardware accelerated. > > > > But the results are strange - unless you use very small boxes > > Xlib should be _much_ faster than X on a Matrox card. > > Is it because LibGGI uses async accels for the matroxfb target? You read to fast. ;) matroxfb has little to do with the speed of X and Xlib. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 16 17:27:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA21516 for ; Wed, 16 Jun 1999 17:27:01 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA29870; Wed, 16 Jun 1999 14:14:43 -0700 Resent-Date: Wed, 16 Jun 1999 14:14:43 -0700 Sender: marcus@e.kth.se Message-ID: <376813BC.3D1C4684@stacken.kth.se> Date: Wed, 16 Jun 1999 21:14:36 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: driver info. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"4j5_T2.0.AI7.1F1Qt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13361 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Leimy wrote: > > Well I have almost gone nuts looking for documentation for the Trident > Chipset. None of what I have found is readable to me so I suppose I will > have to throw in the towel. I really want to do something substantial > this summer as far as linux programming goes. I am going to a computer > show this weekend and will probably pick up a new graphics card there. I > need to know though of the two which I should get. RIVA TNT or 3DFX? > > So far 3dFX controls the Windows market. But I see theTNT cards are > holding their own. > > Documentation-wise TNT seems to be the way to go. > > Any suggestions especially relating to compatibility with this project > would be greatly appreciated. Well TNT is already supported by KGIcon to some extent, while 3DFX doesn't seem likely to be supported by any free project within the forseeable future. 3DFX is even sueing Creative for implementing the Glide API for non 3DFX hardware... (Wonder if they will sue me for implementing part of the Glide API for no hardware ;) The Voodoo II and Voodoo Graphics has the advantage (if you already have a good 2D card) that you can keep your normal 2D card, hook up an extra monitor, and run normal LibGGI apps and XGGI on the 3DFX card. But with Voodoo 3 I see no advantage over a TNT card, especially as Voodoo 3 AFAIK isn't as good as the TNT (it doesn't support AGP texturing for example, so when textures are getting larger a Voodoo 3 will start crawling) //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 16 18:08:59 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA22279 for ; Wed, 16 Jun 1999 18:08:58 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA13938; Wed, 16 Jun 1999 14:57:15 -0700 Resent-Date: Wed, 16 Jun 1999 14:57:15 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique Date: Wed, 16 Jun 1999 23:54:24 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <37677EB7.6D0AC83C@stacken.kth.se> MIME-Version: 1.0 Message-Id: <99061623592800.04490@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"_0AyU1.0.SP3.vs1Qt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13362 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg´s crap from Mit, 16 Jun 1999: > Yes, as of LibGGI 2.0beta2.1 matroxfb is hardware accelerated. How is it possible, It even works for a normal user. Are the accelerations in matroxfb? > But the results are strange - unless you use very small boxes > Xlib should be _much_ faster than X on a Matrox card. even big boxes are very small, i use XFree 3.9Ps, maybe it is unaccelerated, I will try 3.3.3.1 tonight. I looked at ggiCrossBlit and hoped that it provides screen to screen blit. But the examples only show mem_vis->screen_vis. Is it impossible? Should I use ggiCopyBox and put the source images into the lower region of the screen (I mean virtual resolution higher than real). Also: What about blit with colorkeying? I need to blit transparent images. And: Alpha shaded rectangles? (possible, hardware?) -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Wed Jun 16 18:25:06 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA22611 for ; Wed, 16 Jun 1999 18:25:05 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA20748; Wed, 16 Jun 1999 15:13:20 -0700 Resent-Date: Wed, 16 Jun 1999 15:13:20 -0700 Sender: marcus@e.kth.se Message-ID: <37682160.332C7C82@stacken.kth.se> Date: Wed, 16 Jun 1999 22:12:48 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique References: <37677EB7.6D0AC83C@stacken.kth.se> <99061623592800.04490@master> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"dYeVI1.0.p35.-52Qt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13363 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > > Marcus Sundberg´s crap from Mit, 16 Jun 1999: > > > Yes, as of LibGGI 2.0beta2.1 matroxfb is hardware accelerated. > > How is it possible, It even works for a normal user. > Are the accelerations in matroxfb? matroxfb allows you to mmap() the accel registers as well as the framebuffer, so you just map it in and use the registers directly. > > But the results are strange - unless you use very small boxes > > Xlib should be _much_ faster than X on a Matrox card. > > even big boxes are very small, Umm, what do you mean by that? ;) > I looked at ggiCrossBlit and hoped that it provides screen to screen blit. > But the examples only show mem_vis->screen_vis. > Is it impossible? > > Should I use ggiCopyBox and put the source images into the > lower region of the screen (I mean virtual resolution higher than real). Currently either this, or use a separate frame for the source images and blit from that (use ggiSetReadFrame to select the source frame). > Also: What about blit with colorkeying? I need to blit transparent images. > And: Alpha shaded rectangles? (possible, hardware?) Someone will need to write an (or possibly more than one) extension to handle these things. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 16 18:52:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA23260 for ; Wed, 16 Jun 1999 18:52:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA03769; Wed, 16 Jun 1999 15:39:01 -0700 Resent-Date: Wed, 16 Jun 1999 15:39:01 -0700 Date: Wed, 16 Jun 1999 18:25:54 -0400 (EDT) From: Leimy To: Marcus Sundberg cc: ggi-develop@eskimo.com Subject: Re: driver info. In-Reply-To: <376813BC.3D1C4684@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"8eWr12.0.xt._T2Qt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13364 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I almost forgot to mention I only have PCI and ISA ports no AGP. I am one of those continuous upgraders who didn't think far enough ahead on last years motherboard purchase. dave > Leimy wrote: > > > > Well I have almost gone nuts looking for documentation for the Trident > > Chipset. None of what I have found is readable to me so I suppose I will > > have to throw in the towel. I really want to do something substantial > > this summer as far as linux programming goes. I am going to a computer > > show this weekend and will probably pick up a new graphics card there. I > > need to know though of the two which I should get. RIVA TNT or 3DFX? > > > > So far 3dFX controls the Windows market. But I see theTNT cards are > > holding their own. > > > > Documentation-wise TNT seems to be the way to go. > > > > Any suggestions especially relating to compatibility with this project > > would be greatly appreciated. > > Well TNT is already supported by KGIcon to some extent, while 3DFX > doesn't seem likely to be supported by any free project within > the forseeable future. 3DFX is even sueing Creative for implementing > the Glide API for non 3DFX hardware... > (Wonder if they will sue me for implementing part of the Glide API > for no hardware ;) > > The Voodoo II and Voodoo Graphics has the advantage (if you already > have a good 2D card) that you can keep your normal 2D card, hook up > an extra monitor, and run normal LibGGI apps and XGGI on the 3DFX card. > But with Voodoo 3 I see no advantage over a TNT card, especially > as Voodoo 3 AFAIK isn't as good as the TNT (it doesn't support AGP > texturing for example, so when textures are getting larger a Voodoo 3 > will start crawling) > > //Marcus > -- > -------------------------------+------------------------------------ > Marcus Sundberg | http://www.stacken.kth.se/~mackan/ > Royal Institute of Technology | Phone: +46 707 295404 > Stockholm, Sweden | E-Mail: mackan@stacken.kth.se > > From ggi-develop-request@eskimo.com Wed Jun 16 21:14:09 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA25025 for ; Wed, 16 Jun 1999 21:14:08 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA29834; Wed, 16 Jun 1999 17:54:40 -0700 Resent-Date: Wed, 16 Jun 1999 17:54:40 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique Date: Thu, 17 Jun 1999 00:19:13 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <37682160.332C7C82@stacken.kth.se> MIME-Version: 1.0 Message-Id: <99061700293501.04490@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"xWqp-3.0.tH7.ET4Qt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13365 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg´s crap from Don, 17 Jun 1999: > matroxfb allows you to mmap() the accel registers as well as the > framebuffer, so you just map it in and use the registers directly. Ah, my normal user has access to /dev/mem. Do the kgi drivers work like this or are they kernel modules? > > > But the results are strange - unless you use very small boxes > > > Xlib should be _much_ faster than X on a Matrox card. > > > > even big boxes are very small, > > Umm, what do you mean by that? ;) Funny, I mean "even big boxes are slow" ;-) > > I looked at ggiCrossBlit and hoped that it provides screen to screen blit. > > But the examples only show mem_vis->screen_vis. > > Is it impossible? > > > > Should I use ggiCopyBox and put the source images into the > > lower region of the screen (I mean virtual resolution higher than real). > > Currently either this, or use a separate frame for the source images > and blit from that (use ggiSetReadFrame to select the source frame). Which targets support accelerated ggiCopyBox? > > Also: What about blit with colorkeying? I need to blit transparent images. > > And: Alpha shaded rectangles? (possible, hardware?) > > Someone will need to write an (or possibly more than one) extension to > handle these things. I will have a look at extensions. Another problem: The glide target worked very well and fast without DirectBuffer (using ggiPutBox for system backbuffer). But when I use DirectBuffer on it, it is much slower 66->20 fps. Maybe the system memory works as a buffer which handles the blits of small images better than writing each of them over the bus. Are there any MTRR regions I could set for my Voodoo2? -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Wed Jun 16 21:54:00 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA25528 for ; Wed, 16 Jun 1999 21:53:59 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id SAA11324; Wed, 16 Jun 1999 18:39:45 -0700 Resent-Date: Wed, 16 Jun 1999 18:39:45 -0700 X-Authentication-Warning: mir.static.net: tetron owned process doing -bs Date: Wed, 16 Jun 1999 21:48:58 -0400 (EDT) From: Peter Amstutz X-Sender: tetron@mir.static.net Reply-To: tetron@student.umass.edu To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique In-Reply-To: <99061700293501.04490@master> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"kdK732.0.Ym2.V75Qt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13366 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Denis Oliver Kropp wrote: > Another problem: > The glide target worked very well and fast without DirectBuffer (using ggiPutBox for system > backbuffer). But when I use DirectBuffer on it, it is much slower 66->20 fps. > Maybe the system memory works as a buffer which handles > the blits of small images better than writing each of them over the bus. I think frame buffer access from the bus for the voodoo1/2 is generally very slow because it was optimized to be accessed from the on-card rendering chips, not directly from the CPU. On the other hand you have to do a lot of large texture downloads, so it's probably optimized for burst performance over the PCI bus. That would be my guess as to why you'd get a slowdown with DirectBuffer... Of course it would be really cool if someone were to write a glide-specific sprite extension library that downloaded sprits as textures (with transparency info) to the 3dfx and used the on-card texturemapping accel to display them :) Does libggi2d do sprites even in software yet? ------------------ Peter Amstutz -------------------- -------------- tetron@student.umass.edu ------------- ------- http://www-unix.oit.umass.edu/~tetron ------- ----------------------------------------------------- From ggi-develop-request@eskimo.com Thu Jun 17 01:43:12 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA29355 for ; Thu, 17 Jun 1999 01:43:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA21845; Wed, 16 Jun 1999 22:30:15 -0700 Resent-Date: Wed, 16 Jun 1999 22:30:15 -0700 Date: Thu, 17 Jun 1999 02:15:34 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: GII nitpicks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"59Hm23.0.1L5.bV8Qt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13367 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Barring any intrusion by the "real world" expect a GII:: perl5 XS module set tomorrow evening my time. I really don't care much about input handling personally, but wanted the modules done right as perl may be a great language but doesn't always promote great code :-}. Some people even seem to forget it's OO. Anyway I can't believe I spent so much time writing this just so I could subclass GGI:: objects under it on mere principle :) So, I need someone very familiar with LibGII and somewhat Perl literate to run it into the ground and find the bugs, and to write the source tree test suite which is pretty basic at the moment. This was the first time I really looked at LibGII hard, and I have come up with a couple of nitpicks with the GII API. 1) The order of the h,w members of gii_expose_event is counterintuitive. Not worth breaking binary compatibility over of course. (Perhaps we should decide what version bump of GGI/GII is going to break binary compatibility beforehand and then we could add #if directives to implement the change when we bump the version, then take them out at our leisure. That way noone has to keep a big list of trivial unimportant changes.) 2) There should be an evPtrButtonRepeat event. For two reasons. One is that Vojtech's new input drivers implement soft repeat for mice buttons. The other reason pertains to press-and-hold functions e.g. the way MAC OS lets you edit the filename on an icon. Apps wanting this type of interface can just wait for N repeat events. This gives the user a system wide way to configure the mouse press-and-hold "responsiveness" by setting the mouse repeat rate. This would typically be on the order of > 0.5 seconds so it wouldn't cause a flood of events. 3) Not sure I like the fact that a joined input effectively destroys the old event handles, but I've a workaround. Seems a bit tacky, though. 4) Default quit handler on CTRL-C for would be nice if it could be made to gracefully get out of the way of non-newbies and their signal/event handlers. Couple other questions: Under what normal (app, not library) circumstances would one call g(g|i)iInit() more than once? Currently my modules call it when the package is use()d, but if there's a reason to offer calling it again in the Perl5 API I want to. Is the #if 0'd filter stuff on the way in, or on the way out? Docs available anywhere if the former? P.S. Oh, Vojtech's softrepeat code I believe has hooks for setting repeat rates on individual keys/buttons; somone may want to standardize a set of commands to deal with this. Also, is there a standard way to tell an input driver to switch to using valuator events and drop the prefab Ptr events, JOOC? -- Brian S. Julin From ggi-develop-request@eskimo.com Thu Jun 17 03:40:58 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA00958 for ; Thu, 17 Jun 1999 03:40:55 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA14042; Thu, 17 Jun 1999 00:28:09 -0700 Resent-Date: Thu, 17 Jun 1999 00:28:09 -0700 Sender: marcus@e.kth.se Message-ID: <3768A37F.29EE105D@stacken.kth.se> Date: Thu, 17 Jun 1999 07:27:59 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: GII nitpicks References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"h6riU3.0.WQ3.5EAQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13368 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Brian S. Julin wrote: > 1) The order of the h,w members of gii_expose_event is > counterintuitive. Not worth breaking binary compatibility > over of course. (Perhaps we should decide what version bump of > GGI/GII is going to break binary compatibility beforehand and > then we could add #if directives to implement the change > when we bump the version, then take them out at our leisure. That > way noone has to keep a big list of trivial unimportant changes.) Ouch! Know I see what you mean. Weird... This should be changed for the next beta. Very few applications (any other than nixterm?) use those parameters anyway. > 2) There should be an evPtrButtonRepeat event. For two reasons. > One is that Vojtech's new input drivers implement soft repeat for > mice buttons. The other reason pertains to press-and-hold > functions e.g. the way MAC OS lets you edit the filename on an icon. > Apps wanting this type of interface can just wait for N repeat events. > This gives the user a system wide way to configure the mouse > press-and-hold "responsiveness" by setting the mouse repeat rate. > This would typically be on the order of > 0.5 seconds so it wouldn't > cause a flood of events. Yes, this should be added when we have an input driver that generates repeat events for mouse buttons. > 3) Not sure I like the fact that a joined input effectively > destroys the old event handles, but I've a workaround. Seems > a bit tacky, though. There is already planned a giiDup() function call, which among other things will allow you to do giiJoinInputs(inp1, giiDup(inp2)); If you explain what you want to do and why it may be possible to adapt this for your purpose too. > 4) Default quit handler on CTRL-C for would be nice if it could > be made to gracefully get out of the way of non-newbies and their > signal/event handlers. This is easy to implement as a filter. > Couple other questions: > > Under what normal (app, not library) circumstances would one call > g(g|i)iInit() more than once? There is no reason to call them more than once, it's just allowed for convenience. > Is the #if 0'd filter stuff on the way in, or on the way out? Already gone. Filters are now the same as inputs. > P.S. Oh, Vojtech's softrepeat code I believe has hooks for setting > repeat rates on individual keys/buttons; somone may want to standardize a set > of commands to deal with this. This is not something that apps has to care or know about. It should be handled with a config file specific to the inputlib in question. Someone is welcome to suggest a standard format for this file and implement a parser. > Also, is there a standard way to tell > an input driver to switch to using valuator events and drop the > prefab Ptr events, JOOC? No. Such things should be handled by separate filters, or ideally you should use LibGIC. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Thu Jun 17 03:46:56 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA01059 for ; Thu, 17 Jun 1999 03:46:55 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA14976; Thu, 17 Jun 1999 00:35:13 -0700 Resent-Date: Thu, 17 Jun 1999 00:35:13 -0700 Sender: marcus@e.kth.se Message-ID: <3768A529.128D957@stacken.kth.se> Date: Thu, 17 Jun 1999 07:35:05 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"djDHN.0.jf3.mKAQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13369 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Peter Amstutz wrote: > Does libggi2d do sprites even in software yet? You can not do sprites in software. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Thu Jun 17 03:54:29 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA01115 for ; Thu, 17 Jun 1999 03:54:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA15797; Thu, 17 Jun 1999 00:42:01 -0700 Resent-Date: Thu, 17 Jun 1999 00:42:01 -0700 From: becka@rz.uni-duesseldorf.de Message-Id: <199906170740.JAA28481@zeus.rz.uni-duesseldorf.de> Subject: Re: GII nitpicks In-Reply-To: <3768A37F.29EE105D@stacken.kth.se> from Marcus Sundberg at "Jun 17, 99 07:27:59 am" To: ggi-develop@eskimo.com Date: Thu, 17 Jun 1999 09:40:54 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"fVI2N.0.bs3.8RAQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13370 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > 2) There should be an evPtrButtonRepeat event. For two reasons. > Yes, this should be added when we have an input driver that generates > repeat events for mouse buttons. IMHO we should rather start to move the mouse drivers to be valuator/key devices just like joysticks are and autoload the mouse translator module. The evPtr stuff is IMHO a relic of old apps expecting a separated Mouse and Keyboard and nothing else. The concept of only having keys and valuators is much nicer IMHO. > > Under what normal (app, not library) circumstances would one call > > g(g|i)iInit() more than once? > There is no reason to call them more than once, it's just allowed > for convenience. This is intended for wrappers, helper libs, extensions, whatever. Say you for some reason have a program that uses LibGGI directly _and_ a lib that uses LibGGI internally either for output or e.g. to generate gifs using a file target. Then both would call ggiInit and exit at their entry/exit points, and we would get a double-cleanup, if this counting behaviour wouldn't be there. > > Also, is there a standard way to tell > > an input driver to switch to using valuator events and drop the > > prefab Ptr events, JOOC? > No. Such things should be handled by separate filters, or ideally > you should use LibGIC. As I said above, it would be a good idea to have everything report valuators (especially as one can query their properties) and have a filter do the translation. Adding valuators to the mouse filter should be just as trivial as adding a "donteatoriginalevent" flag which might be convenient sometimes. CU, Andy -- Andreas Beck | Email : From ggi-develop-request@eskimo.com Thu Jun 17 04:12:20 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA01251 for ; Thu, 17 Jun 1999 04:12:19 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA17655; Thu, 17 Jun 1999 00:59:33 -0700 Resent-Date: Thu, 17 Jun 1999 00:59:33 -0700 Sender: Rodolphe.Ortalo@cert.fr Message-ID: <3768AAA9.2D31@cert.fr> Date: Thu, 17 Jun 1999 09:58:33 +0200 From: Rodolphe Ortalo Organization: ONERA X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.6 sun4m) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique References: <3768A529.128D957@stacken.kth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"GCS5g3.0.aJ4.ahAQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13371 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg wrote: > Peter Amstutz wrote: > > Does libggi2d do sprites even in software yet? > > You can not do sprites in software. Why do you insist on that Marcus? You can not move sprites, but, at least, a software lib could draw them, no ? (This corresponds to using a pixel-precision mask, unless I'm mistaken.) Maybe glyphs that cannot be moved around do not deserve the 'sprites' denomination, but wouldn't it be useful to have a draw-only thing ? (With {fb,main}memory management, hw-accel. drawing, etc.) Of course, it may not be worth a specific API as one can already achieve something similar using a virtual area and conventional blitting... Rodolphe From ggi-develop-request@eskimo.com Thu Jun 17 09:12:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA04116 for ; Thu, 17 Jun 1999 09:12:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA01615; Thu, 17 Jun 1999 05:57:55 -0700 Resent-Date: Thu, 17 Jun 1999 05:57:55 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Sucking the marrow out of hardware (Re: libGGI on matroxfb with Mystique) Date: Thu, 17 Jun 1999 14:47:20 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <37677EB7.6D0AC83C@stacken.kth.se> MIME-Version: 1.0 Message-Id: <99061714590700.00896@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"xNwgG1.0.qO.C3FQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13372 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg´s crap from Mit, 16 Jun 1999: > Denis Oliver Kropp wrote: > > > > Wow, > > > > I started writing a benchmark program for ClanLib. > > The first test is filled rectangles: > > within 5 seconds 800x600x16 > > X 326 > > Xlib 75 > > fbdev 23576 <------------ > > > > What is this? Is it hardware accelerated? > > Yes, as of LibGGI 2.0beta2.1 matroxfb is hardware accelerated. > > But the results are strange - unless you use very small boxes > Xlib should be _much_ faster than X on a Matrox card. Oops, I saw that I use ggiDrawBox only on DirectBuffer targets. The problem is, that ClanLib has its software rendering, this rendering is done on a backbuffer, this backbuffer is in system memory (using final ggiPutBox) if there is no DirectBuffer support. So a call to ggiDrawBox with Xlib would draw the box in video mem and the final ggiPutBox of ClanLib´s backbuffer would overwrite it. A solution would be to implement ALL rendering using ggi calls, but problems are alpharects, transblits, blits with alpha channel, ... ----- Which targets don´t support blitting from offscreen space? Are they emulated then? (sysmem or vidmem, does not matter) This means: Can I do the following steps with every target? 1. Create a visual with virtual height greater than visible height. 2. ggiPutBox into the resulting "dead" area. 3. ggiCopyBox from them. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Thu Jun 17 10:00:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA04987 for ; Thu, 17 Jun 1999 10:00:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA18028; Thu, 17 Jun 1999 06:46:52 -0700 Resent-Date: Thu, 17 Jun 1999 06:46:52 -0700 Date: Thu, 17 Jun 1999 10:32:26 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique In-Reply-To: <3768AAA9.2D31@cert.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"FgDuF2.0.SP4.AnFQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13373 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Rodolphe Ortalo wrote: > Maybe glyphs that cannot be moved around do not > deserve the 'sprites' denomination, Right -- sprites is a term reserved for overlays that can be moved around without corrupting the data underneath them or interfering with drawing operations which intersect them. > but wouldn't > it be useful to have a draw-only thing ? (With > {fb,main}memory management, hw-accel. drawing, etc.) That's a "BOB" (Blitter OBject). Those can be software emulated. Sprites can too but in a very clumsy inefficient way (you have to hide/unhide them before and after drawing apps.) While I'd probably leave the door open a crack for doing this, it won't be the preferred mode of operation by any long shot. (Something like "here are the hide/unhide function stubs; if you want your app to work on targets that have to emulate sprites, use them, but if that would be too slow for your app anyway, don't bother.") > Of course, it may not be worth a specific API as one > can already achieve something similar using a virtual > area and conventional blitting... It's worth it when you want to use a lower color depth on the BOBs to conserve memory, because then you have something between CopyBox and CrossBlit when the BOB actually is in the video memory. -- Brian From ggi-develop-request@eskimo.com Thu Jun 17 13:41:43 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA10989 for ; Thu, 17 Jun 1999 13:41:42 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA17011; Thu, 17 Jun 1999 10:29:10 -0700 Resent-Date: Thu, 17 Jun 1999 10:29:10 -0700 Date: Thu, 17 Jun 1999 13:26:47 -0400 (EDT) From: Peter I Amstutz Subject: Re: libGGI on matroxfb with Mystique In-reply-to: <3768A529.128D957@stacken.kth.se> X-Sender: tetron@wilde.oit.umass.edu To: ggi-develop@eskimo.com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Authentication-warning: wilde.oit.umass.edu: tetron owned process doing -bs Resent-Message-ID: <"u022r.0.284.81JQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13374 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Marcus Sundberg wrote: > Peter Amstutz wrote: > > Does libggi2d do sprites even in software yet? > > You can not do sprites in software. Alright, let me restate that: is there libggi2d support for drawing images with transparency or stenciling quickly with the specialized purpose of doing small-animated-images-moving-around-against-a-background in software or hardware? ------------------ Peter Amstutz -------------------- -------------- tetron@student.umass.edu ------------- ------- http://www-unix.oit.umass.edu/~tetron ------- ----------------------------------------------------- From ggi-develop-request@eskimo.com Thu Jun 17 14:20:40 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA12075 for ; Thu, 17 Jun 1999 14:20:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA01502; Thu, 17 Jun 1999 11:09:33 -0700 Resent-Date: Thu, 17 Jun 1999 11:09:33 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990617191255.B494@rz.uni-duesseldorf.de> Date: Thu, 17 Jun 1999 19:12:55 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique Mail-Followup-To: ggi-develop@eskimo.com References: <37682160.332C7C82@stacken.kth.se> <99061700293501.04490@master> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99061700293501.04490@master>; from Denis Oliver Kropp on Thu, Jun 17, 1999 at 12:19:13AM +0200 Resent-Message-ID: <"6K3VX.0.FN.RdJQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13375 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > matroxfb allows you to mmap() the accel registers as well as the > > framebuffer, so you just map it in and use the registers directly. > Ah, my normal user has access to /dev/mem. No - that's not needed You need access to /dev/fb*. After the FB, the accel regs are mapped. > Do the kgi drivers work like this or are they kernel modules? They are kernel modules, but they can as well do the same trick. > > Currently either this, or use a separate frame for the source images > > and blit from that (use ggiSetReadFrame to select the source frame). > Which targets support accelerated ggiCopyBox? Fbdev and xlib come to mind. Glide maybe ? > The glide target worked very well and fast without DirectBuffer (using ggiPutBox for system > backbuffer). But when I use DirectBuffer on it, it is much slower 66->20 fps. > Maybe the system memory works as a buffer which handles > the blits of small images better than writing each of them over the bus. > Are there any MTRR regions I could set for my Voodoo2? IIRC the Glide stuff starts to crawl when accessed as vidram. And if you need a lot of lock/unlock that might take time as well. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Thu Jun 17 14:21:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA12101 for ; Thu, 17 Jun 1999 14:21:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA01662; Thu, 17 Jun 1999 11:10:00 -0700 Resent-Date: Thu, 17 Jun 1999 11:10:00 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990617193649.A531@rz.uni-duesseldorf.de> Date: Thu, 17 Jun 1999 19:36:49 +0200 From: Andreas Beck To: mailing list GGI Subject: Re: Professional graphics Mail-Followup-To: mailing list GGI References: <99061620154903.00258@starbase42> <99061614185000.22469@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99061614185000.22469@mongoose>; from Garrett B on Wed, Jun 16, 1999 at 02:19:04PM -0500 Resent-Message-ID: <"duX4i2.0.aP.rdJQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13376 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > MDL: ? > Did you mean MGL up there? Thats the scitech cross platform graphics > library http://www.scitechsoft.com/devprod.html BTW: Why don't we have a target for that ... doesn't anyone use it ? CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Thu Jun 17 14:22:55 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA12145 for ; Thu, 17 Jun 1999 14:22:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA01727; Thu, 17 Jun 1999 11:10:04 -0700 Resent-Date: Thu, 17 Jun 1999 11:10:04 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990617193748.B531@rz.uni-duesseldorf.de> Date: Thu, 17 Jun 1999 19:37:48 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: ggi rox Mail-Followup-To: ggi-develop@eskimo.com References: <19990616122628.A9105@vulcain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990616122628.A9105@vulcain>; from Erik Thiele on Wed, Jun 16, 1999 at 12:26:28PM +0200 Resent-Message-ID: <"DhwBc3.0.SQ.vdJQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13377 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > i just needed some graphical output to visualize the output > of my numerical differential equation approximation simulation ;))) > in the past i used DOS+borland+bgi for this. > but since GGI i can now finally do this on linux too ! *grin* I'm doing similar things with it (visualizing measurement data) :-) Funny. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Thu Jun 17 14:23:20 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA12158 for ; Thu, 17 Jun 1999 14:23:19 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA01765; Thu, 17 Jun 1999 11:10:07 -0700 Resent-Date: Thu, 17 Jun 1999 11:10:07 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990617201154.F531@rz.uni-duesseldorf.de> Date: Thu, 17 Jun 1999 20:11:54 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique Mail-Followup-To: ggi-develop@eskimo.com References: <37677EB7.6D0AC83C@stacken.kth.se> <99061623592800.04490@master> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99061623592800.04490@master>; from Denis Oliver Kropp on Wed, Jun 16, 1999 at 11:54:24PM +0200 Resent-Message-ID: <"KaZfx3.0.lQ.wdJQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13378 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Yes, as of LibGGI 2.0beta2.1 matroxfb is hardware accelerated. > How is it possible, It even works for a normal user. > Are the accelerations in matroxfb? Yes and no. matroxfb give an extra piece of "memory" that is mapped after the framebuffer. This is a map to the cards accel regs. > I looked at ggiCrossBlit and hoped that it provides screen to screen blit. It does, but that's a bit slow. It is intended for blitting between different visuals > But the examples only show mem_vis->screen_vis. > Is it impossible? No. You can copy vis->same_vis, but that's not the fastest way to do it. > Should I use ggiCopyBox and put the source images into the > lower region of the screen (I mean virtual resolution higher than real). Yes. As long as this is available, it should be pretty fast. > Also: What about blit with colorkeying? I need to blit transparent images. > And: Alpha shaded rectangles? (possible, hardware?) LibGGI2D might take care of that. Haven't looked for a while, though. cU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Thu Jun 17 14:25:13 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA12200 for ; Thu, 17 Jun 1999 14:25:12 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA01806; Thu, 17 Jun 1999 11:10:12 -0700 Resent-Date: Thu, 17 Jun 1999 11:10:12 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990617195149.D531@rz.uni-duesseldorf.de> Date: Thu, 17 Jun 1999 19:51:49 +0200 From: Andreas Beck To: "Terry 'Mongoose' Hendrix" Cc: mailing list GGI Subject: Re: First ggi project, need help Mail-Followup-To: Terry 'Mongoose' Hendrix , mailing list GGI References: <19990616010350.C578@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from mongoose on Tue, Jun 15, 1999 at 11:41:17PM -0400 Resent-Message-ID: <"3Wvj73.0.tR.0eJQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13379 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > >If these repeatedly draw to the same regions, this can cause flashing. > >Calling Flush() is a NOOP on directly mapped targets like fbcon. > I may have forgot to mention I was X target. Ah. On the X target, ggiFlush() in deed _does_ flush the screen. On X enabling ASYNC mode might cure your problem, as there will be no interfering automatic syncs, then. > oops. Ggi svga wrapper locks up on me, Take care about the vocabulary here: the SVGAlib _wrapper_ is the lib that lets SVGAlib apps run on LibGGI. The SVGAlib _target_ is what makes LibGGI display via a true SVGAlib. > and the matrox fb seems to be worse. Regarding blinking ? Yes, that is due to the way you draw probably. Can you put up the source somewhere, so we can have a look ? > I'm generally drawing a 640x480 image from a ggi buffer in memory, then > drawing other images over that for docks, text, and buttons. I haven't > got scaling started yet, so this is 1:1 drawing. So you probably see the "old" gadgets get overwritten by the background, and the reappearing - right ? You will either have to use doublebuffering or a clever updating scheme, that only updates what must be updated. A very simple way would be to draw on a memvisual and then crossblit it to screen. > Oh... I'm using ggi for svga/win32/x11 portability. I guess I need to > grep the headers. =/ Oh yes ... good you remind me of it ... got to hack some win :-) ... > >Hmm - you're not the first to notice that ... Seems we need to write > >something up. We expected people to do what most of us would do ... > >ignore the docs and look at some sample code ... > I used all the sample code I could find, it's just I can't find sprite > like methods for ggi. Yes. LibGGI is very basic. It has no sprite methods. This is scheduled for an extension ... I'll try to get into that business with Marcus ASAP. CU, ANdy > I'm tring to write my own, but I have no book on > grpahics and I can't find detailed API docs. Simple BOBs should be relatively trivial. Basically you go through then pixel by pixel and blit if the color is not the "transparent" key color. The cube3d demo shows some ways to do it. > >BTW: I started writing a file called "The big dummies guide to graphics > >programming" a while ago ... I haven't worked on it for quite some time > >... anyone here to take it an improve it ? > Are you going to release that as a living document to the ggi list? > Living documents for programming guides are always very helpful. If you > send out copies I'll take one. ;) I'll upload it into the repository. Should appear in the snapshots, then. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Thu Jun 17 15:13:48 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA13649 for ; Thu, 17 Jun 1999 15:13:47 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA22338; Thu, 17 Jun 1999 11:59:48 -0700 Resent-Date: Thu, 17 Jun 1999 11:59:48 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: ggi rox Date: Thu, 17 Jun 1999 14:56:53 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <19990617193748.B531@rz.uni-duesseldorf.de> MIME-Version: 1.0 Message-Id: <99061714594301.01916@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"DYQ_u1.0.oS5.UMKQt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13380 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Andreas Beck wrote: > > i just needed some graphical output to visualize the output > > of my numerical differential equation approximation simulation ;))) > > in the past i used DOS+borland+bgi for this. > > but since GGI i can now finally do this on linux too ! > > *grin* I'm doing similar things with it (visualizing measurement data) :-) > Funny. Im making another scorched earth clone to learn linux. Im trying to make my transition from Windows to Linux now. Its amazing how a huge API like DirectX doesn't even have a simple function for drawing a horizontal line. And debugging a directX app was impossible unlike GGI with DDD. aaahh I love DDD..... From ggi-develop-request@eskimo.com Thu Jun 17 15:16:26 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA13687 for ; Thu, 17 Jun 1999 15:16:25 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id MAA14314; Thu, 17 Jun 1999 12:04:12 -0700 (PDT) Resent-Date: Thu, 17 Jun 1999 12:04:12 -0700 (PDT) From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: Professional graphics Date: Thu, 17 Jun 1999 14:51:53 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <19990617193649.A531@rz.uni-duesseldorf.de> MIME-Version: 1.0 Message-Id: <99061714563900.01916@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"AQDm8.0.1V3.sPKQt"@mx2> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13381 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Andreas Beck wrote: > > > MDL: ? > > Did you mean MGL up there? Thats the scitech cross platform graphics > > library http://www.scitechsoft.com/devprod.html > > BTW: Why don't we have a target for that ... doesn't anyone use it ? I tried it for windows once It didn't seem like anything great. And I think they expect you to buy the books of documentation to use it. BTW why does GGI target so many different libraries? I mean shouldn't it just target the basic low level stuff of the system like SVGAlib, xlib, DirectX, the basics of each platform. Why target other libraries too? From ggi-develop-request@eskimo.com Thu Jun 17 15:20:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA13799 for ; Thu, 17 Jun 1999 15:20:00 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA24983; Thu, 17 Jun 1999 12:08:23 -0700 Resent-Date: Thu, 17 Jun 1999 12:08:23 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Date: Thu, 17 Jun 1999 15:07:10 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99061715081602.01916@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"JDyo92.0.366.bUKQt"@mx1> Resent-From: ggi-develop@eskimo.com Subject: Unidentified subject! X-Mailing-List: archive/latest/13382 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Where do I get the libggi2d library? I can't find it on the ftp. -- -Mongoose WPI student majoring in Computer Science and an over obsessed game fanatic. From ggi-develop-request@eskimo.com Thu Jun 17 15:58:30 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA14839 for ; Thu, 17 Jun 1999 15:58:27 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA08700; Thu, 17 Jun 1999 12:46:34 -0700 Resent-Date: Thu, 17 Jun 1999 12:46:34 -0700 Date: Thu, 17 Jun 1999 15:44:49 -0400 (EDT) From: Peter I Amstutz Subject: Re: ggi rox In-reply-to: <99061714594301.01916@mongoose> X-Sender: tetron@wilde.oit.umass.edu To: ggi-develop@eskimo.com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Authentication-warning: wilde.oit.umass.edu: tetron owned process doing -bs Resent-Message-ID: <"1X1lh3.0.h72.P2LQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13383 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Garrett B wrote: > Im making another scorched earth clone to learn linux. Im trying to > make my transition from Windows to Linux now. Its amazing how a huge API like > DirectX doesn't even have a simple function for drawing a horizontal line. And > debugging a directX app was impossible unlike GGI with DDD. aaahh I love > DDD..... Hmmm, I'm way ahead of you. I've been working on a sc*ch*d **rth clone called "King of the Hill" (KOTH). It's fully client/server networked for multiplayer, uses GGI, and I've put in quite a bit of work to make it extensible and fairly easy to hack on... Right now I have a todo list of things I wanted to do before release, but if you're really interested I could go ahead and just dump the source to the world now... It's not as portable as I'd like, and there are of course bugs, but then again it does at least compile :) You can see a couple of pre-pre-pre-alpha-prototype screenshots here: http://www-unix.oit.umass.edu/~tetron/king.html The real game does more than these pictures reveal, of course :) ------------------ Peter Amstutz -------------------- -------------- tetron@student.umass.edu ------------- ------- http://www-unix.oit.umass.edu/~tetron ------- ----------------------------------------------------- From ggi-develop-request@eskimo.com Thu Jun 17 16:02:11 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA14922 for ; Thu, 17 Jun 1999 16:02:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA10406; Thu, 17 Jun 1999 12:49:48 -0700 Resent-Date: Thu, 17 Jun 1999 12:49:48 -0700 Date: Thu, 17 Jun 1999 15:49:21 -0400 (EDT) From: Peter I Amstutz Subject: Re: Professional graphics In-reply-to: <99061714563900.01916@mongoose> X-Sender: tetron@wilde.oit.umass.edu To: ggi-develop@eskimo.com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Authentication-warning: wilde.oit.umass.edu: tetron owned process doing -bs Resent-Message-ID: <"4AUkR1.0.CY2.Q5LQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13384 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Garrett B wrote: > BTW why does GGI target so many different libraries? I mean shouldn't > it just target the basic low level stuff of the system like SVGAlib, xlib, > DirectX, the basics of each platform. Why target other libraries too? Because we can :) In fact the libGGI structure was originally meant primarily (and still is) to handle card-specific lowlevel userspace accleration libraries for various video hardware, which would be loaded at runtime. Since KGI got a bit... delayed, people turned to writing targets for other display methods. It really shows off libGGI's flexibility, even if it is really just ad-hoc object-oriented programming in C :) ------------------ Peter Amstutz -------------------- -------------- tetron@student.umass.edu ------------- ------- http://www-unix.oit.umass.edu/~tetron ------- ----------------------------------------------------- From ggi-develop-request@eskimo.com Thu Jun 17 16:15:54 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA15211 for ; Thu, 17 Jun 1999 16:15:52 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA17123; Thu, 17 Jun 1999 13:04:05 -0700 Resent-Date: Thu, 17 Jun 1999 13:04:05 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990617203117.C735@rz.uni-duesseldorf.de> Date: Thu, 17 Jun 1999 20:31:17 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Sucking the marrow out of hardware (Re: libGGI on matroxfb with Mystique) Mail-Followup-To: ggi-develop@eskimo.com References: <37677EB7.6D0AC83C@stacken.kth.se> <99061714590700.00896@master> X-Mailer: Mutt 0.91.1 In-Reply-To: <99061714590700.00896@master>; from Denis Oliver Kropp on Thu, Jun 17, 1999 at 02:47:20PM +0200 MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: 8bit Resent-Message-ID: <"J3vUO1.0.mA4.lILQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13385 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Which targets don´t support blitting from offscreen space? > Are they emulated then? (sysmem or vidmem, does not matter) You can always crossblit from a memvisual. Note, that the memory target has a tricky mode that might help you: # memory-target # # Emulates a linear framebuffer in main memory. This memory area can be # a shared memory segemnt, an area specified by the application, or be # malloc()ed by the memory-target itself. # # Arguments # # [-input:][shmid:|keyfile:::|pointer] # * shmid - use existing shmid # * keyfile - create a new shm segment with id ftok(,) # of size (preferred method !) # * pointer - use the memory pointed to by argptr. You could thus create a memvisual that contains your internal backbuffer and use LibGGI drawing functions on it. > This means: Can I do the following steps with every target? > 1. Create a visual with virtual height greater than visible height. No. Some targets cannot do that. All video cards, when they are out of RAM. > 2. ggiPutBox into the resulting "dead" area. > 3. ggiCopyBox from them. That wouldn't gain much. You could as well directly put to the final destination. Only advantage I see is when CopyBoxing is much faster than PutBoxing, as then you will have less flicker. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Thu Jun 17 16:42:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA15858 for ; Thu, 17 Jun 1999 16:42:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA28936; Thu, 17 Jun 1999 13:31:24 -0700 Resent-Date: Thu, 17 Jun 1999 13:31:24 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: Sucking the marrow out of hardware (Re: libGGI on matroxfb with Mystique) Date: Fri, 18 Jun 1999 00:29:12 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <19990617203117.C735@rz.uni-duesseldorf.de> MIME-Version: 1.0 Message-Id: <99061800340300.00265@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"BA9Sx3.0.t37.PiLQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13386 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck´s crap from Don, 17 Jun 1999: > > This means: Can I do the following steps with every target? > > 1. Create a visual with virtual height greater than visible height. > > No. Some targets cannot do that. All video cards, when they are out of RAM. Which targets? > > > 2. ggiPutBox into the resulting "dead" area. > > 3. ggiCopyBox from them. I meant, that the putbox is only done once. copybox often. Short: I want to make ClanLib as fast as possible, therefore I want to use ggiCopyBox for vid to vid mem. I just have to care about targets where this is not supported. (the "from" area must not be visible, but in video memory) For example Xlib target, how to use the fast XCopyArea call through ggi? Sorry, but it is so simple in DirectX, create an offscreen surface and blit from that. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Thu Jun 17 17:13:53 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA16860 for ; Thu, 17 Jun 1999 17:13:51 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA10446; Thu, 17 Jun 1999 14:01:09 -0700 Resent-Date: Thu, 17 Jun 1999 14:01:09 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: ggi rox Date: Thu, 17 Jun 1999 16:56:45 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: MIME-Version: 1.0 Message-Id: <99061717010100.03935@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"MHlVh3.0.0Z2.K8MQt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13387 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Peter I Amstutz wrote: > On Thu, 17 Jun 1999, Garrett B wrote: > > > Im making another scorched earth clone to learn linux. Im trying to > > make my transition from Windows to Linux now. Its amazing how a huge API like > > DirectX doesn't even have a simple function for drawing a horizontal line. And > > debugging a directX app was impossible unlike GGI with DDD. aaahh I love > > DDD..... > > Hmmm, I'm way ahead of you. I've been working on a sc*ch*d **rth clone > called "King of the Hill" (KOTH). It's fully client/server networked for > multiplayer, uses GGI, and I've put in quite a bit of work to make it > extensible and fairly easy to hack on... > > Right now I have a todo list of things I wanted to do before release, but > if you're really interested I could go ahead and just dump the source to > the world now... It's not as portable as I'd like, and there are of > course bugs, but then again it does at least compile :) > > You can see a couple of pre-pre-pre-alpha-prototype screenshots here: > http://www-unix.oit.umass.edu/~tetron/king.html > > The real game does more than these pictures reveal, of course :) I just wanted to get the feel for how GGI and more importantly linux worked. I was working on an RTS for windows and it was coming along pretty well but it was such a huge project with just me working on it, and programming for windows is a pain. And plus all the good coders code in linux. =) After I putz around with this scorched earth clone I might move onto another rts for linux. Linux needs more games. From ggi-develop-request@eskimo.com Thu Jun 17 17:36:08 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA17503 for ; Thu, 17 Jun 1999 17:36:04 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA16920; Thu, 17 Jun 1999 14:23:25 -0700 Resent-Date: Thu, 17 Jun 1999 14:23:25 -0700 Date: Thu, 17 Jun 1999 17:28:50 -0400 (EDT) From: David Waite X-Sender: root@localhost.localdomain To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique In-Reply-To: <19990617191255.B494@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"R4Q3g3.0.S74.BTMQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13388 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > The glide target worked very well and fast without DirectBuffer (using ggiPutBox for system > > backbuffer). But when I use DirectBuffer on it, it is much slower 66->20 fps. > > Maybe the system memory works as a buffer which handles > > the blits of small images better than writing each of them over the bus. > > Are there any MTRR regions I could set for my Voodoo2? MTRR regions should be set up as part of the 3dfx device kernel module. -David Waite From ggi-develop-request@eskimo.com Thu Jun 17 18:10:52 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA18623 for ; Thu, 17 Jun 1999 18:10:52 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA29818; Thu, 17 Jun 1999 14:58:37 -0700 Resent-Date: Thu, 17 Jun 1999 14:58:37 -0700 Sender: marcus@e.kth.se Message-ID: <37696F84.6A4EE317@stacken.kth.se> Date: Thu, 17 Jun 1999 21:58:28 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique References: <37682160.332C7C82@stacken.kth.se> <99061700293501.04490@master> <19990617191255.B494@rz.uni-duesseldorf.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Iz-oq2.0.gH7.B-MQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13389 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Which targets support accelerated ggiCopyBox? > > Fbdev and xlib come to mind. Glide maybe ? No, unfortunately (for XGGI) not. DGA target is hardware accelerated on DGA 1.1 though. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Thu Jun 17 18:17:44 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA18717 for ; Thu, 17 Jun 1999 18:17:41 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA00330; Thu, 17 Jun 1999 15:06:13 -0700 Resent-Date: Thu, 17 Jun 1999 15:06:13 -0700 Sender: marcus@e.kth.se Message-ID: <3769714B.753495D8@stacken.kth.se> Date: Thu, 17 Jun 1999 22:06:03 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: libGGI on matroxfb with Mystique References: <3768A529.128D957@stacken.kth.se> <3768AAA9.2D31@cert.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"ciYHF1.0.w4.J5NQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13390 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Rodolphe Ortalo wrote: > > Marcus Sundberg wrote: > > Peter Amstutz wrote: > > > Does libggi2d do sprites even in software yet? > > > > You can not do sprites in software. > > Why do you insist on that Marcus? You can not > move sprites, but, at least, a software lib could > draw them, no ? A sprite is an object which is overlayed on the framebuffer image without affecting it. You can not do this in software without removing huge parts of functionality and/or speed from LibGGI. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Thu Jun 17 18:19:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA18769 for ; Thu, 17 Jun 1999 18:19:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA01391; Thu, 17 Jun 1999 15:07:35 -0700 Resent-Date: Thu, 17 Jun 1999 15:07:35 -0700 Sender: marcus@e.kth.se Message-ID: <376971A1.4F1771BB@stacken.kth.se> Date: Thu, 17 Jun 1999 22:07:29 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Unidentified subject! References: <99061715081602.01916@mongoose> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"ElmRk1.0.WL.a6NQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13391 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B wrote: > > Where do I get the libggi2d library? I can't find it on the ftp. It's in CVS. If you can't use CVS you can find snapshots in the ggi-snapshots directory on our FTP site. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Thu Jun 17 22:59:54 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA24570 for ; Thu, 17 Jun 1999 22:59:49 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA27438; Thu, 17 Jun 1999 19:45:51 -0700 Resent-Date: Thu, 17 Jun 1999 19:45:51 -0700 Date: Thu, 17 Jun 1999 23:31:34 -0400 (EDT) From: "Brian S. Julin" Reply-To: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: GII:: v.01 ALPHA (Perl XS Modules) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"v5Uyt2.0.Li6.QBRQt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13392 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com As promised, here's the GII half (well, actually it's about 2/3rds, LibGII's much more complex than I first thought.) of the Perl5 XS modules. http://www.calyx.com/~bri/projects/GGI/ggi-perl/gii-perl-0.1.tar.gz This one's more complete/usable than the first release of the GGI::, modules, but those will catch up as they're more fun for me... Perl5 GII:: XS modules TODO list, NNiOoI: 0) Why does $inp->queued (giiEventsQueued) burn CPU and hang? 1) Look at LibGIC, decide whether to encapsulate it, or to diverge from the LibG* libraries at this point for a more perlish OO structure. 2) Write an GII::Valuator class to cushify working with GII::Event::Valuator and GII::Event::Command::Valuator. 3) ^GII::Valuator^GII::Device 4) Error handling mechanism + Panic 5) Get a mouse button repeat type added to LibGGI and uncomment the relevant code to handle it. 6) Figure out the correct guts for the confdir method 7) Add stringification and integer overloads 8) Enhance the test suite 9) Support struct timeval and perl Time classes. 10) Filehandle overloads? 11) Join From ggi-develop-request@eskimo.com Fri Jun 18 00:57:08 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA26951 for ; Fri, 18 Jun 1999 00:57:06 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id VAA06305; Thu, 17 Jun 1999 21:44:31 -0700 (PDT) Resent-Date: Thu, 17 Jun 1999 21:44:31 -0700 (PDT) From: Andrew Apted Message-ID: <19990618144156.23264@ajax.netspace.net.au> Date: Fri, 18 Jun 1999 14:41:56 +1000 To: ggi-develop@eskimo.com Subject: Re: ggi rox Reply-To: ggi-develop@eskimo.com References: <99061714594301.01916@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Peter I Amstutz on Thu, Jun 17, 1999 at 03:44:49PM -0400 Resent-Message-ID: <"tPM7E3.0.HY1.TwSQt"@mx2> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13393 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Peter I Amstutz writes: > Hmmm, I'm way ahead of you. I've been working on a sc*ch*d **rth clone > called "King of the Hill" (KOTH). It's fully client/server networked for > multiplayer, uses GGI, and I've put in quite a bit of work to make it > extensible and fairly easy to hack on... Looks like we need a libggiscorchedearth extension :-)). Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Fri Jun 18 11:08:48 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA10909 for ; Fri, 18 Jun 1999 11:08:47 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA00875; Fri, 18 Jun 1999 07:57:06 -0700 Resent-Date: Fri, 18 Jun 1999 07:57:06 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: ggi rox Date: Fri, 18 Jun 1999 10:54:47 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <19990618144156.23264@ajax.netspace.net.au> MIME-Version: 1.0 Message-Id: <99061810565901.02239@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"ep7ug.0.mB.wubQt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13394 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Andrew Apted wrote: > Peter I Amstutz writes: > > > Hmmm, I'm way ahead of you. I've been working on a sc*ch*d **rth clone > > called "King of the Hill" (KOTH). It's fully client/server networked for > > multiplayer, uses GGI, and I've put in quite a bit of work to make it > > extensible and fairly easy to hack on... > > Looks like we need a libggiscorchedearth extension :-)). Ya, I guess Ill be skipping my big Scorched Earth clone project I was going to do since everyone else has already done it. =) I was thinking of making an Open RTS. Basically a skeletal workings of an RTS engine that other people could use in creating their RTS games. Like how the Crystal Space engine is for 3D games, this would be for 2D RTS games, and as of now, it would be based on GGI. From ggi-develop-request@eskimo.com Fri Jun 18 11:50:50 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA12069 for ; Fri, 18 Jun 1999 11:50:49 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA19569; Fri, 18 Jun 1999 08:38:42 -0700 Resent-Date: Fri, 18 Jun 1999 08:38:42 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Date: Fri, 18 Jun 1999 11:37:17 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99061811384200.02482@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"FFtRA3.0.Zn4.1WcQt"@mx1> Resent-From: ggi-develop@eskimo.com Subject: Unidentified subject! X-Mailing-List: archive/latest/13395 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Does ggiCrossBlt() support acceleration if the hardware supports it? -- -Mongoose WPI student majoring in Computer Science and an over obsessed game fanatic. From ggi-develop-request@eskimo.com Fri Jun 18 13:40:26 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA14583 for ; Fri, 18 Jun 1999 13:40:22 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA00106; Fri, 18 Jun 1999 10:29:09 -0700 Resent-Date: Fri, 18 Jun 1999 10:29:09 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990618193205.B496@rz.uni-duesseldorf.de> Date: Fri, 18 Jun 1999 19:32:05 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Sucking the marrow out of hardware (Re: libGGI on matroxfb with Mystique) Mail-Followup-To: ggi-develop@eskimo.com References: <19990617203117.C735@rz.uni-duesseldorf.de> <99061800340300.00265@master> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99061800340300.00265@master>; from Denis Oliver Kropp on Fri, Jun 18, 1999 at 12:29:12AM +0200 Resent-Message-ID: <"Jy00T2.0.F1.U7eQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13396 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > > This means: Can I do the following steps with every target? > > > 1. Create a visual with virtual height greater than visible height. > > No. Some targets cannot do that. All video cards, when they are out of RAM. > Which targets? fbdev, SVGAlib, whatever ... as long as it maps to a physical device this device can run out of RAM. > > > 2. ggiPutBox into the resulting "dead" area. > > > 3. ggiCopyBox from them. > I meant, that the putbox is only done once. copybox often. Ah. BOBs. > Short: I want to make ClanLib as fast as possible, therefore I want to use > ggiCopyBox for vid to vid mem. I just have to care about targets where this > is not supported. (the "from" area must not be visible, but in video memory) > For example Xlib target, how to use the fast XCopyArea call through ggi? The idea would be to just do it with ggiCopyBox. Don't know, if this is implemented, though. We will work on that sprite/bob stuff ASAP, as it starts to bother many people. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Fri Jun 18 14:32:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA15841 for ; Fri, 18 Jun 1999 14:32:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA20410; Fri, 18 Jun 1999 11:21:12 -0700 Resent-Date: Fri, 18 Jun 1999 11:21:12 -0700 Sender: marcus@e.kth.se Message-ID: <376A8E0E.7394C585@stacken.kth.se> Date: Fri, 18 Jun 1999 18:21:02 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Unidentified subject! References: <99061811384200.02482@mongoose> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"7UGAW1.0.f-4.LueQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13397 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B wrote: > > Does ggiCrossBlt() support acceleration if the hardware supports it? All functions support acceleration if the hardware supports it - once someone has implemented it. Currently no targets have an accelerated crossblit. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Fri Jun 18 14:53:23 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA16371 for ; Fri, 18 Jun 1999 14:53:22 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id LAA09397; Fri, 18 Jun 1999 11:43:31 -0700 (PDT) Resent-Date: Fri, 18 Jun 1999 11:43:31 -0700 (PDT) Date: Fri, 18 Jun 1999 20:20:07 +0200 (MEST) To: Garrett B cc: ggi-develop@eskimo.com Subject: Re: ggi rox In-Reply-To: <99061717010100.03935@mongoose> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"JHU4G.0.ZI2.9DfQt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13398 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 17 Jun 1999, Garrett B wrote: > I just wanted to get the feel for how GGI and more importantly linux worked. I > was working on an RTS for windows and it was coming along pretty well but it was > such a huge project with just me working on it, and programming for windows is > a pain. And plus all the good coders code in linux. =) After I putz around > with this scorched earth clone I might move onto another rts for linux. Linux > needs more games. > *grin* Don't worry! In the latest Linux-Magazin (http://www.linux-magazin.de) is a article about linux-games: Loki Entertainment Software has recently specialized in porting Windows games to Linux by itself. :-) The first port is Civilization III. In soon future three games will be ported too: MYTH II, RAILROAD TYCOON II and ERIC's ULTIMATE SOFTWARE. And the world are waiting and looking for Quake3arena (and the german people are looking for the indicating :-)) The latest beta for Mac and Linux aren't SMP-ready yet, but ID-Software will it do it as soon as possible. Christoph Egger E-Mail: Christoph_Egger@t-online.de From ggi-develop-request@eskimo.com Fri Jun 18 15:08:06 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA17017 for ; Fri, 18 Jun 1999 15:08:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA03204; Fri, 18 Jun 1999 11:56:41 -0700 Resent-Date: Fri, 18 Jun 1999 11:56:41 -0700 Date: Fri, 18 Jun 1999 11:56:37 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: Unidentified subject! In-Reply-To: <376A8E0E.7394C585@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"jHqDn.0.nn.dPfQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13399 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 18 Jun 1999, Marcus Sundberg wrote: > Garrett B wrote: > > > > Does ggiCrossBlt() support acceleration if the hardware supports it? > > All functions support acceleration if the hardware supports it - once > someone has implemented it. > > Currently no targets have an accelerated crossblit. The Savage4 KGI driver supports it. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 18 15:28:46 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA17860 for ; Fri, 18 Jun 1999 15:28:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA12903; Fri, 18 Jun 1999 12:17:09 -0700 Resent-Date: Fri, 18 Jun 1999 12:17:09 -0700 From: Thad Phetteplace Message-Id: <199906190020.TAA00917@dexter.glaci.com> Subject: Re: Unidentified subject! To: ggi-develop@eskimo.com Date: Fri, 18 Jun 1999 19:20:51 -0500 (CDT) In-Reply-To: <376A8E0E.7394C585@stacken.kth.se> from "Marcus Sundberg" at Jun 18, 99 06:21:02 pm Content-Type: text Resent-Message-ID: <"3U_8P2.0.M93.qifQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13400 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Does ggiCrossBlt() support acceleration if the hardware supports it? > > All functions support acceleration if the hardware supports it - once > someone has implemented it. I plan on implementing 2d acceleration on as many cards as I can lay my hands on. I first need to finish and submit the the BlitOp code I've been sporadically working on. Now that I've finally submitted my last chapter for The RedHat Linux Bible, I should be able to get more time in on GGI hacking. I do have a few other projects on my plate (technical book review for Prentice Hall, programming job for an insurance company, and a four day camping trip) but those should not cut into my time nearly as much as the book did. I assume hardware specs for 2d accel are generally more available than 3d? Later, Thad From ggi-develop-request@eskimo.com Fri Jun 18 15:30:52 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA17914 for ; Fri, 18 Jun 1999 15:30:49 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA15069; Fri, 18 Jun 1999 12:19:42 -0700 Resent-Date: Fri, 18 Jun 1999 12:19:42 -0700 Message-ID: X-Mailer: NailMail 1.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 ECHELON: nuclear,Saddam,CIA,Milosevic,Clinton,dead,Plutonium,KGB,USA,bomb,terror Date: Fri, 18 Jun 1999 21:20:05 +0200 (CEST) Sender: thomas@ffii.org From: Thomas Tanner To: ggi-develop@eskimo.com Subject: job offer (found on www.deja.com) Resent-Message-ID: <"7qj8d2.0.Zg3.ClfQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13401 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com ------------------------------- Subject: US-AZ-Phx-Programmer/SW Engineer Date: 1999/06/17 From: keltecaz Kelly IT and Engineering Resources is a full service contract employer offering 401k, direct deposit, weekly pay, packaged per diem, and optional employee paid HMO. Kelly Resources is currently offering contract and permanent assignments with major employers in the Phoenix Arizona metropolitan area as follows: Immediate Opening- Position: Programmer GGI is a library of graphics, porting GGI graphics subsystem to a SA1100 board with a linux operating system. XWindows or other, Linux kernel experience. Low-level driver programming would be a plus. Duration: 6 months Rate: DOE Location: Chandler, AZ ***Must be authorized to work in the USA*** Qualified candidates should apply immediately to: Kelly IT and Engineering Resources 3030 N. 3rd Street, Suite 1060 Phoenix, AZ. 85012 Phone: (602)222-2477 Fax: (602)222-8790 E-Mail: baggerm@kellyservices.com Check out our website at: www.kellyIT.com ------------------------------- Thomas Tanner ----------------------------------------- email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de) web: http://home.pages.de/~tanner GGI/Picasso: http://picasso.ffii.org From ggi-develop-request@eskimo.com Fri Jun 18 15:59:04 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA19015 for ; Fri, 18 Jun 1999 15:59:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA29124; Fri, 18 Jun 1999 12:47:58 -0700 Resent-Date: Fri, 18 Jun 1999 12:47:58 -0700 From: Aki M Laukkanen Message-Id: <199906181947.WAA00723@vesuri.Helsinki.FI> Subject: beta2.0b2.1 fixes To: ggi-develop@eskimo.com Date: Fri, 18 Jun 1999 22:47:53 +0300 (EET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"nrU042.0.j67.j9gQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13402 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello, I had to make these small changes to get my test applications to work on the fbdev target (vesafb): o stdformat not setup so crossblit falls back to the unearthly slow unmap/map version. o vesafb does not support panning and hence not multiple frames. [apologies for possible problems, copying diff by hand] --- libggi/display/fbdev/mode.c Mon May 17 12:00:00 1999 +++ libggi-2.0b2.1/display/fbdev/mode.c Mon May 17 12:00:00 1999 @@ -38,6 +38,7 @@ #include #include +#include "../common/pixfmt-setup.inc" #include "../common/ggi-auto.inc" #include "../common/gt-auto.inc" @@ -425,6 +426,8 @@ LIBGGI_PIXFMT(vis)->bg_mask = 0xf000; break; } + + setup_pixfmt(LIBGGI_PIXFMT(vis), gt); _ggi_build_pixfmt(LIBGGI_PIXFMT(vis)); /* Set up DirectBuffers */ @@ -671,6 +674,11 @@ if (mode->virt.y < mode->visible.y) { mode->virt.y = mode->visible.y; + err = -1; + } + + if (!priv->orig_fix.ypanstep && mode->frames > 1) { + mode->frames = 1; err = -1; } -- D. From ggi-develop-request@eskimo.com Fri Jun 18 16:30:39 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA20230 for ; Fri, 18 Jun 1999 16:30:38 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA10313; Fri, 18 Jun 1999 13:19:02 -0700 Resent-Date: Fri, 18 Jun 1999 13:19:02 -0700 Sender: marcus@e.kth.se Message-ID: <376AA9B1.24D17677@stacken.kth.se> Date: Fri, 18 Jun 1999 20:18:57 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes References: <199906181947.WAA00723@vesuri.Helsinki.FI> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"VKKvD.0.qW2.qcgQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13403 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Aki M Laukkanen wrote: > > Hello, I had to make these small changes to get my test applications to > work on the fbdev target (vesafb): Thanks. > o stdformat not setup so crossblit falls back to the unearthly > slow unmap/map version. > o vesafb does not support panning and hence not multiple frames. > > [apologies for possible problems, copying diff by hand] > > --- libggi/display/fbdev/mode.c Mon May 17 12:00:00 1999 > +++ libggi-2.0b2.1/display/fbdev/mode.c Mon May 17 12:00:00 1999 > @@ -38,6 +38,7 @@ > #include > #include > > +#include "../common/pixfmt-setup.inc" > #include "../common/ggi-auto.inc" > #include "../common/gt-auto.inc" > > @@ -425,6 +426,8 @@ > LIBGGI_PIXFMT(vis)->bg_mask = 0xf000; > break; > } > + > + setup_pixfmt(LIBGGI_PIXFMT(vis), gt); > _ggi_build_pixfmt(LIBGGI_PIXFMT(vis)); > > /* Set up DirectBuffers */ This is wrong. setup_pixfmt() is a really stupid function which will destroy the parameters set up above. I will fix _ggi_build_pixfmt() to handle stdformat too. > @@ -671,6 +674,11 @@ > > if (mode->virt.y < mode->visible.y) { > mode->virt.y = mode->visible.y; > + err = -1; > + } > + > + if (!priv->orig_fix.ypanstep && mode->frames > 1) { > + mode->frames = 1; > err = -1; > } Ah yes, CheckMode really needs to be improved for the fbdev target. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Fri Jun 18 16:36:20 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA20379 for ; Fri, 18 Jun 1999 16:36:19 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA12310; Fri, 18 Jun 1999 13:25:16 -0700 Resent-Date: Fri, 18 Jun 1999 13:25:16 -0700 Sender: marcus@e.kth.se Message-ID: <376AAAEF.64F977FA@stacken.kth.se> Date: Fri, 18 Jun 1999 20:24:15 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Unidentified subject! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"hlYkr.0.003.higQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13404 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > > Currently no targets have an accelerated crossblit. > > The Savage4 KGI driver supports it. Cool. How does it do that? First copy to offscreen area and then bitblt? Or does the Savage4 have a special area like the Matrox cards, to which you can copy the data directly? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Fri Jun 18 17:38:34 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA21496 for ; Fri, 18 Jun 1999 17:38:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA03716; Fri, 18 Jun 1999 14:26:53 -0700 Resent-Date: Fri, 18 Jun 1999 14:26:53 -0700 Date: Fri, 18 Jun 1999 14:26:46 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: Accelerated CrossBlits In-Reply-To: <376AAAEF.64F977FA@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"5yWzu2.0.sv.RchQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13405 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 18 Jun 1999, Marcus Sundberg wrote: > Jon M. Taylor wrote: > > > Currently no targets have an accelerated crossblit. > > > > The Savage4 KGI driver supports it. > > Cool. How does it do that? You load the data into AGP memory and then fire the CrossBlit op which transfers the data to framebuffer memory (which I support) or another chunk of AGP memory (which I do not yet support) and reformats it as it goes. Source/destination formats can be YCbCr420 planar, YCbCr422 packed, RGB565 or XRGB888 (the first two are for TV/digitizer support). So it will be necessary to implement a two-stage fallback, where the source data will have to be soft-crossblitted to the appropriate hardware-supported format first, if it is not already in such a format. In some (most? all?) cases, it may (will?) be cheaper to fall back to a completely soft-based CrossBlit if the exact source/dest format types are not directly supported by the hardware... I don't know yet. I doubt that the ACCEL_CROSSBLIT handling will be in the first beta anyway, as it is pretty kludgey right now and AFAIK LibGGI doesn't handle it right now anyway, so it is pretty much untested.... Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 18 18:55:46 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA22998 for ; Fri, 18 Jun 1999 18:55:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA03245; Fri, 18 Jun 1999 15:44:13 -0700 Resent-Date: Fri, 18 Jun 1999 15:44:13 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Async mode and double buffering Date: Fri, 18 Jun 1999 18:39:01 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99061818441300.04549@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"Rx23X2.0.So.xkiQt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13406 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Is there any point in using double buffering when using GGIFLAG_ASYNC mode to avoid tearing? Because when your drawing to the visual the visual will never update until you call a ggiFlush() right? Im only running GGI on X right now so Im not sure about other targets. -Mongoose WPI student majoring in Computer Science and an over obsessed game fanatic. From ggi-develop-request@eskimo.com Fri Jun 18 20:21:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA24228 for ; Fri, 18 Jun 1999 20:21:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA31274; Fri, 18 Jun 1999 17:09:32 -0700 Resent-Date: Fri, 18 Jun 1999 17:09:32 -0700 Date: Fri, 18 Jun 1999 17:09:28 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: job offer (found on www.deja.com) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"amn8d3.0.Oe7.v-jQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13407 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 18 Jun 1999, Thomas Tanner wrote: [snip] > GGI is a library of graphics, porting GGI graphics subsystem to a SA1100 [snip] ^^^^^^ > Location: Chandler, AZ ^^^^^^^^^^^^ [snip] ...And on the site, they said that the CPU for this board project will be ARM. These three pieces of info tell me that the company involved here is probably Intel! Wow! The big boys are finally taking notice of GGI, it seems. Let me offer a word of caution to anyone on this list that might be considering applying for this position, though: I worked internal phone tech support for Intel for ~5 months several years back and it was the most horrible job experience I have ever had. Now, tech support is very different from driver development, but we did get to interact with people from all over the rest of the company and it didn't seem a whole lot better anywhere else... The company has a well-deverved reputation for burning people out quickly. Make sure they compensate you well and that you have freedom to "do your thing" or they will chew you up and spit you out. Remember that case a while back, where a pissed-off ex-Intel empolyee representing a group called FACE (Former and Current Employees of Intel) was spamming the public e-mail addresses of Intel employees? Well, when I was working there I got the first wave of that stuff, and I checked out the FACE dude's website. Pretty apalling stuff, even if it was never proven in court. I don't want to get too specific because I am still worried about facing legal action |-<. Intel _has_ gotten slapped down pretty hard by the antitrust suit they settled and by the increasingly public descriptions of horrible working conditions, but they are still the company that many people allege explicitly colluded with Microsoft to create the WinTel duopoly, and we all know what conditions are reputed to be like inside of M$. If you apply for this job, be _VERY_ careful and keep your eyes open. 'Nuff said. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 18 20:21:36 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA24236 for ; Fri, 18 Jun 1999 20:21:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA31445; Fri, 18 Jun 1999 17:10:24 -0700 Resent-Date: Fri, 18 Jun 1999 17:10:24 -0700 Date: Fri, 18 Jun 1999 17:10:19 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: CrossBlit In-Reply-To: <199906190020.TAA00917@dexter.glaci.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"B3AyR3.0.yg7.k_jQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13408 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 18 Jun 1999, Thad Phetteplace wrote: > > > Does ggiCrossBlt() support acceleration if the hardware supports it? > > > > All functions support acceleration if the hardware supports it - once > > someone has implemented it. > > I plan on implementing 2d acceleration on as many cards as I can lay my > hands on. I first need to finish and submit the the BlitOp code I've > been sporadically working on. Now that I've finally submitted my last > chapter for The RedHat Linux Bible, I should be able to get more time in > on GGI hacking. I do have a few other projects on my plate (technical > book review for Prentice Hall, programming job for an insurance company, > and a four day camping trip) but those should not cut into my time nearly > as much as the book did. I assume hardware specs for 2d accel are > generally more available than 3d? Yes, in general. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 18 20:25:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA24566 for ; Fri, 18 Jun 1999 20:25:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA00623; Fri, 18 Jun 1999 17:14:30 -0700 Resent-Date: Fri, 18 Jun 1999 17:14:30 -0700 Date: Fri, 18 Jun 1999 17:14:27 -0700 (PDT) From: "Jon M. Taylor" To: Garrett B cc: ggi-develop@eskimo.com Subject: Re: Async mode and double buffering In-Reply-To: <99061818441300.04549@mongoose> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"S1I6o2.0.V9.a3kQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13409 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 18 Jun 1999, Garrett B wrote: > Is there any point in using double buffering when using GGIFLAG_ASYNC mode to > avoid tearing? Yes. > Because when your drawing to the visual the visual will never > update until you call a ggiFlush() right? Yes, but in order for this to work you have to be sure that ggiFlush() is called during the vblank interval when the screen is not being redrawn. Currently the only target which supports the GGIMisc extension's ggiWaitRayPos() function is the SVGALib target, so.... > Im only running GGI on X right now so > Im not sure about other targets. With X you will need to use double buffering. Actually you really should always use double buffering so that targets which support hardware pageflipping can be taken advantage of. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Fri Jun 18 22:25:40 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA26223 for ; Fri, 18 Jun 1999 22:25:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA01294; Fri, 18 Jun 1999 19:13:29 -0700 Resent-Date: Fri, 18 Jun 1999 19:13:29 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990619015324.C14339@rz.uni-duesseldorf.de> Date: Sat, 19 Jun 1999 01:53:24 +0200 From: Andreas Beck To: mongoose@wpi.edu Cc: mailing list GGI Subject: Re: Async mode and double buffering Mail-Followup-To: mongoose@wpi.edu, mailing list GGI References: <99061818441300.04549@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99061818441300.04549@mongoose>; from Garrett B on Fri, Jun 18, 1999 at 06:39:01PM -0500 Resent-Message-ID: <"JhjRa1.0.zJ.7plQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13410 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Is there any point in using double buffering when using GGIFLAG_ASYNC mode to > avoid tearing? Because when your drawing to the visual the visual will never > update until you call a ggiFlush() right? No. This is only true on inherently asynchronous targets like X. Inherently synchronous targets like fbdev or other dircetly HW-mapped stuff will draw whenever they feel like it. ggiFlush only ensures that the drawn stuff will appear "real soon" on the output device. It might already be there. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Fri Jun 18 23:41:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA26945 for ; Fri, 18 Jun 1999 23:41:07 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA22420; Fri, 18 Jun 1999 20:29:28 -0700 Resent-Date: Fri, 18 Jun 1999 20:29:28 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Creating buffers Date: Fri, 18 Jun 1999 23:26:31 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99061823292800.07839@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"4gDji3.0.3U5.KwmQt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13411 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Im kinda confused after reading the webpages. What do you do to create a new visual to store a picture in? And when you create it, can GGI automatically put it in video memory if the space is available and then fallback to system memory? -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Sat Jun 19 02:36:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id CAA28247 for ; Sat, 19 Jun 1999 02:36:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA01822; Fri, 18 Jun 1999 23:24:47 -0700 Resent-Date: Fri, 18 Jun 1999 23:24:47 -0700 Date: Sat, 19 Jun 1999 08:09:26 +0200 (MEST) To: GGI-Mailing-Liste Subject: libgii - mysterious mouse implementation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"tJ6NT2.0.AS.jUpQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13412 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi all! I tried to hack in libgii the third mouse button recognization of a serial mouse using the microsoft-protocol. But here I detected a mysterious thing: When I apply the following patch the inputdump demo recognize the middle mouse button as both left and right mouse button... --- input/mouse/packetparse.c.old Wed Apr 7 16:24:59 1999 +++ input/mouse/packetparse.c Thu Apr 8 14:07:23 1999 @@ -128,9 +132,32 @@ dx = (sint8) (((buf[0] & 0x03) << 6) | (buf[1] & 0x3f)); dy = (sint8) (((buf[0] & 0x0c) << 4) | (buf[2] & 0x3f)); - buttons = ((buf[0] & 0x10) >> 3) - | ((buf[0] & 0x20) >> 5); + /* third button added by Christoph Egger (Christoph_Egger@t-online.de) */ + if (buf[0] == 0x40 && !(mpriv->button_state|buf[1]|buf[2])) + buttons = GII_PBUTTON_MIDDLE; /* third button on MS compatible mouse */ + else + buttons = ((buf[0] & 0x10) >> 3) + | ((buf[0] & 0x20) >> 5); When I apply the following patch instead, inputdump recognizes the middle mouse button as expected... --- input/mouse/packetparse.c.old Wed Apr 7 16:24:59 1999 +++ input/mouse/packetparse.c Thu Apr 8 14:07:23 1999 @@ -128,9 +132,32 @@ dx = (sint8) (((buf[0] & 0x03) << 6) | (buf[1] & 0x3f)); dy = (sint8) (((buf[0] & 0x0c) << 4) | (buf[2] & 0x3f)); - buttons = ((buf[0] & 0x10) >> 3) - | ((buf[0] & 0x20) >> 5); + /* third button added by Christoph Egger (Christoph_Egger@t-online.de) */ + if (buf[0] == 0x40 && !(mpriv->button_state|buf[1]|buf[2])) + buttons = 4; /* third button on MS compatible mouse */ + else + buttons = ((buf[0] & 0x10) >> 3) + | ((buf[0] & 0x20) >> 5); Can anyone explain this? Note: GII_PBUTTON_MIDDLE is defined as #define GII_PBUTTON_MIDDLE 3 Christoph Egger E-Mail: Christoph_Egger@t-online.de From ggi-develop-request@eskimo.com Sat Jun 19 05:58:12 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA29169 for ; Sat, 19 Jun 1999 05:58:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA27122; Sat, 19 Jun 1999 02:46:03 -0700 Resent-Date: Sat, 19 Jun 1999 02:46:03 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes Date: Sat, 19 Jun 1999 11:42:49 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <199906181947.WAA00723@vesuri.Helsinki.FI> MIME-Version: 1.0 Message-Id: <99061911435805.00747@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"mG3c9.0.Vd6.PRsQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13414 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Aki M Laukkanen´s crap from Fre, 18 Jun 1999: > Hello, I had to make these small changes to get my test applications to > work on the fbdev target (vesafb): > > o stdformat not setup so crossblit falls back to the unearthly > slow unmap/map version. > o vesafb does not support panning and hence not multiple frames. It supports panning for multiple frames, if you set ywrap in boot options. Anyway thanks for the patch. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Sat Jun 19 05:58:52 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA29188 for ; Sat, 19 Jun 1999 05:58:51 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA27042; Sat, 19 Jun 1999 02:44:36 -0700 Resent-Date: Sat, 19 Jun 1999 02:44:36 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: clanlib@dark.x.dtu.dk, devel@XFree86.Org, ggi-develop@eskimo.com Subject: Fwd: [g200-dev]G400 specs released Date: Sat, 19 Jun 1999 11:45:37 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99061911460906.00747@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"JDUkz1.0.Jc6.3QsQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13413 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com ---------- Forwarded ---------- Subject: [g200-dev]G400 specs released Date: Fri, 18 Jun 1999 19:07:41 -0500 From: Stephen Crowley The G400 specs have been released, you have to be a register matrox developer to access them (but it's free). http://www.matrox.com/mga/dev_relations/chips_tech/matrox_g400.htm -- | Stephen Crowley | Debian GNU/Linux | _______________________________________________ G200-dev maillist - G200-dev@lists.openprojects.net http://lists.openprojects.net/mailman/listinfo/g200-dev -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Sat Jun 19 06:35:44 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA29365 for ; Sat, 19 Jun 1999 06:35:43 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA30484; Sat, 19 Jun 1999 03:24:17 -0700 Resent-Date: Sat, 19 Jun 1999 03:24:17 -0700 From: Aki M Laukkanen Message-Id: <199906191024.NAA32089@vesuri.Helsinki.FI> Subject: Re: beta2.0b2.1 fixes To: ggi-develop@eskimo.com Date: Sat, 19 Jun 1999 13:24:13 +0300 (EET DST) In-Reply-To: <99061911435805.00747@master> from "Denis Oliver Kropp" at Jun 19, 99 11:42:49 am MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"HnGYY2.0._R7.G_sQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13415 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > o vesafb does not support panning and hence not multiple frames. > It supports panning for multiple frames, if you set ywrap in boot options. Oh, I was a bit vague on that statement. The panning support is in vesafb but of course needs VESA PMI support to work. However on many BIOSes PMI isn't implemented or is buggy even if they claim to be 2.0 compliant. Atleast this is true on my laptop (a Toshiba 220CS). -- D. From ggi-develop-request@eskimo.com Sat Jun 19 09:43:50 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA00737 for ; Sat, 19 Jun 1999 09:43:50 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA17406; Sat, 19 Jun 1999 06:31:06 -0700 Resent-Date: Sat, 19 Jun 1999 06:31:06 -0700 From: Andrew Apted Message-ID: <19990619124806.00048@ajax.netspace.net.au> Date: Sat, 19 Jun 1999 12:48:06 +1000 To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes Reply-To: ggi-develop@eskimo.com References: <199906181947.WAA00723@vesuri.Helsinki.FI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <199906181947.WAA00723@vesuri.Helsinki.FI>; from Aki M Laukkanen on Fri, Jun 18, 1999 at 10:47:53PM +0300 Resent-Message-ID: <"d2jP02.0.CF4.KkvQt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13416 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Aki M Laukkanen writes: > o vesafb does not support panning and hence not multiple frames. Which kernel is that ? I'm fairly sure that vesafb does support panning, just that in certain kernel versions it is buggy (like here in 2.1.126 it causes a segfault). If I remember correctly, there is a special kernel command line (something like "vesafb=scroll") that enables it. > + if (!priv->orig_fix.ypanstep && mode->frames > 1) { > + mode->frames = 1; > err = -1; > } Are you sure that is the correct fix ? To me that says: "if the _original_ mode cannot do panning, then the future one cannot as well", which I don't think is right in the general case (I must admit I've forgotten all the subtleties of the fbdev API -- anyone know if they have written a good API docco on it yet ?). Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Sat Jun 19 09:45:57 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA00749 for ; Sat, 19 Jun 1999 09:45:56 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA17756; Sat, 19 Jun 1999 06:33:35 -0700 Resent-Date: Sat, 19 Jun 1999 06:33:35 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990619131014.A579@rz.uni-duesseldorf.de> Date: Sat, 19 Jun 1999 13:10:14 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: libgii - mysterious mouse implementation Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Christoph Egger on Sat, Jun 19, 1999 at 08:09:26AM +0200 Resent-Message-ID: <"E7qNB.0.CL4.kmvQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13417 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I tried to hack in libgii the third mouse button recognization of a serial > mouse using the microsoft-protocol. But here I detected a mysterious > thing: When I apply the following patch the inputdump demo recognize the > middle mouse button as both left and right mouse button... > + /* third button added by Christoph Egger (Christoph_Egger@t-online.de) */ > + if (buf[0] == 0x40 && !(mpriv->button_state|buf[1]|buf[2])) > + buttons = GII_PBUTTON_MIDDLE; /* third button on MS compatible mouse */ > When I apply the following patch instead, inputdump recognizes the middle > mouse button as expected... > + /* third button added by Christoph Egger (Christoph_Egger@t-online.de) */ > + if (buf[0] == 0x40 && !(mpriv->button_state|buf[1]|buf[2])) > + buttons = 4; /* third button on MS compatible mouse */ > Can anyone explain this? Yes. Look at mouse_send_buttons. The buttons variable in the parser works as a bitfield, while the communication with the application works on a keypress/release basis. GII_PBUTTON_MIDDLE now happens to be 3, which will cause mouse_send_buttons to send press/release events as required to say "buttons 1 and 2 are on". BTW: When I look at your patch, I get the impression, that one cannot press the middle button together with the outer buttons. Is that correct ? Then someone should go and shoot the one that designed that protocol ... I was already pretty upset, when we had a little Q**** match in the lunchbreak and I had a 2 button M$ mouse only, which caused me to need to use the keyboard for backing up and defeated running and shooting at the same time, as pressing both buttons caused the X server's chord-middle function to kick in .... GRRR ... CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sat Jun 19 10:08:26 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA00926 for ; Sat, 19 Jun 1999 10:08:25 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA20451; Sat, 19 Jun 1999 06:54:45 -0700 Resent-Date: Sat, 19 Jun 1999 06:54:45 -0700 From: Andrew Apted Message-ID: <19990620000018.31454@ajax.netspace.net.au> Date: Sun, 20 Jun 1999 00:00:18 +1000 To: ggi-develop@eskimo.com Subject: Re: libgii - mysterious mouse implementation Reply-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Christoph Egger on Sat, Jun 19, 1999 at 08:09:26AM +0200 Resent-Message-ID: <"a1aAR1.0.E_4.a4wQt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13418 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Christoph Egger writes: > I tried to hack in libgii the third mouse button recognization of a serial > mouse using the microsoft-protocol. If I remember correctly, the third mouse button in ms protocol is a hack (something like both buttons appear to be pressed at the same time, and dx=dy=0 -- read the gpm sources for more info). At the time, I deemed it too unreliable to be worth supporting. > But here I detected a mysterious > thing: When I apply the following patch the inputdump demo recognize the > middle mouse button as both left and right mouse button... [SNIP] > When I apply the following patch instead, inputdump recognizes the middle > mouse button as expected... [SNIP] > Can anyone explain this? Yes: the `buttons' variable is an internal variable which is a _bitmask_ of the buttons. The GII_BUTTON thingies are button _numbers_ (1, 2, 3, 4, ...). "Mystery" solved :-) Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Sat Jun 19 10:26:44 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA01298 for ; Sat, 19 Jun 1999 10:26:42 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA23688; Sat, 19 Jun 1999 07:10:05 -0700 Resent-Date: Sat, 19 Jun 1999 07:10:05 -0700 From: Aki M Laukkanen Message-Id: <199906191410.RAA00398@vesuri.Helsinki.FI> Subject: Re: beta2.0b2.1 fixes To: ggi-develop@eskimo.com Date: Sat, 19 Jun 1999 17:10:01 +0300 (EET DST) In-Reply-To: <19990619124806.00048@ajax.netspace.net.au> from "Andrew Apted" at Jun 19, 99 12:48:06 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"LeNT91.0.vn5.yIwQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13419 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > special kernel command line (something like "vesafb=scroll") that Yes, see my other reply for clarification. The kernel options are "vesa:ypan" and "vesa:ywrap". > > + if (!priv->orig_fix.ypanstep && mode->frames > 1) { > > + mode->frames = 1; > > err = -1; > Are you sure that is the correct fix ? To me that says: "if the > _original_ mode cannot do panning, then the future one cannot as well", > which I don't think is right in the general case (I must admit I've That snippet is from GGI_fbdev_checkmode() and if I understood the code correctly priv->fix is not fetched until do_change_mode(). Besides if the driver is really so silly that it would return ypanstep differently for different modes then it could just aswell be that the ypanstep is zero for the current mode but not for the original mode. All the other tests in that function refer to priv->orig_fix too. > forgotten all the subtleties of the fbdev API -- anyone know if they > have written a good API docco on it yet ?). I only know about the one Geert wrote. Btw. fbdev does not currently set a signal handler for the VT switch. Is there a reason for it and would you accept a patch for it? -- D. From ggi-develop-request@eskimo.com Sat Jun 19 14:01:37 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA02789 for ; Sat, 19 Jun 1999 14:01:36 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA04744; Sat, 19 Jun 1999 10:49:53 -0700 Resent-Date: Sat, 19 Jun 1999 10:49:53 -0700 Date: Sat, 19 Jun 1999 19:42:41 +0200 (MEST) To: ggi-develop@eskimo.com Subject: Re: libgii - mysterious mouse implementation In-Reply-To: <19990619131014.A579@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"-SrJ13.0.h91.vWzQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13420 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sat, 19 Jun 1999, Andreas Beck wrote: > > I tried to hack in libgii the third mouse button recognization of a serial > > mouse using the microsoft-protocol. But here I detected a mysterious > > thing: When I apply the following patch the inputdump demo recognize the > > middle mouse button as both left and right mouse button... > > > + /* third button added by Christoph Egger (Christoph_Egger@t-online.de) */ > > + if (buf[0] == 0x40 && !(mpriv->button_state|buf[1]|buf[2])) > > + buttons = GII_PBUTTON_MIDDLE; /* third button on MS compatible mouse */ > > > When I apply the following patch instead, inputdump recognizes the middle > > mouse button as expected... > > > + /* third button added by Christoph Egger (Christoph_Egger@t-online.de) */ > > + if (buf[0] == 0x40 && !(mpriv->button_state|buf[1]|buf[2])) > > + buttons = 4; /* third button on MS compatible mouse */ > > > Can anyone explain this? > > Yes. Look at mouse_send_buttons. The buttons variable in the parser works as > a bitfield, while the communication with the application works on a > keypress/release basis. GII_PBUTTON_MIDDLE now happens to be 3, which will > cause mouse_send_buttons to send press/release events as required to say > "buttons 1 and 2 are on". Ah! "Mystery" solved. :-) > > BTW: When I look at your patch, I get the impression, that one cannot press > the middle button together with the outer buttons. Is that correct ? No. Inputdump recognizes all pressed buttons as expected (when I use the second patch above). But inputdump doesn't recognize the middle mouse button, when I am moving the mouse... :-( Christoph Egger E-Mail: Christoph_Egger@t-online.de From ggi-develop-request@eskimo.com Sat Jun 19 14:01:53 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA02793 for ; Sat, 19 Jun 1999 14:01:52 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA04825; Sat, 19 Jun 1999 10:50:06 -0700 Resent-Date: Sat, 19 Jun 1999 10:50:06 -0700 Date: Sat, 19 Jun 1999 19:49:01 +0200 (MEST) To: ggi-develop@eskimo.com Subject: Re: libgii - mysterious mouse implementation In-Reply-To: <19990620000018.31454@ajax.netspace.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"1DzOL1.0.pA1.CXzQt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13421 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sun, 20 Jun 1999, Andrew Apted wrote: > Christoph Egger writes: > > > I tried to hack in libgii the third mouse button recognization of a serial > > mouse using the microsoft-protocol. > > If I remember correctly, the third mouse button in ms protocol is a hack > (something like both buttons appear to be pressed at the same time, and > dx=dy=0 -- read the gpm sources for more info). At the time, I deemed > it too unreliable to be worth supporting. Well, I have a multi-protocol three button mouse. The standard protocol is the microsoft protocol. The other is mouse systems. To switch the protocol to mouse systems I must press the left mouse button every time I boot up my computer. That's ... *GRRR* ... not so good... so I want to use the middle mouse button with the microsoft protocol! > > > But here I detected a mysterious > > thing: When I apply the following patch the inputdump demo recognize the > > middle mouse button as both left and right mouse button... > [SNIP] > > When I apply the following patch instead, inputdump recognizes the middle > > mouse button as expected... > [SNIP] > > Can anyone explain this? > > Yes: the `buttons' variable is an internal variable which is a _bitmask_ > of the buttons. The GII_BUTTON thingies are button _numbers_ (1, 2, 3, > 4, ...). > > "Mystery" solved :-) Thanks! Cheers, Christoph Egger E-Mail: Christoph_Egger@t-online.de From ggi-develop-request@eskimo.com Sat Jun 19 17:46:19 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA04928 for ; Sat, 19 Jun 1999 17:46:18 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA31174; Sat, 19 Jun 1999 14:34:11 -0700 Resent-Date: Sat, 19 Jun 1999 14:34:11 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990619212052.A849@rz.uni-duesseldorf.de> Date: Sat, 19 Jun 1999 21:20:52 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: libgii - mysterious mouse implementation Mail-Followup-To: ggi-develop@eskimo.com References: <19990619131014.A579@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Christoph Egger on Sat, Jun 19, 1999 at 07:42:41PM +0200 Resent-Message-ID: <"k9OZa.0.Tc7.Bp0Rt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13422 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi ! > > BTW: When I look at your patch, I get the impression, that one cannot press > > the middle button together with the outer buttons. Is that correct ? > No. Inputdump recognizes all pressed buttons as expected (when I use the > second patch above). But inputdump doesn't recognize the middle mouse > button, when I am moving the mouse... :-( O.K. - so if it works nicely, we should include it in our sources, right ? Could you resend me the right patch ? I'll then take care for including it. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sat Jun 19 18:18:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA05152 for ; Sat, 19 Jun 1999 18:18:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA03988; Sat, 19 Jun 1999 15:07:22 -0700 Resent-Date: Sat, 19 Jun 1999 15:07:22 -0700 Sender: marcus@e.kth.se Message-ID: <376C1497.2422D5B5@stacken.kth.se> Date: Sat, 19 Jun 1999 22:07:19 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Fwd: [g200-dev]G400 specs released References: <99061911460906.00747@master> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Uv-cd3.0.3-.OI1Rt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13423 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > The G400 specs have been released, Awesome! Full specs released to the public at the same time as the hardware. Wish all HW manufacturers were like this... //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sat Jun 19 18:36:38 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA05524 for ; Sat, 19 Jun 1999 18:36:37 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA06782; Sat, 19 Jun 1999 15:25:36 -0700 Resent-Date: Sat, 19 Jun 1999 15:25:36 -0700 Sender: marcus@e.kth.se Message-ID: <376C18DE.7321B5C1@stacken.kth.se> Date: Sat, 19 Jun 1999 22:25:34 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes References: <199906191410.RAA00398@vesuri.Helsinki.FI> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"NoD8J3.0.hf1.VZ1Rt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13424 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Aki M Laukkanen wrote: > Btw. fbdev does not currently set a signal handler for the VT switch. > Is there a reason for it and would you accept a patch for it? VT switching is handled by helper-linvtsw. Do you have any problem with VT switching in LibGGI? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sat Jun 19 20:33:37 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA06571 for ; Sat, 19 Jun 1999 20:33:36 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA30076; Sat, 19 Jun 1999 17:21:55 -0700 Resent-Date: Sat, 19 Jun 1999 17:21:55 -0700 Sender: peter@lime.idonex.se To: ggi-develop@eskimo.com Subject: Re: job offer (found on www.deja.com) References: Content-Transfer-Encoding: 8BIT X-Face: #.`T$>|mFxfHna0Wy-(\k3d5TWne~qr.cVHv(ye95XPctC&SXXcZJOPdbqzjWOsgO9AK"/9 unLFS+cdbl&EIVhO2yVW ~z8*h(Rbpng{9B+,_gj+OM{%8O|h5~'Lo=N6jPvwp.vp240Z"`&I(\(#s5[:`y%MIX,%[L=vQJi[S, `B:!}As%w97=Ut[9Eg<(*(^LDD8g Content-Type: TEXT/PLAIN; charset=ISO-8859-1 MIME-Version: 1.0 From: Peter Bortas Date: 20 Jun 1999 02:21:07 +0200 In-Reply-To: "Jon M. Taylor"'s message of "Fri, 18 Jun 1999 17:09:28 -0700 (PDT)" Message-ID: <76u2s3rabw.fsf@lime.idonex.se> Lines: 14 User-Agent: Gnus/5.07008 (Pterodactyl Gnus v0.80) XEmacs/20.4 (Emerald) Resent-Message-ID: <"gIWTM3.0.jL7.XG3Rt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13425 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com "Jon M. Taylor" writes: > ...And on the site, they said that the CPU for this board project will > be ARM. These three pieces of info tell me that the company involved here is > probably Intel! Wow! The big boys are finally taking notice of GGI, it > seems. Actually, I just heard two days ago that Ericsson have 100 prototype Communicator-type telephones running GGI. Sadly, the same rumor say they will probably not hit the market. -- Peter Bortas http://peter.bortas.org Idonex AB http://www.idonex.com From ggi-develop-request@eskimo.com Sat Jun 19 22:29:59 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA07279 for ; Sat, 19 Jun 1999 22:29:58 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA16275; Sat, 19 Jun 1999 19:17:41 -0700 Resent-Date: Sat, 19 Jun 1999 19:17:41 -0700 Date: Sat, 19 Jun 1999 22:17:36 -0400 (EDT) From: James Simmons X-Sender: jsimmons@elmwood.afterfive.com To: ggi-develop Subject: Re: [linux-fbdev] newer patch. (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"SxCoA2.0.1-3.3z4Rt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13426 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com >From Geert himself about my patch. Two basic accel functions look like they will be going into the 2.3.x kernel. Other accel funtions will implemented in /dev/gfx. They are much more open to the idea of /dev/gfx as well. Also Geert suggested that it looks like its time to seperate the VC switching code from the console code. Its being discussed. So it looks like all the work this group done is starting to merge into the kernel. thank you guys for laying the foundation for this work. I toke your ideas and pushed them foward. -------------------------------------------------------------------- - FBIO_FILLRECT, FBIO_COPYAREA: Well, they're trivial to implement. So why not? :-) ------------------------------------------------------------------ From ggi-develop-request@eskimo.com Sun Jun 20 00:06:11 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA08739 for ; Sun, 20 Jun 1999 00:06:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA32129; Sat, 19 Jun 1999 20:54:01 -0700 Resent-Date: Sat, 19 Jun 1999 20:54:01 -0700 From: Andrew Apted Message-ID: <19990620135920.08068@ajax.netspace.net.au> Date: Sun, 20 Jun 1999 13:59:20 +1000 To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes Reply-To: ggi-develop@eskimo.com References: <19990619124806.00048@ajax.netspace.net.au> <199906191410.RAA00398@vesuri.Helsinki.FI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <199906191410.RAA00398@vesuri.Helsinki.FI>; from Aki M Laukkanen on Sat, Jun 19, 1999 at 05:10:01PM +0300 Resent-Message-ID: <"FxZ-b2.0.pr7.LN6Rt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13427 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Aki M Laukkanen writes: > > Are you sure that is the correct fix ? To me that says: "if the > > _original_ mode cannot do panning, then the future one cannot as well", > > which I don't think is right in the general case (I must admit I've > > That snippet is from GGI_fbdev_checkmode() and if I understood > the code correctly priv->fix is not fetched until do_change_mode(). Yep. > Besides if the driver is really so silly that it would return ypanstep > differently for different modes Why is that silly ? The current mode might by 1024x768x16, and there is not enough memory to do any panning, so ypan = 0. The new mode might be 640x480x8 where there *is* enough memory to do panning, so ypan > 0. Or even this: in the current mode, yvres == yres and so ypanstep is 0 (since there is no virtual area to pan into). I can't remember if the fbdev drivers do this or not, but it doesn't seem unreasonable. > then it could just aswell be that the > ypanstep is zero for the current mode but not for the original mode. Yes. Our main problem is that the fbdev API has no notion of "checkmode" like the LibGGI API does, so we have to do a lot of guesswork, and until we set the mode we don't know for sure what it will be like. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Sun Jun 20 03:06:43 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA11653 for ; Sun, 20 Jun 1999 03:06:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA20323; Sat, 19 Jun 1999 23:54:01 -0700 Resent-Date: Sat, 19 Jun 1999 23:54:01 -0700 Date: Sun, 20 Jun 1999 08:52:56 +0200 (MEST) To: ggi-develop@eskimo.com cc: Andreas Beck Subject: Re: libgii - mysterious mouse implementation In-Reply-To: <19990619212052.A849@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"M26mU1.0.Ez4.709Rt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13428 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sat, 19 Jun 1999, Andreas Beck wrote: > Hi ! > > > > BTW: When I look at your patch, I get the impression, that one cannot press > > > the middle button together with the outer buttons. Is that correct ? > > > No. Inputdump recognizes all pressed buttons as expected (when I use the > > second patch above). But inputdump doesn't recognize the middle mouse > > button, when I am moving the mouse... :-( > > O.K. - so if it works nicely, we should include it in our sources, right ? Yes. > > Could you resend me the right patch ? I'll then take care for including it. Of course. Here is it: --- input/mouse/packetparse.c.old Wed Apr 7 16:24:59 1999 +++ input/mouse/packetparse.c Thu Apr 8 14:07:23 1999 @@ -128,9 +132,32 @@ dx = (sint8) (((buf[0] & 0x03) << 6) | (buf[1] & 0x3f)); dy = (sint8) (((buf[0] & 0x0c) << 4) | (buf[2] & 0x3f)); - buttons = ((buf[0] & 0x10) >> 3) - | ((buf[0] & 0x20) >> 5); + /* third button added by Christoph Egger (Christoph_Egger@t-online.de) */ + if (buf[0] == 0x40 && !(mpriv->button_state|buf[1]|buf[2])) + buttons = 4; /* third button on MS compatible mouse */ + else + buttons = ((buf[0] & 0x10) >> 3) + | ((buf[0] & 0x20) >> 5); Cheers, Christoph Egger E-Mail: Christoph_Egger@t-online.de From ggi-develop-request@eskimo.com Sun Jun 20 04:47:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA12152 for ; Sun, 20 Jun 1999 04:47:08 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA10233; Sun, 20 Jun 1999 01:35:37 -0700 Resent-Date: Sun, 20 Jun 1999 01:35:37 -0700 From: Aki M Laukkanen Message-Id: <199906200835.LAA03961@vesuri.Helsinki.FI> Subject: Re: beta2.0b2.1 fixes To: ggi-develop@eskimo.com Date: Sun, 20 Jun 1999 11:35:31 +0300 (EET DST) In-Reply-To: <19990620135920.08068@ajax.netspace.net.au> from "Andrew Apted" at Jun 20, 99 01:59:20 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"_WLH12.0.CV2.MVARt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13429 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Besides if the driver is really so silly that it would return ypanstep > > differently for different modes > Why is that silly ? The current mode might by 1024x768x16, and there is > not enough memory to do any panning, so ypan = 0. The new mode might be > 640x480x8 where there *is* enough memory to do panning, so ypan > 0. Well, you could see it like that but I guess all of the current framebuffer devices choose to implement it as xres == xres_virtual and yres == yres_virtual. By grepping the source for ypanstep I couldn't find a single instance where ypanstep would change after it was first set. > Yes. Our main problem is that the fbdev API has no notion of > "checkmode" like the LibGGI API does, so we have to do a lot of > guesswork, and until we set the mode we don't know for sure what > it will be like. Yes, I can't remember what the exact semantics of FB_ACTIVATE_TEST were supposed to be but I would've liked them to be similar with checkmode. As of now I don't think most of the drivers even check that. -- D. From ggi-develop-request@eskimo.com Sun Jun 20 04:53:40 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA12199 for ; Sun, 20 Jun 1999 04:53:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA11647; Sun, 20 Jun 1999 01:42:13 -0700 Resent-Date: Sun, 20 Jun 1999 01:42:13 -0700 From: Aki M Laukkanen Message-Id: <199906200842.LAA27347@vesuri.Helsinki.FI> Subject: Re: beta2.0b2.1 fixes To: ggi-develop@eskimo.com Date: Sun, 20 Jun 1999 11:42:09 +0300 (EET DST) In-Reply-To: <376C18DE.7321B5C1@stacken.kth.se> from "Marcus Sundberg" at Jun 19, 99 10:25:34 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"zkS9z.0.lr2.ZbARt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13430 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Btw. fbdev does not currently set a signal handler for the VT switch. > > Is there a reason for it and would you accept a patch for it? > VT switching is handled by helper-linvtsw. > Do you have any problem with VT switching in LibGGI? Oh, sorry I didn't notice that. Anyway atleast with the two apps I tried it with (cube3d and a test app of my own), I couldn't get it to switch VTs. I'll have to investigate a bit to find out why. -- D. From ggi-develop-request@eskimo.com Sun Jun 20 07:32:35 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA12707 for ; Sun, 20 Jun 1999 07:32:34 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA12217; Sun, 20 Jun 1999 04:20:48 -0700 Resent-Date: Sun, 20 Jun 1999 04:20:48 -0700 Date: Sun, 20 Jun 1999 07:20:42 -0400 (EDT) From: James Simmons X-Sender: jsimmons@elmwood.afterfive.com To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes In-Reply-To: <199906200835.LAA03961@vesuri.Helsinki.FI> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"DHeK53.0.h-2.EwCRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13431 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Yes. Our main problem is that the fbdev API has no notion of > > "checkmode" like the LibGGI API does, so we have to do a lot of > > guesswork, and until we set the mode we don't know for sure what > > it will be like. > > Yes, I can't remember what the exact semantics of FB_ACTIVATE_TEST > were supposed to be but I would've liked them to be similar with > checkmode. As of now I don't think most of the drivers even check > that. Actually FB_ACTIVATE_TEST is used to check a mode. All the drivers use this. You create a fb_var_screeninfo struct and set var->activate to FB_ACTIVATE_TEST. Then you use the FBIOPUT_VSCREENINFO with this value. It will return a error if it didn't work. It always returns var back to the user. From ggi-develop-request@eskimo.com Sun Jun 20 09:47:14 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA13719 for ; Sun, 20 Jun 1999 09:47:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA26153; Sun, 20 Jun 1999 06:35:32 -0700 Resent-Date: Sun, 20 Jun 1999 06:35:32 -0700 From: Thad Phetteplace Message-Id: <199906201840.NAA01539@dexter.glaci.com> Subject: Re: Fwd: [g200-dev]G400 specs released To: ggi-develop@eskimo.com Date: Sun, 20 Jun 1999 13:40:08 -0500 (CDT) In-Reply-To: <376C1497.2422D5B5@stacken.kth.se> from "Marcus Sundberg" at Jun 19, 99 10:07:19 pm Content-Type: text Resent-Message-ID: <"88iNC1.0.7O6.TuERt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13432 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Denis Oliver Kropp wrote: > > The G400 specs have been released, > > Awesome! > Full specs released to the public at the same time as the hardware. > Wish all HW manufacturers were like this... I'd prefer advanced specs and free prototype hardware for the open source developers... but this is good too. :-) Thad From ggi-develop-request@eskimo.com Sun Jun 20 10:25:11 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA13940 for ; Sun, 20 Jun 1999 10:25:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA02269; Sun, 20 Jun 1999 07:12:15 -0700 Resent-Date: Sun, 20 Jun 1999 07:12:15 -0700 From: Andrew Apted Message-ID: <19990621001754.11145@ajax.netspace.net.au> Date: Mon, 21 Jun 1999 00:17:54 +1000 To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes Reply-To: ggi-develop@eskimo.com References: <199906200835.LAA03961@vesuri.Helsinki.FI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from James Simmons on Sun, Jun 20, 1999 at 07:20:42AM -0400 Resent-Message-ID: <"rp4_C1.0.EZ.-QFRt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13433 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com James Simmons writes: > > Yes, I can't remember what the exact semantics of FB_ACTIVATE_TEST > > were supposed to be but I would've liked them to be similar with > > checkmode. As of now I don't think most of the drivers even check > > that. > > Actually FB_ACTIVATE_TEST is used to check a mode. All the drivers use > this. I guess they've been updated since 2.1.126 :->, in my sources most of the fbdev drivers don't even check the activate field. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Sun Jun 20 10:29:38 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA13951 for ; Sun, 20 Jun 1999 10:29:38 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA03549; Sun, 20 Jun 1999 07:16:17 -0700 Resent-Date: Sun, 20 Jun 1999 07:16:17 -0700 From: Andrew Apted Message-ID: <19990621002156.12522@ajax.netspace.net.au> Date: Mon, 21 Jun 1999 00:21:56 +1000 To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes Reply-To: ggi-develop@eskimo.com References: <19990620135920.08068@ajax.netspace.net.au> <199906200835.LAA03961@vesuri.Helsinki.FI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <199906200835.LAA03961@vesuri.Helsinki.FI>; from Aki M Laukkanen on Sun, Jun 20, 1999 at 11:35:31AM +0300 Resent-Message-ID: <"5gSAn3.0.At.mUFRt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13434 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Aki M Laukkanen writes: > > Yes. Our main problem is that the fbdev API has no notion of > > "checkmode" like the LibGGI API does, so we have to do a lot of > > guesswork, and until we set the mode we don't know for sure what > > it will be like. > > Yes, I can't remember what the exact semantics of FB_ACTIVATE_TEST > were supposed to be but I would've liked them to be similar with > checkmode. Yeah, me too. It may happen...... Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Sun Jun 20 11:29:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA14548 for ; Sun, 20 Jun 1999 11:29:43 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA18675; Sun, 20 Jun 1999 08:18:16 -0700 Resent-Date: Sun, 20 Jun 1999 08:18:16 -0700 Message-ID: <19990620081807.H12720@localhost> Date: Sun, 20 Jun 1999 08:18:07 -0700 From: Aaron Van Couwenberghe To: ggi-develop@eskimo.com Subject: Re: Fwd: [g200-dev]G400 specs released Mail-Followup-To: ggi-develop@eskimo.com References: <99061911460906.00747@master> <376C1497.2422D5B5@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <376C1497.2422D5B5@stacken.kth.se>; from Marcus Sundberg on Sat, Jun 19, 1999 at 10:07:19PM +0000 Sender: Resent-Message-ID: <"8_h_k2.0.WZ4.qOGRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13435 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sat, Jun 19, 1999 at 10:07:19PM +0000, Marcus Sundberg wrote: > Denis Oliver Kropp wrote: > > The G400 specs have been released, > > Awesome! > Full specs released to the public at the same time as the hardware. > Wish all HW manufacturers were like this... Looks like everyone is moving this direction, between nVidia and Matrox's recent behavior. I personally prefer specs to pre-written driver code, but both do equally well. -- ..Aaron Van Couwenberghe... ..vanco@sonic.net.. ..aaronv@debian.org.... Berlin: http://www.berlin-consortium.org Debian GNU/Linux: http://www.debian.org There are three kinds of people in this world: those who can count and those who can't. From ggi-develop-request@eskimo.com Sun Jun 20 11:35:19 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA14576 for ; Sun, 20 Jun 1999 11:35:18 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA19540; Sun, 20 Jun 1999 08:23:45 -0700 Resent-Date: Sun, 20 Jun 1999 08:23:45 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990620124432.B507@rz.uni-duesseldorf.de> Date: Sun, 20 Jun 1999 12:44:32 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes Mail-Followup-To: ggi-develop@eskimo.com References: <376C18DE.7321B5C1@stacken.kth.se> <199906200842.LAA27347@vesuri.Helsinki.FI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <199906200842.LAA27347@vesuri.Helsinki.FI>; from Aki M Laukkanen on Sun, Jun 20, 1999 at 11:42:09AM +0300 Resent-Message-ID: <"fSr_23.0.2n4.0UGRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13436 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Do you have any problem with VT switching in LibGGI? > Oh, sorry I didn't notice that. Anyway atleast with the two apps I > tried it with (cube3d That's strange. I just checked. It works fine here. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sun Jun 20 11:52:36 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA14673 for ; Sun, 20 Jun 1999 11:52:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA22320; Sun, 20 Jun 1999 08:39:47 -0700 Resent-Date: Sun, 20 Jun 1999 08:39:47 -0700 From: Aki M Laukkanen Message-Id: <199906201539.SAA24940@vesuri.Helsinki.FI> Subject: RFC: Integration of HERMES with LibGGI To: ggi-develop@eskimo.com Date: Sun, 20 Jun 1999 18:39:42 +0300 (EET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"AoLlb3.0.XS5.2jGRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13437 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello, being bored on sunday afternoon I decided to try to integrate HERMES to LibGGI. HERMES is a pixel format conversion library and you can find more about it at: http://hermes.terminal.at/ The following patch replaces the default ggiCrossBlit() implementation when it thinks that the conversion could be done with HERMES. This is the very first working version and I've only tested the conversion from 8bit memory target to 24bit X target. I did some benchmarks but forgot to save the results from the LibGGI only implementation so I can't give you exact results. There was some speed gain as expected since the HERMES routines are in optimized assembly. Comments? PS. I only included the minimal patch and you need to rerun automake/autoconf to build the source. Building with HERMES is enabled by specifying a new configure option "--with-hermes[=DIR]". diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/acconfig.h libggi-HERMES/acconfig.h --- libggi-2.0b2.1/acconfig.h Sun May 9 03:16:23 1999 +++ libggi-HERMES/acconfig.h Fri Jun 18 20:31:53 1999 @@ -13,6 +13,9 @@ /* Define to use run-time debugging */ #undef DEBUG +/* Define when compiling with HERMES */ +#undef USE_HERMES + /* Define if you have the header file. */ #undef HAVE_NCURSES_H diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/config.h.in libggi-HERMES/config.h.in --- libggi-2.0b2.1/config.h.in Sun May 9 03:17:12 1999 +++ libggi-HERMES/config.h.in Fri Jun 18 20:35:30 1999 @@ -64,6 +64,9 @@ /* Define to use run-time debugging */ #undef DEBUG +/* Define when compiling with HERMES */ +#undef USE_HERMES + /* Define if you have the header file. */ #undef HAVE_NCURSES_H diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/configure.in libggi-HERMES/configure.in --- libggi-2.0b2.1/configure.in Fri May 14 21:59:24 1999 +++ libggi-HERMES/configure.in Fri Jun 18 20:38:00 1999 @@ -21,7 +21,11 @@ use_debug="yes" use_threads="no" + +use_hermes="no" + THREADLIBS="" +HERMESLIBS="" sublib_libs="" dynload_libs="-lgii -lgg" @@ -156,6 +160,16 @@ [ --disable-debug don't build with run-time debugging (speed freaks)], use_debug=$enableval) +AC_ARG_WITH(hermes, +[ --with-hermes[=DIR] use the HERMES pixel format conversion library], +use_hermes="yes" +if test $withval != "yes"; then + CFLAGS="$CFLAGS -I$withval/include" + CPPFLAGS="$CPPFLAGS -I$withval/include" + LDFLAGS="$LDFLAGS -L$withval/lib" +fi) + + GGI_EXTRA_PATHS @@ -294,6 +308,23 @@ fi fi +have_hermes="no" +if test "x$use_hermes" != "xno"; then + AC_MSG_CHECKING(for HERMES library) + TMP_SAVE_LIBS=$LIBS + LIBS="$LIBS -lHermes" + AC_TRY_LINK([ +#include +],[ +Hermes_Init() +], + have_hermes="yes" + AC_MSG_RESULT(yes), + use_hermes="no" + AC_MSG_RESULT(no) + LIBS=$TMP_SAVE_LIBS) +fi + if test "x$build_aa_target" != "xno"; then AC_CHECK_HEADER(aalib.h, AC_CHECK_LIB(aa, aa_autoinit, foo=bar, build_aa_target="no"), @@ -630,6 +661,7 @@ AC_SUBST(DLLEXT) AC_SUBST(THREADLIBS) +AC_SUBST(HERMESLIBS) AC_SUBST(sublib_libs) AC_SUBST(dynload_libs) @@ -668,6 +700,11 @@ if test "x$use_debug" = "xyes"; then AC_DEFINE(DEBUG) +fi + +if test "x$use_hermes" = "xyes"; then + AC_DEFINE(USE_HERMES) + HERMESLIBS="-lHermes" fi AM_CONFIG_HEADER(config.h) diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/display/fbdev/fbdev.conf libggi-HERMES/display/fbdev/fbdev.conf --- libggi-2.0b2.1/display/fbdev/fbdev.conf Thu Jan 1 02:00:00 1970 +++ libggi-HERMES/display/fbdev/fbdev.conf Sun Jun 20 17:48:06 1999 @@ -0,0 +1,10 @@ +# Mapping file for config-strings to accel libraries +# config-name library_name +# ------------ -------------------------- + +# Native drivers +tgt-fbdev-mga-2164w default/fbdev/mga/m2164w.so + + +# KGIcon drivers +tgt-fbdev-kgicon-generic default/fbdev/kgi/genkgi.so diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/ggi/Makefile.am libggi-HERMES/ggi/Makefile.am --- libggi-2.0b2.1/ggi/Makefile.am Thu Apr 1 03:38:55 1999 +++ libggi-HERMES/ggi/Makefile.am Sun Jun 20 16:48:38 1999 @@ -5,6 +5,6 @@ libggi_la_SOURCES = db.c dl.c events.c gc.c init.c internal.c mode.c stubs.c \ visual.c unix.c libggi_la_LDFLAGS = ${extra_libraries} -version-info 2:0 -libggi_la_LIBADD = -lgii -lgg +libggi_la_LIBADD = -lgii -lgg ${HERMESLIBS} EXTRA_DIST = EXPSYMS diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/ggi/dl.c libggi-HERMES/ggi/dl.c --- libggi-2.0b2.1/ggi/dl.c Thu Apr 1 18:22:10 1999 +++ libggi-HERMES/ggi/dl.c Wed Jun 16 17:19:03 1999 @@ -119,7 +119,7 @@ const char *filename; int err; - GGIDPRINT_LIBS("_ggiAddDL(%p, \"%s\", \"%s\", 0x%x) called\n", + fprintf(stderr, "_ggiAddDL(%p, \"%s\", \"%s\", 0x%x) called\n", vis, name, args ? args : "(null)", type); if ((filename = ggMatchConfig(_ggiConfigHandle, name, NULL)) == NULL) { diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/ggi/init.c libggi-HERMES/ggi/init.c --- libggi-2.0b2.1/ggi/init.c Fri Mar 19 02:16:13 1999 +++ libggi-HERMES/ggi/init.c Sun Jun 20 17:19:50 1999 @@ -35,6 +35,10 @@ #include #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ + /* Global variables */ uint32 _ggiDebugState = 0; int _ggiDebugSync = 0; @@ -72,6 +76,14 @@ return err; } +#ifdef USE_HERMES + err = Hermes_Init(); + if (!err) { + fprintf(stderr, "LibGGI: unable to initialize HERMES\n"); + return GGI_EUNKNOWN; + } +#endif /* USE_HERMES */ + if ((_ggiVisuals.mutex = ggLockCreate()) == NULL) { fprintf(stderr, "LibGGI: unable to initialize core mutex.\n"); giiExit(); @@ -140,6 +152,9 @@ } ggFreeConfig(_ggiConfigHandle); +#ifdef USE_HERMES + Hermes_Done(); +#endif /* USE_HERMES */ giiExit(); _ggiLibIsUp = 0; @@ -341,6 +356,22 @@ return NULL; } } + +#ifdef USE_HERMES + vis->conv_inst = Hermes_ConverterInstance(HERMES_CONVERT_NORMAL); + if (!vis->conv_inst) { + GGIDPRINT_CORE("Cannot get a HERMES converter instance\n"); + ggiClose(vis); + return NULL; + } + + vis->pal_inst = Hermes_PaletteInstance(); + if (!vis->pal_inst) { + GGIDPRINT_CORE("Cannot get a HERMES palette instance\n"); + ggiClose(vis); + return NULL; + } +#endif /* USE_HERMES */ return vis; } diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/ggi/internal.c libggi-HERMES/ggi/internal.c --- libggi-2.0b2.1/ggi/internal.c Mon May 17 10:39:46 1999 +++ libggi-HERMES/ggi/internal.c Sun Jun 20 18:10:11 1999 @@ -27,6 +27,37 @@ #include +#ifdef USE_HERMES +#include + +void _ggi_set_hermes_palette(ggi_visual *vis) +{ + ggi_color *src; + int32 *iter; + int nocols; + + nocols = 1 << GT_DEPTH(LIBGGI_GT(vis)); + + iter = Hermes_PaletteGet(vis->pal_inst); + if (!iter) + return; + + src = vis->palette; + if (!src) + return; + + GGIDPRINT_COLOR("Setting HERMES palette: %d\n", nocols); + + while (nocols--) { + *iter = (src->r & 0xff00) << 8; + *iter |= (src->g & 0xff00); + *iter++ |= src->b >> 8; + src++; + } + + Hermes_PaletteInvalidateCache(vis->pal_inst); +} +#endif /* USE_HERMES */ int _ggi_mask2shift(uint32 mask) { diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/ggi/mode.c libggi-HERMES/ggi/mode.c --- libggi-2.0b2.1/ggi/mode.c Wed Feb 17 02:10:58 1999 +++ libggi-HERMES/ggi/mode.c Sun Jun 20 17:40:53 1999 @@ -33,6 +33,9 @@ #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ /* Static variables */ static ggi_mode _ggiDefaultMode = @@ -126,6 +129,41 @@ col.b = 0; ggiSetGCForeground(vis, ggiMapColor(vis, &col)); ggiSetGCBackground(vis, ggiMapColor(vis, &col)); + +#ifdef USE_HERMES + GGIDPRINT_CORE("ggiSetMode: Initializing HermesFormat\n"); + + memset(&vis->curformat, 0, sizeof (vis->curformat)); + + switch (GT_SCHEME(tm->graphtype)) { + case GT_PALETTE: + case GT_STATIC_PALETTE: + _ggi_set_hermes_palette(vis); + vis->curformat.indexed = 1; + break; + case GT_GREYSCALE: /* FIXME: must emulate with a fake palette */ + vis->curformat.indexed = 1; + break; + case GT_TRUECOLOR: + vis->curformat.r = LIBGGI_PIXFMT(vis)->red_mask; + vis->curformat.g = LIBGGI_PIXFMT(vis)->green_mask; + vis->curformat.b = LIBGGI_PIXFMT(vis)->blue_mask; + vis->curformat.a = LIBGGI_PIXFMT(vis)->alpha_mask; + break; + case GT_TEXT: + default: + /* a flag to remind us not to touch these */ + vis->curformat.indexed = 0x7f; + break; + } + + vis->curformat.bits = LIBGGI_PIXFMT(vis)->size; + + /* reverse endian and other flags */ + if (LIBGGI_PIXFMT(vis)->flags) + vis->curformat.indexed = 0x7f; +#endif /* USE_HERMES */ + /* Clear frames to black */ for (i = 0; i < tm->frames; i++) { GGIDPRINT_CORE("ggiSetMode: SetWriteFrame %d\n", i); diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/ggi/stubs.c libggi-HERMES/ggi/stubs.c --- libggi-2.0b2.1/ggi/stubs.c Fri May 7 00:40:45 1999 +++ libggi-HERMES/ggi/stubs.c Sun Jun 20 17:27:59 1999 @@ -29,6 +29,10 @@ #undef putc +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ + /************** Mode info ****************/ int ggiSetFlags(ggi_visual *vis,ggi_flags flags) @@ -102,7 +106,14 @@ /* Palette, colors, etc... */ int ggiSetPalette(ggi_visual *vis,int s,int len,ggi_color *cmap) -{ return vis->opcolor->setpalvec(vis,s,len,cmap); } +{ + int err = vis->opcolor->setpalvec(vis,s,len,cmap); +#ifdef USE_HERMES + if (err >= 0) + _ggi_set_hermes_palette(vis); +#endif /* USE_HERMES */ + return err; +} int ggiGetPalette(ggi_visual *vis,int s,int len,ggi_color *cmap) { return vis->opcolor->getpalvec(vis,s,len,cmap); } @@ -226,6 +237,22 @@ if (src == dst) { return dst->opdraw->copybox(dst, sx, sy, w, h, dx, dy); } + +#ifdef USE_HERMES + if (src->curformat.indexed != 0x7f && dst->curformat.indexed != 0x7f + && src->r_frame && src->r_frame->layout == src->w_frame->layout + && dst->w_frame->buffer.plb.pixelformat->stdformat + && Hermes_ConverterRequest(dst->conv_inst, &src->curformat, &dst->curformat)) { + if (src->curformat.indexed || dst->curformat.indexed) + Hermes_ConverterPalette(dst->conv_inst, src->pal_inst, dst->pal_inst); + + if (Hermes_ConverterCopy(dst->conv_inst, LIBGGI_CURREAD(src), sx, sy, + w, h, LIBGGI_FB_R_STRIDE(src), LIBGGI_CURWRITE(dst), + dx, dy, w, h, LIBGGI_FB_W_STRIDE(dst))) + return 0; + } +#endif /* USE_HERMES */ + /* Note: We use dst to map the request to, as it will normally be the "smarter" device. */ return dst->opdraw->crossblit(src, sx, sy, w, h, dst, dx, dy); diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/ggi/visual.c libggi-HERMES/ggi/visual.c --- libggi-2.0b2.1/ggi/visual.c Tue Mar 23 02:11:50 1999 +++ libggi-HERMES/ggi/visual.c Sun Jun 20 17:20:15 1999 @@ -29,6 +29,10 @@ #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ + /* ****************************************************************************** Default functions for op-structs @@ -269,6 +273,14 @@ vis->palette = NULL; vis->input = NULL; +#ifdef USE_HERMES + vis->conv_inst = 0; + vis->pal_inst = 0; + vis->curformat.r = vis->curformat.g = vis->curformat.b = vis->curformat.a = 0; + vis->curformat.bits = 0; + vis->curformat.indexed = 0xff; +#endif /* USE_HERMES */ + _ggiZapMode(vis,~0); return vis; @@ -281,6 +293,10 @@ vis->input=NULL; } _ggiCloseDL(vis,~0); +#ifdef USE_HERMES + Hermes_PaletteReturn(vis->pal_inst); + Hermes_ConverterReturn(vis->conv_inst); +#endif /* USE_HERMES */ free(vis->opdisplay); free(vis->opcolor); free(vis->opdraw); diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/include/ggi/internal/internal.h libggi-HERMES/include/ggi/internal/internal.h --- libggi-2.0b2.1/include/ggi/internal/internal.h Thu Apr 1 18:24:27 1999 +++ libggi-HERMES/include/ggi/internal/internal.h Sun Jun 20 16:26:40 1999 @@ -76,6 +76,9 @@ void _ggi_build_palette(ggi_color *pal, int num); void _ggi_smart_match_palettes(ggi_color *pal, int size, ggi_color *ref_pal, int ref_size); +#ifdef USE_HERMES +void _ggi_set_hermes_palette(ggi_visual *vis); +#endif /* USE_HERMES */ /* mode.c */ void _ggiSetDefaultMode(const char *str); diff -urN --exclude=Makefile.in --exclude=configure libggi-2.0b2.1/include/ggi/internal/structs.h libggi-HERMES/include/ggi/internal/structs.h --- libggi-2.0b2.1/include/ggi/internal/structs.h Thu Apr 1 18:30:29 1999 +++ libggi-HERMES/include/ggi/internal/structs.h Sat Jun 19 14:50:58 1999 @@ -42,6 +42,12 @@ #include +#ifdef USE_HERMES +#include + +#include +#endif /* USE_HERMES */ + #define GGI_VERSION_DLL 1 /* Create a OP version number from the library and structure revisions @@ -195,6 +201,11 @@ ggi_db_list *app_dbs; /* List of public DBs */ ggi_db_list *priv_dbs; /* List of private DBs */ ggi_dlhandle_l *dlhandle; /* Handles to dynamic libs */ +#ifdef USE_HERMES + HermesHandle conv_inst; /* returned by Hermes_ConverterInstance() */ + HermesHandle pal_inst; /* returned by Hermes_PaletteInstance() */ + HermesFormat curformat; /* Current mode for HERMES */ +#endif /* USE_HERMES */ /* Extension stuff */ ggi_dlhandle_l *extlib; /* Dynamic libs from extensions */ -- D. From ggi-develop-request@eskimo.com Sun Jun 20 13:03:23 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA15480 for ; Sun, 20 Jun 1999 13:03:22 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA06182; Sun, 20 Jun 1999 09:52:10 -0700 Resent-Date: Sun, 20 Jun 1999 09:52:10 -0700 Sender: ken@eskimo.com Message-ID: <376D1C08.D5FCC8EC@canit.se> Date: Sun, 20 Jun 1999 18:51:20 +0200 From: Kenneth Johansson Organization: Homenet based on two debian boxes X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Fwd: [g200-dev]G400 specs released References: <99061911460906.00747@master> <376C1497.2422D5B5@stacken.kth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"ucMs13.0.JW1.umHRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13438 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg wrote: > Denis Oliver Kropp wrote: > > The G400 specs have been released, > > Awesome! > Full specs released to the public at the same time as the hardware. > Wish all HW manufacturers were like this... > I downloaded the doc (9meg uncompressed) as I wanted to know how sprites was handled but could not really figure it out. Sprite as a word exist exactly one time in the entire document where it's mentioned that g400 have an unlimited amount of them :) From ggi-develop-request@eskimo.com Sun Jun 20 13:16:57 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA15580 for ; Sun, 20 Jun 1999 13:16:56 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA09850; Sun, 20 Jun 1999 10:05:45 -0700 Resent-Date: Sun, 20 Jun 1999 10:05:45 -0700 X-Authentication-Warning: sandra.lysator.liu.se: altic owned process doing -bs Date: Sun, 20 Jun 1999 19:05:31 +0200 (MET DST) From: =?iso-8859-1?Q?Peter_=C5strand?= To: ggi-develop@eskimo.com Subject: KGIcon and monosync-monitor Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"DyB1C1.0.hP2.ezHRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13439 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I'm trying to compile KGIcon for the fixed-frequence monitor HP-A1097C. I have made an entry in ../monitor/monosync/monitors.inc, and it compiles allright. But when I try "insmod kgicon.o", I get: kgicon.o: init_module: Device or resource busy And in the syslog: Jun 20 17:58:15 j250 kernel: Matrox mga2x64 chipset driver rev $Revision: 1.9 $ loaded Jun 20 17:58:15 j250 kernel: Monosync monitor driver rev $Revision: 1.8 $ Jun 20 17:58:15 j250 kernel: monosync.c:116: Hewlett-Packard A1097C (1280x1024 p xl, 380 x 280 mm, 78-78 kHz, 72-72 Hz) Jun 20 17:58:15 j250 kernel: TVP 3026 DAC driver rev $Revison: 1.10 $ Jun 20 17:58:15 j250 kernel: tvp3026.c:318: TVP 3026 rev 01.01 detected. Jun 20 17:58:15 j250 kernel: tvp3026.c:335: Using 135 MHz mode Jun 20 17:58:15 j250 kernel: TVP 3026 PLL driver rev $Revision: 1.6 $ Jun 20 17:58:15 j250 kernel: Matrox Millennium (I/II) accelerator driver rev $Re vision: 1.9 $ loaded Jun 20 17:58:15 j250 kernel: Matrox Graphics Matrox mga2x64 (I/II) driver loaded . Jun 20 17:58:15 j250 kernel: error: kgifb_set_var: Unsupported bpp '1'. Jun 20 17:58:15 j250 last message repeated 2 times Jun 20 17:58:15 j250 kernel: error: kgicon: Cannot find any usable video mode. Jun 20 17:58:15 j250 kernel: TVP 3026 PLL driver removed Jun 20 17:58:15 j250 kernel: TVP 3026 DAC driver removed. Jun 20 17:58:15 j250 kernel: Monosync monitor driver removed. Jun 20 17:58:15 j250 kernel: Matrox mga2x64 chipset driver rev $Revision: 1.9 $ removed Jun 20 17:58:15 j250 kernel: exit_kgi: Finished. I've checked fbcon-kgi.c, but I'm not sure I understand it. Is Unsupported bpp '1' a general error? My setup is Matrox Millenium I, HP1097C and RedHat 6.0 with original kernel. I got the same error with monosync/MDA, but monosync/SVGA works fine. ///// o o -... said Peter From ggi-develop-request@eskimo.com Sun Jun 20 16:24:33 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA17422 for ; Sun, 20 Jun 1999 16:24:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA20270; Sun, 20 Jun 1999 13:13:18 -0700 Resent-Date: Sun, 20 Jun 1999 13:13:18 -0700 Sender: e94_msu@e.kth.se Message-ID: <376D4B4B.8C939A61@stacken.kth.se> Date: Sun, 20 Jun 1999 22:12:59 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: RFC: Integration of HERMES with LibGGI References: <199906201539.SAA24940@vesuri.Helsinki.FI> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"KUzh-1.0.Ny4.NjKRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13440 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Aki M Laukkanen wrote: > > Hello, being bored on sunday afternoon I decided to try to integrate > HERMES to LibGGI. HERMES is a pixel format conversion library and > you can find more about it at: > > http://hermes.terminal.at/ > > The following patch replaces the default ggiCrossBlit() implementation > when it thinks that the conversion could be done with HERMES. This is > the very first working version and I've only tested the conversion from > 8bit memory target to 24bit X target. I did some benchmarks but forgot > to save the results from the LibGGI only implementation so I can't give > you exact results. There was some speed gain as expected since the > HERMES routines are in optimized assembly. Comments? Well first of all - thanks! I've been thinking of hermes, but haven't had any time to look at that. Now the comments. Putting the hook in ggi/stubs.c is wrong, because it will override accelerated crossblits. I'd like to see some benchmarks before putting the code in, and also timings of the ggiSetPalette() overhead. In any case the current _ggi_set_hermes_palette() implementation is unacceptable because it will crawl for apps which set one color at a time. Also, how big is the compiled hermes library, and where can I find the source? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sun Jun 20 16:42:53 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA17625 for ; Sun, 20 Jun 1999 16:42:51 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA23504; Sun, 20 Jun 1999 13:31:55 -0700 Resent-Date: Sun, 20 Jun 1999 13:31:55 -0700 Sender: e94_msu@e.kth.se Message-ID: <376D4FB4.A9E8604B@stacken.kth.se> Date: Sun, 20 Jun 1999 22:31:48 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: beta2.0b2.1 fixes References: <199906200835.LAA03961@vesuri.Helsinki.FI> <19990621001754.11145@ajax.netspace.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"KrlPb2.0._k5.v-KRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13441 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andrew Apted wrote: > > James Simmons writes: > > > > Yes, I can't remember what the exact semantics of FB_ACTIVATE_TEST > > > were supposed to be but I would've liked them to be similar with > > > checkmode. As of now I don't think most of the drivers even check > > > that. > > > > Actually FB_ACTIVATE_TEST is used to check a mode. All the drivers use > > this. > > I guess they've been updated since 2.1.126 :->, in my sources most of > the fbdev drivers don't even check the activate field. It seems they have. And KGIcon doesn't support FB_ACTIVATE_TEST yet... Shame on us! ;) Guess it's time to do some hacking on KGIcon. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sun Jun 20 16:50:14 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA17712 for ; Sun, 20 Jun 1999 16:50:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA25868; Sun, 20 Jun 1999 13:38:47 -0700 Resent-Date: Sun, 20 Jun 1999 13:38:47 -0700 X-Authentication-Warning: sandra.lysator.liu.se: altic owned process doing -bs Date: Sun, 20 Jun 1999 22:38:33 +0200 (MET DST) From: =?iso-8859-1?Q?Peter_=C5strand?= To: ggi-develop@eskimo.com Subject: Re: KGIcon and monosync-monitor In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"Ihg1i1.0.vJ6.M5LRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13442 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I'm trying to compile KGIcon for the fixed-frequence monitor HP-A1097C. I > have made an entry in ../monitor/monosync/monitors.inc, and it compiles > allright. But when I try "insmod kgicon.o", I get: > > kgicon.o: init_module: Device or resource busy By increasing the debuglevel, I get this: Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:1189: Activating kgicon mode 1280x1024#1280x1024[16]. Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:234: check_mode:cmd=0; cnt=9 Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:242: check_mode: clock OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:250: check_mode: ramdac OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:258: check_mode: chipset OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:276: check_mode: accel OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:284: check_mode: monitor OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:234: check_mode:cmd=1; cnt=8 Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:242: check_mode: clock OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:250: check_mode: ramdac OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:258: check_mode: chipset OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:267: Second clock check OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:276: check_mode: accel OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:284: check_mode: monitor OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:234: check_mode:cmd=3; cnt=7 Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:242: check_mode: clock OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:250: check_mode: ramdac OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:258: check_mode: chipset OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:276: check_mode: accel OK Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:1037: Activating failed. Somehow the "monitor OK" doesn't happen. I suppose it's because my monitor definition is wrong. Here is how I thought, in monosync/monitors.inc #ifdef __HP_A1097C__ /* ** */ #define MON_VERSION "0.00 ALPHA" static struct kgi_monitor monitor = { "Hewlett-Packard", /* manufacturer */ "A1097C", /* model */ GM_ALL, /* supported modes */ FL_MON_NORMAL, /* special capabilities */ { 1280, 1024 }, /* maximum resolution */ NULL, /* Private data hook */ { 380, 280 }, /* picture size [mm] */ RGB_DISPLAY, /* RGB monitor */ SYNC_ON_GREEN, /* Sync-on-Green */ { 0, 135000000 }, /* pixel clock range */ # I'm not sure about the line above. I know that the monitors bandwidth is # 135, but can the lower bound be zero? { 78125, 78125 }, /* hfreq range */ { 72, 72 } /* vfreq range */ # The monitors VertRefresh is actually 72.008, but I suppose this should be an integer value? }; #define HTIMINGS 1 #define VTIMINGS 1 static struct kgi_timing vtiming[VTIMINGS] = /* vertical timing in lines */ { /* width bstart sstart send bend total polarity & htiming */ { 1024, 1026, 1027, 1030, 1080, 1085, HPOS | VPOS | 0 } }; # My Xfree-modeline was: # Modeline "1280x1024-2" 135.00 1280 1344 1536 1728 1024 1027 1030 1085 # What about HPOS and VPOS? Where do I get such information? static struct kgi_timing htiming[HTIMINGS] = /* horizontal timing in ns, descending hfreq */ {/* width bstart sstart send bend total dummy */ { 9481, 9481, 9955, 11377, 11377, 12800, 0 } }; # 1/135000000*E9 = 7.4074 ns # 1280 * 74074 =~ 9481, etc. Does it matter if one truncate or round # these values? #endif /* __HP_A1097C__ */ ///// o o -... said Peter. From ggi-develop-request@eskimo.com Sun Jun 20 22:26:38 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA20939 for ; Sun, 20 Jun 1999 22:26:37 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA15028; Sun, 20 Jun 1999 19:13:24 -0700 Resent-Date: Sun, 20 Jun 1999 19:13:24 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990621015256.B24899@rz.uni-duesseldorf.de> Date: Mon, 21 Jun 1999 01:52:56 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: KGIcon and monosync-monitor Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: =?iso-8859-1?Q?=3CPine=2EGSO=2E4=2E00=2E9906201857430=2E6731-100000=40sa?= =?iso-8859-1?Q?ndra=2Elysator=2Eliu=2Ese=3E=3B_from_Peter_=C5strand_on_S?= =?iso-8859-1?Q?un=2C_Jun_20=2C_1999_at_07:05:31PM_+0200?= Resent-Message-ID: <"blXNl2.0.Ug3.0_PRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13443 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Jun 20 17:58:15 j250 kernel: error: kgifb_set_var: Unsupported bpp '1'. > Jun 20 17:58:15 j250 last message repeated 2 times > Jun 20 17:58:15 j250 kernel: error: kgicon: Cannot find any usable video > mode. > I've checked fbcon-kgi.c, but I'm not sure I understand it. Is Unsupported > bpp '1' a general error? You should give the kgicon driver a mode to start up with using insmod kgicon.o kgicon_bpp=8 kgicon_width=1280 kgicon_height=1024 CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sun Jun 20 22:26:59 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA20943 for ; Sun, 20 Jun 1999 22:26:58 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA15202; Sun, 20 Jun 1999 19:13:40 -0700 Resent-Date: Sun, 20 Jun 1999 19:13:40 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990621015043.A24899@rz.uni-duesseldorf.de> Date: Mon, 21 Jun 1999 01:50:43 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: KGIcon and monosync-monitor Mail-Followup-To: ggi-develop@eskimo.com References: X-Mailer: Mutt 0.91.1 In-Reply-To: =?iso-8859-1?Q?=3CPine=2EGSO=2E4=2E00=2E9906202223540=2E7654-100000=40sa?= =?iso-8859-1?Q?ndra=2Elysator=2Eliu=2Ese=3E=3B_from_Peter_=C5strand_on_S?= =?iso-8859-1?Q?un=2C_Jun_20=2C_1999_at_10:38:33PM_+0200?= MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: 8bit Resent-Message-ID: <"0acav3.0.Bj3.I_PRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13444 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Peter Åstrand wrote: > > I'm trying to compile KGIcon for the fixed-frequence monitor HP-A1097C. I > > have made an entry in ../monitor/monosync/monitors.inc, and it compiles > > allright. But when I try "insmod kgicon.o", I get: I'd try generic/generic, as you can then change the setup on the fly, and it is well tested, but the others should work as well. > Jun 20 22:06:48 j250 kernel: fbcon-kgi.c:1189: Activating kgicon mode > 1280x1024#1280x1024[16]. Oh - I see you have thought about that catch. You of course need to use a mode that from the number of lines allows for a 1083 lines mode. It would also help to use a somewhat bigger range for the frequencies. 2-5% should by easily achieveable, as the physical tolerances in any device should be big enough. > #define MON_VERSION "0.00 ALPHA" > static struct kgi_monitor > monitor = { > "Hewlett-Packard", /* manufacturer */ > "A1097C", /* model */ > GM_ALL, /* supported modes */ > FL_MON_NORMAL, /* special capabilities */ > { 1280, 1024 }, /* maximum resolution */ > NULL, /* Private data hook */ > { 380, 280 }, /* picture size [mm] */ > RGB_DISPLAY, /* RGB monitor */ > SYNC_ON_GREEN, /* Sync-on-Green */ > { 0, 135000000 }, /* pixel clock range */ > # I'm not sure about the line above. I know that the monitors bandwidth is > # 135, but can the lower bound be zero? Yes. That can never be achieved anyway as the other setting defy that. No problem anyway. > { 78125, 78125 }, /* hfreq range */ > { 72, 72 } /* vfreq range */ Give those some slack. 76563-79687kHz will allow for 2% deviation, which should be tolerable. 70-74 Hz should do as well. > static struct kgi_timing > vtiming[VTIMINGS] = /* vertical timing in lines */ > { /* width bstart sstart send bend total polarity & htiming */ > { 1024, 1026, 1027, 1030, 1080, 1085, HPOS | VPOS | 0 } > }; > # My Xfree-modeline was: > # Modeline "1280x1024-2" 135.00 1280 1344 1536 1728 1024 1027 1030 1085 > # What about HPOS and VPOS? Where do I get such information? Looks o.k. The sync polarity shouldn't matter for you anyway, as you want to do SOG - right ? > static struct kgi_timing > htiming[HTIMINGS] = /* horizontal timing in ns, descending hfreq */ > {/* width bstart sstart send bend total dummy */ > { 9481, 9481, 9955, 11377, 11377, 12800, 0 } > }; > # 1/135000000*E9 = 7.4074 ns > # 1280 * 74074 =~ 9481, etc. Does it matter if one truncate or round > # these values? Hmm - would have to check, but I'd round up, as the mode checker will probably round down ... CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sun Jun 20 23:24:52 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA21723 for ; Sun, 20 Jun 1999 23:24:51 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA31480; Sun, 20 Jun 1999 20:12:14 -0700 Resent-Date: Sun, 20 Jun 1999 20:12:14 -0700 X-Authentication-Warning: sandra.lysator.liu.se: altic owned process doing -bs Date: Mon, 21 Jun 1999 05:11:57 +0200 (MET DST) From: =?iso-8859-1?Q?Peter_=C5strand?= To: ggi-develop@eskimo.com Subject: Re: KGIcon and monosync-monitor In-Reply-To: <19990621015043.A24899@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"PJBqG2.0.eh7.DsQRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13445 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > It would also help to use a somewhat bigger range for the frequencies. > 2-5% should by easily achieveable, as the physical tolerances in any > device should be big enough. Ok. > Give those some slack. 76563-79687kHz will allow for 2% deviation, which should > be tolerable. 70-74 Hz should do as well. This solved the problem, now it works! It's just wonderful with VCs in 1280x1024 :-) Thanks. ///// o o -... said Peter. From ggi-develop-request@eskimo.com Mon Jun 21 03:47:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA24217 for ; Mon, 21 Jun 1999 03:47:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA12096; Mon, 21 Jun 1999 00:33:56 -0700 Resent-Date: Mon, 21 Jun 1999 00:33:56 -0700 From: Aki M Laukkanen Message-Id: <199906210733.KAA14702@vesuri.Helsinki.FI> Subject: Re: RFC: Integration of HERMES with LibGGI To: ggi-develop@eskimo.com Date: Mon, 21 Jun 1999 10:33:51 +0300 (EET DST) In-Reply-To: <376D4B4B.8C939A61@stacken.kth.se> from "Marcus Sundberg" at Jun 20, 99 10:12:59 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"raCj32.0.oy2.YhURt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13446 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Putting the hook in ggi/stubs.c is wrong, because it will override > accelerated crossblits. Oh yes, forgot about those. > I'd like to see some benchmarks before putting the code in, and also I'm trying to do some benchmarks today. > timings of the ggiSetPalette() overhead. In any case the current It's not much I think because it just calculates the 256 entry lookup table which is done currently in ggiCrossBlit() for the 8->16/24/32 bit cases. > _ggi_set_hermes_palette() implementation is unacceptable because > it will crawl for apps which set one color at a time. Yes, it'll have to change and there's some code missing for the GT_GREYSCALE case (have to emulate it as a palette based mode). Btw. does anything use that? > Also, how big is the compiled hermes library, and where can I find > the source? libc5 and gcc 2.7.2.3: -rwxr-xr-x 1 amlaukka tkol 85251 Jun 16 19:18 libHermes.so.1.0.2* (Interesting, it grew by 2 KB when I tried to strip --strip-debug it.) and source etc. at: http://hermes.terminal.at/ -- D. From ggi-develop-request@eskimo.com Mon Jun 21 11:15:24 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA28964 for ; Mon, 21 Jun 1999 11:15:23 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA30235; Mon, 21 Jun 1999 08:02:42 -0700 Resent-Date: Mon, 21 Jun 1999 08:02:42 -0700 Message-Id: <199906211502.IAA12155@nova.botz.org> X-Mailer: exmh version 2.0.2 2/24/98 To: ggi-develop@eskimo.com Subject: Re: Fwd: [g200-dev]G400 specs released In-Reply-To: Your message of "Sun, 20 Jun 1999 08:18:07 PDT." <19990620081807.H12720@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Jun 1999 08:02:35 -0700 From: Jurgen Botz Resent-Message-ID: <"Otyre3.0.3O7.DGbRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13447 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Aaron Van Couwenberghe wrote: > Looks like everyone is moving this direction, between nVidia and Matrox's > recent behavior. I personally prefer specs to pre-written driver code, > but both do equally well. No they don't. Specs are much better than even a source driver, because when you have specs you can fix bugs in a driver someone else has written. When you don't have specs you can only guess at what is right or wrong or do some trial-and-error checking. So specs are better. But best is for a company to release specs /and/ an open source driver, or sponsor open source driver development. From ggi-develop-request@eskimo.com Mon Jun 21 19:32:28 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA12593 for ; Mon, 21 Jun 1999 19:32:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA22380; Mon, 21 Jun 1999 16:19:49 -0700 Resent-Date: Mon, 21 Jun 1999 16:19:49 -0700 Date: Tue, 22 Jun 1999 01:19:25 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: ggi acting up? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"vHZJx3.0.AR5.2YiRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13448 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi. I hope I didn't just screw up here, cos I'm getting a little tired... My setup: kernel 2.2.9 libggi-2.0b2.1 libgii-0.6 Matrox Millenium I Voodoo II (glide demos are working) Glide2x_SDK-2.1-3.i386.rpm Glide_V2-2.53-1.i386.glibc.rpm RedHat 6.0 did I forget anything? I have been using GGI for a while, and it worked fine. Today I installed Glide (Glide2x_SDK-2.1-3.i386.rpm) and compiled GGI with glide-support. I don't even know if this has anything to do with the problem I'm having, but it's the only thing I can remember having done. When I try to run any GGI-demos from the console, they crash my console, and I have to press Alt-SysRQ-K to get it back. Setting GGI_DEBUG=255 doesn't give any output. Also, the following is snipped from an xterm. [ketil@ns demos]$ ./demo Trying mode F1.[] Suggested mode 640x480.V640x480.F1.D1x1.[C16/16] white=65535 black=0 DrawBox(): 2182 boxes DrawLine(): 3784 lines CopyBox(): 0 seconds [ketil@ns demos]$ export GGI_DEBUG=255 [ketil@ns demos]$ ./demo Segmentation fault (core dumped) Isn't this a little strange? The program works, but not when I set GGI_DEBUG=255...? strace ends like this: open("/usr/local/etc/ggi/libgii.conf", O_RDONLY) = 3 fstat(3, {st_mode=0, st_size=0, ...}) = 0 mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40023000 read(3, "# Mapping file for suggest-strin"..., 4096) = 900 read(3, "", 4096) = 0 close(3) = 0 munmap(0x40023000, 4096) = 0 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ and the backtrace looks like this (to get the backtrace, I ran programs/demos/.libs/lt-demo instead of programs/demos/demo): #0 0x4011b5a8 in main_arena () #1 0x4007bf06 in buffered_vfprintf (s=0x4011b500, format=0x4002049e "%s: ", args=0xbffed598) at vfprintf.c:1752 #2 0x40077856 in _IO_vfprintf (s=0x4011b500, format=0x4002049e "%s: ", ap=0xbffed598) at vfprintf.c:1018 #3 0x4007f6f7 in fprintf (stream=0x4011b500, format=0x4002049e "%s: ") at fprintf.c:32 #4 0x4001f985 in ggDPrintf (sync=0, subsys=0x4003184a "LibGII", form=0x4003183c "Debugging=%d\n") at debug.c:38 #5 0x4002fa7e in giiInit () at init.c:115 #6 0x40017670 in ggiInit () at init.c:69 #7 0x80493b3 in main (argc=0, argv=0xbffffb54) at demo.c:293 #8 0x4004acb3 in __libc_start_main (main=0x80491e8
, argc=1, argv=0xbffffb54, init=0x8048c18 <_init>, fini=0x804a92c <_fini>, rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffb4c) at ../sysdeps/generic/libc-start.c:78 All this doesn't tell me much at all. All I know is I have to head off to bed so I can go to work early in the morning :) I don't have time to recompile ggi without glide to test that, but I don't see how that should affect anything anyway... PS. Is it possible to run XGGI multiheaded, one on the matrox and one on the VoodooII? If so, I want to :) I even have 2 screens here now. Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Mon Jun 21 19:45:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA12818 for ; Mon, 21 Jun 1999 19:45:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA28541; Mon, 21 Jun 1999 16:33:32 -0700 Resent-Date: Mon, 21 Jun 1999 16:33:32 -0700 Date: Mon, 21 Jun 1999 19:34:17 -0400 From: tentacle tentacle boat To: ggi-develop@eskimo.com Subject: cvs checkout degas, constantly failing Message-ID: <19990621193417.A10428@greenbytes.greenbytes.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Resent-Message-ID: <"9kzzC1.0.kz6.BliRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13449 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello, i have been trying to get the latest source via cvs, for 2 days now, i find that cvs will only get the first 3-4 files, then lockup i am pretty sure this isn't a problem on my end because i have no problem getting source from other cvs repositories.. john From ggi-develop-request@eskimo.com Mon Jun 21 19:57:56 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA13089 for ; Mon, 21 Jun 1999 19:57:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA31948; Mon, 21 Jun 1999 16:44:40 -0700 Resent-Date: Mon, 21 Jun 1999 16:44:40 -0700 Sender: marcus@e.kth.se Message-ID: <376ECE5F.3AD97257@stacken.kth.se> Date: Mon, 21 Jun 1999 23:44:31 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: cvs checkout degas, constantly failing References: <19990621193417.A10428@greenbytes.greenbytes.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"mKFZx3.0.po7.bviRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13450 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com tentacle tentacle boat wrote: > > Hello, i have been trying to get the latest source via cvs, for 2 days > now, i find that cvs will only get the first 3-4 files, then lockup > i am pretty sure this isn't a problem on my end because i have > no problem getting source from other cvs repositories.. Hi, you might want to CC this to our anon-CVS maintainer Todd Fries at toddf@acm.org, as I haven't seen him on the list for some time. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 22 01:20:37 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id BAA18042 for ; Tue, 22 Jun 1999 01:20:34 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id WAA19523; Mon, 21 Jun 1999 22:03:17 -0700 Resent-Date: Mon, 21 Jun 1999 22:03:17 -0700 Date: Tue, 22 Jun 1999 01:53:06 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Re: ggi acting up? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"BNhcy.0.em4.HanRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13451 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Ketil Froyn wrote: > read(3, "# Mapping file for suggest-strin"..., 4096) = 900 > read(3, "", 4096) = 0 > close(3) = 0 > munmap(0x40023000, 4096) = 0 > --- SIGSEGV (Segmentation fault) --- > +++ killed by SIGSEGV +++ No idea what the problem is -- but I just had a thought -- what about an environment variable, e.g. GGI_SEGV_GRACEFUL_RESET, if it's set, then libGGI installs a handler for SIGSEGV and tries to gracefully shut down and reset the console. That could help people a bunch when they are debugging. -- Brian From ggi-develop-request@eskimo.com Tue Jun 22 03:10:26 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA19106 for ; Tue, 22 Jun 1999 03:10:25 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA18724; Mon, 21 Jun 1999 23:56:33 -0700 Resent-Date: Mon, 21 Jun 1999 23:56:33 -0700 Date: Tue, 22 Jun 1999 08:56:23 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"RZdB6.0.Ca4.VEpRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13452 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Brian S. Julin wrote: > No idea what the problem is -- but I just had a thought -- > what about an environment variable, e.g. GGI_SEGV_GRACEFUL_RESET, > if it's set, then libGGI installs a handler for SIGSEGV > and tries to gracefully shut down and reset the console. That > could help people a bunch when they are debugging. Is there a reason why this isn't on by default? I'll give it a go, though. Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Tue Jun 22 08:13:25 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA21547 for ; Tue, 22 Jun 1999 08:13:24 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA04432; Tue, 22 Jun 1999 04:57:35 -0700 Resent-Date: Tue, 22 Jun 1999 04:57:35 -0700 Date: Tue, 22 Jun 1999 07:44:20 -0400 (EDT) From: Leimy To: ggi-develop@eskimo.com Subject: nvidia RIVA TNT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"A5JZm2.0.x41.hetRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13453 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com anyone know if there is a target in the new kgi for this card? I would like to "play" around with it. I have purchased the older card at a show this past weekend and would like to see if I could get some graphical stuff going on GGI and KGI. (Game Demo -- something). Also does anyone know if POVRAY can be used with GGI? Dave From ggi-develop-request@eskimo.com Tue Jun 22 09:41:51 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA22836 for ; Tue, 22 Jun 1999 09:41:50 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA30868; Tue, 22 Jun 1999 06:27:00 -0700 Resent-Date: Tue, 22 Jun 1999 06:27:00 -0700 Date: Tue, 22 Jun 1999 10:16:59 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Re: ggi acting up? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"v85YT3.0._X7.YyuRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13454 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Ketil Froyn wrote: > On Tue, 22 Jun 1999, Brian S. Julin wrote: > > > No idea what the problem is -- but I just had a thought -- > > what about an environment variable, e.g. GGI_SEGV_GRACEFUL_RESET, > > if it's set, then libGGI installs a handler for SIGSEGV > > and tries to gracefully shut down and reset the console. That > > could help people a bunch when they are debugging. > > Is there a reason why this isn't on by default? > I'll give it a go, though. Umm... sorry you misunderstood. I was suggesting a new feature; that isn't implemented yet. -- Brian From ggi-develop-request@eskimo.com Tue Jun 22 10:06:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA23227 for ; Tue, 22 Jun 1999 10:06:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA07054; Tue, 22 Jun 1999 06:54:32 -0700 Resent-Date: Tue, 22 Jun 1999 06:54:32 -0700 Date: Tue, 22 Jun 1999 15:54:24 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"wWuXl3.0.0k1.NMvRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13455 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Brian S. Julin wrote: > > Is there a reason why this isn't on by default? > > I'll give it a go, though. > Umm... sorry you misunderstood. I was suggesting a new feature; > that isn't implemented yet. Ah... OK, I'll give it a miss instead, then :) Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Tue Jun 22 11:34:58 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA24809 for ; Tue, 22 Jun 1999 11:34:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA00831; Tue, 22 Jun 1999 08:11:34 -0700 Resent-Date: Tue, 22 Jun 1999 08:11:34 -0700 Sender: tim@lgc.com Message-ID: <376FA758.F98B7AB8@lgc.com> Date: Tue, 22 Jun 1999 10:10:16 -0500 From: Timothy MacDonald Reply-To: tmacdonald@lgc.com X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.9-56 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: speed question Content-Type: multipart/alternative; boundary="------------FD7D5A429259ECEA8909B33F" Resent-Message-ID: <"Zp4Cq.0.F9.IUwRt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13456 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --------------FD7D5A429259ECEA8909B33F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ok first off let me apologize for any stupid questions I may ask. I am trying to brush up on my coding skills and I have been away from the compiler for a while ( my last program was compiled on a 386 with borland turbo c ). I am writing a 2d tank game ( think atari 2600 combat, the cartridge that came with the system ), and I would like to use libggi2d. Is it reasonably speedy to store all my bitmaps in a memory visual and use ggiBlitTrans to write them out onto screen? Do I have to init both ggi and ggi2d? Also, I recently downloaded the current snapshot ( last friday ) and installed it. If I set GGI_DISPLAY to fbdev as root and run a ggi program while running X everthing works fine. However, if I do the same thing as a regular user the program runs, but if I type anything the display starts to become corrupted. It's as if the X desktop is bleeding through on to the ggi visual. Quitting the program left me in a bogus resolution with a corrupted desktop. I had to ctrl-alt-backspace and kill my X server. The specs on my machine are: Redhat Linux 6.0 Kernel Version 2.2.9 Gnome / Enlightenment It is just a guess but I am running transparent windows under enlightenment ( i.e. the xterms show the desktop wallpaper as the background ). It could be that enlightenment is writing that texture directly to the framebuffer to refresh it and thereby doing bad things. Lastly I want to say that ggi is way cool, and I put my vote in for a ggi sprite engine! :) Thanks for the help, -- Timothy MacDonald Landmark Graphics tmacdonald@lgc.com (281)560-1418 "Hell is other people." - Sartre --------------FD7D5A429259ECEA8909B33F Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Ok first off let me apologize for any stupid questions I may ask. I am
trying to brush up on my coding skills and I have been away from the
compiler for a while ( my last program was compiled on a 386 with
borland turbo c ). I am writing a 2d tank game ( think atari 2600
combat, the cartridge that came with the system ), and I would like to
use libggi2d. Is it reasonably speedy to store all my bitmaps in a
memory visual and use ggiBlitTrans to write them out onto screen? Do I
have to init both ggi and ggi2d?

Also, I recently downloaded the current snapshot ( last friday ) and
installed it. If I set GGI_DISPLAY to fbdev as root and run a ggi
program while running X everthing works fine. However, if I do the same
thing as a regular user the program runs, but if I type anything the
display starts to become corrupted. It's as if the X desktop is bleeding
through on to the ggi visual. Quitting the program left me in a bogus
resolution with a corrupted desktop. I had to ctrl-alt-backspace and
kill my X server. The specs on my machine are:

Redhat Linux 6.0
Kernel Version 2.2.9
Gnome / Enlightenment

It is just a guess but I am running transparent windows under
enlightenment ( i.e. the xterms show the desktop wallpaper as the
background ). It could be that enlightenment is writing that texture
directly to the framebuffer to refresh it and thereby doing bad things.

Lastly I want to say that ggi is way cool, and I put my vote in for a
ggi sprite engine! :)
 

Thanks for the help, 

-- 

Timothy MacDonald
Landmark Graphics
tmacdonald@lgc.com
(281)560-1418

"Hell is other people." - Sartre
  --------------FD7D5A429259ECEA8909B33F-- From ggi-develop-request@eskimo.com Tue Jun 22 11:52:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA25270 for ; Tue, 22 Jun 1999 11:52:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA08863; Tue, 22 Jun 1999 08:34:49 -0700 Resent-Date: Tue, 22 Jun 1999 08:34:49 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: speed question Date: Tue, 22 Jun 1999 11:31:04 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <376FA758.F98B7AB8@lgc.com> MIME-Version: 1.0 Message-Id: <99062211345300.09750@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"IqTb71.0.HA2.OqwRt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13457 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Timothy MacDonald wrote: > Lastly I want to say that ggi is way cool, and I put my vote in for a > ggi sprite engine! :) Ya, Im waiting for a transparent bltting function, in the meantime Ill have to make my own software bltter for transparents blts. Other than that Im going to start working on a tile engine using GGI. Not an actual game but a library that allows people to make tile based games. -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Tue Jun 22 12:02:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA25456 for ; Tue, 22 Jun 1999 12:02:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA12957; Tue, 22 Jun 1999 08:47:50 -0700 Resent-Date: Tue, 22 Jun 1999 08:47:50 -0700 Date: Tue, 22 Jun 1999 11:47:32 -0400 (EDT) From: Peter I Amstutz Subject: Re: speed question In-reply-to: <376FA758.F98B7AB8@lgc.com> X-Sender: tetron@emily.oit.umass.edu To: Timothy MacDonald Cc: ggi-develop@eskimo.com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Authentication-warning: emily.oit.umass.edu: tetron owned process doing -bs Resent-Message-ID: <"je0AJ3.0.R93.Q0xRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13458 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Timothy MacDonald wrote: > Also, I recently downloaded the current snapshot ( last friday ) and > installed it. If I set GGI_DISPLAY to fbdev as root and run a ggi > program while running X everthing works fine. However, if I do the same > thing as a regular user the program runs, but if I type anything the > display starts to become corrupted. It's as if the X desktop is bleeding fbdev in X? Evil bad. fbdev explicitly means _full screen_ rendering. It sounds like fbdev and your X server are fighting over video memory, which is why it's spewing garbage all over your screen. What you _wanted_ to do was either a) use the X target and draw in a window or b) ctl-alt-f? to a text console and run your program there. > through on to the ggi visual. Quitting the program left me in a bogus > resolution with a corrupted desktop. I had to ctrl-alt-backspace and > kill my X server. The specs on my machine are: > > Redhat Linux 6.0 > Kernel Version 2.2.9 > Gnome / Enlightenment > > It is just a guess but I am running transparent windows under > enlightenment ( i.e. the xterms show the desktop wallpaper as the > background ). It could be that enlightenment is writing that texture > directly to the framebuffer to refresh it and thereby doing bad things. Transparent terminal windows, while cool looking, are just a hack. It basically captures the background image from where the window is, shades it, then draws your text on that. X isn't really capable of real tranparency (notice if you move an [aeg]term over another window, you don't see that window below it). Berlin on the other hand... :) > Lastly I want to say that ggi is way cool, and I put my vote in for a > ggi sprite engine! :) Yea, there seems to be quite a bit of desire for libggi2d to support hardware sprites along with the necessary blitting functions to implement sprite-like things in software (in particular stenciled drawing and/or drawing with transparency (maybe with alpha channel?)). How is this coming along? Pretty much _every_ prospective writer of a game using GGI or a game SDK using ggi as a backend pretty much needs this functionality and it's the first thing people ask... ------------------ Peter Amstutz -------------------- -------------- tetron@student.umass.edu ------------- ------- http://www-unix.oit.umass.edu/~tetron ------- ----------------------------------------------------- From ggi-develop-request@eskimo.com Tue Jun 22 12:48:05 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA26554 for ; Tue, 22 Jun 1999 12:48:04 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA32746; Tue, 22 Jun 1999 09:34:12 -0700 Resent-Date: Tue, 22 Jun 1999 09:34:12 -0700 From: "David L. Bilbey" Message-Id: <199906221633.MAA20944@colossus.csl.mtu.edu> Subject: Re: IDE To: ggi-develop@eskimo.com Date: Tue, 22 Jun 1999 12:33:37 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"7swiX.0.pz7.0ixRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13459 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com What is the learning curve like on KDevelop? I'm used to vi and make. bilbey -- "There's a world that we know nothing about, that we can only imagine. And that is the world of books." --Jack Handey From ggi-develop-request@eskimo.com Tue Jun 22 13:28:40 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA27321 for ; Tue, 22 Jun 1999 13:28:38 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA17815; Tue, 22 Jun 1999 10:15:35 -0700 Resent-Date: Tue, 22 Jun 1999 10:15:35 -0700 Date: Tue, 22 Jun 1999 18:15:17 +0100 From: Tristan Wibberley To: ggi-develop@eskimo.com Subject: Re: speed question Message-ID: <19990622181517.A28858@ps.cus.umist.ac.uk> References: <376FA758.F98B7AB8@lgc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Peter I Amstutz on Tue, Jun 22, 1999 at 11:47:32AM -0400 Resent-Message-ID: <"JGFZE2.0.7M4.qIyRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13460 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, Jun 22, 1999 at 11:47:32AM -0400, Peter I Amstutz wrote: > On Tue, 22 Jun 1999, Timothy MacDonald wrote: > > > It is just a guess but I am running transparent windows under > > enlightenment ( i.e. the xterms show the desktop wallpaper as the > > background ). It could be that enlightenment is writing that texture > > directly to the framebuffer to refresh it and thereby doing bad things. > > Transparent terminal windows, while cool looking, are just a hack. It > basically captures the background image from where the window is, shades > it, then draws your text on that. X isn't really capable of real > tranparency (notice if you move an [aeg]term over another window, you > don't see that window below it). Berlin on the other hand... :) There must be some serious security concerns with that. Not just from deliberate attacks, but from buggy, transparent window using apps that can *see* what's going on underneath? -- Tristan Wibberley From ggi-develop-request@eskimo.com Tue Jun 22 13:59:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA27944 for ; Tue, 22 Jun 1999 13:59:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA00944; Tue, 22 Jun 1999 10:47:30 -0700 Resent-Date: Tue, 22 Jun 1999 10:47:30 -0700 Message-ID: <376FCB9D.33ACA461@home.com> Date: Tue, 22 Jun 1999 11:45:01 -0600 From: Jim Meier X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: speed question References: <376FA758.F98B7AB8@lgc.com> <19990622181517.A28858@ps.cus.umist.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"687bU2.0.OE.lmyRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13461 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Tristan Wibberley wrote: > On Tue, Jun 22, 1999 at 11:47:32AM -0400, Peter I Amstutz wrote: > > > > Transparent terminal windows, while cool looking, are just a hack. It > > basically captures the background image from where the window is, shades > > it, then draws your text on that. X isn't really capable of real > > tranparency (notice if you move an [aeg]term over another window, you > > don't see that window below it). Berlin on the other hand... :) > > There must be some serious security concerns with that. Not just from deliberate attacks, but from buggy, transparent window using apps that can *see* what's going on underneath? No; The app only sees the root window(the background image or pattern) in this scheme. But ANY window in X is able to take a screenshot, no? I've never heard of any exploit taking advantage of that, but it's interesting .. -- "No, the C code is buggy and all guarantees are off." --Guido van Rossum From ggi-develop-request@eskimo.com Tue Jun 22 15:08:24 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA29372 for ; Tue, 22 Jun 1999 15:08:23 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA27409; Tue, 22 Jun 1999 11:56:41 -0700 Resent-Date: Tue, 22 Jun 1999 11:56:41 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: Sucking the marrow out of hardware (Re: libGGI on matroxfb with Mystique) Date: Tue, 22 Jun 1999 20:55:28 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <19990618193205.B496@rz.uni-duesseldorf.de> MIME-Version: 1.0 Message-Id: <99062220562604.00227@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"ZENEi1.0.mh6.dnzRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13463 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck´s crap from Fre, 18 Jun 1999: > The idea would be to just do it with ggiCopyBox. Don't know, if this is > implemented, though. > > We will work on that sprite/bob stuff ASAP, as it starts to bother many > people. I used ggiCopyBox for that, but I have to "puzzle" the BOBs into the (third) frame. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Tue Jun 22 15:08:30 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA29373 for ; Tue, 22 Jun 1999 15:08:23 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA27323; Tue, 22 Jun 1999 11:56:36 -0700 Resent-Date: Tue, 22 Jun 1999 11:56:36 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com, clanlib@dark.x.dtu.dk, Subject: Re: IDE Date: Tue, 22 Jun 1999 20:47:36 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <199906221633.MAA20944@colossus.csl.mtu.edu> MIME-Version: 1.0 Message-Id: <99062220510202.00227@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"C3tLJ3.0.Fe6.VnzRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13462 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com David L. Bilbey´s crap from Die, 22 Jun 1999: > What is the learning curve like on KDevelop? I'm used to vi and make. You don´t have to switch between editing and making. You have syntax highlighting and easier cunt and paste. You can "browse" through errors with F4. You have a cool ClassBrowser. You have cool configure+stuff management. You can sit there and just develop... That´s nearly all folks ;-) -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Tue Jun 22 15:16:10 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA29512 for ; Tue, 22 Jun 1999 15:16:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA29201; Tue, 22 Jun 1999 12:03:54 -0700 Resent-Date: Tue, 22 Jun 1999 12:03:54 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: IDE Date: Tue, 22 Jun 1999 15:02:52 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <99062220510202.00227@master> MIME-Version: 1.0 Message-Id: <99062215035400.10674@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"fCytb3.0._77.PuzRt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13464 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Denis Oliver Kropp wrote: > David L. Bilbey´s crap from Die, 22 Jun 1999: > > What is the learning curve like on KDevelop? I'm used to vi and make. > > You don´t have to switch between editing and making. > You have syntax highlighting and easier cunt and paste. > You can "browse" through errors with F4. > You have a cool ClassBrowser. > You have cool configure+stuff management. > You can sit there and just develop... > > That´s nearly all folks ;-) Code crusader, now thats the way to go. Although it pretty much has all those features you said and a few more things. -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Tue Jun 22 15:19:12 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA29588 for ; Tue, 22 Jun 1999 15:19:09 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA30253; Tue, 22 Jun 1999 12:07:35 -0700 Resent-Date: Tue, 22 Jun 1999 12:07:35 -0700 Date: Tue, 22 Jun 1999 12:07:25 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: ggi acting up? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"EfyKY1.0.VO7.sxzRt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13465 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Brian S. Julin wrote: > On Tue, 22 Jun 1999, Ketil Froyn wrote: > > read(3, "# Mapping file for suggest-strin"..., 4096) = 900 > > read(3, "", 4096) = 0 > > close(3) = 0 > > munmap(0x40023000, 4096) = 0 > > --- SIGSEGV (Segmentation fault) --- > > +++ killed by SIGSEGV +++ > > No idea what the problem is -- but I just had a thought -- > what about an environment variable, e.g. GGI_SEGV_GRACEFUL_RESET, > if it's set, then libGGI installs a handler for SIGSEGV > and tries to gracefully shut down and reset the console. That > could help people a bunch when they are debugging. I have wished for exactly this many, many times.... Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Tue Jun 22 15:58:13 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA00467 for ; Tue, 22 Jun 1999 15:58:12 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA09401; Tue, 22 Jun 1999 12:46:44 -0700 Resent-Date: Tue, 22 Jun 1999 12:46:44 -0700 Date: Tue, 22 Jun 1999 21:46:33 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: IDE In-Reply-To: <199906221633.MAA20944@colossus.csl.mtu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"qonbP2.0.hI2.YW-Rt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13466 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, David L. Bilbey wrote: > What is the learning curve like on KDevelop? I'm used to vi and make. If you can figure vi out, nothing should be a problem! :D Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Tue Jun 22 16:45:36 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA01810 for ; Tue, 22 Jun 1999 16:45:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA26304; Tue, 22 Jun 1999 13:34:00 -0700 Resent-Date: Tue, 22 Jun 1999 13:34:00 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Full scrreen mode in X? Date: Tue, 22 Jun 1999 16:31:25 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99062216335200.11084@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"cEsJM1.0._P6.lC_Rt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13467 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com How do you setup a full screen mode in X at the resolution you want? -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Tue Jun 22 17:18:42 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA02657 for ; Tue, 22 Jun 1999 17:18:40 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id NAA13356; Tue, 22 Jun 1999 13:56:07 -0700 (PDT) Resent-Date: Tue, 22 Jun 1999 13:56:07 -0700 (PDT) Date: Tue, 22 Jun 1999 16:53:08 -0400 (EDT) From: Peter I Amstutz Subject: Re: Full scrreen mode in X? In-reply-to: <99062216335200.11084@mongoose> X-Sender: tetron@emily.oit.umass.edu To: Garrett B Cc: ggi-develop@eskimo.com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Authentication-warning: emily.oit.umass.edu: tetron owned process doing -bs Resent-Message-ID: <"aXttN3.0.OE3.jW_Rt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13468 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Garrett B wrote: > How do you setup a full screen mode in X at the resolution you want? You want to use the DGA target. I'm not sure if you can set it to arbitrary screen mode though... ------------------ Peter Amstutz -------------------- -------------- tetron@student.umass.edu ------------- ------- http://www-unix.oit.umass.edu/~tetron ------- ----------------------------------------------------- From ggi-develop-request@eskimo.com Tue Jun 22 18:19:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA03991 for ; Tue, 22 Jun 1999 18:19:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA03502; Tue, 22 Jun 1999 15:07:26 -0700 Resent-Date: Tue, 22 Jun 1999 15:07:26 -0700 Sender: marcus@e.kth.se Message-ID: <37700910.7EB6AFBC@stacken.kth.se> Date: Tue, 22 Jun 1999 22:07:12 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Async mode and double buffering References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"S2miF.0.Xs.Ta0St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13471 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > > On Fri, 18 Jun 1999, Garrett B wrote: > > Because when your drawing to the visual the visual will never > > update until you call a ggiFlush() right? Wrong, see Andys reply. > > Im only running GGI on X right now so > > Im not sure about other targets. > > With X you will need to use double buffering. Actually you really > should always use double buffering so that targets which support hardware > pageflipping can be taken advantage of. On the X target the only effect of double buffering is that you waste twice as much memory. That's why nice apps have double buffering as an option which can be turned off. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 22 18:19:19 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA03995 for ; Tue, 22 Jun 1999 18:19:18 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA03266; Tue, 22 Jun 1999 15:06:59 -0700 Resent-Date: Tue, 22 Jun 1999 15:06:59 -0700 Sender: marcus@e.kth.se Message-ID: <377008F6.67525BEB@stacken.kth.se> Date: Tue, 22 Jun 1999 22:06:46 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: ggi acting up? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"X5elp.0.Eo.0a0St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13469 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > > On Tue, 22 Jun 1999, Brian S. Julin wrote: > > No idea what the problem is -- but I just had a thought -- > > what about an environment variable, e.g. GGI_SEGV_GRACEFUL_RESET, > > if it's set, then libGGI installs a handler for SIGSEGV > > and tries to gracefully shut down and reset the console. That > > could help people a bunch when they are debugging. > > I have wished for exactly this many, many times.... This is excactly what ggRegisterCleanup() does, but in an insanely more nice way than a simple signal handler would, and without any user interaction. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 22 18:19:26 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA03999 for ; Tue, 22 Jun 1999 18:19:25 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA03420; Tue, 22 Jun 1999 15:07:16 -0700 Resent-Date: Tue, 22 Jun 1999 15:07:16 -0700 Sender: marcus@e.kth.se Message-ID: <37700903.65855DDC@stacken.kth.se> Date: Tue, 22 Jun 1999 22:06:59 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: speed question References: <376FA758.F98B7AB8@lgc.com> <19990622181517.A28858@ps.cus.umist.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"bqAd7.0._q.Ia0St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13470 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Tristan Wibberley wrote: > There must be some serious security concerns with that. Not just from > deliberate attacks, but from buggy, transparent window using apps that > can *see* what's going on underneath? What security? The security in X is in restricting who's allowed to connect to the X server. Once you are connected you can read screen contents, write screen contents, send events, steal events or peek at events without anyone noticing. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 22 18:21:16 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA04028 for ; Tue, 22 Jun 1999 18:21:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA03845; Tue, 22 Jun 1999 15:07:34 -0700 Resent-Date: Tue, 22 Jun 1999 15:07:34 -0700 Sender: marcus@e.kth.se Message-ID: <37700917.5A8AAA8B@stacken.kth.se> Date: Tue, 22 Jun 1999 22:07:19 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: KGIcon text modes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"z5pHz3.0.lx.ba0St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13472 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com What is the reason for using 13 bpp to represent text mode in KGIcon when all other fbcon drivers use 0 bpp? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 22 18:22:40 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA04065 for ; Tue, 22 Jun 1999 18:22:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA06155; Tue, 22 Jun 1999 15:10:53 -0700 Resent-Date: Tue, 22 Jun 1999 15:10:53 -0700 Sender: marcus@e.kth.se Message-ID: <377009E4.78C8339A@stacken.kth.se> Date: Tue, 22 Jun 1999 22:10:44 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Full scrreen mode in X? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"yjD-53.0.yV1.hd0St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13473 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Peter I Amstutz wrote: > > On Tue, 22 Jun 1999, Garrett B wrote: > > > How do you setup a full screen mode in X at the resolution you want? > > You want to use the DGA target. I'm not sure if you can set it to > arbitrary screen mode though... Only valid modes listed in /etc/XF86Config (or whatever) can be set by the X server. This is true whether you use DGA or not. Also you can't change the bit-depth runtime in XFree <= 3.x. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 22 19:00:42 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA04688 for ; Tue, 22 Jun 1999 19:00:41 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA29435; Tue, 22 Jun 1999 15:49:00 -0700 Resent-Date: Tue, 22 Jun 1999 15:49:00 -0700 Date: Tue, 22 Jun 1999 19:39:16 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Re: KGIcon text modes In-Reply-To: <37700917.5A8AAA8B@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"Kj9vi2.0.fB7.RB1St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13474 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, Marcus Sundberg wrote: > What is the reason for using 13 bpp to represent text mode in KGIcon > when all other fbcon drivers use 0 bpp? My guess is that kgicon did text modes before all the other fbcon drivers did :). Whoever changes this, don't forget to grep the docs/webspace and change those too. -- Brian From ggi-develop-request@eskimo.com Tue Jun 22 19:07:08 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA04812 for ; Tue, 22 Jun 1999 19:07:07 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA00742; Tue, 22 Jun 1999 15:55:15 -0700 Resent-Date: Tue, 22 Jun 1999 15:55:15 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990622200953.A498@rz.uni-duesseldorf.de> Date: Tue, 22 Jun 1999 20:09:53 +0200 From: Andreas Beck To: mailing list GGI Subject: Re: speed question Mail-Followup-To: mailing list GGI References: <376FA758.F98B7AB8@lgc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <376FA758.F98B7AB8@lgc.com>; from Timothy MacDonald on Tue, Jun 22, 1999 at 10:10:16AM -0500 Resent-Message-ID: <"XP1Zf.0.1B.GH1St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13475 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > use libggi2d. Is it reasonably speedy to store all my bitmaps in a > memory visual and use ggiBlitTrans to write BlitTrans ? I don't know much about LibGGI2D, though headers say it hasn't got such a function. LibGGI has ggiCrossBlit, which is reasonably speedy, if you have the same layout in the memory and the main visual. > them out onto screen? Do I have to init both ggi and ggi2d? Yes. In the order ggi first, then ggi2d. In theory ggi2D could do that for you, but according to the source it doesn't. > Also, I recently downloaded the current snapshot ( last friday ) and > installed it. If I set GGI_DISPLAY to fbdev as root and run a ggi > program while running X everthing works fine. However, if I do the same > thing as a regular user the program runs, but if I type anything the > display starts to become corrupted. It's as if the X desktop is bleeding > through on to the ggi visual. One shouldn't do that. Use an X window or DGA for it. The reason it works for root is probably, that it allocates a new console for it. > It is just a guess but I am running transparent windows under > enlightenment ( i.e. the xterms show the desktop wallpaper as the > background ). It could be that enlightenment is writing that texture > directly to the framebuffer to refresh it and thereby doing bad things. No. While the X server is running, it assumes it has full control over the screen unless you are using DGA. Note that you are lucky, as some chipsets lock up, if two processes hit them at once, as you have to arbitrate direct vidmem access and accel access on them. > Lastly I want to say that ggi is way cool, and I put my vote in for a > ggi sprite engine! :) Working on it ... :-) CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 22 22:30:35 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA07768 for ; Tue, 22 Jun 1999 22:30:34 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA09956; Tue, 22 Jun 1999 19:17:37 -0700 Resent-Date: Tue, 22 Jun 1999 19:17:37 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990623010714.A998@rz.uni-duesseldorf.de> Date: Wed, 23 Jun 1999 01:07:14 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: speed question Mail-Followup-To: ggi-develop@eskimo.com References: <376FA758.F98B7AB8@lgc.com> <19990622181517.A28858@ps.cus.umist.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990622181517.A28858@ps.cus.umist.ac.uk>; from Tristan Wibberley on Tue, Jun 22, 1999 at 06:15:17PM +0100 Resent-Message-ID: <"iqfv82.0.wP2.yE4St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13477 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > it, then draws your text on that. X isn't really capable of real > > tranparency (notice if you move an [aeg]term over another window, you > > don't see that window below it). Berlin on the other hand... :) > There must be some serious security concerns with that. Not just from > deliberate attacks, but from buggy, transparent window using apps that > can *see* what's going on underneath? AFAIK the idea is, that they can _not_ see it. If I got the berlin philosophy right, it's quite like the apps running on the sides of the GGI cube. They can _NOT_ see their background, as they consider themselves running on some visual that happens to be a window (which they more-or-less don't know), which happens to be rendered semitransparent, which is again done without their assistance - right ? CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 22 22:31:28 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA07783 for ; Tue, 22 Jun 1999 22:31:27 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA09958; Tue, 22 Jun 1999 19:17:37 -0700 Resent-Date: Tue, 22 Jun 1999 19:17:37 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990623010927.B998@rz.uni-duesseldorf.de> Date: Wed, 23 Jun 1999 01:09:27 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: speed question Mail-Followup-To: ggi-develop@eskimo.com References: <376FA758.F98B7AB8@lgc.com> <19990622181517.A28858@ps.cus.umist.ac.uk> <37700903.65855DDC@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <37700903.65855DDC@stacken.kth.se>; from Marcus Sundberg on Tue, Jun 22, 1999 at 10:06:59PM +0000 Resent-Message-ID: <"pJo6b1.0.RP2.wE4St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13476 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > There must be some serious security concerns with that. Not just from > > deliberate attacks, but from buggy, transparent window using apps that > > can *see* what's going on underneath? > What security? The security in X is in restricting who's allowed > to connect to the X server. > Once you are connected you can read screen contents, write screen > contents, send events, steal events or peek at events without anyone > noticing. That's not completely true. The paranoid here might know the "Secure Keyboard" option of xterm. It will grab the keyboard and ignore SendEvents, thus basically shielding the xterm from the rest of the windowsystem. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Wed Jun 23 00:01:03 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA09069 for ; Wed, 23 Jun 1999 00:01:02 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA07806; Tue, 22 Jun 1999 20:46:56 -0700 Resent-Date: Tue, 22 Jun 1999 20:46:56 -0700 From: Andrew Apted Message-ID: <19990623135221.03631@ajax.netspace.net.au> Date: Wed, 23 Jun 1999 13:52:21 +1000 To: ggi-develop@eskimo.com Subject: Re: KGIcon text modes Reply-To: ggi-develop@eskimo.com References: <37700917.5A8AAA8B@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Brian S. Julin on Tue, Jun 22, 1999 at 07:39:16PM -0400 Resent-Message-ID: <"i9NKk1.0.ev1.jY5St"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13478 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Brian S. Julin writes: > On Tue, 22 Jun 1999, Marcus Sundberg wrote: > > > What is the reason for using 13 bpp to represent text mode in KGIcon > > when all other fbcon drivers use 0 bpp? > > My guess is that kgicon did text modes before all the other fbcon > drivers did :). Correct :-). The fbdev API has no notion of "mode type", only bpp, so I picked an insanely stupid number and used that. (The new way of using 0 is still a hack IMHO -- but the fbdev people are tying themselves to backwards compatibility). Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Wed Jun 23 00:09:58 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA09156 for ; Wed, 23 Jun 1999 00:09:56 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA11301; Tue, 22 Jun 1999 20:57:44 -0700 Resent-Date: Tue, 22 Jun 1999 20:57:44 -0700 Sender: peter@placeholder.idonex.se To: ggi-develop@eskimo.com Subject: Re: cvs checkout degas, constantly failing References: <19990621193417.A10428@greenbytes.greenbytes.cx> <376ECE5F.3AD97257@stacken.kth.se> Content-Transfer-Encoding: 8BIT X-Face: #.`T$>|mFxfHna0Wy-(\k3d5TWne~qr.cVHv(ye95XPctC&SXXcZJOPdbqzjWOsgO9AK"/9 unLFS+cdbl&EIVhO2yVW ~z8*h(Rbpng{9B+,_gj+OM{%8O|h5~'Lo=N6jPvwp.vp240Z"`&I(\(#s5[:`y%MIX,%[L=vQJi[S, `B:!}As%w97=Ut[9Eg<(*(^LDD8g Content-Type: TEXT/PLAIN; charset=ISO-8859-1 MIME-Version: 1.0 From: Peter Bortas Date: 23 Jun 1999 05:57:39 +0200 In-Reply-To: Marcus Sundberg's message of "Mon, 21 Jun 1999 23:44:31 +0000" Message-ID: <76lndbmuvg.fsf@placeholder.idonex.se> Lines: 20 User-Agent: Gnus/5.07008 (Pterodactyl Gnus v0.80) XEmacs/21.1 (20 Minutes to Nikko) Resent-Message-ID: <"42KWx3.0.Pm2.ti5St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13479 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg writes: > tentacle tentacle boat wrote: > > > > Hello, i have been trying to get the latest source via cvs, for 2 days > > now, i find that cvs will only get the first 3-4 files, then lockup > > i am pretty sure this isn't a problem on my end because i have > > no problem getting source from other cvs repositories.. > > Hi, > > you might want to CC this to our anon-CVS maintainer Todd Fries > at toddf@acm.org, as I haven't seen him on the list for some time. Ah. That would be why no one answered my letter about my CVS-mirror. I'll try mailing Todd instead. -- Peter Bortas http://peter.bortas.org Idonex AB http://www.idonex.com From ggi-develop-request@eskimo.com Wed Jun 23 00:18:16 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA09254 for ; Wed, 23 Jun 1999 00:18:14 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA14242; Tue, 22 Jun 1999 21:05:33 -0700 Resent-Date: Tue, 22 Jun 1999 21:05:33 -0700 Sender: peter@placeholder.idonex.se To: mongoose@wpi.edu Cc: ggi-develop@eskimo.com Subject: Re: IDE References: <99062220510202.00227@master> <99062215035400.10674@mongoose> X-Face: #.`T$>|mFxfHna0Wy-(\k3d5TWne~qr.cVHv(ye95XPctC&SXXcZJOPdbqzjWOsgO9AK"/9 unLFS+cdbl&EIVhO2yVW ~z8*h(Rbpng{9B+,_gj+OM{%8O|h5~'Lo=N6jPvwp.vp240Z"`&I(\(#s5[:`y%MIX,%[L=vQJi[S, `B:!}As%w97=Ut[9Eg<(*(^LDD8g MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit From: Peter Bortas Date: 23 Jun 1999 06:05:25 +0200 In-Reply-To: Garrett B's message of "Tue, 22 Jun 1999 15:02:52 -0500" Message-ID: <76g13jmuii.fsf@placeholder.idonex.se> Lines: 23 User-Agent: Gnus/5.07008 (Pterodactyl Gnus v0.80) XEmacs/21.1 (20 Minutes to Nikko) Resent-Message-ID: <"lK8PL.0.KU3.Cq5St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13480 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B writes: > On Tue, 22 Jun 1999, Denis Oliver Kropp wrote: > > David L. Bilbey´s crap from Die, 22 Jun 1999: > > > What is the learning curve like on KDevelop? I'm used to vi and make. > > > > You don´t have to switch between editing and making. > > You have syntax highlighting and easier cunt and paste. > > You can "browse" through errors with F4. > > You have a cool ClassBrowser. > > You have cool configure+stuff management. > > You can sit there and just develop... > > > > That´s nearly all folks ;-) > > Code crusader, now thats the way to go. Although it pretty much has all > those features you said and a few more things. You can do all that and more with XEmacs. 'nuff said. :) -- Peter Bortas http://peter.bortas.org Idonex AB http://www.idonex.com From ggi-develop-request@eskimo.com Wed Jun 23 00:25:47 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA09405 for ; Wed, 23 Jun 1999 00:25:46 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA22085; Tue, 22 Jun 1999 21:13:39 -0700 Resent-Date: Tue, 22 Jun 1999 21:13:39 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: Peter Bortas Subject: Re: IDE Date: Wed, 23 Jun 1999 00:11:17 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <76g13jmuii.fsf@placeholder.idonex.se> Cc: ggi-develop@eskimo.com MIME-Version: 1.0 Message-Id: <99062300132700.00611@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"nwsGz2.0.jO5.ox5St"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13481 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 22 Jun 1999, you wrote: > Garrett B writes: > > > On Tue, 22 Jun 1999, Denis Oliver Kropp wrote: > > > David L. Bilbey´s crap from Die, 22 Jun 1999: > > > > What is the learning curve like on KDevelop? I'm used to vi and make. > > > > > > You don´t have to switch between editing and making. > > > You have syntax highlighting and easier cunt and paste. > > > You can "browse" through errors with F4. > > > You have a cool ClassBrowser. > > > You have cool configure+stuff management. > > > You can sit there and just develop... > > > > > > That´s nearly all folks ;-) > > > > Code crusader, now thats the way to go. Although it pretty much has all > > those features you said and a few more things. > > You can do all that and more with XEmacs. 'nuff said. :) Ugh, I have to say emacs is over glorified, at least in my opinion. Theres so many other IDE's that I find much better to code in. -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Wed Jun 23 04:32:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA11443 for ; Wed, 23 Jun 1999 04:32:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA07138; Wed, 23 Jun 1999 01:20:02 -0700 Resent-Date: Wed, 23 Jun 1999 01:20:02 -0700 Message-ID: <19990623011953.A377@localhost> Date: Wed, 23 Jun 1999 01:19:53 -0700 From: Aaron Van Couwenberghe To: ggi-develop@eskimo.com Subject: Re: speed question Mail-Followup-To: ggi-develop@eskimo.com References: <376FA758.F98B7AB8@lgc.com> <19990622181517.A28858@ps.cus.umist.ac.uk> <19990623010714.A998@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <19990623010714.A998@rz.uni-duesseldorf.de>; from Andreas Beck on Wed, Jun 23, 1999 at 01:07:14AM +0200 Sender: Resent-Message-ID: <"B2xXV1.0.Cl1.iY9St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13482 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, Jun 23, 1999 at 01:07:14AM +0200, Andreas Beck wrote: > AFAIK the idea is, that they can _not_ see it. If I got the berlin > philosophy right, it's quite like the apps running on the sides of the GGI > cube. They can _NOT_ see their background, as they consider themselves > running on some visual that happens to be a window (which they more-or-less > don't know), which happens to be rendered semitransparent, which is again > done without their assistance - right ? a berlin application is given access to nothing but a 'region', which to itself is the entire display. The app then proceeds to draw all over this 'region' with the Warsaw API, which re-maps the calls back into a pluggable windowing mechanism that actually takes care of placement. One cool advantage of this (whether it be useful or not) is that berlin widgets (which are the same class of citizen as a window) can have linear transformations arbirarily applied to them. So, right, in berlin a widget (which might be a window widget) will never be able to see events that another window is listening to (although it itself may be able to listen for them as well), the calls another window is making, the contents of another window.... each 'graphic' operates on its own private axis which is translated meaningfully inside the display server. -- ..Aaron Van Couwenberghe... ..vanco@sonic.net.. ..aaronv@debian.org.... Berlin: http://www.berlin-consortium.org Debian GNU/Linux: http://www.debian.org There are three kinds of people in this world: those who can count and those who can't. From ggi-develop-request@eskimo.com Wed Jun 23 08:23:04 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA12961 for ; Wed, 23 Jun 1999 08:23:03 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA07363; Wed, 23 Jun 1999 05:10:05 -0700 Resent-Date: Wed, 23 Jun 1999 05:10:05 -0700 Date: Wed, 23 Jun 1999 07:56:48 -0400 (EDT) From: Leimy To: ggi-develop@eskimo.com Subject: Re: IDE In-Reply-To: <99062300132700.00611@mongoose> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mx1.eskimo.com id FAA07341 Resent-Message-ID: <"A_gQ2.0.to1.RwCSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13483 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 23 Jun 1999, Garrett B wrote: > On Tue, 22 Jun 1999, you wrote: > > Garrett B writes: > > > > > On Tue, 22 Jun 1999, Denis Oliver Kropp wrote: > > > > David L. Bilbey´s crap from Die, 22 Jun 1999: > > > > > What is the learning curve like on KDevelop? I'm used to vi and make. > > > > > > > > You don´t have to switch between editing and making. > > > > You have syntax highlighting and easier cunt and paste. > > > > You can "browse" through errors with F4. > > > > You have a cool ClassBrowser. > > > > You have cool configure+stuff management. > > > > You can sit there and just develop... > > > > > > > > That´s nearly all folks ;-) > > > > > > Code crusader, now thats the way to go. Although it pretty much has all > > > those features you said and a few more things. > > > > You can do all that and more with XEmacs. 'nuff said. :) > > Ugh, I have to say emacs is over glorified, at least in my opinion. Theres > so many other IDE's that I find much better to code in. > Is this discussion really necessary? > -Mongoose, WPI student majoring in Computer Science. > > "Whenever you find yourself on the side of the majority, > it's time to pause and reflect." -Mark Twain > > From ggi-develop-request@eskimo.com Wed Jun 23 11:04:59 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA16033 for ; Wed, 23 Jun 1999 11:04:58 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA21587; Wed, 23 Jun 1999 07:51:47 -0700 Resent-Date: Wed, 23 Jun 1999 07:51:47 -0700 Sender: core@orb.suntech.fr Message-ID: <3770F505.274B1A0D@ggi-project.org> Date: Wed, 23 Jun 1999 16:53:57 +0200 From: Emmanuel Marty Organization: Suntech X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.9 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Job offers: what I have been doing for the past year. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"cFq7Q3.0.TG5.zHFSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13484 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello again, This messages isn't directly related to GGI but the target audience here matches what I want :) I also asked for Andy's agreement before spamming you all :) My company ("my" not possessively), suntech, is a start-up located in south of France as you [hopefully] know one way or other by now ;) Besides hosting and developing sites for companies on large bandwidth, and selling solutions based around customized linux systems, we have been working, for a year now, on a rather exciting software project. This project is the reason why I have been so silent on the list and so inactive on GGI (besides maintaining the cvs repository, dns and email, which don't amount to that much); I've been working fulltime on it since past may. Revelation #2 :) we have hired our fearful GGI leader, Andreas Beck, to work on this project as well, as freelance since he's doing his thesis at the same time. He's been working on it at regular intervals since past August and we are happy of his excellent work. (not that this is really a surprise) The project is a fully component-based operating system; ie. even memory management is a seperate module; all of them export an interface through a generic scheme. It is not slow, because the system doesn't impose message-passing for everything. I started it and am managing the technical parts of it. Ironically, it almost maps 1:1 to what Jon M. Taylor described last year for libggi3D concept-wise. Components, with a generic interface, object oriented, without hierarchy. I must say that the system was started way before he released his ideas and that Andreas and I were already tempted to tell him ;) Revelation #3, Andreas, among others, has ported KGI over to this new system, and wrapped it into a component. Currently the VGA and Permedia2 drivers have been tested to work, but no doubt that all others do. Today we have a functional system (to a certain extent of functionality, but it is) and need to hire people to expand it. I won't discuss our business plans here but most of the system will be liberated as opensource, and the nonliberated parts will not be of any interest for running the system on regular desktop or server boxes, as it's not what we are targetting. We're currently in the process of getting bigtime funding for the project. We will hire a bunch of people and plan to work with paid freelancers for specific components or tools. We will start officially recruiting people mid-July through normal ways, but since the clue level on this list is exceptionally high, I thought I'd post this and maybe recruit a few gifted people in specific areas. I'll post to a few other places while I'm at it too. Example of work to be distributed: * Writing or porting a macromedia flash player * Porting an IP stack * Porting a JVM * Writing drivers for specific, non massmarket hardware * Helping general system design * etc. Cross-development tools run under linux of course. If you're interested in freelancing for us, please email me privately at core@suntech.fr; the most important is to sum up what you already have done, what are your areas of interest, what you are good at; be honest, there are many areas to cover so there is no need to be exceptionally broad (if you honestly are tho, like Andy, it's even better :) Adding a formal resume to that is preferred but not mandatory for freelancers. If after a while you're interested in physically working at suntech and profit from the fast internet link, microwave, fridge, developer-friendly suits, 100baseTX local link to degas :), modern offices with restrooms as big as a meeting room, and sunny south france, 5 km away from the beach, this can be arranged too. Even if not you will be working in freelance with people (not just me) who are suntech employees. We'll listen to everyone's opinions though. Okay, let me know if you think you can fit in :) -- Emmanuel From ggi-develop-request@eskimo.com Wed Jun 23 11:05:57 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA16047 for ; Wed, 23 Jun 1999 11:05:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA21592; Wed, 23 Jun 1999 07:51:48 -0700 Resent-Date: Wed, 23 Jun 1999 07:51:48 -0700 Sender: core@orb.suntech.fr Message-ID: <3770EBF2.5128B3E@ggi-project.org> Date: Wed, 23 Jun 1999 16:15:14 +0200 From: Emmanuel Marty Organization: Suntech X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.9 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: CVS REPOSITORY: Interruption of service thursday june 24, 1999 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"8klQV.0.6H5.2IFSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13485 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hello all, Tomorrow afternoon (in Europe, ie. early morning in the USA) we are shutting down our links to the internet for approximately two hours. It will probably be a shorter downtime but expect something around that. When the links come back up our entire backbone will be fiber. Should cope with the rapidly growing demand :) I will also profit from the downtime for putting Degas in a 19" rack in our server bay rather than the desktop-ish PC case it is in now; will also upgrade it a little bit hardware-wise and swap the 10baseT card for a 100baseTX one. The concerned services are the ones hosted by degas: master (developer) cvs repository, ggi-project.org email aliases and primary DNS (but secondaries will still be serving the zone). Services hosted at UNC chapel hill such as the website and the ftp server will still be up. I'll make another post tomorrow when the repository is up again. Sorry for the short (24 hours) notice, but our upstream, softway/ISDnet, the coolest international backbone on earth, are needed, and they only confirmed today when they would come. Be sure to email me privately with big capital letters in the subject :) if anything doesn't work properly when degas comes back up. -- Emmanuel From ggi-develop-request@eskimo.com Wed Jun 23 11:08:30 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA16085 for ; Wed, 23 Jun 1999 11:08:29 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA22807; Wed, 23 Jun 1999 07:55:03 -0700 Resent-Date: Wed, 23 Jun 1999 07:55:03 -0700 Sender: jul@reliam.teaser.fr Message-ID: <3770F5D5.549E21C2@easter-eggs.fr> Date: Wed, 23 Jun 1999 16:57:25 +0200 From: Julien Tayon Organization: Easter-eggs X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: fr, en MIME-Version: 1.0 To: ggi kgi , GGI developp Subject: about KGI and KGIcon Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"a66Vr2.0.9a5.6LFSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13486 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Can someone make me clear on one point? concerning the developement of a driver. It is said in the KGI 0.9 snapshot that it is developped far enough for being able to write a driver. However the writing a driver help file, namely refers to the GGI source tree and the kgi directory there belongs to kgicon. The makefile of the kgi-0.9 only takes care of its own tree. I am quite puzzled and really wonders what are the sources needed to developp a driver. And, especially considering that there is no makefile in degas concerning KGI directly (as a module or as a patch of the kernel...) Then does it means that the libggi developped in degas can not target KGI ? Julien Tayon -- Easter-eggs Linux System Integrator 17 bis rue du Dr Zamenhof - 92500 Rueil Malmaison - France Phone: +33 (0) 1 41 29 10 01 - Fax: +33 (0) 1 41 29 11 71 mailto:jtayon@easter-eggs.com - http://www.easter-eggs.com From ggi-develop-request@eskimo.com Wed Jun 23 11:46:07 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA16820 for ; Wed, 23 Jun 1999 11:46:06 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA04477; Wed, 23 Jun 1999 08:32:41 -0700 Resent-Date: Wed, 23 Jun 1999 08:32:41 -0700 Date: Wed, 23 Jun 1999 16:32:26 +0100 From: Tristan Wibberley To: ggi-develop@eskimo.com Subject: Re: speed question Message-ID: <19990623163226.A12623@ps.cus.umist.ac.uk> References: <376FA758.F98B7AB8@lgc.com> <19990622181517.A28858@ps.cus.umist.ac.uk> <37700903.65855DDC@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <37700903.65855DDC@stacken.kth.se>; from Marcus Sundberg on Tue, Jun 22, 1999 at 10:06:59PM +0000 Resent-Message-ID: <"bNWaJ.0.-41.NuFSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13487 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, Jun 22, 1999 at 10:06:59PM +0000, Marcus Sundberg wrote: > Tristan Wibberley wrote: > > There must be some serious security concerns with that. Not just from > > deliberate attacks, but from buggy, transparent window using apps that > > can *see* what's going on underneath? > > What security? The security in X is in restricting who's allowed > to connect to the X server. > Once you are connected you can read screen contents, write screen > contents, send events, steal events or peek at events without anyone > noticing. Security isn't just about protecting your system against malicious attacks, it includes accidents. X should at least have a *way* to guarantee that the contents of particular windows will only ever be copied to your screen under *any* circumstances, accidental or otherwise. People often have private information that buffer overflows (eg in an IRC client) should not be able to expose in any way. Imagine if I was talking to a client on IRC, they were giving me some info so I could retrieve some data and encrypt it for them. While I'm retreiving that data, I would like to be able to guarantee that only trusted apps can get a snapshot of the window. As it is, I'd have to ask for the info in email, request more via email, etc, and I'd have to do that with an xterm. -- Tristan Wibberley From ggi-develop-request@eskimo.com Wed Jun 23 11:49:53 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA16921 for ; Wed, 23 Jun 1999 11:49:52 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA06358; Wed, 23 Jun 1999 08:36:48 -0700 Resent-Date: Wed, 23 Jun 1999 08:36:48 -0700 Date: Wed, 23 Jun 1999 16:36:35 +0100 From: Tristan Wibberley To: ggi-develop@eskimo.com Subject: Re: speed question Message-ID: <19990623163635.B12623@ps.cus.umist.ac.uk> References: <376FA758.F98B7AB8@lgc.com> <19990622181517.A28858@ps.cus.umist.ac.uk> <19990623010714.A998@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990623010714.A998@rz.uni-duesseldorf.de>; from Andreas Beck on Wed, Jun 23, 1999 at 01:07:14AM +0200 Resent-Message-ID: <"GxnkU3.0.jY1.EyFSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13488 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, Jun 23, 1999 at 01:07:14AM +0200, Andreas Beck wrote: > > > it, then draws your text on that. X isn't really capable of real > > > tranparency (notice if you move an [aeg]term over another window, you > > > don't see that window below it). Berlin on the other hand... :) > > > There must be some serious security concerns with that. Not just from > > deliberate attacks, but from buggy, transparent window using apps that > > can *see* what's going on underneath? > > AFAIK the idea is, that they can _not_ see it. If I got the berlin > philosophy right, it's quite like the apps running on the sides of the GGI > cube. They can _NOT_ see their background, as they consider themselves > running on some visual that happens to be a window (which they more-or-less > don't know), which happens to be rendered semitransparent, which is again > done without their assistance - right ? That would satisfy my obsessive security desires, but then if the app didn't know what it's background was like, it couldn't make arrangements to flow things around what's behind it (for aesthetic reasons). A window should be able to be declared as containing sensitive data, then it cannot be seen by any other applications. It's a simple yet effective security measure. -- Tristan Wibberley From ggi-develop-request@eskimo.com Wed Jun 23 11:52:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA17007 for ; Wed, 23 Jun 1999 11:52:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA06855; Wed, 23 Jun 1999 08:39:15 -0700 Resent-Date: Wed, 23 Jun 1999 08:39:15 -0700 Sender: Rodolphe.Ortalo@cert.fr Message-ID: <3770FF5F.3B75@cert.fr> Date: Wed, 23 Jun 1999 17:38:07 +0200 From: Rodolphe Ortalo Organization: ONERA X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.6 sun4m) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Job offers: what I have been doing for the past year. References: <3770F505.274B1A0D@ggi-project.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"zbZu52.0.og1.X-FSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13489 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Emmanuel Marty wrote: > Revelation #2 :) we have hired our fearful GGI leader, > Andreas Beck, to work on this project as well. Project sounds nice, and that's nice to have hired Andreas... Nice to meet yet a new OS inventor. ;-) > Revelation #3 > room, and sunny south france, 5 km away from the beach, Revelation #3.2 : Unfortuntaly, the guys of this city spend too much time on the beach and don't know to play rugby. Furthermore, typically, that's the second fanciest town in that area... but of course, they won't agree. May I ask a question (just to try to motivate yet-another- revelation): why do mention this facts just right now ? Is there some competition somewhere? ;-) Rodolphe From ggi-develop-request@eskimo.com Wed Jun 23 12:05:26 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA17374 for ; Wed, 23 Jun 1999 12:05:25 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA11636; Wed, 23 Jun 1999 08:52:58 -0700 Resent-Date: Wed, 23 Jun 1999 08:52:58 -0700 Date: Wed, 23 Jun 1999 16:52:45 +0100 From: Tristan Wibberley To: ggi-develop@eskimo.com Subject: Re: Job offers: what I have been doing for the past year. Message-ID: <19990623165245.C12623@ps.cus.umist.ac.uk> References: <3770F505.274B1A0D@ggi-project.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <3770F505.274B1A0D@ggi-project.org>; from Emmanuel Marty on Wed, Jun 23, 1999 at 04:53:57PM +0200 Resent-Message-ID: <"hZ3ty1.0.6r2.PBGSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13490 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, Jun 23, 1999 at 04:53:57PM +0200, Emmanuel Marty wrote: > > Cross-development tools run under linux of course. > > If you're interested in freelancing for us, please > email me privately at core@suntech.fr; the most important > is to sum up what you already have done, what are your > areas of interest, what you are good at; be honest, > there are many areas to cover so there is no need to > be exceptionally broad (if you honestly are tho, like Andy, > it's even better :) Adding a formal resume to that is > preferred but not mandatory for freelancers. > > If after a while you're interested in physically working > at suntech and profit from the fast internet link, microwave, > fridge, developer-friendly suits, 100baseTX local link to > degas :), modern offices with restrooms as big as a meeting > room, and sunny south france, 5 km away from the beach, > this can be arranged too. It's moments like this I wish I was born a couple of years earlier. I wanna live in the south of France with a cool job (or at least be paid to work on cool software from UK), but I'm not good enough at programming yet :( -- Tristan Wibberley From ggi-develop-request@eskimo.com Wed Jun 23 12:13:52 1999 Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA17620 for ; Wed, 23 Jun 1999 12:13:49 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id JAA00118; Wed, 23 Jun 1999 09:02:41 -0700 (PDT) Resent-Date: Wed, 23 Jun 1999 09:02:41 -0700 (PDT) Sender: core@orb.suntech.fr Message-ID: <3771069A.2F46EF81@ggi-project.org> Date: Wed, 23 Jun 1999 18:08:58 +0200 From: Emmanuel Marty Organization: Suntech X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.9 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Job offers: what I have been doing for the past year. References: <3770F505.274B1A0D@ggi-project.org> <19990623165245.C12623@ps.cus.umist.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"DW2HE3.0.kK7.GKGSt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13491 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Tristan Wibberley wrote: > It's moments like this I wish I was born a couple of years earlier. I wanna > live in the south of France with a cool job (or at least be paid to > work on cool software from UK), but I'm not good enough at > programming yet :( Hehe.. Don't worry too much then, we'll still be at it in a couple of years :) -- Emmanuel From ggi-develop-request@eskimo.com Wed Jun 23 12:19:47 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA17771 for ; Wed, 23 Jun 1999 12:19:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA16669; Wed, 23 Jun 1999 09:07:50 -0700 Resent-Date: Wed, 23 Jun 1999 09:07:50 -0700 Date: Wed, 23 Jun 1999 18:07:44 +0200 From: =?iso-8859-1?Q?Niklas_H=F6glund?= To: ggi-develop@eskimo.com Subject: Re: ggi acting up? Message-ID: <19990623180743.A4485@canit.se> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Ketil Froyn on Tue, Jun 22, 1999 at 01:19:25AM +0200 Resent-Message-ID: <"r3f-l.0.-34.LPGSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13492 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, Jun 22, 1999 at 01:19:25AM +0200, Ketil Froyn wrote: > #0 0x4011b5a8 in main_arena () > #1 0x4007bf06 in buffered_vfprintf (s=0x4011b500, format=0x4002049e "%s: > ", > args=0xbffed598) at vfprintf.c:1752 > #2 0x40077856 in _IO_vfprintf (s=0x4011b500, format=0x4002049e "%s: ", > ap=0xbffed598) at vfprintf.c:1018 > #3 0x4007f6f7 in fprintf (stream=0x4011b500, format=0x4002049e "%s: ") > at fprintf.c:32 > #4 0x4001f985 in ggDPrintf (sync=0, subsys=0x4003184a "LibGII", > form=0x4003183c "Debugging=%d\n") at debug.c:38 > #5 0x4002fa7e in giiInit () at init.c:115 > #6 0x40017670 in ggiInit () at init.c:69 > #7 0x80493b3 in main (argc=0, argv=0xbffffb54) at demo.c:293 > #8 0x4004acb3 in __libc_start_main (main=0x80491e8
, argc=1, > argv=0xbffffb54, init=0x8048c18 <_init>, fini=0x804a92c <_fini>, > rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffb4c) > at ../sysdeps/generic/libc-start.c:78 I recognise this. I don't know for sure what I did to solve it, but it might have been upgrading glibc or egcs. -- Niklas From ggi-develop-request@eskimo.com Wed Jun 23 12:48:14 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA18494 for ; Wed, 23 Jun 1999 12:48:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA26140; Wed, 23 Jun 1999 09:36:22 -0700 Resent-Date: Wed, 23 Jun 1999 09:36:22 -0700 Sender: tim@lgc.com Message-ID: <37710CC0.6857F5AE@lgc.com> Date: Wed, 23 Jun 1999 11:35:12 -0500 From: Timothy MacDonald Reply-To: tmacdonald@lgc.com X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.9-56 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: speed question References: <376FA758.F98B7AB8@lgc.com> <19990622200953.A498@rz.uni-duesseldorf.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"aqbBi1.0.FO6.5qGSt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13493 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck wrote: > > use libggi2d. Is it reasonably speedy to store all my bitmaps in a > > memory visual and use ggiBlitTrans to write > > BlitTrans ? I don't know much about LibGGI2D, though headers say it hasn't > got such a function. > hrm.. the libggi2d documentation on www.ggi-project.org specifies this function. Of course it is in the old docs section. Maybe I should have taken the word "old" more seriously. :) Oh well, I guess I have to go back to writing my own transparent blitter. Timothy MacDonald Landmark Graphics tmacdonald@lgc.com (281)560-1418 "Hell is other people." - Sartre From ggi-develop-request@eskimo.com Wed Jun 23 12:58:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA18780 for ; Wed, 23 Jun 1999 12:58:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA30515; Wed, 23 Jun 1999 09:46:38 -0700 Resent-Date: Wed, 23 Jun 1999 09:46:38 -0700 From: becka@rz.uni-duesseldorf.de Message-Id: <199906231516.RAA27724@zeus.rz.uni-duesseldorf.de> Subject: Re: ggi_pixelformat In-Reply-To: <199906231443.KAA22527@csmctmto.interpoint.net> from #!/usr/bin/entropy --why-me at "Jun 23, 99 10:43:04 am" To: davidws@csmctmto.interpoint.net (#!/usr/bin/entropy --why-me) Date: Wed, 23 Jun 1999 17:16:13 +0200 (MET DST) Cc: ggi-develop@eskimo.com (mailing list GGI) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"1XBLR3.0.QS7.jzGSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13494 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I am having an annoying problem with ggi_pixelformat. > I have successfully setup a display target "display-X" and have set the > Mode for 8 bit color. When I call ggiGetPixelFormat() the values for > xxx_shift xxx_mask (where xxx can be red,green,blue ) are all 0. Look at clut-shift and clut-mask. 8 bit modes usually use a color look up table. Have a look at the SetPal/GetPal functions and the Map/Unmap functions. > I am able to draw to the display but I can't use the pixelformat so I have > to hard code ggi_pixel values. > Is there something about display-X that would affect ggi_pixelformat ? Not about display-X, but about truecolor versus colormapped modes. CU, ANdy -- Andreas Beck | Email : From ggi-develop-request@eskimo.com Wed Jun 23 14:48:16 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id OAA22249 for ; Wed, 23 Jun 1999 14:48:15 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA19848; Wed, 23 Jun 1999 11:36:31 -0700 Resent-Date: Wed, 23 Jun 1999 11:36:31 -0700 Sender: core@orb.suntech.fr Message-ID: <37712BE0.AD9645EC@ggi-project.org> Date: Wed, 23 Jun 1999 20:48:00 +0200 From: Emmanuel Marty Organization: Suntech X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.10 i686) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Job offers: what I have been doing for the past year. References: <3770F505.274B1A0D@ggi-project.org> <3770FF5F.3B75@cert.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"SgwIP.0.lr4.eaISt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13495 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Rodolphe Ortalo wrote: > > Revelation #3 > > room, and sunny south france, 5 km away from the beach, > > Revelation #3.2 : Unfortuntaly, the guys of this city spend > too much time on the beach and don't know to play rugby. Well, what is better to attract developers, the fact there is a rugby team, or a beach? ;) > Furthermore, typically, that's the second fanciest town > in that area... but of course, they won't agree. Mmmm.. *ponders* No, I won't :-) > May I ask a question (just to try to motivate yet-another- > revelation): why do mention this facts just right now ? > Is there some competition somewhere? ;-) Oh, no - well, there is always competition, not exactly in what we're doing but there will always be - but that's not what motivated this. We just spent the past year quietly developing our thing and now that it is starting to work, we are collecting funds and hiring people, so we have to talk about it some way or other ;) Rodolphe, we have in mind to approach the LAAS at some point in the future when we need extreme torture testing, by the way :) -- Emmanuel From ggi-develop-request@eskimo.com Wed Jun 23 15:00:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA22592 for ; Wed, 23 Jun 1999 15:00:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA26677; Wed, 23 Jun 1999 11:49:13 -0700 Resent-Date: Wed, 23 Jun 1999 11:49:13 -0700 X-Authentication-Warning: sandra.lysator.liu.se: altic owned process doing -bs Date: Wed, 23 Jun 1999 20:48:56 +0200 (MET DST) From: =?iso-8859-1?Q?Peter_=C5strand?= To: ggi-develop@eskimo.com Subject: LibGII+XGGI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"l0JlS3.0.QW6.cmISt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13496 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Sorry if this is a FAQ, but: How do I specify what mouse-type to use for XGGI? I suppose it is using libgii, but can't find suitable documentation. I have a MS Wheelmouse, specified as IMPS/2 in XF86Config. ///// o o -... said Peter. From ggi-develop-request@eskimo.com Wed Jun 23 15:04:30 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA22707 for ; Wed, 23 Jun 1999 15:04:29 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA29906; Wed, 23 Jun 1999 11:53:15 -0700 Resent-Date: Wed, 23 Jun 1999 11:53:15 -0700 Date: Wed, 23 Jun 1999 14:53:09 -0400 (EDT) From: Steve Cheng Sender: steve@sephiroth To: ggi-develop@eskimo.com Subject: Re: KGIcon text modes In-Reply-To: <19990623135221.03631@ajax.netspace.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"LqeWs3.0.7J7.QqISt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13497 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 23 Jun 1999, Andrew Apted wrote: > > > What is the reason for using 13 bpp to represent text mode in KGIcon > > > when all other fbcon drivers use 0 bpp? > Correct :-). The fbdev API has no notion of "mode type", only bpp, so I > picked an insanely stupid number and used that. (The new way of using 0 Heh, insanely stupid? I've just noticed, 13 is unlucky in Western culture :) -- Steve Cheng email: steve@ggi-project.org www: From ggi-develop-request@eskimo.com Wed Jun 23 15:17:23 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA23173 for ; Wed, 23 Jun 1999 15:17:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA01745; Wed, 23 Jun 1999 12:06:24 -0700 Resent-Date: Wed, 23 Jun 1999 12:06:24 -0700 Sender: e94_msu@e.kth.se Message-ID: <37713023.CCD5B97F@stacken.kth.se> Date: Wed, 23 Jun 1999 21:06:11 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com CC: ggi kgi Subject: Re: about KGI and KGIcon References: <3770F5D5.549E21C2@easter-eggs.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"B7t9s2.0.rQ.k0JSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13498 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Julien Tayon wrote: > > Can someone make me clear on one point? > concerning the developement of a driver. It is said in the KGI 0.9 > snapshot that it is developped far enough for being able to write a > driver. However the writing a driver help file, namely refers to the GGI > source tree and the kgi directory there belongs to kgicon. KGI 0.9 is not documented anywhere else than in Steffen's snapshots. Any other documentation either refers to the obsolete old KGI, or KGIcon. > The makefile of the kgi-0.9 only takes care of its own tree. > I am quite puzzled and really wonders what are the sources needed to > developp a driver. Everything related to use and develop for KGI 0.9 is in Steffen's snapshot. > And, especially considering that there is no makefile in degas > concerning KGI directly (as a module or as a patch of the kernel...) > Then does it means that the libggi developped in degas can not target > KGI ? When it is possible to access KGI 0.9 drivers from user-space LibGGI will be able to target KGI 0.9. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 23 15:37:39 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA23862 for ; Wed, 23 Jun 1999 15:37:37 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA11223; Wed, 23 Jun 1999 12:25:26 -0700 Resent-Date: Wed, 23 Jun 1999 12:25:26 -0700 Sender: e94_msu@e.kth.se Message-ID: <37713498.8D560564@stacken.kth.se> Date: Wed, 23 Jun 1999 21:25:12 +0200 From: Marcus Sundberg X-Mailer: Mozilla 4.08 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: LibGII+XGGI References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"Ohoxz3.0.9l2.bIJSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13499 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Peter Åstrand wrote: > > Sorry if this is a FAQ, but: > > How do I specify what mouse-type to use for XGGI? I suppose it is using > libgii, but can't find suitable documentation. I have a MS Wheelmouse, > specified as IMPS/2 in XF86Config. $ cat > ~/.ggi/input/linux-mouse mouse IMPS/2 mdev /dev/psaux ^D $ Or as root if you want it global: # cat > prefix/etc/ggi/input/linux-mouse mouse IMPS/2 mdev /dev/psaux ^D # (where prefix is the directory where you installed LibGII) //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 23 17:20:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA26905 for ; Wed, 23 Jun 1999 17:20:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA20718; Wed, 23 Jun 1999 14:08:40 -0700 Resent-Date: Wed, 23 Jun 1999 14:08:40 -0700 X-Authentication-Warning: sandra.lysator.liu.se: altic owned process doing -bs Date: Wed, 23 Jun 1999 23:08:21 +0200 (MET DST) From: =?iso-8859-1?Q?Peter_=C5strand?= To: ggi-develop@eskimo.com Subject: Re: LibGII+XGGI In-Reply-To: <37713498.8D560564@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"i-mNQ3.0.N35.KpKSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13500 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > How do I specify what mouse-type to use for XGGI? I suppose it is using > > libgii, but can't find suitable documentation. I have a MS Wheelmouse, > > specified as IMPS/2 in XF86Config. > > $ cat > ~/.ggi/input/linux-mouse > mouse IMPS/2 > mdev /dev/psaux It doesn't work. I guess it's because my mouse is a "WheelMouse", released a bit later then IntelliMouse. Setting GGI_DEBUG gives this: LibGII: linux_mouse: prot=`imps2' dev=`/dev/psaux' opts=`' LibGII: linux-mouse: Opened mouse file '/dev/psaux' Read/Write. ... LibGII: Adding event type 1, size 116 at pos 0 LibGII: giiEventPoll(0x81d5310, 0x3ffe, 0xbfffd898) called LibGII: _giiPollAll(0x81d5310, 0x3ffe, (nil)) called LibGII: GII_mouse_poll(0x81d5310, (nil)) called LibGII: Invalid IntelliMouse PS/2 packet LibGII: packet used 1 bytes LibGII: Invalid IntelliMouse PS/2 packet It works great with gpm and Xfree, so probably the drivers just have to be adjusted a bit. Anyway, I solved it by using gpm as a relay via /dev/gpmdata. Also, I had some problems with the font-path. It seems XGGI refuses to start if not _all_ hardcoded font-paths are available. My 100dpi-dir was missing, and I had some trouble before understanding the problem. Is there any user-documentation for LibGII? I need to adjust my keyboard a bit. ///// o o -... said Peter. From ggi-develop-request@eskimo.com Thu Jun 24 02:56:43 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id CAA06364 for ; Thu, 24 Jun 1999 02:56:41 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA03230; Wed, 23 Jun 1999 23:43:11 -0700 Resent-Date: Wed, 23 Jun 1999 23:43:11 -0700 Message-ID: <19990624064326.26501.rocketmail@web119.yahoomail.com> Date: Wed, 23 Jun 1999 23:43:26 -0700 (PDT) From: Kien Pham Subject: Re: Job offers: what I have been doing for the past year. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"kUwBd2.0.6o.pDTSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13501 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- Emmanuel Marty wrote: > * Porting a JVM You might want to look at "http://www.transvirtual.com" Their Open Source "Kaffe" vm is the leading Open Source vm. If you have a Unix emulation layer(on the compilation level), it would be very easy to port. (Read as not easy for me...but many people can.) ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggi-develop-request@eskimo.com Thu Jun 24 05:27:20 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA07716 for ; Thu, 24 Jun 1999 05:27:19 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA29436; Thu, 24 Jun 1999 02:13:37 -0700 Resent-Date: Thu, 24 Jun 1999 02:13:37 -0700 X-Authentication-Warning: brin.cs.umn.edu: dejong owned process doing -bs Date: Thu, 24 Jun 1999 04:13:25 -0500 (CDT) From: Moses DeJong To: ggi-develop@eskimo.com Subject: Re: Job offers: what I have been doing for the past year. In-Reply-To: <19990624064326.26501.rocketmail@web119.yahoomail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"x1l2K.0.iB7.uQVSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13502 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 23 Jun 1999, Kien Pham wrote: > > > --- Emmanuel Marty wrote: > > > * Porting a JVM Actually, the open source version has a new home. It is now hosted at http://www.kaffe.org. The transvirtual site is for the verison that they sell. later mo dejong > You might want to look at "http://www.transvirtual.com" > Their Open Source "Kaffe" vm is the leading Open Source vm. > > If you have a Unix emulation layer(on the compilation > level), it would be very easy to port. (Read as not easy > for me...but many people can.) > > ~K.P. > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > From ggi-develop-request@eskimo.com Thu Jun 24 05:42:55 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA07850 for ; Thu, 24 Jun 1999 05:42:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA31236; Thu, 24 Jun 1999 02:31:37 -0700 Resent-Date: Thu, 24 Jun 1999 02:31:37 -0700 Date: Thu, 24 Jun 1999 11:31:31 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up? In-Reply-To: <19990623180743.A4485@canit.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mx1.eskimo.com id CAA31212 Resent-Message-ID: <"e_kWt.0.ud7.thVSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13503 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 23 Jun 1999, Niklas Höglund wrote: > On Tue, Jun 22, 1999 at 01:19:25AM +0200, Ketil Froyn wrote: > I recognise this. I don't know for sure what I did to solve it, but it > might have been upgrading glibc or egcs. Hmm... I'm running RH6.0 with the glibc and egcs that came with them. Perhaps that is what has done this, I think I compiled GGI only with RH5.2... Do you have newer glibc and egcs than those that come with 6.0, i.e: egcs-2.91.66 glibc-2.1.1-6 Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Thu Jun 24 09:48:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA10559 for ; Thu, 24 Jun 1999 09:48:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA14191; Thu, 24 Jun 1999 06:35:10 -0700 Resent-Date: Thu, 24 Jun 1999 06:35:10 -0700 From: becka@rz.uni-duesseldorf.de Message-Id: <199906241327.PAA12055@zeus.rz.uni-duesseldorf.de> Subject: Re: ggi acting up? In-Reply-To: from Ketil Froyn at "Jun 24, 99 11:31:31 am" To: ggi-develop@eskimo.com Date: Thu, 24 Jun 1999 15:27:42 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"CA3Mf.0.VT3.CGZSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13504 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi ! > > I recognise this. I don't know for sure what I did to solve it, but it > > might have been upgrading glibc or egcs. > > Hmm... I'm running RH6.0 with the glibc and egcs that came with them. > Perhaps that is what has done this, I think I compiled GGI only with > RH5.2... You upgraded ? Make sure you have killed all config.cache files. They might lead to false decisions on include files and such. CU, ANdy -- Andreas Beck | Email : From ggi-develop-request@eskimo.com Thu Jun 24 09:53:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA10721 for ; Thu, 24 Jun 1999 09:53:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA16839; Thu, 24 Jun 1999 06:40:59 -0700 Resent-Date: Thu, 24 Jun 1999 06:40:59 -0700 From: "Jacek Konieczny" Date: Tue, 22 Jun 1999 16:46:07 +0200 To: ggi-develop@eskimo.com Subject: GGI and mono displays Message-ID: <19990622164607.A6249@koniu.local.net> Mail-Followup-To: ggi-develop@eskimo.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Resent-Message-ID: <"LRxBW2.0.X64.fLZSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13505 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I have two coputers at home - one with SVGA and one wit Hercules. The Hercules is very nice even fo X (xevil is cool), but most apps (games) would like more than 2 color. I thought GGI might help (for GGI and svgalib programs). The first thing I tried was Quake (I know it is silly idea) - but it wouldn't work as the machine lacks swap-space. Remotely it won't work neither - this time it is GGI/svgalib-wrapper problem. So I tried GGI demos. In fact I have tried two of them, which mostly worked on other targets - flying_ggis and stars. Only the second worked. Then I tried "trueemu" - it should solve my problems (but probably is slow), but it crashed with "INTERNAL ERROR". But flying_ggis work with "palemu" target although they shouldn't. However they are not perfect - it seems dots are drawn only every 4/8 pixels. I think trueemu should be fixed, as 2-colors targets are those which need dithering most. Maybe then (and after I buy a hard-drive) I could play quake on my local net :-) Greets, Jacek -- +---------+--------------------------------------------------------+ ! , ! Jacek Konieczny, Gliwice, Poland ! ! Jajcus ! email: jajcus@zeus.polsl.gliwice.pl, jacek@kde.org ! ! ! ICQ# 7149127 WWW: none (yet) ! +---------+--------------------------------------powered-by-Linux--+ From ggi-develop-request@eskimo.com Thu Jun 24 09:53:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA10724 for ; Thu, 24 Jun 1999 09:53:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA16860; Thu, 24 Jun 1999 06:41:02 -0700 Resent-Date: Thu, 24 Jun 1999 06:41:02 -0700 From: "Jacek Konieczny" Date: Thu, 24 Jun 1999 15:00:31 +0200 To: ggi-develop@eskimo.com Subject: Re: IDE Message-ID: <19990624150031.A947@koniu.local.net> Mail-Followup-To: ggi-develop@eskimo.com References: <199906221633.MAA20944@colossus.csl.mtu.edu> <99062220510202.00227@master> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <99062220510202.00227@master>; from Denis Oliver Kropp on Tue, Jun 22, 1999 at 08:47:36PM +0200 Resent-Message-ID: <"dnVNh2.0.u64.hLZSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13506 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, Jun 22, 1999 at 08:47:36PM +0200, Denis Oliver Kropp wrote: > David L. Bilbey´s crap from Die, 22 Jun 1999: > > What is the learning curve like on KDevelop? I'm used to vi and make. > > You don´t have to switch between editing and making. In VIM too (:mak) > You have syntax highlighting In VIM too > and easier cunt and paste. It depends das easier mean to somebody > You can "browse" through errors with F4. In VIM with '+' > You have a cool ClassBrowser. AFAIK there are some external ClassBrowser > You have cool configure+stuff management. But with no GGI support. AFAIK you have to write yout configure.in yourself anyway. > You can sit there and just develop... In vim too.... :-) Greets, Jacek PS. This is just my opinion, but I just don't think KDevelop is good for GGI development, and we are on GGI list. And VI-clone doesn't mean primitive. -- +---------+--------------------------------------------------------+ ! , ! Jacek Konieczny, Gliwice, Poland ! ! Jajcus ! email: jajcus@zeus.polsl.gliwice.pl, jacek@kde.org ! ! ! ICQ# 7149127 WWW: none (yet) ! +---------+--------------------------------------powered-by-Linux--+ From ggi-develop-request@eskimo.com Thu Jun 24 10:02:25 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA11063 for ; Thu, 24 Jun 1999 10:02:25 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA19779; Thu, 24 Jun 1999 06:49:01 -0700 Resent-Date: Thu, 24 Jun 1999 06:49:01 -0700 Date: Thu, 24 Jun 1999 15:48:55 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up? In-Reply-To: <199906241327.PAA12055@zeus.rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"p7dsW3.0.aq4.CTZSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13507 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Thu, 24 Jun 1999 becka@rz.uni-duesseldorf.de wrote: > > > I recognise this. I don't know for sure what I did to solve it, but it > > > might have been upgrading glibc or egcs. > > Hmm... I'm running RH6.0 with the glibc and egcs that came with them. > > Perhaps that is what has done this, I think I compiled GGI only with > > RH5.2... > You upgraded ? Make sure you have killed all config.cache files. They > might lead to false decisions on include files and such. I deleted it about 50 times before I was able to make it see that I have glide installed now. :) But I think I've recompiled ggi and not gii. Is that a problem? I can't look at it until sunday, but if that's a problem I can see if this is fixed by recompiling gii too. Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Thu Jun 24 10:12:51 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA11343 for ; Thu, 24 Jun 1999 10:12:50 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA20904; Thu, 24 Jun 1999 06:52:10 -0700 Resent-Date: Thu, 24 Jun 1999 06:52:10 -0700 From: Aki M Laukkanen Message-Id: <199906241352.QAA07135@vesuri.Helsinki.FI> Subject: HERMES integration (take 2) To: ggi-develop@eskimo.com Date: Thu, 24 Jun 1999 16:52:05 +0300 (EET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"kMAhY1.0.L65.9WZSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13508 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Now that I found some time to work with LibGGI again I'm attaching an updated patch of the HERMES stuff. Changes: o _ggi_set_hermes_palette takes two additional arguments: start and len. o the crossblit stuff is moved out from stubs to default/linear_xx directories. In addition I did some benchmarks but these cover only two cases of the many possible. The tests were done with a test application of mine which rendered a graphical effect to a 8-bit memory visual and crossblitted it. 1024x768x24 (display-x) on PII/450: no hermes: Name |Time (ms)|Times -------------------------+---------+----- ggiFlush | 71.141| 155 ggiCrossBlit | 18.561| 155 [the rest omitted] hermes: Name |Time (ms)|Times -------------------------+---------+----- ggiFlush | 71.807| 222 ggiCrossBlit | 22.225| 222 This shows a moderate speed enhancement with ggiCrossBlit(). It doesn't show in the framerate though. I think upgrading to 2.2.x with its MTRR support would take the ggiFlush() time down. Unfortunately this is my work machine and I have no root privileges. 800x600x8 (display-fbdev) on Pentium (classic)/133: no hermes: Name |Time (ms)|Times -------------------------+---------+----- ggiFlush | 0.011| 98 ggiCrossBlit | 17.536| 98 hermes: Name |Time (ms)|Times -------------------------+---------+----- ggiFlush | 0.011| 171 ggiCrossBlit | 17.504| 171 Not much difference here because both visuals have the same pixelformat. 800x600x16 (display-x) on Pentium (classic)/133 no hermes: Name |Time (ms)|Times -------------------------+---------+----- ggiFlush | 35.042| 200 ggiCrossBlit | 64.162| 200 hermes: Name |Time (ms)|Times -------------------------+---------+----- ggiFlush | 35.000| 105 ggiCrossBlit | 23.969| 105 On a slower machine HERMES shows its speed (LibGGI compiled with -O2 -fomit-frame-pointer -mpentium arguments to egcs 1.1.2). The difference in framerate is clearly visible. diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/acconfig.h libggi-HERMES/acconfig.h --- libggi-2.0b2.1/acconfig.h Sun May 9 03:16:23 1999 +++ libggi-HERMES/acconfig.h Fri Jun 18 20:31:53 1999 @@ -13,6 +13,9 @@ /* Define to use run-time debugging */ #undef DEBUG +/* Define when compiling with HERMES */ +#undef USE_HERMES + /* Define if you have the header file. */ #undef HAVE_NCURSES_H diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/config.h.in libggi-HERMES/config.h.in --- libggi-2.0b2.1/config.h.in Sun May 9 03:17:12 1999 +++ libggi-HERMES/config.h.in Fri Jun 18 20:35:30 1999 @@ -64,6 +64,9 @@ /* Define to use run-time debugging */ #undef DEBUG +/* Define when compiling with HERMES */ +#undef USE_HERMES + /* Define if you have the header file. */ #undef HAVE_NCURSES_H diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/configure.in libggi-HERMES/configure.in --- libggi-2.0b2.1/configure.in Fri May 14 21:59:24 1999 +++ libggi-HERMES/configure.in Fri Jun 18 20:38:00 1999 @@ -21,7 +21,11 @@ use_debug="yes" use_threads="no" + +use_hermes="no" + THREADLIBS="" +HERMESLIBS="" sublib_libs="" dynload_libs="-lgii -lgg" @@ -156,6 +160,16 @@ [ --disable-debug don't build with run-time debugging (speed freaks)], use_debug=$enableval) +AC_ARG_WITH(hermes, +[ --with-hermes[=DIR] use the HERMES pixel format conversion library], +use_hermes="yes" +if test $withval != "yes"; then + CFLAGS="$CFLAGS -I$withval/include" + CPPFLAGS="$CPPFLAGS -I$withval/include" + LDFLAGS="$LDFLAGS -L$withval/lib" +fi) + + GGI_EXTRA_PATHS @@ -294,6 +308,23 @@ fi fi +have_hermes="no" +if test "x$use_hermes" != "xno"; then + AC_MSG_CHECKING(for HERMES library) + TMP_SAVE_LIBS=$LIBS + LIBS="$LIBS -lHermes" + AC_TRY_LINK([ +#include +],[ +Hermes_Init() +], + have_hermes="yes" + AC_MSG_RESULT(yes), + use_hermes="no" + AC_MSG_RESULT(no) + LIBS=$TMP_SAVE_LIBS) +fi + if test "x$build_aa_target" != "xno"; then AC_CHECK_HEADER(aalib.h, AC_CHECK_LIB(aa, aa_autoinit, foo=bar, build_aa_target="no"), @@ -630,6 +661,7 @@ AC_SUBST(DLLEXT) AC_SUBST(THREADLIBS) +AC_SUBST(HERMESLIBS) AC_SUBST(sublib_libs) AC_SUBST(dynload_libs) @@ -668,6 +700,11 @@ if test "x$use_debug" = "xyes"; then AC_DEFINE(DEBUG) +fi + +if test "x$use_hermes" = "xyes"; then + AC_DEFINE(USE_HERMES) + HERMESLIBS="-lHermes" fi AM_CONFIG_HEADER(config.h) diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/default/linear_16/crossblit.c libggi-HERMES/default/linear_16/crossblit.c --- libggi-2.0b2.1/default/linear_16/crossblit.c Thu Apr 1 02:12:11 1999 +++ libggi-HERMES/default/linear_16/crossblit.c Thu Jun 24 14:21:11 1999 @@ -31,6 +31,9 @@ #include #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ #define DOSHIFT(val, shift) \ (((shift) >= 0) ? (val) << (shift) : (val) >> -(shift)) @@ -310,12 +313,24 @@ and that the destination pixelformat is sane. */ if (src->r_frame && src->r_frame->layout == dst->w_frame->layout) { - uint32 srcformat - = src->r_frame->buffer.plb.pixelformat->stdformat; - uint32 dstformat - = dst->w_frame->buffer.plb.pixelformat->stdformat; + uint32 srcformat, dstformat; PREPARE_FB(src); +#ifdef USE_HERMES + if (src->curformat.indexed != 0x7f && dst->curformat.indexed != 0x7f + && Hermes_ConverterRequest(dst->conv_inst, &src->curformat, &dst->curformat)) { + if (src->curformat.indexed == 1) + Hermes_ConverterPalette(dst->conv_inst, src->pal_inst, dst->pal_inst); + + if (Hermes_ConverterCopy(dst->conv_inst, LIBGGI_CURREAD(src), sx, sy, + w, h, LIBGGI_FB_R_STRIDE(src), LIBGGI_CURWRITE(dst), + dx, dy, w, h, LIBGGI_FB_W_STRIDE(dst))) + return 0; + } +#endif /* USE_HERMES */ + + srcformat = src->r_frame->buffer.plb.pixelformat->stdformat; + dstformat = dst->w_frame->buffer.plb.pixelformat->stdformat; if (dstformat != 0) { if (srcformat == GGI_DB_STD_8a8i8 && w * h > 256 ) { diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/default/linear_24/crossblit.c libggi-HERMES/default/linear_24/crossblit.c --- libggi-2.0b2.1/default/linear_24/crossblit.c Thu Apr 1 02:12:11 1999 +++ libggi-HERMES/default/linear_24/crossblit.c Thu Jun 24 14:38:52 1999 @@ -31,6 +31,9 @@ #include #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ #define DOSHIFT(val, shift) \ (((shift) >= 0) ? (val) << (shift) : (val) >> -(shift)) @@ -338,12 +341,24 @@ and that the destination pixelformat is sane. */ if (src->r_frame && src->r_frame->layout == dst->w_frame->layout) { - uint32 srcformat - = src->r_frame->buffer.plb.pixelformat->stdformat; - uint32 dstformat - = dst->w_frame->buffer.plb.pixelformat->stdformat; + uint32 srcformat, dstformat; PREPARE_FB(src); +#ifdef USE_HERMES + if (src->curformat.indexed != 0x7f && dst->curformat.indexed != 0x7f + && Hermes_ConverterRequest(dst->conv_inst, &src->curformat, &dst->curformat)) { + if (src->curformat.indexed == 1) + Hermes_ConverterPalette(dst->conv_inst, src->pal_inst, dst->pal_inst); + + if (Hermes_ConverterCopy(dst->conv_inst, LIBGGI_CURREAD(src), sx, sy, + w, h, LIBGGI_FB_R_STRIDE(src), LIBGGI_CURWRITE(dst), + dx, dy, w, h, LIBGGI_FB_W_STRIDE(dst))) + return 0; + } +#endif /* USE_HERMES */ + + srcformat = src->r_frame->buffer.plb.pixelformat->stdformat; + dstformat = dst->w_frame->buffer.plb.pixelformat->stdformat; if (dstformat != 0) { if (srcformat == GGI_DB_STD_8a8i8 && w * h > 256 ) { diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/default/linear_32/crossblit.c libggi-HERMES/default/linear_32/crossblit.c --- libggi-2.0b2.1/default/linear_32/crossblit.c Thu Apr 1 02:12:12 1999 +++ libggi-HERMES/default/linear_32/crossblit.c Thu Jun 24 14:40:53 1999 @@ -31,6 +31,9 @@ #include #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ #define DOSHIFT(val, shift) \ (((shift) >= 0) ? (val) << (shift) : (val) >> -(shift)) @@ -314,12 +317,24 @@ and that the destination pixelformat is sane. */ if (src->r_frame && src->r_frame->layout == dst->w_frame->layout) { - uint32 srcformat - = src->r_frame->buffer.plb.pixelformat->stdformat; - uint32 dstformat - = dst->w_frame->buffer.plb.pixelformat->stdformat; + uint32 srcformat, dstformat; PREPARE_FB(src); +#ifdef USE_HERMES + if (src->curformat.indexed != 0x7f && dst->curformat.indexed != 0x7f + && Hermes_ConverterRequest(dst->conv_inst, &src->curformat, &dst->curformat)) { + if (src->curformat.indexed == 1) + Hermes_ConverterPalette(dst->conv_inst, src->pal_inst, dst->pal_inst); + + if (Hermes_ConverterCopy(dst->conv_inst, LIBGGI_CURREAD(src), sx, sy, + w, h, LIBGGI_FB_R_STRIDE(src), LIBGGI_CURWRITE(dst), + dx, dy, w, h, LIBGGI_FB_W_STRIDE(dst))) + return 0; + } +#endif /* USE_HERMES */ + + srcformat = src->r_frame->buffer.plb.pixelformat->stdformat; + dstformat = dst->w_frame->buffer.plb.pixelformat->stdformat; if (dstformat != 0) { if (srcformat == GGI_DB_STD_8a8i8 && w * h > 256 ) { diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/default/linear_8/crossblit.c libggi-HERMES/default/linear_8/crossblit.c --- libggi-2.0b2.1/default/linear_8/crossblit.c Thu Apr 1 02:12:12 1999 +++ libggi-HERMES/default/linear_8/crossblit.c Thu Jun 24 14:20:18 1999 @@ -31,6 +31,9 @@ #include #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ /* Default fallback */ static inline void @@ -156,13 +159,25 @@ */ if (src->r_frame && src->r_frame->layout == dst->w_frame->layout && dst->w_frame->buffer.plb.pixelformat->stdformat != 0) { - uint32 srcformat - = src->r_frame->buffer.plb.pixelformat->stdformat; - uint32 dstformat - = dst->w_frame->buffer.plb.pixelformat->stdformat; - int pixels = w*h; + uint32 srcformat, dstformat; + int pixels; PREPARE_FB(src); +#ifdef USE_HERMES + if (src->curformat.indexed != 0x7f && dst->curformat.indexed != 0x7f + && Hermes_ConverterRequest(dst->conv_inst, &src->curformat, &dst->curformat)) { + Hermes_ConverterPalette(dst->conv_inst, src->pal_inst, dst->pal_inst); + + if (Hermes_ConverterCopy(dst->conv_inst, LIBGGI_CURREAD(src), sx, sy, + w, h, LIBGGI_FB_R_STRIDE(src), LIBGGI_CURWRITE(dst), + dx, dy, w, h, LIBGGI_FB_W_STRIDE(dst))) + return 0; + } +#endif /* USE_HERMES */ + + srcformat = src->r_frame->buffer.plb.pixelformat->stdformat; + dstformat = dst->w_frame->buffer.plb.pixelformat->stdformat; + pixels = w*h; /* These are the accelerated cases. If neither suits then * fall back to the default. diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/ggi/Makefile.am libggi-HERMES/ggi/Makefile.am --- libggi-2.0b2.1/ggi/Makefile.am Thu Apr 1 03:38:55 1999 +++ libggi-HERMES/ggi/Makefile.am Sun Jun 20 16:48:38 1999 @@ -5,6 +5,6 @@ libggi_la_SOURCES = db.c dl.c events.c gc.c init.c internal.c mode.c stubs.c \ visual.c unix.c libggi_la_LDFLAGS = ${extra_libraries} -version-info 2:0 -libggi_la_LIBADD = -lgii -lgg +libggi_la_LIBADD = -lgii -lgg ${HERMESLIBS} EXTRA_DIST = EXPSYMS diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/ggi/init.c libggi-HERMES/ggi/init.c --- libggi-2.0b2.1/ggi/init.c Fri Mar 19 02:16:13 1999 +++ libggi-HERMES/ggi/init.c Sun Jun 20 17:19:50 1999 @@ -35,6 +35,10 @@ #include #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ + /* Global variables */ uint32 _ggiDebugState = 0; int _ggiDebugSync = 0; @@ -72,6 +76,14 @@ return err; } +#ifdef USE_HERMES + err = Hermes_Init(); + if (!err) { + fprintf(stderr, "LibGGI: unable to initialize HERMES\n"); + return GGI_EUNKNOWN; + } +#endif /* USE_HERMES */ + if ((_ggiVisuals.mutex = ggLockCreate()) == NULL) { fprintf(stderr, "LibGGI: unable to initialize core mutex.\n"); giiExit(); @@ -140,6 +152,9 @@ } ggFreeConfig(_ggiConfigHandle); +#ifdef USE_HERMES + Hermes_Done(); +#endif /* USE_HERMES */ giiExit(); _ggiLibIsUp = 0; @@ -341,6 +356,22 @@ return NULL; } } + +#ifdef USE_HERMES + vis->conv_inst = Hermes_ConverterInstance(HERMES_CONVERT_NORMAL); + if (!vis->conv_inst) { + GGIDPRINT_CORE("Cannot get a HERMES converter instance\n"); + ggiClose(vis); + return NULL; + } + + vis->pal_inst = Hermes_PaletteInstance(); + if (!vis->pal_inst) { + GGIDPRINT_CORE("Cannot get a HERMES palette instance\n"); + ggiClose(vis); + return NULL; + } +#endif /* USE_HERMES */ return vis; } diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/ggi/internal.c libggi-HERMES/ggi/internal.c --- libggi-2.0b2.1/ggi/internal.c Mon May 17 10:39:46 1999 +++ libggi-HERMES/ggi/internal.c Thu Jun 24 14:08:14 1999 @@ -27,6 +27,34 @@ #include +#ifdef USE_HERMES +#include + +void _ggi_set_hermes_palette(ggi_visual *vis, int start, int len) +{ + ggi_color *src; + int32 *iter; + + iter = Hermes_PaletteGet(vis->pal_inst) + start; + if (!iter) + return; + + src = vis->palette + start; + if (!src) + return; + + GGIDPRINT_COLOR("Setting HERMES palette: %d:%d\n", start, len); + + while (len--) { + *iter = (src->r & 0xff00) << 8; + *iter |= (src->g & 0xff00); + *iter++ |= src->b >> 8; + src++; + } + + Hermes_PaletteInvalidateCache(vis->pal_inst); +} +#endif /* USE_HERMES */ int _ggi_mask2shift(uint32 mask) { diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/ggi/mode.c libggi-HERMES/ggi/mode.c --- libggi-2.0b2.1/ggi/mode.c Wed Feb 17 02:10:58 1999 +++ libggi-HERMES/ggi/mode.c Thu Jun 24 14:11:05 1999 @@ -33,6 +33,9 @@ #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ /* Static variables */ static ggi_mode _ggiDefaultMode = @@ -126,6 +129,41 @@ col.b = 0; ggiSetGCForeground(vis, ggiMapColor(vis, &col)); ggiSetGCBackground(vis, ggiMapColor(vis, &col)); + +#ifdef USE_HERMES + GGIDPRINT_CORE("ggiSetMode: Initializing HermesFormat\n"); + + memset(&vis->curformat, 0, sizeof (vis->curformat)); + + switch (GT_SCHEME(tm->graphtype)) { + case GT_PALETTE: + case GT_STATIC_PALETTE: + _ggi_set_hermes_palette(vis, 0, 1 << GT_DEPTH(tm->graphtype)); + vis->curformat.indexed = 1; + break; + case GT_GREYSCALE: /* FIXME: must emulate with a fake palette */ + vis->curformat.indexed = 1; + break; + case GT_TRUECOLOR: + vis->curformat.r = LIBGGI_PIXFMT(vis)->red_mask; + vis->curformat.g = LIBGGI_PIXFMT(vis)->green_mask; + vis->curformat.b = LIBGGI_PIXFMT(vis)->blue_mask; + vis->curformat.a = LIBGGI_PIXFMT(vis)->alpha_mask; + break; + case GT_TEXT: + default: + /* a flag to remind us not to touch these */ + vis->curformat.indexed = 0x7f; + break; + } + + vis->curformat.bits = LIBGGI_PIXFMT(vis)->size; + + /* reverse endian and other flags */ + if (LIBGGI_PIXFMT(vis)->flags) + vis->curformat.indexed = 0x7f; +#endif /* USE_HERMES */ + /* Clear frames to black */ for (i = 0; i < tm->frames; i++) { GGIDPRINT_CORE("ggiSetMode: SetWriteFrame %d\n", i); diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/ggi/stubs.c libggi-HERMES/ggi/stubs.c --- libggi-2.0b2.1/ggi/stubs.c Fri May 7 00:40:45 1999 +++ libggi-HERMES/ggi/stubs.c Thu Jun 24 14:15:03 1999 @@ -29,6 +29,10 @@ #undef putc +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ + /************** Mode info ****************/ int ggiSetFlags(ggi_visual *vis,ggi_flags flags) @@ -102,7 +106,14 @@ /* Palette, colors, etc... */ int ggiSetPalette(ggi_visual *vis,int s,int len,ggi_color *cmap) -{ return vis->opcolor->setpalvec(vis,s,len,cmap); } +{ + int err = vis->opcolor->setpalvec(vis,s,len,cmap); +#ifdef USE_HERMES + if (err >= 0) + _ggi_set_hermes_palette(vis, s, len); +#endif /* USE_HERMES */ + return err; +} int ggiGetPalette(ggi_visual *vis,int s,int len,ggi_color *cmap) { return vis->opcolor->getpalvec(vis,s,len,cmap); } diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/ggi/visual.c libggi-HERMES/ggi/visual.c --- libggi-2.0b2.1/ggi/visual.c Tue Mar 23 02:11:50 1999 +++ libggi-HERMES/ggi/visual.c Sun Jun 20 17:20:15 1999 @@ -29,6 +29,10 @@ #include +#ifdef USE_HERMES +#include +#endif /* USE_HERMES */ + /* ****************************************************************************** Default functions for op-structs @@ -269,6 +273,14 @@ vis->palette = NULL; vis->input = NULL; +#ifdef USE_HERMES + vis->conv_inst = 0; + vis->pal_inst = 0; + vis->curformat.r = vis->curformat.g = vis->curformat.b = vis->curformat.a = 0; + vis->curformat.bits = 0; + vis->curformat.indexed = 0xff; +#endif /* USE_HERMES */ + _ggiZapMode(vis,~0); return vis; @@ -281,6 +293,10 @@ vis->input=NULL; } _ggiCloseDL(vis,~0); +#ifdef USE_HERMES + Hermes_PaletteReturn(vis->pal_inst); + Hermes_ConverterReturn(vis->conv_inst); +#endif /* USE_HERMES */ free(vis->opdisplay); free(vis->opcolor); free(vis->opdraw); diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/include/ggi/internal/internal.h libggi-HERMES/include/ggi/internal/internal.h --- libggi-2.0b2.1/include/ggi/internal/internal.h Thu Apr 1 18:24:27 1999 +++ libggi-HERMES/include/ggi/internal/internal.h Thu Jun 24 15:01:39 1999 @@ -76,6 +76,9 @@ void _ggi_build_palette(ggi_color *pal, int num); void _ggi_smart_match_palettes(ggi_color *pal, int size, ggi_color *ref_pal, int ref_size); +#ifdef USE_HERMES +void _ggi_set_hermes_palette(ggi_visual *vis, int start, int len); +#endif /* USE_HERMES */ /* mode.c */ void _ggiSetDefaultMode(const char *str); diff -urN --exclude=Makefile.in --exclude=configure --exclude=Makefile --exclude=*~ libggi-2.0b2.1/include/ggi/internal/structs.h libggi-HERMES/include/ggi/internal/structs.h --- libggi-2.0b2.1/include/ggi/internal/structs.h Thu Apr 1 18:30:29 1999 +++ libggi-HERMES/include/ggi/internal/structs.h Sat Jun 19 14:50:58 1999 @@ -42,6 +42,12 @@ #include +#ifdef USE_HERMES +#include + +#include +#endif /* USE_HERMES */ + #define GGI_VERSION_DLL 1 /* Create a OP version number from the library and structure revisions @@ -195,6 +201,11 @@ ggi_db_list *app_dbs; /* List of public DBs */ ggi_db_list *priv_dbs; /* List of private DBs */ ggi_dlhandle_l *dlhandle; /* Handles to dynamic libs */ +#ifdef USE_HERMES + HermesHandle conv_inst; /* returned by Hermes_ConverterInstance() */ + HermesHandle pal_inst; /* returned by Hermes_PaletteInstance() */ + HermesFormat curformat; /* Current mode for HERMES */ +#endif /* USE_HERMES */ /* Extension stuff */ ggi_dlhandle_l *extlib; /* Dynamic libs from extensions */ -- D. From ggi-develop-request@eskimo.com Thu Jun 24 10:33:53 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA11782 for ; Thu, 24 Jun 1999 10:33:52 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA30393; Thu, 24 Jun 1999 07:22:07 -0700 Resent-Date: Thu, 24 Jun 1999 07:22:07 -0700 From: Aki M Laukkanen Message-Id: <199906241422.RAA25321@vesuri.Helsinki.FI> Subject: Re: HERMES integration (take 2) To: ggi-develop@eskimo.com Date: Thu, 24 Jun 1999 17:22:04 +0300 (EET DST) In-Reply-To: <199906241352.QAA07135@vesuri.Helsinki.FI> from "Aki M Laukkanen" at Jun 24, 99 04:52:05 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"bkoIM2.0.dQ7.EyZSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13509 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Duh. > no hermes: > Name |Time (ms)|Times > -------------------------+---------+----- > ggiFlush | 71.141| 155 > ggiCrossBlit | 18.561| 155 > [the rest omitted] > > hermes: > Name |Time (ms)|Times > -------------------------+---------+----- > ggiFlush | 71.807| 222 > ggiCrossBlit | 22.225| 222 Of course these are reversed. The lower value is for HERMES. -- D. From ggi-develop-request@eskimo.com Thu Jun 24 11:27:23 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA13000 for ; Thu, 24 Jun 1999 11:27:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA20224; Thu, 24 Jun 1999 08:15:01 -0700 Resent-Date: Thu, 24 Jun 1999 08:15:01 -0700 Date: Thu, 24 Jun 1999 19:14:33 +0200 (CEST) From: Johan Karlberg X-Sender: wlfshmn@bovine To: ggi-develop@eskimo.com Subject: Re: Job offers: what I have been doing for the past year. In-Reply-To: <37712BE0.AD9645EC@ggi-project.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"2VxbP.0.Qx4.pjaSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13510 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 23 Jun 1999, Emmanuel Marty wrote: > Rodolphe Ortalo wrote: > > > > Revelation #3 > > > room, and sunny south france, 5 km away from the beach, > > > > Revelation #3.2 : Unfortuntaly, the guys of this city spend > > too much time on the beach and don't know to play rugby. > > Well, what is better to attract developers, the fact there > is a rugby team, or a beach? ;) > Actually, a room without windows and free beer would seem more logical to me... > > Furthermore, typically, that's the second fanciest town > > in that area... but of course, they won't agree. > > Mmmm.. *ponders* No, I won't :-) > > > May I ask a question (just to try to motivate yet-another- > > revelation): why do mention this facts just right now ? > > Is there some competition somewhere? ;-) > > Oh, no - well, there is always competition, not exactly in > what we're doing but there will always be - but that's not what > motivated this. We just spent the past year quietly developing > our thing and now that it is starting to work, we are collecting > funds and hiring people, so we have to talk about it some way > or other ;) > > Rodolphe, we have in mind to approach the LAAS at some point > in the future when we need extreme torture testing, by the way :) > > -- > Emmanuel > > > From ggi-develop-request@eskimo.com Thu Jun 24 12:55:06 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA15963 for ; Thu, 24 Jun 1999 12:55:05 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA12880; Thu, 24 Jun 1999 09:42:56 -0700 Resent-Date: Thu, 24 Jun 1999 09:42:56 -0700 From: Andrew Apted Message-ID: <19990625010742.32590@ajax.netspace.net.au> Date: Fri, 25 Jun 1999 01:07:42 +1000 To: ggi-develop@eskimo.com Subject: Re: GGI and mono displays Reply-To: ggi-develop@eskimo.com References: <19990622164607.A6249@koniu.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <19990622164607.A6249@koniu.local.net>; from Jacek Konieczny on Tue, Jun 22, 1999 at 04:46:07PM +0200 Resent-Message-ID: <"qphsk3.0.-83.C0cSt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13511 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jacek Konieczny writes: > I have two coputers at home - one with SVGA and one wit Hercules. > The Hercules is very nice even fo X (xevil is cool), but most apps > (games) would like more than 2 color. [snip] > Then I tried "trueemu" - it should solve my problems (but probably is > slow), but it crashed with "INTERNAL ERROR". Truecolor emulation is not supported on 1 bit modes. It's a pretty funny idea, trying to emulate 16 million colours with just 2, yeah ? > But flying_ggis work with "palemu" target although they shouldn't. > However they are not perfect - it seems dots are drawn only every 4/8 > pixels. Various bits of code which handle 1 bit modes (especially in palemu) probably haven't been tested for a long time, and may be broken. There is not much interest in it these days. One program that should always work is the one simply called `demo'. Have you tried that one ? > I think trueemu should be fixed, as 2-colors targets are those which > need dithering most. If there were 127 hours in the day (C'mon Andy, we need 'em ! :->), I would merge the palemu and trueemu into one big target that could emulate anything on anything (using a dirty-rectangles method for reasonable speed), ooh yeah it would support DirectBuffer too. Unfortunately I don't have the time to hack on that. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Thu Jun 24 15:20:49 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA20114 for ; Thu, 24 Jun 1999 15:20:48 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA16779; Thu, 24 Jun 1999 12:08:11 -0700 Resent-Date: Thu, 24 Jun 1999 12:08:11 -0700 Date: Thu, 24 Jun 1999 12:08:06 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: about KGI and KGIcon In-Reply-To: <3770F5D5.549E21C2@easter-eggs.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"5pBND1.0.t54.O8eSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13512 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 23 Jun 1999, Julien Tayon wrote: > Can someone make me clear on one point? > concerning the developement of a driver. It is said in the KGI 0.9 > snapshot that it is developped far enough for being able to write a > driver. However the writing a driver help file, namely refers to the GGI > source tree and the kgi directory there belongs to kgicon. > The makefile of the kgi-0.9 only takes care of its own tree. > I am quite puzzled and really wonders what are the sources needed to > developp a driver. I have made a lot of changes and cleanups to the KGI-0.9 headers (removed the ggi_ namespace, etc) which Steffen has not yet integrated back into the master KGI-0.9 tree. Therefore, KGIcon would be a bit better to do driver development with. However, even KGIcon 0.9 is not yet fully operational, here is the status: * The KGIcon 0.9 tree has been revamped and is now based on autoconf * Everything builds * kgicon.o loads but most of the management framework is missing * The driver modules for permedia build, but the wrapper-driver which will emulate the Dali environment to bind together the chipset, ramdac, clockchip, accel, and monitor drivers at runtime has not yet been written. So the drivers are unuseable right now. So it isn't ready yet. If you want to develop a driver for KGI 0.9, either sit on your hands for a while or get hooked up with Emmanuel Marty and Andy, and that custom OS they are developing appears to be the only stable and working KGI 0.9 development environment right now. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Thu Jun 24 17:10:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA22636 for ; Thu, 24 Jun 1999 17:10:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA00457; Thu, 24 Jun 1999 13:59:12 -0700 Resent-Date: Thu, 24 Jun 1999 13:59:12 -0700 Sender: marcus@e.kth.se Message-ID: <37729C13.5D214859@stacken.kth.se> Date: Thu, 24 Jun 1999 20:58:59 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: about KGI and KGIcon References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"48e8Z.0.o6.RmfSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13513 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > So it isn't ready yet. If you want to develop a driver for KGI 0.9, > either sit on your hands for a while or get hooked up with Emmanuel Marty and > Andy, and that custom OS they are developing appears to be the only stable > and working KGI 0.9 development environment right now. "that custom OS" still uses the Dali KGI. At least it did last time I managed to squeeze a few bits of information out of Andy. ;) //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Fri Jun 25 03:13:32 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id DAA02158 for ; Fri, 25 Jun 1999 03:13:31 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id XAA10551; Thu, 24 Jun 1999 23:56:55 -0700 Resent-Date: Thu, 24 Jun 1999 23:56:55 -0700 Date: Fri, 25 Jun 1999 08:56:29 +0200 From: Jacek Konieczny To: ggi-develop@eskimo.com Subject: Re: GGI and mono displays Message-ID: <19990625085629.C9289@merlin.ise.polsl.gliwice.pl> Mail-Followup-To: ggi-develop@eskimo.com References: <19990622164607.A6249@koniu.local.net> <19990625010742.32590@ajax.netspace.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 X-Mailer: Mutt 0.95i In-Reply-To: <19990625010742.32590@ajax.netspace.net.au> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mx1.eskimo.com id XAA10176 Resent-Message-ID: <"lcZba2.0.aV2.lWoSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13514 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On pi±, 25 cze 1999, Andrew Apted wrote: > Jacek Konieczny writes: > > > I have two coputers at home - one with SVGA and one wit Hercules. > > The Hercules is very nice even fo X (xevil is cool), but most apps > > (games) would like more than 2 color. > [snip] > > Then I tried "trueemu" - it should solve my problems (but probably is > > slow), but it crashed with "INTERNAL ERROR". > > Truecolor emulation is not supported on 1 bit modes. It's a pretty > funny idea, trying to emulate 16 million colours with just 2, yeah ? But truecolor can be used to emulate anything else. I whould see it this way: - calculate brightness of pixel (a*R+b*G+c*B) - strip it to reasonable no of bits (example: 4) - do the dithering But its probably not what trueemu target does. Maybe I'll try do some "monodither" target or something.... > > > But flying_ggis work with "palemu" target although they shouldn't. > > However they are not perfect - it seems dots are drawn only every 4/8 > > pixels. > > Various bits of code which handle 1 bit modes (especially in palemu) > probably haven't been tested for a long time, and may be broken. There > is not much interest in it these days. > > One program that should always work is the one simply called `demo'. > Have you tried that one ? I was trying programs which were installed from my RPMs. And "demo" is not a thing to package. But I'll try > > I think trueemu should be fixed, as 2-colors targets are those which > > need dithering most. > > If there were 127 hours in the day (C'mon Andy, we need 'em ! :->), Yes, I whouldn't mind 127 hours a day neither :-) > I would merge the palemu and trueemu into one big target that could > emulate anything on anything (using a dirty-rectangles method for > reasonable speed), ooh yeah it would support DirectBuffer too. > Unfortunately I don't have the time to hack on that. I don't think its really needed. Using trueemu and palemu is simple, and GGI is supposed to be simple (but also fast...) Greets, Jacek -- +---------+--------------------------------------------------------+ ! , ! Jacek Konieczny, Gliwice, Poland ! ! Jajcus ! email: jajcus@zeus.polsl.gliwice.pl, jacek@kde.org ! ! ! ICQ# 7149127 WWW: none (yet) ! +---------+--------------------------------------powered-by-Linux--+ From ggi-develop-request@eskimo.com Fri Jun 25 04:54:28 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA02783 for ; Fri, 25 Jun 1999 04:54:27 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA01702; Fri, 25 Jun 1999 01:41:38 -0700 Resent-Date: Fri, 25 Jun 1999 01:41:38 -0700 Date: Fri, 25 Jun 1999 10:42:05 +0200 From: Erik Thiele To: ggi-develop@eskimo.com Subject: X multiwindowed game on multiple computers Message-ID: <19990625104205.A13949@vulcain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Resent-Message-ID: <"lKIHM3.0.RQ.z2qSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13515 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com hi i play freeciv (www.freeciv.org) it uses athena widget set or gtk widget set it opens multiple windows i have not big enough screen i have multiple computers. first idea was use XGGI to make bigger screen. but XGGI cannot display on remote X target (it sais no directbuffer on Xlib target and on X target it works but displays black only screen it creates BIG network load and won'T accept C-c to kill the XGGI program. it must be killed with -9. if a client connects to the server the client get's stuck in a select(... call. ) there are no other remote GGI targets. so i cannot do this with GGI last idea would be AA and then xterm on other host but this sucks. now i tried some X tools. but i can't find out which ones would do the job. any ideas ? cu erik -- EMAIL: erikyyy@studbox.uni-stuttgart.de \\\\ thieleek@tick.informatik.uni-stuttgart.de o `QQ'_ IRC: erikyyy / __8 WWW: http://wwwcip.rus.uni-stuttgart.de/~inf24628/ ' ` http://tick.informatik.uni-stuttgart.de/~thieleek/ From ggi-develop-request@eskimo.com Fri Jun 25 05:30:51 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA03060 for ; Fri, 25 Jun 1999 05:30:50 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA05299; Fri, 25 Jun 1999 02:18:48 -0700 Resent-Date: Fri, 25 Jun 1999 02:18:48 -0700 From: Steffen Seeger Message-Id: <199906250917.LAA28985@demonti.physik.tu-chemnitz.de> Subject: Re: about KGI and KGIcon In-Reply-To: from "Jon M. Taylor" at "Jun 24, 99 12:08:06 pm" To: ggi-develop@eskimo.com Date: Fri, 25 Jun 1999 11:17:48 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"CL0Ht3.0.LI1.mbqSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13516 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > So it isn't ready yet. If you want to develop a driver for KGI 0.9, > either sit on your hands for a while or get hooked up with Emmanuel Marty and > Andy, and that custom OS they are developing appears to be the only stable > and working KGI 0.9 development environment right now. Just to clarify: This is a port of the KGI from ggi-0.0.9. Steffen ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- From ggi-develop-request@eskimo.com Fri Jun 25 05:41:48 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA03131 for ; Fri, 25 Jun 1999 05:41:47 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA06202; Fri, 25 Jun 1999 02:29:44 -0700 Resent-Date: Fri, 25 Jun 1999 02:29:44 -0700 From: becka@rz.uni-duesseldorf.de Message-Id: <199906250927.LAA25074@zeus.rz.uni-duesseldorf.de> Subject: Re: X multiwindowed game on multiple computers In-Reply-To: <19990625104205.A13949@vulcain> from Erik Thiele at "Jun 25, 99 10:42:05 am" To: ggi-develop@eskimo.com Date: Fri, 25 Jun 1999 11:27:23 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"FdrWZ.0.jW1.7mqSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13517 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi ! > it uses athena widget set or gtk widget set > it opens multiple windows > i have not big enough screen What about using a virtual window manager ? > i have multiple computers. > use XGGI to make bigger screen. > but XGGI cannot display on remote X target > (it sais no directbuffer on Xlib target > and on X target it works but displays black only screen > it creates BIG network load and won'T accept C-c to kill > the XGGI program. it must be killed with -9. if a client > connects to the server the client get's stuck in a > select(... call. > ) Yes. The network load is the problem here. XGGI runs in SYNC mode (it's very difficult to find reasonable places in the X server where a Flush() would be appropriate). You can decrease the network load (and thus get the stuff running) as documents in doc/env.txt: GGI_MANSYNC_FPS - Specify the framerate for targets using mansync to do SYNC mode. The default is 20fps. If you are experiencing problems with the X target over realtively slow remote connections it might be due to connection overload. You might want to try with a lower GGI_MANSYNC_FPS setting. > there are no other remote GGI targets. What about the tele target ? > now i tried some X tools. but i can't find out which ones would > do the job. I'd use a virtual screen. Either using the vistual resolution of the X server, or a virtual window manager like fvwm, olvwm, ... CU, ANdy -- Andreas Beck | Email : From ggi-develop-request@eskimo.com Fri Jun 25 06:19:03 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA03358 for ; Fri, 25 Jun 1999 06:19:02 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA15588; Fri, 25 Jun 1999 03:06:26 -0700 Resent-Date: Fri, 25 Jun 1999 03:06:26 -0700 Message-ID: <19990625100647.15224.rocketmail@web106.yahoomail.com> Date: Fri, 25 Jun 1999 03:06:47 -0700 (PDT) From: Kien Pham Subject: Re: Job offers: what I have been doing for the past year. To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"lu0bi3.0.Nn3.WIrSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13518 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --- Moses DeJong wrote: > On Wed, 23 Jun 1999, Kien Pham wrote: > > > > > > > --- Emmanuel Marty wrote: > > > > > * Porting a JVM > > Actually, the open source version has a new home. It is > now hosted > at http://www.kaffe.org. The transvirtual site is for the > verison > that they sell. There's a downloadable desktop version on Transvirtual too. The desktop version is Open Source. I forgot about the GNU endorsed one. "Japhar" http://www.japhar.org The only problem is the the GC doesn't work. But you can steal it from Kaffe and plug it in. :) ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From ggi-develop-request@eskimo.com Fri Jun 25 06:22:26 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA03385 for ; Fri, 25 Jun 1999 06:22:25 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA17166; Fri, 25 Jun 1999 03:09:30 -0700 Resent-Date: Fri, 25 Jun 1999 03:09:30 -0700 Date: Fri, 25 Jun 1999 12:10:08 +0200 From: Erik Thiele To: ggi-develop@eskimo.com Subject: Re: X multiwindowed game on multiple computers Message-ID: <19990625121008.A19754@vulcain> References: <19990625104205.A13949@vulcain> <199906250927.LAA25074@zeus.rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199906250927.LAA25074@zeus.rz.uni-duesseldorf.de>; from becka@rz.uni-duesseldorf.de on Fri, Jun 25, 1999 at 11:27:23AM +0200 Resent-Message-ID: <"uB3rd2.0.-B4.PLrSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13519 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, Jun 25, 1999 at 11:27:23AM +0200, becka@rz.uni-duesseldorf.de wrote: > Hi ! > > > it uses athena widget set or gtk widget set > > it opens multiple windows > > i have not big enough screen > > What about using a virtual window manager ? i use one. but i want the same application run on multiple X displays (!!) and the application doesn't support this. > > > i have multiple computers. > > > use XGGI to make bigger screen. > > but XGGI cannot display on remote X target > > (it sais no directbuffer on Xlib target > > and on X target it works but displays black only screen > > it creates BIG network load and won'T accept C-c to kill > > the XGGI program. it must be killed with -9. if a client > > connects to the server the client get's stuck in a > > select(... call. > > ) > > Yes. The network load is the problem here. XGGI runs in SYNC mode (it's very difficult to find reasonable places in the X server where a Flush() would be > appropriate). You can decrease the network load (and thus get the stuff > running) as documents in doc/env.txt: > > GGI_MANSYNC_FPS - Specify the framerate for targets using mansync to do > SYNC mode. The default is 20fps. > If you are experiencing problems with the X target over > realtively slow remote connections it might be due to > connection overload. You might want to try with a lower > GGI_MANSYNC_FPS setting. > > > there are no other remote GGI targets. > > What about the tele target ? i have no such target > > > now i tried some X tools. but i can't find out which ones would > > do the job. > > I'd use a virtual screen. Either using the vistual resolution of the X server, or a virtual window manager like fvwm, olvwm, ... i now managed (with GGI_MANSYNC_FPS) to get XGGI running ./XGGI :3 -targets "(x:torgan:0):(x:localhost:1)" does the trick. but i found out that this is ONE display with TWO screens. if i now fvwm -display :3 then i can move mouse to the right and get to my other computer but i can start apps on the left and on the right. but not in the middle. i cannot move part of apps from left to right this is not what i wanted. such things are also possible with tools like x2x and other X stuff. what i want is ./XGGI :3 -targets "multi:(x:torgan:0):(x:localhost:1)" but then he sais multi has no directbuffer. example: i start gimp now i want to move the tooltips to the display of my other computer :-) but i want to keep the menu window on my old display. this is what i want. it need not be split (half left half right) but at least i must be able to move the whole tooltips window to the other display and this is not possible without explicit support for that in the application (gimp) and it is not possible with X tricks. (x2x,xnest,fvwm etc.) and it is not possible with ggi. because the multi target has no directbuffer support. cu erik -- EMAIL: erikyyy@studbox.uni-stuttgart.de \\\\ thieleek@tick.informatik.uni-stuttgart.de o `QQ'_ IRC: erikyyy / __8 WWW: http://wwwcip.rus.uni-stuttgart.de/~inf24628/ ' ` http://tick.informatik.uni-stuttgart.de/~thieleek/ From ggi-develop-request@eskimo.com Fri Jun 25 07:46:11 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA03824 for ; Fri, 25 Jun 1999 07:46:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA09493; Fri, 25 Jun 1999 04:31:51 -0700 Resent-Date: Fri, 25 Jun 1999 04:31:51 -0700 From: Andrew Apted Message-ID: <19990625213738.00332@ajax.netspace.net.au> Date: Fri, 25 Jun 1999 21:37:38 +1000 To: ggi-develop@eskimo.com Subject: Re: GGI and mono displays Reply-To: ggi-develop@eskimo.com References: <19990622164607.A6249@koniu.local.net> <19990625010742.32590@ajax.netspace.net.au> <19990625085629.C9289@merlin.ise.polsl.gliwice.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <19990625085629.C9289@merlin.ise.polsl.gliwice.pl>; from Jacek Konieczny on Fri, Jun 25, 1999 at 08:56:29AM +0200 Resent-Message-ID: <"e4CZf.0.9K2.bYsSt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13520 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jacek Konieczny writes: > But truecolor can be used to emulate anything else. > I whould see it this way: > - calculate brightness of pixel (a*R+b*G+c*B) > - strip it to reasonable no of bits (example: 4) > - do the dithering One way of doing it, is by running the trueemu target on the palemu target. For example: export GGI_DISPLAY=trueemu:palemu Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Fri Jun 25 07:48:39 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA03844 for ; Fri, 25 Jun 1999 07:48:39 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA10012; Fri, 25 Jun 1999 04:36:47 -0700 Resent-Date: Fri, 25 Jun 1999 04:36:47 -0700 From: Andrew Apted Message-ID: <19990625214236.31172@ajax.netspace.net.au> Date: Fri, 25 Jun 1999 21:42:36 +1000 To: ggi-develop@eskimo.com Subject: Re: X multiwindowed game on multiple computers Reply-To: ggi-develop@eskimo.com References: <19990625104205.A13949@vulcain> <199906250927.LAA25074@zeus.rz.uni-duesseldorf.de> <19990625121008.A19754@vulcain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <19990625121008.A19754@vulcain>; from Erik Thiele on Fri, Jun 25, 1999 at 12:10:08PM +0200 Resent-Message-ID: <"2A-JK2.0.GS2.EdsSt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13521 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Erik Thiele writes: > > > there are no other remote GGI targets. > > > > What about the tele target ? > i have no such target And the tele target doesn't support DirectBuffer anyway. > .../XGGI :3 -targets "multi:(x:torgan:0):(x:localhost:1)" > but then he sais multi has no directbuffer. The tile target supports directbuffer. Read the docs about it in targets.txt & try that. Hope that helps. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Fri Jun 25 08:06:46 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA04009 for ; Fri, 25 Jun 1999 08:06:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA12072; Fri, 25 Jun 1999 04:55:06 -0700 Resent-Date: Fri, 25 Jun 1999 04:55:06 -0700 Date: Fri, 25 Jun 1999 13:55:49 +0200 From: Erik Thiele To: ggi-develop@eskimo.com Subject: Re: X multiwindowed game on multiple computers Message-ID: <19990625135549.A20587@vulcain> References: <19990625104205.A13949@vulcain> <199906250927.LAA25074@zeus.rz.uni-duesseldorf.de> <19990625121008.A19754@vulcain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990625121008.A19754@vulcain>; from Erik Thiele on Fri, Jun 25, 1999 at 12:10:08PM +0200 Resent-Message-ID: <"3jq6y2.0.Ny2.OusSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13522 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com strike. i am an idiot :-) i forgot the "tile" target. now i did export GGI_MANSYNC_FPS=5 export GGI_DISPLAY="tile:0,0,800,600,(x):800,0,400,100,(x:torgan:0)" ./XGGI :3 but 5 fps is WAY too slow. the only thing missing is i want speed FPS on (x) and slow FPS on (x:torgan:0) is that possible ? cu erik PS: it is incredibly cool to have two mouses that move the same cursor ;) and two keyboards typing to the same app ;) also funny is caps-lock handling ;) -- EMAIL: erikyyy@studbox.uni-stuttgart.de \\\\ thieleek@tick.informatik.uni-stuttgart.de o `QQ'_ IRC: erikyyy / __8 WWW: http://wwwcip.rus.uni-stuttgart.de/~inf24628/ ' ` http://tick.informatik.uni-stuttgart.de/~thieleek/ From ggi-develop-request@eskimo.com Fri Jun 25 09:43:11 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA05505 for ; Fri, 25 Jun 1999 09:43:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA06124; Fri, 25 Jun 1999 06:30:24 -0700 Resent-Date: Fri, 25 Jun 1999 06:30:24 -0700 Sender: jul@reliam.teaser.fr Message-ID: <37738507.3FEF5F2B@easter-eggs.fr> Date: Fri, 25 Jun 1999 15:32:55 +0200 From: Julien Tayon Organization: Easter-eggs X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: fr, en MIME-Version: 1.0 To: GGI developp , ggi kgi Subject: still KGI 0.9 ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"au4KX1.0.TV1.kHuSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13523 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Tell me if I am wrong: I need a driver pretty fast working with libggi -2-, so I shoud rather a framebuffer device, and write a driver for it. By the way I can boot with kgi :) (kernel 2.2.[2,4]) see the splash yellowish cursor if network freeze when loading eth0 else work pretty fine 'reset ' necessary after midnight commander Julien Tayon @++; -- Easter-eggs Linux System Integrator 17 bis rue du Dr Zamenhof - 92500 Rueil Malmaison - France Phone: +33 (0) 1 41 29 10 01 - Fax: +33 (0) 1 41 29 11 71 mailto:jtayon@easter-eggs.com - http://www.easter-eggs.com From ggi-develop-request@eskimo.com Fri Jun 25 10:17:12 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA06062 for ; Fri, 25 Jun 1999 10:17:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA23575; Fri, 25 Jun 1999 07:04:51 -0700 Resent-Date: Fri, 25 Jun 1999 07:04:51 -0700 From: becka@rz.uni-duesseldorf.de Message-Id: <199906251403.QAA14167@zeus.rz.uni-duesseldorf.de> Subject: Re: X multiwindowed game on multiple computers In-Reply-To: <19990625135549.A20587@vulcain> from Erik Thiele at "Jun 25, 99 01:55:49 pm" To: ggi-develop@eskimo.com Date: Fri, 25 Jun 1999 16:03:44 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"lrR301.0.5m5.1ouSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13524 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi ! > the only thing missing is > i want speed FPS on (x) and slow FPS on (x:torgan:0) > is that possible ? You would have to hack something like that into the function GGI_tile_flush_db in mode.c of the tile target. The tile target disables the SYNC behaviour of all childs and syncs them all from a central place. One would have to add options like "-skipframe 1,5" or something like that to the target, that would make e.g. the first target show every frame, and the second only every fifth. CU, ANdy -- Andreas Beck | Email : From ggi-develop-request@eskimo.com Fri Jun 25 10:48:08 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA06783 for ; Fri, 25 Jun 1999 10:48:08 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA05093; Fri, 25 Jun 1999 07:35:29 -0700 Resent-Date: Fri, 25 Jun 1999 07:35:29 -0700 Date: Fri, 25 Jun 1999 16:36:14 +0200 From: Erik Thiele To: ggi-develop@eskimo.com Subject: Re: X multiwindowed game on multiple computers Message-ID: <19990625163614.B20883@vulcain> References: <19990625135549.A20587@vulcain> <199906251403.QAA14167@zeus.rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199906251403.QAA14167@zeus.rz.uni-duesseldorf.de>; from becka@rz.uni-duesseldorf.de on Fri, Jun 25, 1999 at 04:03:44PM +0200 Resent-Message-ID: <"HW36I2.0.IF1.kEvSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13525 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, Jun 25, 1999 at 04:03:44PM +0200, becka@rz.uni-duesseldorf.de wrote: > Hi ! > > > the only thing missing is > > i want speed FPS on (x) and slow FPS on (x:torgan:0) > > is that possible ? > > You would have to hack something like that into the function > > GGI_tile_flush_db in mode.c of the tile target. The tile target disables > the SYNC behaviour of all childs and syncs them all from a central place. > > One would have to add options like "-skipframe 1,5" or something like that > to the target, that would make e.g. the first target show every frame, and the > second only every fifth. > is something planned to make networked tilescreen possible in a reasonable speed ? (needn't be on top of X of course. but until now i think X target is the only remote target. maybe the "tele" target, whatever that is ;) at least it is not in the beta) cu erik -- EMAIL: erikyyy@studbox.uni-stuttgart.de \\\\ thieleek@tick.informatik.uni-stuttgart.de o `QQ'_ IRC: erikyyy / __8 WWW: http://wwwcip.rus.uni-stuttgart.de/~inf24628/ ' ` http://tick.informatik.uni-stuttgart.de/~thieleek/ From ggi-develop-request@eskimo.com Fri Jun 25 10:55:16 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id KAA06873 for ; Fri, 25 Jun 1999 10:55:15 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA07655; Fri, 25 Jun 1999 07:43:27 -0700 Resent-Date: Fri, 25 Jun 1999 07:43:27 -0700 From: Steffen Seeger Message-Id: <199906251443.QAA29961@demonti.physik.tu-chemnitz.de> Subject: Re: still KGI 0.9 ... In-Reply-To: <37738507.3FEF5F2B@easter-eggs.fr> from Julien Tayon at "Jun 25, 99 03:32:55 pm" To: ggi-develop@eskimo.com Date: Fri, 25 Jun 1999 16:43:10 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"9eia-3.0.Pt1.EMvSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13526 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Tell me if I am wrong: > I need a driver pretty fast working with libggi -2-, so I shoud rather > a framebuffer device, and write a driver for it. Write a driver for the old KGI and port it later. > By the way I can boot with kgi :) (kernel 2.2.[2,4]) > see the splash > yellowish cursor > if network > freeze when loading eth0 Does it work with a plain 2.2.[2,4]? What's your setup exactly? Steffen ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- From ggi-develop-request@eskimo.com Fri Jun 25 12:01:46 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA08314 for ; Fri, 25 Jun 1999 12:01:45 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA00221; Fri, 25 Jun 1999 08:46:10 -0700 Resent-Date: Fri, 25 Jun 1999 08:46:10 -0700 Sender: jul@reliam.teaser.fr Message-ID: <3773A4C6.72AAC4FF@easter-eggs.fr> Date: Fri, 25 Jun 1999 17:48:22 +0200 From: Julien Tayon Organization: Easter-eggs X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: fr, en MIME-Version: 1.0 To: Steffen Seeger , GGI developp Subject: Re: still KGI 0.9 ... References: <199906251443.QAA29961@demonti.physik.tu-chemnitz.de> Content-Type: multipart/mixed; boundary="------------4D5D85A0662897AFEE9DB1E2" Resent-Message-ID: <"FPdxI.0.q2._GwSt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13527 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com This is a multi-part message in MIME format. --------------4D5D85A0662897AFEE9DB1E2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Does it work with a plain 2.2.[2,4]? > What's your setup exactly? I used both 2.2.2 and 2.2.4 kernel, here is one of the config file that worked and a shortened version of the kernel messages -- Easter-eggs Linux System Integrator 17 bis rue du Dr Zamenhof - 92500 Rueil Malmaison - France Phone: +33 (0) 1 41 29 10 01 - Fax: +33 (0) 1 41 29 11 71 mailto:jtayon@easter-eggs.com - http://www.easter-eggs.com --------------4D5D85A0662897AFEE9DB1E2 Content-Type: text/plain; charset=us-ascii; name="hard" Content-Disposition: inline; filename="hard" Content-Transfer-Encoding: 7bit Detected 451030220 Hz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 450.56 BogoMIPS Memory: 127648k/131008k available (996k kernel code, 412k reserved, 1568k data, 60k init) VFS: Diskquotas version dquot_6.4.0 initialized Pentium-III serial number disabled. CPU: Intel 00/07 stepping 02 Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.26 (19981001) Richard Gooch (rgooch@atnf.csiro.au) PCI: PCI BIOS revision 2.10 entry at 0xf0720 PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP Initializing RT netlink socket Starting kswapd v 1.5 Detected PS/2 Mouse Port. Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A pty: 256 Unix98 ptys configured apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) Real Time Clock Driver v1.09 RAM disk driver initialized: 16 RAM disks of 4096K size PIIX4: IDE controller on PCI bus 00 dev 21 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:pio, hdd:pio hda: 36X CD-ROM, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: ATAPI 24X CD-ROM drive, 128kB Cache Floppy drive(s): fd0 is 1.44M md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 raid5: measuring checksumming speed using fastest function: pII_mmx (1098.423 MB/sec) scsi : 0 hosts. scsi : detected total. md.c: sizeof(mdp_super_t) = 4096 Partition check: RAMDISK: Compressed image found at block 0 autodetecting RAID arrays VFS: Mounted root (ext2 filesystem). (scsi0) found at PCI 6/0 scsi : 1 host. (scsi0:0:0:0) Synchronous at 80.0 Mbyte/sec, offset 15. Vendor: IBM Model: DDRS-34560D Rev: DC1B Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: hdwr sector= 512 bytes. Sectors= 8925000 [4357 MB] [4.4 GB] sda: sda1 sda2 sda3 sda4 < sda5 sda6 > VFS: Mounted root (ext2 filesystem) readonly. Adding Swap: 128516k swap-space (priority -1) eth0: Intel EtherExpress Pro 10/100 at 0xb800, 00:E0:18:98:9E:47, IRQ 12. Board assembly 668081-002, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x24c9f043). Receiver lock-up workaround activated. Installing knfsd (copyright (C) 1996 okir@monad.swb.de). nfsd_init: initialized fhcache, entries=256 --------------4D5D85A0662897AFEE9DB1E2 Content-Type: text/plain; charset=us-ascii; name="config.kgi.1" Content-Disposition: inline; filename="config.kgi.1" Content-Transfer-Encoding: 7bit # # Automatically generated by make menuconfig: don't edit # # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set CONFIG_M686=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_SMP=y # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set # CONFIG_KMOD is not set # # General setup # CONFIG_NET=y CONFIG_PCI=y CONFIG_PCI_GOBIOS=y # CONFIG_PCI_GODIRECT is not set # CONFIG_PCI_GOANY is not set CONFIG_PCI_BIOS=y CONFIG_PCI_QUIRKS=y # CONFIG_PCI_OPTIMIZE is not set CONFIG_PCI_OLD_PROC=y # CONFIG_MCA is not set # CONFIG_VISWS is not set CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_BINFMT_JAVA is not set # CONFIG_PARPORT is not set # CONFIG_APM is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set CONFIG_BLK_DEV_CMD640=y # CONFIG_BLK_DEV_CMD640_ENHANCED is not set CONFIG_BLK_DEV_RZ1000=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_VIA82C586 is not set # CONFIG_BLK_DEV_CMD646 is not set # CONFIG_IDE_CHIPSETS is not set # CONFIG_BLK_DEV_LOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_XD is not set CONFIG_PARIDE_PARPORT=y # CONFIG_PARIDE is not set # CONFIG_BLK_DEV_HD is not set # # Networking options # CONFIG_PACKET=y # CONFIG_NETLINK is not set # CONFIG_FIREWALL is not set # CONFIG_NET_ALIAS is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_IP_ROUTER is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_ALIAS is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_RARP is not set CONFIG_IP_NOSR=y CONFIG_SKB_LARGE=y # CONFIG_IPV6 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_BRIDGE is not set # CONFIG_LLC is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_FASTROUTE is not set # CONFIG_NET_HW_FLOWCONTROL is not set # CONFIG_CPU_IS_SLOW is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # SCSI support # CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_BLK_DEV_SR is not set # CONFIG_CHR_DEV_SG is not set CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y # CONFIG_SCSI_LOGGING is not set # # SCSI low-level drivers # # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 is not set # CONFIG_SCSI_AHA1740 is not set CONFIG_SCSI_AIC7XXX=y # CONFIG_OVERRIDE_CMDS is not set CONFIG_AIC7XXX_PROC_STATS=y CONFIG_AIC7XXX_RESET_DELAY=5 # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_IN2000 is not set # CONFIG_SCSI_AM53C974 is not set # CONFIG_SCSI_MEGARAID is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DTC3280 is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_EATA_DMA is not set # CONFIG_SCSI_EATA_PIO is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_GENERIC_NCR5380 is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_NCR53C406A is not set # CONFIG_SCSI_NCR53C7xx is not set CONFIG_SCSI_NCR53C8XX=y CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=4 CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32 CONFIG_SCSI_NCR53C8XX_SYNC=20 # CONFIG_SCSI_NCR53C8XX_PROFILE is not set # CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set # CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set # CONFIG_SCSI_PAS16 is not set # CONFIG_SCSI_PCI2000 is not set # CONFIG_SCSI_PCI2220I is not set # CONFIG_SCSI_PSI240I is not set # CONFIG_SCSI_QLOGIC_FAS is not set # CONFIG_SCSI_QLOGIC_ISP is not set # CONFIG_SCSI_SEAGATE is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_T128 is not set # CONFIG_SCSI_U14_34F is not set # CONFIG_SCSI_ULTRASTOR is not set # CONFIG_SCSI_DEBUG is not set # # Network device support # CONFIG_NETDEVICES=y # CONFIG_ARCNET is not set CONFIG_DUMMY=m # CONFIG_EQUALIZER is not set CONFIG_NET_ETHERNET=y # CONFIG_NET_VENDOR_3COM is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # CONFIG_RTL8139 is not set # CONFIG_YELLOWFIN is not set # CONFIG_ACENIC is not set # CONFIG_NET_ISA is not set CONFIG_NET_EISA=y # CONFIG_PCNET32 is not set # CONFIG_AC3200 is not set # CONFIG_APRICOT is not set # CONFIG_CS89x0 is not set # CONFIG_DE4X5 is not set # CONFIG_DEC_ELCP is not set # CONFIG_DGRS is not set CONFIG_EEXPRESS_PRO100=y # CONFIG_LNE390 is not set # CONFIG_NE3210 is not set # CONFIG_NE2K_PCI is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_ES3210 is not set # CONFIG_EPIC100 is not set # CONFIG_ZNET is not set # CONFIG_NET_POCKET is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_DLCI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_NET_RADIO is not set # CONFIG_TR is not set # CONFIG_SHAPER is not set # CONFIG_HOSTESS_SV11 is not set # CONFIG_COSA is not set # CONFIG_RCPCI is not set # # Amateur Radio support # # CONFIG_HAMRADIO is not set # # IrDA subsystem support # # CONFIG_IRDA is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_KGI=y CONFIG_KGI_SPLASH=y CONFIG_KGI_TERM_DUMB=y CONFIG_KGI_TERM_XTERM=y CONFIG_KGI_VT_LINUX=y CONFIG_KGI_DEV_GRAPHIC=y CONFIG_KGI_DEV_EVENT=y CONFIG_KGI_SCROLL_COLOR=y CONFIG_KGI_SCROLL_MONO=y CONFIG_KGI_SCROLL_8BPP=y CONFIG_KGI_SCROLL_16BPP=y CONFIG_KGI_SCROLL_24BPP=y CONFIG_KGI_SCROLL_32BPP=y CONFIG_SERIAL=y # CONFIG_SERIAL_CONSOLE is not set # CONFIG_SERIAL_EXTENDED is not set # CONFIG_SERIAL_NONSTANDARD is not set CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256 # CONFIG_QIC02_TAPE is not set # CONFIG_WATCHDOG is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # # Video For Linux # # CONFIG_VIDEO_DEV is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # # Filesystems # # CONFIG_QUOTA is not set CONFIG_AUTOFS_FS=y # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_FAT_FS is not set # CONFIG_MSDOS_FS is not set # CONFIG_UMSDOS_FS is not set # CONFIG_VFAT_FS is not set CONFIG_ISO9660_FS=y # CONFIG_JOLIET is not set # CONFIG_MINIX_FS is not set # CONFIG_NTFS_FS is not set # CONFIG_HPFS_FS is not set CONFIG_PROC_FS=y CONFIG_DEVPTS_FS=y # CONFIG_QNX4FS_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_EXT2_FS=y # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # # CONFIG_CODA_FS is not set CONFIG_NFS_FS=y # CONFIG_NFSD is not set CONFIG_SUNRPC=y CONFIG_LOCKD=y # CONFIG_SMB_FS is not set # CONFIG_NCP_FS is not set # # Partition Types # # CONFIG_BSD_DISKLABEL is not set # CONFIG_MAC_PARTITION is not set # CONFIG_SMD_DISKLABEL is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_NLS is not set # # Console drivers # CONFIG_VGA_CONSOLE=y # CONFIG_VIDEO_SELECT is not set # CONFIG_MDA_CONSOLE is not set # CONFIG_FB is not set # # Sound # # CONFIG_SOUND is not set # # Kernel hacking # CONFIG_MAGIC_SYSRQ=y --------------4D5D85A0662897AFEE9DB1E2-- From ggi-develop-request@eskimo.com Fri Jun 25 16:25:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA15046 for ; Fri, 25 Jun 1999 16:25:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA00462; Fri, 25 Jun 1999 13:13:52 -0700 Resent-Date: Fri, 25 Jun 1999 13:13:52 -0700 Date: Fri, 25 Jun 1999 22:10:52 +0200 (MEST) To: GGI-Mailing-Liste Subject: New lib in CVS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"Sv6W01.0.U4.sB-St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13528 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi all! In the new snapshot I've downloaded, I found a new lib called libedemo. What does it? What's the aim of it? Christoph Egger E-Mail: Christoph_Egger@t-online.de From ggi-develop-request@eskimo.com Fri Jun 25 16:25:32 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA15050 for ; Fri, 25 Jun 1999 16:25:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA00561; Fri, 25 Jun 1999 13:14:01 -0700 Resent-Date: Fri, 25 Jun 1999 13:14:01 -0700 Date: Fri, 25 Jun 1999 22:09:04 +0200 (MEST) To: GGI-Mailing-Liste cc: Andreas Beck Subject: libgii - patch to fix compiler error Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463811839-1166817471-930341344=:16891" X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"RfqLc1.0.W8.6C-St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13529 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1463811839-1166817471-930341344=:16891 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi all! I've just downloaded the ggi develop 990625 snapshot. When I tried to compile libgii, I got this error: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -Wp,-MD,.deps/packetparse.pp -c -fPIC -DPIC packetparse.c -o packetparse.lo packetparse.c:133: warning: `/*' within comment packetparse.c: In function `parse_ms': packetparse.c:134: parse error before `else' packetparse.c:119: warning: `buttons' might be used uninitialized in this function make[3]: *** [packetparse.lo] Error 1 make[3]: Leaving directory `/home/programmer/ggi/degas/lib/libgii/input/mouse' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/programmer/ggi/degas/lib/libgii/input' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/programmer/ggi/degas/lib/libgii' make: *** [all-recursive-am] Error 2 In the attachment is a patch which fixes that. Christoph Egger E-Mail: Christoph_Egger@t-online.de ---1463811839-1166817471-930341344=:16891 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="packparse.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="packparse.diff" LS0tIGlucHV0L21vdXNlL3BhY2tldHBhcnNlLmMub3JpZwlGcmkgSnVuIDI1 IDIxOjU4OjAyIDE5OTkNCisrKyBpbnB1dC9tb3VzZS9wYWNrZXRwYXJzZS5j CUZyaSBKdW4gMjUgMjE6NTg6NTAgMTk5OQ0KQEAgLTEyOCw3ICsxMjgsNyBA QA0KIAlkeCA9IChzaW50OCkgKCgoYnVmWzBdICYgMHgwMykgPDwgNikgfCAo YnVmWzFdICYgMHgzZikpOw0KIAlkeSA9IChzaW50OCkgKCgoYnVmWzBdICYg MHgwYykgPDwgNCkgfCAoYnVmWzJdICYgMHgzZikpOw0KIA0KLQkvKiB0aGly ZCBidXR0b24gYWRkZWQgYnkgQ2hyaXN0b3BoIEVnZ2VyIChDaHJpc3RvcGhf RWdnZXJAdC1vbmxpbmUuZGUpDQorCS8qIHRoaXJkIGJ1dHRvbiBhZGRlZCBi eSBDaHJpc3RvcGggRWdnZXIgKENocmlzdG9waF9FZ2dlckB0LW9ubGluZS5k ZSkgKi8NCiAJaWYgKGJ1ZlswXSA9PSAweDQwICYmICEobXByaXYtPmJ1dHRv bl9zdGF0ZXxidWZbMV18YnVmWzJdKSkNCiAJCWJ1dHRvbnMgPSA0OyAvKiB0 aGlyZCBidXR0b24gb24gTVMgY29tcGF0aWJsZSBtb3VzZSAqLw0KIAllbHNl DQo= ---1463811839-1166817471-930341344=:16891-- From ggi-develop-request@eskimo.com Fri Jun 25 16:27:58 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA15308 for ; Fri, 25 Jun 1999 16:27:57 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA01821; Fri, 25 Jun 1999 13:16:54 -0700 Resent-Date: Fri, 25 Jun 1999 13:16:54 -0700 Date: Fri, 25 Jun 1999 22:16:04 +0200 (MEST) To: GGI-Mailing-Liste cc: Andreas Beck Subject: Re: libgii - patch to fix compiler error In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"ub8XC2.0.GS.qE-St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13530 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi all! I've just downloaded the ggi develop 990625 snapshot. When I tried to compile libgii, I got this error: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include -g -O2 -D_REENTRANT -D_THREAD_SAFE -g -Wall -Wp,-MD,.deps/packetparse.pp -c -fPIC -DPIC packetparse.c -o packetparse.lo packetparse.c:133: warning: `/*' within comment packetparse.c: In function `parse_ms': packetparse.c:134: parse error before `else' packetparse.c:119: warning: `buttons' might be used uninitialized in this function make[3]: *** [packetparse.lo] Error 1 make[3]: Leaving directory `/home/programmer/ggi/degas/lib/libgii/input/mouse' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/programmer/ggi/degas/lib/libgii/input' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/programmer/ggi/degas/lib/libgii' make: *** [all-recursive-am] Error 2 In the attachment is a patch which fixes that. Christoph Egger E-Mail: Christoph_Egger@t-online.de From ggi-develop-request@eskimo.com Fri Jun 25 17:02:54 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA16307 for ; Fri, 25 Jun 1999 17:02:53 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA15068; Fri, 25 Jun 1999 13:51:26 -0700 Resent-Date: Fri, 25 Jun 1999 13:51:26 -0700 Date: Fri, 25 Jun 1999 22:50:44 +0200 (MEST) To: GGI-Mailing-Liste cc: Andreas Beck Subject: libgii - improved mouse patch Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463811839-1480170047-930343844=:5386" X-Sender: 320056911379-0001@t-online.de From: Christoph_Egger@t-online.de (Christoph Egger) Resent-Message-ID: <"3NJOP2.0.Eh3.Cl-St"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13531 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1463811839-1480170047-930343844=:5386 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi all! I've improved the patch I sent before. It fixes a lack in the handling when the middle mouse button is pressed. The patch is attached. Christoph Egger E-Mail: Christoph_Egger@t-online.de ---1463811839-1480170047-930343844=:5386 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="packparse.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="packparse.diff" LS0tIGlucHV0L21vdXNlL3BhY2tldHBhcnNlLmMub3JpZwlGcmkgSnVuIDI1 IDIxOjU4OjAyIDE5OTkNCisrKyBpbnB1dC9tb3VzZS9wYWNrZXRwYXJzZS5j CUZyaSBKdW4gMjUgMjI6NDU6MTQgMTk5OQ0KQEAgLTEyOCwxMyArMTI4LDI0 IEBADQogCWR4ID0gKHNpbnQ4KSAoKChidWZbMF0gJiAweDAzKSA8PCA2KSB8 IChidWZbMV0gJiAweDNmKSk7DQogCWR5ID0gKHNpbnQ4KSAoKChidWZbMF0g JiAweDBjKSA8PCA0KSB8IChidWZbMl0gJiAweDNmKSk7DQogDQotCS8qIHRo aXJkIGJ1dHRvbiBhZGRlZCBieSBDaHJpc3RvcGggRWdnZXIgKENocmlzdG9w aF9FZ2dlckB0LW9ubGluZS5kZSkNCisJLyogdGhpcmQgYnV0dG9uIGFkZGVk IGJ5IENocmlzdG9waCBFZ2dlciAoQ2hyaXN0b3BoX0VnZ2VyQHQtb25saW5l LmRlKSAqLw0KIAlpZiAoYnVmWzBdID09IDB4NDAgJiYgIShtcHJpdi0+YnV0 dG9uX3N0YXRlfGJ1ZlsxXXxidWZbMl0pKQ0KIAkJYnV0dG9ucyA9IDQ7IC8q IHRoaXJkIGJ1dHRvbiBvbiBNUyBjb21wYXRpYmxlIG1vdXNlICovDQogCWVs c2UNCiAJCWJ1dHRvbnMgPSAoKGJ1ZlswXSAmIDB4MTApID4+IDMpDQogCQkJ fCAoKGJ1ZlswXSAmIDB4MjApID4+IDUpOw0KIAkNCisJLyogU2hvdWxkIGFs bG93IG1vdGlvbiBfYW5kXyBidXR0b24gY2hhbmdlICovDQorCWlmICgoZHgg PT0gMCkgJiYgKGR5ID09IDApDQorCSYmIChidXR0b25zID09IChtcHJpdi0+ YnV0dG9uX3N0YXRlICYgfjQpKSkNCisJew0KKwkJLyogbm8gbW92ZSBvciBj aGFuZ2U6IHRvZ2dsZSBtaWRkbGUgKi8NCisJCWJ1dHRvbnMgPSBtcHJpdi0+ YnV0dG9uX3N0YXRlIF4gNDsNCisJfSBlbHNlIHsNCisJCS8qIGNoYW5nZTog cHJlc2VydmUgbWlkZGxlICovDQorCQlidXR0b25zIHw9IG1wcml2LT5idXR0 b25fc3RhdGUgJiA0Ow0KKwl9IC8vIGlmDQorDQogCW1vdXNlX3NlbmRfbW92 ZW1lbnQoaW5wLCBkeCwgZHksIDAsIDApOw0KIAlpZiAoYnV0dG9ucyAhPSBt cHJpdi0+YnV0dG9uX3N0YXRlKSB7DQogCQltb3VzZV9zZW5kX2J1dHRvbnMo aW5wLCBidXR0b25zLCBtcHJpdi0+YnV0dG9uX3N0YXRlKTsNCg== ---1463811839-1480170047-930343844=:5386-- From ggi-develop-request@eskimo.com Fri Jun 25 18:29:35 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA17797 for ; Fri, 25 Jun 1999 18:29:34 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA26450; Fri, 25 Jun 1999 15:09:20 -0700 Resent-Date: Fri, 25 Jun 1999 15:09:20 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: pitch Date: Fri, 25 Jun 1999 18:04:20 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99062518092600.08485@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"pozsq2.0.1T6.Du_St"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13532 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com If I create a surface doing backvis=ggiOpen("memory"); ggiSetGraphMode(backvis, ...); and then access it to write a picture or something to it will I ever have to worry about the pitch and if so how do I find it? ie if I declare a visual of 800x600 and i go to write a picture to it will I have to write the first 800 pixels, then add the pitch to get the memory location of the beginning of the next line? -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Fri Jun 25 20:16:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA19417 for ; Fri, 25 Jun 1999 20:16:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA05002; Fri, 25 Jun 1999 17:05:10 -0700 Resent-Date: Fri, 25 Jun 1999 17:05:10 -0700 Sender: marcus@e.kth.se Message-ID: <3774192D.7B24858F@stacken.kth.se> Date: Sat, 26 Jun 1999 00:05:01 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: pitch References: <99062518092600.08485@mongoose> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"guAu91.0.2D1.ra1Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13533 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B wrote: > > If I create a surface What do you mean by that? > backvis=ggiOpen("memory"); > ggiSetGraphMode(backvis, ...); > > and then access it to write a picture or something to it will I ever have to > worry about the pitch and if so how do I find it? ie if I declare a visual of > 800x600 and i go to write a picture to it will I have to write the first 800 > pixels, then add the pitch to get the memory location of the beginning of the > next line? If you use DirectBuffer you'll find all the necessary info in the DB struct, otherwise the stride is not relevant. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Fri Jun 25 20:17:25 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA19430 for ; Fri, 25 Jun 1999 20:17:24 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA05461; Fri, 25 Jun 1999 17:05:59 -0700 Resent-Date: Fri, 25 Jun 1999 17:05:59 -0700 Sender: marcus@e.kth.se Message-ID: <37741961.3976D3AB@stacken.kth.se> Date: Sat, 26 Jun 1999 00:05:53 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: New lib in CVS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"zX_ac3.0.1L1.bb1Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13534 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Christoph Egger wrote: > > Hi all! > > In the new snapshot I've downloaded, I found a new lib called libedemo. > What does it? What's the aim of it? Check the README file. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Fri Jun 25 20:23:49 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA19478 for ; Fri, 25 Jun 1999 20:23:48 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA08198; Fri, 25 Jun 1999 17:12:05 -0700 Resent-Date: Fri, 25 Jun 1999 17:12:05 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: pitch Date: Fri, 25 Jun 1999 20:08:05 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <3774192D.7B24858F@stacken.kth.se> MIME-Version: 1.0 Message-Id: <99062520120700.09023@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"ZjAn13.0.u_1.Kh1Tt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13535 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 25 Jun 1999, Marcus Sundberg wrote: > Garrett B wrote: > > > > If I create a surface > > What do you mean by that? I meant a visual. Blah, "surface" is a DirectX hangover... or Direct Death as it should be called. > > backvis=ggiOpen("memory"); > > ggiSetGraphMode(backvis, ...); > > > > and then access it to write a picture or something to it will I ever have to > > worry about the pitch and if so how do I find it? ie if I declare a visual of > > 800x600 and i go to write a picture to it will I have to write the first 800 > > pixels, then add the pitch to get the memory location of the beginning of the > > next line? > > If you use DirectBuffer you'll find all the necessary info in the DB > struct, otherwise the stride is not relevant. ah stride is what its called. Pitch, thats another DX term. -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Fri Jun 25 20:30:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA19529 for ; Fri, 25 Jun 1999 20:30:01 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA09732; Fri, 25 Jun 1999 17:18:17 -0700 Resent-Date: Fri, 25 Jun 1999 17:18:17 -0700 Date: Fri, 25 Jun 1999 20:18:12 -0400 (EDT) From: Isaac Connor To: ggi-develop@eskimo.com Subject: Problems with GII Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"J3MHa2.0.qN2.8n1Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13536 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com I recently got a Millenium I, and so have my Fixed freq monitor going. So I am trying to run XGGI on it. The problem I am having is with GII, it won't take any settings for the mouse. It ignores Env variables, and the settings in ~/.ggi/input/mouse and /usr/local/etc/ggi/input/mouse Setting GGI_DEBUG tells me that no arguments were given (or so it thinks), and it tries to autodetect, which it does incorrectly. So, has anyone else had this problem? Is the error in the docs, or is this a bug? This was with the latest cvs checkout degas... Isaac Connor From ggi-develop-request@eskimo.com Fri Jun 25 20:58:32 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA19821 for ; Fri, 25 Jun 1999 20:58:31 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA16587; Fri, 25 Jun 1999 17:46:44 -0700 Resent-Date: Fri, 25 Jun 1999 17:46:44 -0700 Date: Fri, 25 Jun 1999 21:38:25 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: GII/XGGI/xdm (was: Re: Problems with GII) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"W7PoL2.0.-24.pB2Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13537 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Fri, 25 Jun 1999, Isaac Connor wrote: > I recently got a Millenium I, and so have my Fixed freq monitor going. So > I am trying to run XGGI on it. The problem I am having is with GII, it > won't take any settings for the mouse. It ignores Env variables, and the > settings in ~/.ggi/input/mouse and /usr/local/etc/ggi/input/mouse > Setting GGI_DEBUG tells me that no arguments were given (or so it thinks), > and it tries to autodetect, which it does incorrectly. > > So, has anyone else had this problem? Is the error in the docs, or is Yes, it did something like this when I was trying to get xdm to run it. However, in my case startx worked fine, so maybe another problem other than yours. I was working with the potato Debian packages. (BTW XGGI dumps when given e.g. "vt8" as a command line argument, though it has a "ttyxx" argument which does not seem to work as described, and which seems to be intended to do the same thing.) With xdm, it also refused to open/switch to a new terminal, even when I explicity set GGI_NEWVT, so I was running it on top of the first VC, which was somehow grabbing my mouse/key input. The only way I could get it to work was calling it via /bin/open, and for some reason that wouldn't die when the window manager was exited, so it was fairly useless. BTW, does the Millineum II's SoG matroxfb argument work for you? With my Mystique, it does something to the sync, but apparently not everything it needs to do. -- Brian From ggi-develop-request@eskimo.com Fri Jun 25 21:03:34 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA19881 for ; Fri, 25 Jun 1999 21:03:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA18811; Fri, 25 Jun 1999 17:52:06 -0700 Resent-Date: Fri, 25 Jun 1999 17:52:06 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990626024549.A500@rz.uni-duesseldorf.de> Date: Sat, 26 Jun 1999 02:45:49 +0200 From: Andreas Beck To: mailing list GGI Subject: [Christoph_Egger@t-online.de: New lib in CVS] Mail-Followup-To: mailing list GGI Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 Resent-Message-ID: <"l0hC-3.0.ib4.rG2Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13539 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > In the new snapshot I've downloaded, I found a new lib called libedemo. > What does it? What's the aim of it? It demonstrates how to write extensions. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Fri Jun 25 21:03:36 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id VAA19889 for ; Fri, 25 Jun 1999 21:03:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id RAA18785; Fri, 25 Jun 1999 17:52:04 -0700 Resent-Date: Fri, 25 Jun 1999 17:52:04 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990626025437.A853@rz.uni-duesseldorf.de> Date: Sat, 26 Jun 1999 02:54:37 +0200 From: Andreas Beck To: mailing list GGI Subject: Re: libgii - improved mouse patch Mail-Followup-To: mailing list GGI References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Christoph Egger on Fri, Jun 25, 1999 at 10:50:44PM +0200 Resent-Message-ID: <"ckTWQ1.0.Fb4.pG2Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13538 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I've improved the patch I sent before. It fixes a lack in the handling > when the middle mouse button is pressed. > The patch is attached. Applied. Sorry for messing it up in the first place ... CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Fri Jun 25 22:38:00 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA20767 for ; Fri, 25 Jun 1999 22:37:59 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA10318; Fri, 25 Jun 1999 19:26:47 -0700 Resent-Date: Fri, 25 Jun 1999 19:26:47 -0700 Date: Fri, 25 Jun 1999 23:18:31 -0400 (EDT) From: "Brian S. Julin" To: mailing list GGI Subject: Re: [Christoph_Egger@t-online.de: New lib in CVS] In-Reply-To: <19990626024549.A500@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"cvaeh.0.2X2.cf3Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13540 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sat, 26 Jun 1999, Andreas Beck wrote: > It demonstrates how to write extensions. Coolness -- is this in a final form... i.e. does it provide the desired skeletal autoconf and /etc/ggi structure, so I could use it to complete GGIExtensionHelper.pm, or does it need more work and I should wait a bit? -- Brian From ggi-develop-request@eskimo.com Sat Jun 26 06:04:41 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA24587 for ; Sat, 26 Jun 1999 06:04:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA26234; Sat, 26 Jun 1999 02:53:09 -0700 Resent-Date: Sat, 26 Jun 1999 02:53:09 -0700 Sender: marcus@e.kth.se Message-ID: <3774A2ED.3FE872EF@stacken.kth.se> Date: Sat, 26 Jun 1999 09:52:45 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Problems with GII References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"-8OIz2.0.kP6.pBATt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13541 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Isaac Connor wrote: > > I recently got a Millenium I, and so have my Fixed freq monitor going. So > I am trying to run XGGI on it. The problem I am having is with GII, it > won't take any settings for the mouse. It ignores Env variables, and the > settings in ~/.ggi/input/mouse and /usr/local/etc/ggi/input/mouse > > Setting GGI_DEBUG tells me that no arguments were given (or so it thinks), > and it tries to autodetect, which it does incorrectly. > > So, has anyone else had this problem? Is the error in the docs, or is > this a bug? It's an error in reading the docs. ;-) >From libgii/doc/inputs.txt: In that case we first try to read ~/.ggi/input/linux-mouse and then ^^^^^^^^^^^ $prefix/etc/ggi/input/linux-mouse. In the first file found ^^^^^^^^^^^ we look for the following entries: mouse mdev If none of the files are found we first try to autodetect the mouse, and as a last resort we try parsing /etc/vga/libvga.config to find out the necessary info. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sat Jun 26 06:34:57 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id GAA24669 for ; Sat, 26 Jun 1999 06:34:56 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA30439; Sat, 26 Jun 1999 03:22:53 -0700 Resent-Date: Sat, 26 Jun 1999 03:22:53 -0700 Sender: marcus@e.kth.se Message-ID: <3774A9F6.77810B6B@stacken.kth.se> Date: Sat, 26 Jun 1999 10:22:46 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: [Christoph_Egger@t-online.de: New lib in CVS] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Z2NPR1.0.MR7.ydATt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13542 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Brian S. Julin wrote: > > On Sat, 26 Jun 1999, Andreas Beck wrote: > > It demonstrates how to write extensions. > > Coolness -- is this in a final form... More or less, but some changes will have to be made to the extension mechanism to fix a recently discovered bug when detaching extensions. This may or may not change the prototype for ggiExtensionLoadDL(). > i.e. does it provide the > desired skeletal autoconf and /etc/ggi structure, Yes, the autoconf stuff should be fine to use as reference material. > so I could use > it to complete GGIExtensionHelper.pm, or does it need more work and I > should wait a bit? What is GGIExtensionHelper.pm anyway? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sat Jun 26 07:29:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA24852 for ; Sat, 26 Jun 1999 07:29:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA03313; Sat, 26 Jun 1999 04:16:56 -0700 Resent-Date: Sat, 26 Jun 1999 04:16:56 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: clanlib@dark.x.dtu.dk, bedevtalk@be.com, ggi-develop@eskimo.com Subject: BeOS rules and blitting stuff Date: Sat, 26 Jun 1999 13:09:37 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99062613184900.00387@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"vL_on2.0.Rp.aQBTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13543 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, I implemented the accelerated fill_rect in ClanLib BeOS today. The results for Linux/GGI/FBDev are 23600 rects /5 sec Under BeOS I get 30000 rects /5 sec ;-) I want to implement accelerated put_screen with blits. The problem is, that I have to "puzzle" the offscreen surfaces into the framebuffer, because I only can do a blit(x,y,w,h,dx,dy). Is there any method in GGI or BeOS for blitting from linear sources, so I can put the images into framebuffer with only "one dimensional" fragmentation? I need a blit( source_address, length, dest_x, dest_y, dest_width ) Or blit( source_address, source_width, source_height, dest_x, dest_y) Understood my problem? I think hardware supports that, blits with source_pitch==source_width, but with different dest_pitch. And I think M$ does this in DirectX. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Sat Jun 26 11:08:24 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA26351 for ; Sat, 26 Jun 1999 11:08:23 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA15160; Sat, 26 Jun 1999 07:55:50 -0700 Resent-Date: Sat, 26 Jun 1999 07:55:50 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990626144404.B828@rz.uni-duesseldorf.de> Date: Sat, 26 Jun 1999 14:44:04 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: BeOS rules and blitting stuff Mail-Followup-To: ggi-develop@eskimo.com References: <99062613184900.00387@master> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99062613184900.00387@master>; from Denis Oliver Kropp on Sat, Jun 26, 1999 at 01:09:37PM +0200 Resent-Message-ID: <"kcZFZ.0.bi3.qdETt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13545 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I want to implement accelerated put_screen with blits. > The problem is, that I have to "puzzle" the offscreen surfaces into the framebuffer, > because I only can do a blit(x,y,w,h,dx,dy). Is there any method in GGI or BeOS for blitting from > linear sources, so I can put the images into framebuffer with only "one dimensional" fragmentation? That's a question of the card supporting it. Some do, some don't. That's why I'm working on a Bob/Sprite extension that abstracts that. It will try to use linear blits if possible, or fall back to two-dimensional ones, if not. It can as well do some kind of garbage collection, as the individual objects are referenced by an abstract handle. I can send you a very very preliminary copy for review, if you want. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sat Jun 26 11:08:28 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA26355 for ; Sat, 26 Jun 1999 11:08:27 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA15155; Sat, 26 Jun 1999 07:55:49 -0700 Resent-Date: Sat, 26 Jun 1999 07:55:49 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990626144004.A828@rz.uni-duesseldorf.de> Date: Sat, 26 Jun 1999 14:40:04 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: New lib in CVS Mail-Followup-To: ggi-develop@eskimo.com References: <3774A9F6.77810B6B@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <3774A9F6.77810B6B@stacken.kth.se>; from Marcus Sundberg on Sat, Jun 26, 1999 at 10:22:46AM +0000 Resent-Message-ID: <"repJ_3.0.7i3.odETt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13544 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > so I could use > > it to complete GGIExtensionHelper.pm, or does it need more work and I > > should wait a bit? > What is GGIExtensionHelper.pm anyway? IIRC it's a "stub generator" that you feed with the desired prototypes for an extension. It then outputs a stub tree for that extension - right ? CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Sat Jun 26 11:12:19 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA26386 for ; Sat, 26 Jun 1999 11:12:18 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id HAA15519; Sat, 26 Jun 1999 07:58:00 -0700 Resent-Date: Sat, 26 Jun 1999 07:58:00 -0700 Date: Sat, 26 Jun 1999 11:49:57 -0400 (EDT) From: "Brian S. Julin" Reply-To: "Brian S. Julin" To: Marcus Sundberg cc: ggi-develop@eskimo.com Subject: Re: [Christoph_Egger@t-online.de: New lib in CVS] In-Reply-To: <3774A9F6.77810B6B@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"hpii_3.0.Jo3.sfETt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13546 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sat, 26 Jun 1999, Marcus Sundberg wrote: > What is GGIExtensionHelper.pm anyway? Perl script that automatically lays out the basics of an extension -- I had sent yourself and Andy a copy of the preview edition of that and the accompanying Extension HOWTO URL (below), and was waiting for a sample extension that was in its own tree to adjust it to work that way instead of placing it alongside the ggimisc extension in the libggi tree. I guess this would be it then :). http://calyx.com/~bri/projects/GGI/GGPG/ext.html -- Brian From ggi-develop-request@eskimo.com Sat Jun 26 18:09:20 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA29861 for ; Sat, 26 Jun 1999 18:09:18 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA29496; Sat, 26 Jun 1999 14:56:44 -0700 Resent-Date: Sat, 26 Jun 1999 14:56:44 -0700 Date: Sat, 26 Jun 1999 18:48:18 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Re: New lib in CVS In-Reply-To: <19990626144004.A828@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"Xi78R2.0.4C7._nKTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13547 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sat, 26 Jun 1999, Andreas Beck wrote: > > What is GGIExtensionHelper.pm anyway? > > IIRC it's a "stub generator" that you feed with the desired prototypes for > an extension. It then outputs a stub tree for that extension - right ? Yes, basically the following commands would lay out a stub tree for LibGGINull with a private data area, a (in this case, parameterless) function ggiNop, and a generic/stubs target tree for the extension. GGIExtensionHelper create null GGIExtensionHelper addstruct null void* private NULL GGIExtensionHelper addfunc null nop GGIExtensionHelper addtarget null generic/stubs I stopped short of implementing the last command because I needed to change from building the extension under lib/libggi/extensions and lib/libggi/display and put the new extension in it's own directory under lib/, and I know nothing about creating an autoconf tree. Soooo... I'll do a checkout and see if I can get it to build one like the new sample extension. I should probably start keeping the script in CVS -- where should I put it config/scripts or lib/libggi/scripts? -- Brian From ggi-develop-request@eskimo.com Sun Jun 27 07:07:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA07791 for ; Sun, 27 Jun 1999 07:07:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id DAA13386; Sun, 27 Jun 1999 03:55:39 -0700 Resent-Date: Sun, 27 Jun 1999 03:55:39 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: BeOS rules and blitting stuff Date: Sun, 27 Jun 1999 12:55:54 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <19990626144404.B828@rz.uni-duesseldorf.de> MIME-Version: 1.0 Message-Id: <99062712572700.00284@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"5eLFO2.0.xG3.fCWTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13548 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck´s crap from Sam, 26 Jun 1999: > > I want to implement accelerated put_screen with blits. > > The problem is, that I have to "puzzle" the offscreen surfaces into the framebuffer, > > because I only can do a blit(x,y,w,h,dx,dy). Is there any method in GGI or BeOS for blitting from > > linear sources, so I can put the images into framebuffer with only "one dimensional" fragmentation? > > That's a question of the card supporting it. Some do, some don't. Microsoft has the same problem with DirectX? > That's why I'm working on a Bob/Sprite extension that abstracts that. > It will try to use linear blits if possible, or fall back to two-dimensional > ones, if not. It can as well do some kind of garbage collection, as the > individual objects are referenced by an abstract handle. > > I can send you a very very preliminary copy for review, if you want. Thanks, but I only need an algorithm that "puzzles" me the images into the third frame ;-) With least fragmentation, any idea? -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Sun Jun 27 12:30:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA10987 for ; Sun, 27 Jun 1999 12:30:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA14596; Sun, 27 Jun 1999 09:17:21 -0700 Resent-Date: Sun, 27 Jun 1999 09:17:21 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: clanlib@dark.x.dtu.dk, bedevtalk@be.com, ggi-develop@eskimo.com, devel@XFree86.Org Subject: ClanMarks on BeOS, Linux, Windows Date: Sun, 27 Jun 1999 17:52:14 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99062718071700.00220@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"cZy1W3.0.uZ3.EwaTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13549 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, First: sorry to XFree mailing list, but I think this might interest you. These are the results from ClanMarks, a benchmarking tool that uses ClanLib. The following tests ran with 800x600 16 bit, using video memory directly. I disabled the flip_display() for retrace´s sake. Tested was the performance of fill_rect, fill_rect alpha, put_screen. All tests ran 5 seconds, the numbers are the fills/puts within this 5 seconds. The tag "hw" means obviously hardware acceleration. Windows DirectX --------------------- fill_rect 6352 hw fill_rect alpha 85 put_screen 18867 hw BeOS --------------------- fill_rect 30315 hw fill_rect alpha 65 put_screen 4429 BeOS --------------------- fill_rect 1763 fill_rect alpha 65 put_screen 4426 Linux GGI-on-FBDev --------------------- fill_rect 23719 hw fill_rect alpha 72 put_screen 11798 Linux FBDev --------------------- fill_rect 1486 fill_rect alpha 72 put_screen 11825 All test ran on Celeron 333A, Matrox Mystique 1064sg 4Mb, 64Mb. Don´t ask me why DirectX is that slow, I think it is the HAL ;-) And I think the BeOS graphics hook functions provide the most direct wire to the hardware. No engine syncs were used in BeOS and Linux/GGI, don´t know about DirectX. So what are we gonna do today? -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Sun Jun 27 13:43:48 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA11911 for ; Sun, 27 Jun 1999 13:43:47 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA01689; Sun, 27 Jun 1999 10:32:26 -0700 Resent-Date: Sun, 27 Jun 1999 10:32:26 -0700 Sender: marcus@e.kth.se Message-ID: <37765FF0.24DD9498@stacken.kth.se> Date: Sun, 27 Jun 1999 17:31:28 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com CC: clanlib@dark.x.dtu.dk, bedevtalk@be.com Subject: Re: ClanMarks on BeOS, Linux, Windows References: <99062718071700.00220@master> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"5k8hg2.0.DQ.e0cTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13550 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > BeOS > --------------------- > fill_rect 30315 hw > fill_rect alpha 65 > put_screen 4429 > > BeOS > --------------------- > fill_rect 1763 > fill_rect alpha 65 > put_screen 4426 I can't find any references to BeOS neither in ClanLib CVS or at your web-pages. Where is the code for that? > Linux GGI-on-FBDev > --------------------- > fill_rect 23719 hw > fill_rect alpha 72 > put_screen 11798 > > Linux FBDev > --------------------- > fill_rect 1486 > fill_rect alpha 72 > put_screen 11825 > > All test ran on Celeron 333A, Matrox Mystique 1064sg 4Mb, 64Mb. > > Don´t ask me why DirectX is that slow, I think it is the HAL ;-) > And I think the BeOS graphics hook functions provide the most direct wire to the hardware. How is fill_rect implemented in ClanLib'ss BeOS code? //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sun Jun 27 15:25:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA13328 for ; Sun, 27 Jun 1999 15:25:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA27376; Sun, 27 Jun 1999 12:14:23 -0700 Resent-Date: Sun, 27 Jun 1999 12:14:23 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: ggi-develop@eskimo.com Subject: Re: ClanMarks on BeOS, Linux, Windows Date: Sun, 27 Jun 1999 20:16:00 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain References: <37765FF0.24DD9498@stacken.kth.se> MIME-Version: 1.0 Message-Id: <99062720212001.01220@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"PCxWy3.0.Yh6.EWdTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13551 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Marcus Sundberg´s crap from Son, 27 Jun 1999: > Denis Oliver Kropp wrote: > > BeOS > > --------------------- > > fill_rect 30315 hw > > fill_rect alpha 65 > > put_screen 4429 > > > > BeOS > > --------------------- > > fill_rect 1763 > > fill_rect alpha 65 > > put_screen 4426 > > I can't find any references to BeOS neither in ClanLib CVS or at > your web-pages. Where is the code for that? On my harddrive ;-) very unstable for now. Will possibly merge into ClanLib 0.1.17 > How is fill_rect implemented in ClanLib'ss BeOS code? ClanLib gets a hook function from the driver once: typedef long (*fill16_hook)(long,long,long,long,uint16); fill_rect16 = (fill16_hook)cardHookAt(13); fill_rect() does: fill_rect16( crect.m_x1, crect.m_y1, crect.m_x2, crect.m_y2, pixelcolor ); instead of: ggiSetGCForeground( vis, pixelcolor ); ggiDrawBox( vis, crect.m_x1, crect.m_y1, crect.m_x2 - crect.m_x1, crect.m_y2 - crect.m_y1 ); > > //Marcus > -- > -------------------------------+------------------------------------ > Marcus Sundberg | http://www.stacken.kth.se/~mackan/ > Royal Institute of Technology | Phone: +46 707 295404 > Stockholm, Sweden | E-Mail: mackan@stacken.kth.se -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Sun Jun 27 17:23:12 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA14680 for ; Sun, 27 Jun 1999 17:23:11 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA25194; Sun, 27 Jun 1999 14:11:02 -0700 Resent-Date: Sun, 27 Jun 1999 14:11:02 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: bedevtalk@be.com, clanlib@dark.x.dtu.dk, ggi-develop@eskimo.com Subject: fast_memmove, BIG acceleration Date: Sun, 27 Jun 1999 23:12:19 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: Multipart/Mixed; boundary="Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD" MIME-Version: 1.0 Message-Id: <99062723111700.00311@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"33xee1.0.K96.ZDfTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13552 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD Content-Type: text/plain Content-Transfer-Encoding: 8bit Hi, I took the fast_memmove assembler function from kernel headers and used it for put_screen. The new results are: BeOS --------------------------- fill_rect alpha 75 before: 65 put_screen 14315 before: 4429 ClanBomber´s framerate went from 28 to 98!! For those of you, who don´t have it, I attached string_asm.h Before using this asm function, I wrote a for loop which uses uint32 pointers. It was exactly as fast as this assembler function, but only worked for uint32 aligned values. just include string_asm.h and replace memcpy with fast_memmove ;-) Besides that the flickering is still there. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. --Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD Content-Type: text/x-c; name="string_asm.h" Content-Transfer-Encoding: base64 Content-Description: Assembler memcpy Content-Disposition: attachment; filename="string_asm.h" LyoKICogIGxpbnV4L2RyaXZlcnMvdmlkZW8vZmJjb24uaCAtLSBMb3cgbGV2ZWwgZnJhbWUgYnVm ZmVyIGJhc2VkIGNvbnNvbGUgZHJpdmVyCiAqCiAqCUNvcHlyaWdodCAoQykgMTk5NyBHZWVydCBV eXR0ZXJob2V2ZW4KICoKICogIFRoaXMgZmlsZSBpcyBzdWJqZWN0IHRvIHRoZSB0ZXJtcyBhbmQg Y29uZGl0aW9ucyBvZiB0aGUgR05VIEdlbmVyYWwgUHVibGljCiAqICBMaWNlbnNlLiAgU2VlIHRo ZSBmaWxlIENPUFlJTkcgaW4gdGhlIG1haW4gZGlyZWN0b3J5IG9mIHRoaXMgYXJjaGl2ZQogKiAg Zm9yIG1vcmUgZGV0YWlscy4KICovCgojaWZuZGVmIHN0cmluZ19hc20KI2RlZmluZSBzdHJpbmdf YXNtCgovKiA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PSAqLwovKiAgICAgICAgICAgICAgICAgICAgICBVdGlsaXR5IEFzc2Vt YmxlciBGdW5jdGlvbnMgICAgICAgICAgICAgICAgICAqLwovKiA9PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PSAqLwoKCiNpZiBk ZWZpbmVkKF9fbWM2ODAwMF9fKQoKLyogPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PSAqLwoKLyogVGhvc2Ugb2YgYSBk ZWxpY2F0ZSBkaXNwb3NpdGlvbiBtaWdodCBsaWtlIHRvIHNraXAgdGhlIG5leHQgY291cGxlIG9m CiAqIHBhZ2VzLgogKgogKiBUaGVzZSBmdW5jdGlvbnMgYXJlIGRyb3AgaW4gcmVwbGFjZW1lbnRz IGZvciBtZW1tb3ZlIGFuZAogKiBtZW1zZXQoXywgMCwgXykuIEhvd2V2ZXIgdGhlaXIgZml2ZSBp bnN0YW5jZXMgYWRkIGF0IGxlYXN0IGEga2lsb2J5dGUKICogdG8gdGhlIG9iamVjdCBmaWxlLiBZ b3UgaGF2ZSBiZWVuIHdhcm5lZC4KICoKICogTm90IGEgZ3JlYXQgZmFuIG9mIGFzc2VtYmxlciBm b3IgdGhlIHNha2Ugb2YgaXQsIGJ1dCBJIHRoaW5rCiAqIHRoYXQgdGhlc2Ugcm91dGluZXMgYXJl IGF0IGxlYXN0IDEwIHRpbWVzIGZhc3RlciB0aGFuIHRoZWlyIEMKICogZXF1aXZhbGVudHMgZm9y IGxhcmdlIGJsaXRzLCBhbmQgdGhhdCdzIGltcG9ydGFudCB0byB0aGUgbG93ZXN0IGxldmVsIG9m CiAqIGEgZ3JhcGhpY3MgZHJpdmVyLiBRdWVzdGlvbiBpcyB3aGV0aGVyIHNvbWUgc2NoZW1lIHdp dGggdGhlIGJsaXR0ZXIKICogd291bGQgYmUgZmFzdGVyLiBJIHN1c3BlY3Qgbm90IGZvciBzaW1w bGUgdGV4dCBzeXN0ZW0gLSBub3QgbXVjaAogKiBhc3luY2hyb255LgogKgogKiBDb2RlIGlzIHZl cnkgc2ltcGxlLCBqdXN0IGdydWVzb21lIGV4cGFuc2lvbi4gQmFzaWMgc3RyYXRlZ3kgaXMgdG8K ICogaW5jcmVhc2UgZGF0YSBtb3ZlZC9jbGVhcmVkIGF0IGVhY2ggc3RlcCB0byAxNiBieXRlcyB0 byByZWR1Y2UKICogaW5zdHJ1Y3Rpb24gcGVyIGRhdGEgbW92ZSBvdmVyaGVhZC4gbW92ZW0gbWln aHQgYmUgZmFzdGVyIHN0aWxsCiAqIEZvciBtb3JlIHRoYW4gMTUgYnl0ZXMsIHdlIHRyeSB0byBh bGlnbiB0aGUgd3JpdGUgZGlyZWN0aW9uIG9uIGEKICogbG9uZ3dvcmQgYm91bmRhcnkgdG8gZ2V0 IG1heGltdW0gc3BlZWQuIFRoaXMgaXMgZXZlbiBtb3JlIGdydWVzb21lLgogKiBVbmFsaWduZWQg cmVhZC93cml0ZSB1c2VkIHJlcXVpcmVzIDY4MDIwKyAtIHRoaW5rIHRoaXMgaXMgYSBwcm9ibGVt PwogKgogKiBTb3JyeSEKICovCgoKLyogKytyb21hbjogSSd2ZSBvcHRpbWl6ZWQgUm9iZXJ0J3Mg b3JpZ2luYWwgdmVyc2lvbnMgaW4gc29tZSBtaW5vcgogKiBhc3BlY3RzLCBlLmcuIG1vdmVxIGlu c3RlYWQgb2YgbW92ZWwsIGxldCBnY2MgY2hvb3NlIHRoZSByZWdpc3RlcnMsCiAqIHVzZSBtb3Zl bSBpbiBzb21lIHBsYWNlcy4uLgogKiBGb3Igb3RoZXIgbW9kZXMgdGhhbiAxIHBsYW5lLCBsb3Rz IG9mIG1vcmUgc3VjaCBhc3NlbWJsZXIgZnVuY3Rpb25zCiAqIHdlcmUgbmVlZGVkIChlLmcuIHRo ZSBvbmVzIHVzaW5nIG1vdmVwIG9yIGV4cGFuZGluZyBjb2xvciB2YWx1ZXMpLgogKi8KCi8qICsr YW5kcmVhczogbW9yZSBvcHRpbWl6YXRpb25zOgogICBzdWJsICM2NTUzNixkMCByZXBsYWNlZCBi eSBjbHJ3IGQwOyBzdWJxbCAjMSxkMCBmb3IgZGJjYwogICBhZGRhbCBpcyBmYXN0ZXIgdGhhbiBh ZGRhdwogICBtb3ZlcCBpcyByYXRoZXIgZXhwZW5zaXZlIGNvbXBhcmVkIHRvIG9yZGluYXJ5IG1v dmUncwogICBzb21lIGZ1bmN0aW9ucyByZXdyaXR0ZW4gaW4gQyBmb3IgY2xhcml0eSwgbm8gc3Bl ZWQgbG9zcyAqLwoKc3RhdGljIF9faW5saW5lX18gdm9pZCAqYXNtX21lbWNsZWFyX3NtYWxsKHZv aWQgKnMsIHNpemVfdCBjb3VudCkKewogICBpZiAoIWNvdW50KQogICAgICByZXR1cm4oMCk7Cgog ICBfX2FzbV9fIF9fdm9sYXRpbGVfXygKICAgICAgICAgImxzcmwgICAjMSwlMSA7IGpjYyAxZiA7 IG1vdmViICUyLCUwQC1cblx0IgogICAgICAiMTogbHNybCAgICMxLCUxIDsgamNjIDFmIDsgbW92 ZXcgJTIsJTBALVxuXHQiCiAgICAgICIxOiBsc3JsICAgIzEsJTEgOyBqY2MgMWYgOyBtb3ZlbCAl MiwlMEAtXG5cdCIKICAgICAgIjE6IGxzcmwgICAjMSwlMSA7IGpjYyAxZiA7IG1vdmVsICUyLCUw QC0gOyBtb3ZlbCAlMiwlMEAtXG5cdCIKICAgICAgIjE6IHN1YnFsICAjMSwlMSA7IGpjcyAzZlxu XHQiCiAgICAgICIyOiBtb3ZlbWwgJTIvJTMvJTQvJTUsJTBALVxuXHQiCiAgICAgICAgICJkYnJh ICUxLDJiXG5cdCIKICAgICAgIjM6IgogICAgICAgICA6ICI9YSIgKHMpLCAiPWQiIChjb3VudCkK ICAgICAgICAgOiAgImQiICgwKSwgImQiICgwKSwgImQiICgwKSwgImQiICgwKSwKICAgICAgICAg ICAgIjAiICgoY2hhciAqKXMrY291bnQpLCAiMSIgKGNvdW50KQogICk7CgogICByZXR1cm4oMCk7 Cn0KCgpzdGF0aWMgX19pbmxpbmVfXyB2b2lkICphc21fbWVtY2xlYXIodm9pZCAqcywgc2l6ZV90 IGNvdW50KQp7CiAgIGlmICghY291bnQpCiAgICAgIHJldHVybigwKTsKCiAgIGlmIChjb3VudCA8 IDE2KSB7CiAgICAgIF9fYXNtX18gX192b2xhdGlsZV9fKAogICAgICAgICAgICAibHNybCAgICMx LCUxIDsgamNjIDFmIDsgY2xyYiAlMEArXG5cdCIKICAgICAgICAgIjE6IGxzcmwgICAjMSwlMSA7 IGpjYyAxZiA7IGNscncgJTBAK1xuXHQiCiAgICAgICAgICIxOiBsc3JsICAgIzEsJTEgOyBqY2Mg MWYgOyBjbHJsICUwQCtcblx0IgogICAgICAgICAiMTogbHNybCAgICMxLCUxIDsgamNjIDFmIDsg Y2xybCAlMEArIDsgY2xybCAlMEArXG5cdCIKICAgICAgICAgIjE6IgogICAgICAgICAgICA6ICI9 YSIgKHMpLCAiPWQiIChjb3VudCkKICAgICAgICAgICAgOiAiMCIgKHMpLCAiMSIgKGNvdW50KQog ICAgICk7CiAgIH0gZWxzZSB7CiAgICAgIGxvbmcgdG1wOwogICAgICBfX2FzbV9fIF9fdm9sYXRp bGVfXygKICAgICAgICAgICAgIm1vdmVsICUxLCUyXG5cdCIKICAgICAgICAgICAgImxzcmwgICAj MSwlMiA7IGpjYyAxZiA7IGNscmIgJTBAKyA7IHN1YnF3ICMxLCUxXG5cdCIKICAgICAgICAgICAg ImxzcmwgICAjMSwlMiA7IGpjcyAyZlxuXHQiICAvKiAlMCBpbmNyZWFzZWQ9PmJpdCAyIHN3aXRj aGVkKi8KICAgICAgICAgICAgImNscncgICAlMEArICA7IHN1YnF3ICAjMiwlMSA7IGpyYSAyZlxu XHQiCiAgICAgICAgICIxOiBsc3JsICAgIzEsJTIgOyBqY2MgMmZcblx0IgogICAgICAgICAgICAi Y2xydyAgICUwQCsgIDsgc3VicXcgICMyLCUxXG5cdCIKICAgICAgICAgIjI6IG1vdmV3ICUxLCUy OyBsc3JsICMyLCUxIDsgamVxIDZmXG5cdCIKICAgICAgICAgICAgImxzcmwgICAjMSwlMSA7IGpj YyAzZiA7IGNscmwgJTBAK1xuXHQiCiAgICAgICAgICIzOiBsc3JsICAgIzEsJTEgOyBqY2MgNGYg OyBjbHJsICUwQCsgOyBjbHJsICUwQCtcblx0IgogICAgICAgICAiNDogc3VicWwgICMxLCUxIDsg amNzIDZmXG5cdCIKICAgICAgICAgIjU6IGNscmwgJTBAKzsgY2xybCAlMEArIDsgY2xybCAlMEAr IDsgY2xybCAlMEArXG5cdCIKICAgICAgICAgICAgImRicmEgJTEsNWIgICA7IGNscncgJTE7IHN1 YnFsICMxLCUxOyBqY2MgNWJcblx0IgogICAgICAgICAiNjogbW92ZXcgJTIsJTE7IGJ0c3QgIzEs JTEgOyBqZXEgN2YgOyBjbHJ3ICUwQCtcblx0IgogICAgICAgICAiNzogICAgICAgICAgICA7IGJ0 c3QgIzAsJTEgOyBqZXEgOGYgOyBjbHJiICUwQCtcblx0IgogICAgICAgICAiODoiCiAgICAgICAg ICAgIDogIj1hIiAocyksICI9ZCIgKGNvdW50KSwgIj1kIiAodG1wKQogICAgICAgICAgICA6ICIw IiAocyksICIxIiAoY291bnQpCiAgICAgKTsKICAgfQoKICAgcmV0dXJuKDApOwp9CgoKc3RhdGlj IF9faW5saW5lX18gdm9pZCAqYXNtX21lbXNldCh2b2lkICpzLCBzaXplX3QgY291bnQpCnsKICAg aWYgKCFjb3VudCkKICAgICAgcmV0dXJuKDApOwoKICAgX19hc21fXyBfX3ZvbGF0aWxlX18oCiAg ICAgICAgICJsc3JsICAgIzEsJTEgOyBqY2MgMWYgOyBtb3ZlYiAlMiwlMEAtXG5cdCIKICAgICAg IjE6IGxzcmwgICAjMSwlMSA7IGpjYyAxZiA7IG1vdmV3ICUyLCUwQC1cblx0IgogICAgICAiMTog bHNybCAgICMxLCUxIDsgamNjIDFmIDsgbW92ZWwgJTIsJTBALVxuXHQiCiAgICAgICIxOiBsc3Js ICAgIzEsJTEgOyBqY2MgMWYgOyBtb3ZlbCAlMiwlMEAtIDsgbW92ZWwgJTIsJTBALVxuXHQiCiAg ICAgICIxOiBzdWJxbCAgIzEsJTEgOyBqY3MgM2Zcblx0IgogICAgICAiMjogbW92ZW1sICUyLyUz LyU0LyU1LCUwQC1cblx0IgogICAgICAgICAiZGJyYSAlMSwyYlxuXHQiCiAgICAgICIzOiIKICAg ICAgICAgOiAiPWEiIChzKSwgIj1kIiAoY291bnQpCiAgICAgICAgIDogICJkIiAoLTEpLCAiZCIg KC0xKSwgImQiICgtMSksICJkIiAoLTEpLAogICAgICAgICAgICAiMCIgKChjaGFyICopIHMgKyBj b3VudCksICIxIiAoY291bnQpCiAgKTsKCiAgIHJldHVybigwKTsKfQoKCnN0YXRpYyBfX2lubGlu ZV9fIHZvaWQgKmFzbV9tZW1tb3ZlKHZvaWQgKmQsIGNvbnN0IHZvaWQgKnMsIHNpemVfdCBjb3Vu dCkKewogICBpZiAoZCA8IHMpIHsKICAgICAgaWYgKGNvdW50IDwgMTYpIHsKICAgICAgICAgX19h c21fXyBfX3ZvbGF0aWxlX18oCiAgICAgICAgICAgICAgICJsc3JsICAgIzEsJTIgOyBqY2MgMWYg OyBtb3ZlYiAlMUArLCUwQCtcblx0IgogICAgICAgICAgICAiMTogbHNybCAgICMxLCUyIDsgamNj IDFmIDsgbW92ZXcgJTFAKywlMEArXG5cdCIKICAgICAgICAgICAgIjE6IGxzcmwgICAjMSwlMiA7 IGpjYyAxZiA7IG1vdmVsICUxQCssJTBAK1xuXHQiCiAgICAgICAgICAgICIxOiBsc3JsICAgIzEs JTIgOyBqY2MgMWYgOyBtb3ZlbCAlMUArLCUwQCsgOyBtb3ZlbCAlMUArLCUwQCtcblx0IgogICAg ICAgICAgICAiMToiCiAgICAgICAgICAgICAgIDogIj1hIiAoZCksICI9YSIgKHMpLCAiPWQiIChj b3VudCkKICAgICAgICAgICAgICAgOiAiMCIgKGQpLCAiMSIgKHMpLCAiMiIgKGNvdW50KQogICAg ICAgICk7CiAgICAgIH0gZWxzZSB7CiAgICAgICAgIGxvbmcgdG1wOwogICAgICAgICBfX2FzbV9f IF9fdm9sYXRpbGVfXygKICAgICAgICAgICAgICAgIm1vdmVsICAlMCwlM1xuXHQiCiAgICAgICAg ICAgICAgICJsc3JsICAgIzEsJTMgOyBqY2MgMWYgOyBtb3ZlYiAlMUArLCUwQCsgOyBzdWJxdyAj MSwlMlxuXHQiCiAgICAgICAgICAgICAgICJsc3JsICAgIzEsJTMgOyBqY3MgMmZcblx0IiAgLyog JTAgaW5jcmVhc2VkPT5iaXQgMiBzd2l0Y2hlZCovCiAgICAgICAgICAgICAgICJtb3ZldyAgJTFA KywlMEArICA7IHN1YnF3ICAjMiwlMiA7IGpyYSAyZlxuXHQiCiAgICAgICAgICAgICIxOiBsc3Js ICAgIzEsJTMgOyBqY2MgMmZcblx0IgogICAgICAgICAgICAgICAibW92ZXcgICUxQCssJTBAKyAg OyBzdWJxdyAgIzIsJTJcblx0IgogICAgICAgICAgICAiMjogbW92ZXcgICUyLCUtOyBsc3JsICMy LCUyIDsgamVxIDZmXG5cdCIKICAgICAgICAgICAgICAgImxzcmwgICAjMSwlMiA7IGpjYyAzZiA7 IG1vdmVsICUxQCssJTBAK1xuXHQiCiAgICAgICAgICAgICIzOiBsc3JsICAgIzEsJTIgOyBqY2Mg NGYgOyBtb3ZlbCAlMUArLCUwQCsgOyBtb3ZlbCAlMUArLCUwQCtcblx0IgogICAgICAgICAgICAi NDogc3VicWwgICMxLCUyIDsgamNzIDZmXG5cdCIKICAgICAgICAgICAgIjU6IG1vdmVsICAlMUAr LCUwQCs7bW92ZWwgJTFAKywlMEArXG5cdCIKICAgICAgICAgICAgICAgIm1vdmVsICAlMUArLCUw QCs7bW92ZWwgJTFAKywlMEArXG5cdCIKICAgICAgICAgICAgICAgImRicmEgICAlMiw1YiA7IGNs cncgJTI7IHN1YnFsICMxLCUyOyBqY2MgNWJcblx0IgogICAgICAgICAgICAiNjogbW92ZXcgICUr LCUyOyBidHN0ICMxLCUyIDsgamVxIDdmIDsgbW92ZXcgJTFAKywlMEArXG5cdCIKICAgICAgICAg ICAgIjc6ICAgICAgICAgICAgICA7IGJ0c3QgIzAsJTIgOyBqZXEgOGYgOyBtb3ZlYiAlMUArLCUw QCtcblx0IgogICAgICAgICAgICAiODoiCiAgICAgICAgICAgICAgIDogIj1hIiAoZCksICI9YSIg KHMpLCAiPWQiIChjb3VudCksICI9ZCIgKHRtcCkKICAgICAgICAgICAgICAgOiAiMCIgKGQpLCAi MSIgKHMpLCAiMiIgKGNvdW50KQogICAgICAgICk7CiAgICAgIH0KICAgfSBlbHNlIHsKICAgICAg aWYgKGNvdW50IDwgMTYpIHsKICAgICAgICAgX19hc21fXyBfX3ZvbGF0aWxlX18oCiAgICAgICAg ICAgICAgICJsc3JsICAgIzEsJTIgOyBqY2MgMWYgOyBtb3ZlYiAlMUAtLCUwQC1cblx0IgogICAg ICAgICAgICAiMTogbHNybCAgICMxLCUyIDsgamNjIDFmIDsgbW92ZXcgJTFALSwlMEAtXG5cdCIK ICAgICAgICAgICAgIjE6IGxzcmwgICAjMSwlMiA7IGpjYyAxZiA7IG1vdmVsICUxQC0sJTBALVxu XHQiCiAgICAgICAgICAgICIxOiBsc3JsICAgIzEsJTIgOyBqY2MgMWYgOyBtb3ZlbCAlMUAtLCUw QC0gOyBtb3ZlbCAlMUAtLCUwQC1cblx0IgogICAgICAgICAgICAiMToiCiAgICAgICAgICAgICAg IDogIj1hIiAoZCksICI9YSIgKHMpLCAiPWQiIChjb3VudCkKICAgICAgICAgICAgICAgOiAiMCIg KChjaGFyICopIGQgKyBjb3VudCksICIxIiAoKGNoYXIgKikgcyArIGNvdW50KSwgIjIiIChjb3Vu dCkKICAgICAgICApOwogICAgICB9IGVsc2UgewogICAgICAgICBsb25nIHRtcDsKICAgICAgICAg X19hc21fXyBfX3ZvbGF0aWxlX18oCiAgICAgICAgICAgICAgICJtb3ZlbCAlMCwlM1xuXHQiCiAg ICAgICAgICAgICAgICJsc3JsICAgIzEsJTMgOyBqY2MgMWYgOyBtb3ZlYiAlMUAtLCUwQC0gOyBz dWJxdyAjMSwlMlxuXHQiCiAgICAgICAgICAgICAgICJsc3JsICAgIzEsJTMgOyBqY3MgMmZcblx0 IiAgLyogJTAgaW5jcmVhc2VkPT5iaXQgMiBzd2l0Y2hlZCovCiAgICAgICAgICAgICAgICJtb3Zl dyAgJTFALSwlMEAtICA7IHN1YnF3ICAjMiwlMiA7IGpyYSAyZlxuXHQiCiAgICAgICAgICAgICIx OiBsc3JsICAgIzEsJTMgOyBqY2MgMmZcblx0IgogICAgICAgICAgICAgICAibW92ZXcgICUxQC0s JTBALSAgOyBzdWJxdyAgIzIsJTJcblx0IgogICAgICAgICAgICAiMjogbW92ZXcgJTIsJS07IGxz cmwgIzIsJTIgOyBqZXEgNmZcblx0IgogICAgICAgICAgICAgICAibHNybCAgICMxLCUyIDsgamNj IDNmIDsgbW92ZWwgJTFALSwlMEAtXG5cdCIKICAgICAgICAgICAgIjM6IGxzcmwgICAjMSwlMiA7 IGpjYyA0ZiA7IG1vdmVsICUxQC0sJTBALSA7IG1vdmVsICUxQC0sJTBALVxuXHQiCiAgICAgICAg ICAgICI0OiBzdWJxbCAgIzEsJTIgOyBqY3MgNmZcblx0IgogICAgICAgICAgICAiNTogbW92ZWwg JTFALSwlMEAtO21vdmVsICUxQC0sJTBALVxuXHQiCiAgICAgICAgICAgICAgICJtb3ZlbCAlMUAt LCUwQC07bW92ZWwgJTFALSwlMEAtXG5cdCIKICAgICAgICAgICAgICAgImRicmEgJTIsNWIgOyBj bHJ3ICUyOyBzdWJxbCAjMSwlMjsgamNjIDViXG5cdCIKICAgICAgICAgICAgIjY6IG1vdmV3ICUr LCUyOyBidHN0ICMxLCUyIDsgamVxIDdmIDsgbW92ZXcgJTFALSwlMEAtXG5cdCIKICAgICAgICAg ICAgIjc6ICAgICAgICAgICAgICA7IGJ0c3QgIzAsJTIgOyBqZXEgOGYgOyBtb3ZlYiAlMUAtLCUw QC1cblx0IgogICAgICAgICAgICAiODoiCiAgICAgICAgICAgICAgIDogIj1hIiAoZCksICI9YSIg KHMpLCAiPWQiIChjb3VudCksICI9ZCIgKHRtcCkKICAgICAgICAgICAgICAgOiAiMCIgKChjaGFy ICopIGQgKyBjb3VudCksICIxIiAoKGNoYXIgKikgcyArIGNvdW50KSwgIjIiIChjb3VudCkKICAg ICAgICApOwogICAgICB9CiAgIH0KCiAgIHJldHVybigwKTsKfQoKCi8qICsrYW5kcmVhczogU2lt cGxlIGFuZCBmYXN0IHZlcnNpb24gb2YgbWVtbW92ZSwgYXNzdW1lcyBzaXplIGlzCiAgIGRpdmlz aWJsZSBieSAxNiwgc3VpdGFibGUgZm9yIG1vdmluZyB0aGUgd2hvbGUgc2NyZWVuIGJpdHBsYW5l ICovCnN0YXRpYyBfX2lubGluZV9fIHZvaWQgZmFzdF9tZW1tb3ZlKGNoYXIgKmRzdCwgY29uc3Qg Y2hhciAqc3JjLCBzaXplX3Qgc2l6ZSkKewogIGlmICghc2l6ZSkKICAgIHJldHVybjsKICBpZiAo ZHN0IDwgc3JjKQogICAgX19hc21fXyBfX3ZvbGF0aWxlX18KICAgICAgKCIxOiIKICAgICAgICIg IG1vdmVtbCAlMEArLCUvZDAvJS9kMS8lL2EwLyUvYTFcbiIKICAgICAgICIgIG1vdmVtbCAlL2Qw LyUvZDEvJS9hMC8lL2ExLCUxQFxuIgogICAgICAgIiAgYWRkcWwgIzgsJTE7IGFkZHFsICM4LCUx XG4iCiAgICAgICAiICBkYnJhICUyLDFiXG4iCiAgICAgICAiICBjbHJ3ICUyOyBzdWJxbCAjMSwl MlxuIgogICAgICAgIiAgamNjIDFiIgogICAgICAgOiAiPWEiIChzcmMpLCAiPWEiIChkc3QpLCAi PWQiIChzaXplKQogICAgICAgOiAiMCIgKHNyYyksICIxIiAoZHN0KSwgIjIiIChzaXplIC8gMTYg LSAxKQogICAgICAgOiAiZDAiLCAiZDEiLCAiYTAiLCAiYTEiLCAibWVtb3J5Iik7CiAgZWxzZQog ICAgX19hc21fXyBfX3ZvbGF0aWxlX18KICAgICAgKCIxOiIKICAgICAgICIgIHN1YnFsICM4LCUw OyBzdWJxbCAjOCwlMFxuIgogICAgICAgIiAgbW92ZW1sICUwQCwlL2QwLyUvZDEvJS9hMC8lL2Ex XG4iCiAgICAgICAiICBtb3ZlbWwgJS9kMC8lL2QxLyUvYTAvJS9hMSwlMUAtXG4iCiAgICAgICAi ICBkYnJhICUyLDFiXG4iCiAgICAgICAiICBjbHJ3ICUyOyBzdWJxbCAjMSwlMlxuIgogICAgICAg IiAgamNjIDFiIgogICAgICAgOiAiPWEiIChzcmMpLCAiPWEiIChkc3QpLCAiPWQiIChzaXplKQog ICAgICAgOiAiMCIgKHNyYyArIHNpemUpLCAiMSIgKGRzdCArIHNpemUpLCAiMiIgKHNpemUgLyAx NiAtIDEpCiAgICAgICA6ICJkMCIsICJkMSIsICJhMCIsICJhMSIsICJtZW1vcnkiKTsKfQoKI2Vs aWYgZGVmaW5lZChDT05GSUdfU1VONCkKCi8qIFlvdSBtYXkgdGhpbmsgdGhhdCBJJ20gY3Jhenkg YW5kIHRoYXQgSSBzaG91bGQgdXNlIGdlbmVyaWMKICAgcm91dGluZXMuICBObywgSSdtIG5vdDog c3VuNCdzIGZyYW1lYnVmZmVyIGNyYXNoZXMgaWYgd2Ugc3RkCiAgIGludG8gaXQsIHNvIHdlIGNh bm5vdCB1c2UgbWVtc2V0LiAgKi8KCnN0YXRpYyBfX2lubGluZV9fIHZvaWQgKnN1bjRfbWVtc2V0 KHZvaWQgKnMsIGNoYXIgdmFsLCBzaXplX3QgY291bnQpCnsKICAgIGludCBpOwogICAgZm9yKGk9 MDsgaTxjb3VudDtpKyspCiAgICAgICAgKChjaGFyICopIHMpIFtpXSA9IHZhbDsKICAgIHJldHVy biBzOwp9CgpzdGF0aWMgX19pbmxpbmVfXyB2b2lkICphc21fbWVtc2V0KHZvaWQgKnMsIHNpemVf dCBjb3VudCkKewogICAgcmV0dXJuIHN1bjRfbWVtc2V0KHMsIDI1NSwgY291bnQpOwp9CgpzdGF0 aWMgX19pbmxpbmVfXyB2b2lkICphc21fbWVtY2xlYXIodm9pZCAqcywgc2l6ZV90IGNvdW50KQp7 CiAgICByZXR1cm4gc3VuNF9tZW1zZXQocywgMCwgY291bnQpOwp9CgpzdGF0aWMgX19pbmxpbmVf XyB2b2lkICphc21fbWVtY2xlYXJfc21hbGwodm9pZCAqcywgc2l6ZV90IGNvdW50KQp7CiAgICBy ZXR1cm4gc3VuNF9tZW1zZXQocywgMCwgY291bnQpOwp9CgovKiBUbyBiZSBob25lc3QsIHRoaXMg aXMgc2xvd19tZW1tb3ZlIDopLiBCdXQgc3VuNCBpcyBjcmFwcHksIHNvIHdoYXQgd2UgY2FuIGRv LiAqLwpzdGF0aWMgX19pbmxpbmVfXyB2b2lkIGZhc3RfbWVtbW92ZSh2b2lkICpkLCBjb25zdCB2 b2lkICpzLCBzaXplX3QgY291bnQpCnsKICAgIGludCBpOwogICAgaWYgKGQ8cykgewoJZm9yIChp PTA7IGk8Y291bnQ7IGkrKykKCSAgICAoKGNoYXIgKikgZClbaV0gPSAoKGNoYXIgKikgcylbaV07 CiAgICB9IGVsc2UKCWZvciAoaT0wOyBpPGNvdW50OyBpKyspCgkgICAgKChjaGFyICopIGQpW2Nv dW50LWktMV0gPSAoKGNoYXIgKikgcylbY291bnQtaS0xXTsKfQoKc3RhdGljIF9faW5saW5lX18g dm9pZCAqYXNtX21lbW1vdmUoY2hhciAqZHN0LCBjb25zdCBjaGFyICpzcmMsIHNpemVfdCBzaXpl KQp7CiAgICBmYXN0X21lbW1vdmUoZHN0LCBzcmMsIHNpemUpOwogICAgcmV0dXJuIGRzdDsKfQoK I2Vsc2UKCnN0YXRpYyBfX2lubGluZV9fIHZvaWQgKmFzbV9tZW1jbGVhcl9zbWFsbCh2b2lkICpz LCBzaXplX3QgY291bnQpCnsKICAgIHJldHVybihtZW1zZXQocywgMCwgY291bnQpKTsKfQoKc3Rh dGljIF9faW5saW5lX18gdm9pZCAqYXNtX21lbWNsZWFyKHZvaWQgKnMsIHNpemVfdCBjb3VudCkK ewogICAgcmV0dXJuKG1lbXNldChzLCAwLCBjb3VudCkpOwp9CgpzdGF0aWMgX19pbmxpbmVfXyB2 b2lkICphc21fbWVtc2V0KHZvaWQgKnMsIHNpemVfdCBjb3VudCkKewogICAgcmV0dXJuKG1lbXNl dChzLCAyNTUsIGNvdW50KSk7Cn0KCiNpZiBkZWZpbmVkKF9faTM4Nl9fKQoKc3RhdGljIF9faW5s aW5lX18gdm9pZCBmYXN0X21lbW1vdmUodm9pZCAqZCwgY29uc3Qgdm9pZCAqcywgc2l6ZV90IGNv dW50KQp7CiAgaW50IGQwLCBkMSwgZDIsIGQzOwogICAgaWYgKGQgPCBzKSB7Cl9fYXNtX18gX192 b2xhdGlsZV9fICgKCSJjbGRcblx0IgoJInNocmwgJDEsJSVlY3hcblx0IgoJImpuYyAxZlxuXHQi CgkibW92c2JcbiIKCSIxOlx0c2hybCAkMSwlJWVjeFxuXHQiCgkiam5jIDJmXG5cdCIKCSJtb3Zz d1xuIgoJIjI6XHRyZXBcblx0IgoJIm1vdnNsIgoJOiAiPSZjIiAoZDApLCAiPSZEIiAoZDEpLCAi PSZTIiAoZDIpCgk6IjAiKGNvdW50KSwiMSIoKGxvbmcpZCksIjIiKChsb25nKXMpCgk6Im1lbW9y eSIpOwogICAgfSBlbHNlIHsKX19hc21fXyBfX3ZvbGF0aWxlX18gKAoJInN0ZFxuXHQiCgkic2hy bCAkMSwlJWVjeFxuXHQiCgkiam5jIDFmXG5cdCIKCSJtb3ZiIDMoJSVlc2kpLCUlYWxcblx0IgoJ Im1vdmIgJSVhbCwzKCUlZWRpKVxuXHQiCgkiZGVjbCAlJWVzaVxuXHQiCgkiZGVjbCAlJWVkaVxu IgoJIjE6XHRzaHJsICQxLCUlZWN4XG5cdCIKCSJqbmMgMmZcblx0IgoJIm1vdncgMiglJWVzaSks JSVheFxuXHQiCgkibW92dyAlJWF4LDIoJSVlZGkpXG5cdCIKCSJkZWNsICUlZXNpXG5cdCIKCSJk ZWNsICUlZWRpXG5cdCIKCSJkZWNsICUlZXNpXG5cdCIKCSJkZWNsICUlZWRpXG4iCgkiMjpcdHJl cFxuXHQiCgkibW92c2xcblx0IgoJImNsZCIKCTogIj0mYyIgKGQwKSwgIj0mRCIgKGQxKSwgIj0m UyIgKGQyKSwgIj0mYSIgKGQzKQoJOiIwIihjb3VudCksIjEiKGNvdW50LTQrKGxvbmcpZCksIjIi KGNvdW50LTQrKGxvbmcpcykKCToibWVtb3J5Iik7CiAgICB9Cn0KCnN0YXRpYyBfX2lubGluZV9f IHZvaWQgKmFzbV9tZW1tb3ZlKGNoYXIgKmRzdCwgY29uc3QgY2hhciAqc3JjLCBzaXplX3Qgc2l6 ZSkKewogICAgZmFzdF9tZW1tb3ZlKGRzdCwgc3JjLCBzaXplKTsKICAgIHJldHVybiBkc3Q7Cn0K CiNlbHNlIC8qICFpMzg2ICovCgogICAgLyoKICAgICAqICBBbnlvbmUgd2hvJ2QgbGlrZSB0byB3 cml0ZSBhc20gZnVuY3Rpb25zIGZvciBvdGhlciBDUFVzPwogICAgICogICAoV2h5IGFyZSB0aGVz ZSBmdW5jdGlvbnMgYmV0dGVyIHRoYW4gdGhvc2UgZnJvbSBpbmNsdWRlL2FzbS9zdHJpbmcuaD8p CiAgICAgKi8KCnN0YXRpYyBfX2lubGluZV9fIHZvaWQgKmFzbV9tZW1tb3ZlKHZvaWQgKmQsIGNv bnN0IHZvaWQgKnMsIHNpemVfdCBjb3VudCkKewogICAgcmV0dXJuKG1lbW1vdmUoZCwgcywgY291 bnQpKTsKfQoKc3RhdGljIF9faW5saW5lX18gdm9pZCBmYXN0X21lbW1vdmUoY2hhciAqZHN0LCBj b25zdCBjaGFyICpzcmMsIHNpemVfdCBzaXplKQp7CiAgICBtZW1tb3ZlKGRzdCwgc3JjLCBzaXpl KTsKfQoKI2VuZGlmIC8qICFpMzg2ICovCgojZW5kaWYKCiNlbmRpZgo= --Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD-- From ggi-develop-request@eskimo.com Sun Jun 27 17:48:27 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA14932 for ; Sun, 27 Jun 1999 17:48:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA32435; Sun, 27 Jun 1999 14:37:00 -0700 Resent-Date: Sun, 27 Jun 1999 14:37:00 -0700 Sender: marcus@e.kth.se Message-ID: <3776996C.3EAE9A42@stacken.kth.se> Date: Sun, 27 Jun 1999 21:36:44 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: ClanMarks on BeOS, Linux, Windows References: <37765FF0.24DD9498@stacken.kth.se> <99062720212001.01220@master> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"6xWBh3.0.bw7.wbfTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13553 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Denis Oliver Kropp wrote: > > I can't find any references to BeOS neither in ClanLib CVS or at > > your web-pages. Where is the code for that? > > On my harddrive ;-) very unstable for now. > Will possibly merge into ClanLib 0.1.17 Ok, I was mostly interrested to know what fill_rect does anyway. > > How is fill_rect implemented in ClanLib'ss BeOS code? > > ClanLib gets a hook function from the driver once: > > typedef long (*fill16_hook)(long,long,long,long,uint16); > fill_rect16 = (fill16_hook)cardHookAt(13); > > fill_rect() does: > > fill_rect16( crect.m_x1, crect.m_y1, crect.m_x2, crect.m_y2, pixelcolor ); > > instead of: > > ggiSetGCForeground( vis, pixelcolor ); > ggiDrawBox( vis, crect.m_x1, crect.m_y1, crect.m_x2 - crect.m_x1, crect.m_y2 - crect.m_y1 ); Strange that there should be a difference there. Even on my P233 I have no problem suturating my Millennium II card's accel engine with LibGGI's DrawBox. Hmmm, I'm noticing now that if you do subsequent rectangle fills and the LibGGI code is aware of that you can get away with 3 entries/box in the accel FIFO instead of 4. Maybe that's what BeOS does. I'll try this out and see if it makes any difference. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sun Jun 27 17:51:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA14962 for ; Sun, 27 Jun 1999 17:51:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA00387; Sun, 27 Jun 1999 14:40:13 -0700 Resent-Date: Sun, 27 Jun 1999 14:40:13 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: bedevtalk@be.com, clanlib@dark.x.dtu.dk, ggi-develop@eskimo.com Subject: Flickering solved? Date: Sun, 27 Jun 1999 23:36:30 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99062723422000.00231@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"RO7xy1.0.o5.xefTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13554 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, I just did the WaitForRetrace() AFTER the MoveDisplayArea() and it runs absolutely flicker free! With "full" framerate at 72 (the vertical refresh). Any comments on this behaviour? Maybe it waits for retrace, draws everything within the retrace and flips, no... When framerate is at ~60 there is still no flickering. mmh, anyway, this will be the last e-mail from me, I will hang me on the tree...no no ;-) -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Sun Jun 27 17:53:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA14980 for ; Sun, 27 Jun 1999 17:53:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA00975; Sun, 27 Jun 1999 14:42:20 -0700 Resent-Date: Sun, 27 Jun 1999 14:42:20 -0700 Date: Sun, 27 Jun 1999 23:42:10 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: ggi acting up solved Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"7jD6G1.0.qE.vgfTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13555 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi. Remember I was having trouble with GGI hanging my terminal when I used GGI_DEBUG=255? Well, that was because I had recompiled libggi after I installed RH6, but not libgii, which I had compiled on RH5.2...:) Now everything works fine again. Now there are 2 things I was wondering about: 1) When I run 'demo' on my VoodooII, I get very good rates compared to fbdev (MilleniumI), but the CopyBox() took 4 seconds, veeery slow. What is CopyBox() anyway? 2) I've been trying to get XGGI to run on my VoodooII, but this won't work, cos the glide target doesn't support DirectBuffer. Does that mean I can never run XGGI on it? I really don't know what DirectBuffering is, so pardon the (perhaps) stupid question :) Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Sun Jun 27 18:14:34 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA15240 for ; Sun, 27 Jun 1999 18:14:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA05258; Sun, 27 Jun 1999 15:02:32 -0700 Resent-Date: Sun, 27 Jun 1999 15:02:32 -0700 Sender: marcus@e.kth.se Message-ID: <37769F68.F37ABB9@stacken.kth.se> Date: Sun, 27 Jun 1999 22:02:16 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.6 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"SCdui.0.pH1.izfTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13556 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn wrote: > Now there are 2 things I was wondering about: > 1) When I run 'demo' on my VoodooII, I get very good rates compared to > fbdev (MilleniumI), but the CopyBox() took 4 seconds, veeery slow. What is > CopyBox() anyway? CopyBox is screen-screen-blit, which Glide doesn't support in hardware. > 2) I've been trying to get XGGI to run on my VoodooII, but this won't > work, cos the glide target doesn't support DirectBuffer. Does that mean I > can never run XGGI on it? I really don't know what DirectBuffering is, so > pardon the (perhaps) stupid question :) DirectBuffer means direct access to the framebuffer. This is only supported for the Glide target in recent snapshots. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Sun Jun 27 18:29:07 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA15455 for ; Sun, 27 Jun 1999 18:29:06 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA08056; Sun, 27 Jun 1999 15:17:34 -0700 Resent-Date: Sun, 27 Jun 1999 15:17:34 -0700 Date: Mon, 28 Jun 1999 00:17:25 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved In-Reply-To: <37769F68.F37ABB9@stacken.kth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"49yvR.0.iz1.zBgTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13557 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Sun, 27 Jun 1999, Marcus Sundberg wrote: > DirectBuffer means direct access to the framebuffer. This is only > supported for the Glide target in recent snapshots. In ggi, xggi or glide? :) Just wondering which one I'm looking forward to downloading :) Also, I was wondering about a few other things... Can only root use the glide target? What about /dev/3dfx? I have it, but demos core dump(!) when I try to run them as me. And, I wanted to use my dual screen setup for _something_, so I decided to try to make it look a little impressive(?) by running a demo on the VoodooII. When I try in X, a window pops up and nothing happens before I move the pointer into this window. Then the window places itselt at the top left corner of the screen, and steals my mouse and keyboard until i quit the demo (I tried flying_ggis and stars). When I run a demo from the console, my second screen is blanked when I change consoles. The variable concerning this in targets.txt is GGI_GLIDE_HALTONSWITCH, which does what is happening now. Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Mon Jun 28 04:03:47 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA25290 for ; Mon, 28 Jun 1999 04:03:46 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id AAA23994; Mon, 28 Jun 1999 00:51:10 -0700 Resent-Date: Mon, 28 Jun 1999 00:51:10 -0700 From: Steffen Seeger Message-Id: <199906280750.JAA07133@demonti.physik.tu-chemnitz.de> Subject: Re: still KGI 0.9 ... In-Reply-To: <3773A4C6.72AAC4FF@easter-eggs.fr> from Julien Tayon at "Jun 25, 99 05:48:22 pm" To: ggi-develop@eskimo.com Date: Mon, 28 Jun 1999 09:50:31 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"famzn.0.fs5.hboTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13558 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > Does it work with a plain 2.2.[2,4]? > > What's your setup exactly? > > I used both 2.2.2 and 2.2.4 kernel, here is one of the config > file that worked and a shortened version of the kernel messages > > Detected PS/2 Mouse Port. ... > eth0: Intel EtherExpress Pro 10/100 at 0xb800, 00:E0:18:98:9E:47, IRQ 12. the PS/2 mouse port uses IRQ 12 as well. Do both work under plain 2.2.x? (If not, try to exclude IRQ 12 from assignment to PCI slots marking it 'used by ISA/legacy card' in the BIOS/PCI and PnP Setup. Steffen PS: Please discuss KGI-0.9 related issues at ggi-kgi@kludge.org. Thanks. ----------------- e-mail: seeger@physik.tu-chemnitz.de ----------------- From ggi-develop-request@eskimo.com Mon Jun 28 04:48:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA26085 for ; Mon, 28 Jun 1999 04:48:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA31366; Mon, 28 Jun 1999 01:35:16 -0700 Resent-Date: Mon, 28 Jun 1999 01:35:16 -0700 From: Denis Oliver Kropp Organization: Fischlustig To: clanlib@dark.x.dtu.dk, ggi-develop@eskimo.com Subject: TNT benchmark Date: Mon, 28 Jun 1999 10:31:54 +0200 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99062810363100.00267@master> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"FuMza.0.lf7.2FpTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13559 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Hi, I ran the same tests except that the card is a TNT now. BeOS ----------------- fill_rect 25905 hw fill_rect alpha 82 put_screen 21881 Linux FBDev ----------------- fill_rect 1878 fill_rect alpha 83 put_screen 21228 Linux GGI/FBDev ----------------- fill_rect 2749 fill_rect alpha 89 put_screen 21261 Windows DirectX ----------------- fill_rect 23825 hw fill_rect alpha 97 put_screen 229907 hw (no typo) This means that libGGI should use the TNT in FBDev ;-) ClanBomber ran with 158fps on all targets except windows, because of the retrace. -- Denis Oliver Kropp (dok) + Fischlustig + ClanBomber, the kick ass game that uses kick ass Clanlib. www.fischlustig.de/clanbomber www.clanlib.org Justice, n.: A decision in your favor. From ggi-develop-request@eskimo.com Mon Jun 28 05:14:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA26344 for ; Mon, 28 Jun 1999 05:14:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA07454; Mon, 28 Jun 1999 02:01:41 -0700 Resent-Date: Mon, 28 Jun 1999 02:01:41 -0700 Date: Mon, 28 Jun 1999 11:01:34 +0200 (CEST) From: Jos Hulzink To: ggi-develop@eskimo.com Subject: Accelleration (Was: Re: TNT benchmark) In-Reply-To: <99062810363100.00267@master> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"pJBOg2.0.Jq1.qdpTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13560 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Mon, 28 Jun 1999, Denis Oliver Kropp wrote: > Hi, > > I ran the same tests except that the card is a TNT now. > Cool, running benchmarks on unaccellerated drivers and comparing them with Direct X... The only KGICON drivers that support accelleration AFAIK are the Matrox drivers and the S3 ViRGE drivers on my machine :) In one thing Linus is right: Some parts of the GGI project have no clear goal. In my eyes, there has been no good thinking about the accelleration of drivers. I'm implementing 3D accelleration for the ViRGE now, but to get this working, I have to hack libggi. I thought the idea of a driver was that software doesn't have to deal with driver-specific code anymore ? I have to recompile libggi if I change from the nvriva driver to the S3 virge driver... Nice... :( Jos Hulzink p.s.: ViRGE driver update in a few days. It is cool and should work not only for ViRGE DX. Accellerated screen to screen copy etc... From ggi-develop-request@eskimo.com Mon Jun 28 05:29:11 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA26491 for ; Mon, 28 Jun 1999 05:29:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA09196; Mon, 28 Jun 1999 02:17:29 -0700 Resent-Date: Mon, 28 Jun 1999 02:17:29 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990628110028.A496@rz.uni-duesseldorf.de> Date: Mon, 28 Jun 1999 11:00:28 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved Mail-Followup-To: ggi-develop@eskimo.com References: <37769F68.F37ABB9@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Ketil Froyn on Mon, Jun 28, 1999 at 12:17:25AM +0200 Resent-Message-ID: <"xVK8Z1.0.XF2.espTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13561 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > DirectBuffer means direct access to the framebuffer. This is only > > supported for the Glide target in recent snapshots. > In ggi, xggi or glide? :) Just wondering which one I'm looking forward to > downloading :) GGI. IIRC you already are using Beta2.1 or newer, so xggi should be fine. And AFAIk Glide was always up to that. Note, that the VooDoos are not quite optimized for DB access. > Also, I was wondering about a few other things... Can only root use the > glide target? What about /dev/3dfx? I have it, but demos core dump(!) when > I try to run them as me. That's strange. This could be a problem with VT-switching or needing root-access to use the keyboard. Could you run the core file through a debugger to see where it dumps ? And/or make GGI_DEBUG=255 logs and strace logs ? CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 28 05:29:36 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA26498 for ; Mon, 28 Jun 1999 05:29:35 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA09237; Mon, 28 Jun 1999 02:17:36 -0700 Resent-Date: Mon, 28 Jun 1999 02:17:36 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990628112002.C496@rz.uni-duesseldorf.de> Date: Mon, 28 Jun 1999 11:20:02 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Flickering solved? Mail-Followup-To: ggi-develop@eskimo.com References: <99062723422000.00231@master> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99062723422000.00231@master>; from Denis Oliver Kropp on Sun, Jun 27, 1999 at 11:36:30PM +0200 Resent-Message-ID: <"ViVRY2.0.6G2.lspTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13562 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I just did the WaitForRetrace() AFTER the MoveDisplayArea() > and it runs absolutely flicker free! With "full" framerate at 72 (the vertical refresh). > > Any comments on this behaviour? This is a problem connected to the HW-implementation of frameflipping. There are two common implementations: 1. The change of the visible frame goes into effect immediately. This happens, if e.g. the card recalculates its offset every line based on the global offset. 2. The change gets delayed until the start of the next frame. This happens if the card only reloads its offset register once at frame start and then counts. This leads to two kinds of flicker, depending on the ordering of drawing commands and WaitForRetrace: 1. Drawing-flicker. In case 1. you would have to draw,waitretrace,flip. If you do draw,flip,waitretrace, you will see the inactive frame between flip and waitretrace. This typically flickers. Either due to the point at which the second frame goes into effect changing, which leads to a "jumping line" in the picture or if you already draw on the inactive frame due to the drawing operations being visible. 2. Flipping-flicker. In case 2. you have to use draw,flip,waitretrace. If you use the other method, you might miss the point at which the chip reads out the offset register (thus getting a contraproductive effect - you always [or occasionally, depends on timing] see the wrong frame). We need to abstract that feature finally. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 28 05:31:21 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA26512 for ; Mon, 28 Jun 1999 05:31:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA09270; Mon, 28 Jun 1999 02:17:41 -0700 Resent-Date: Mon, 28 Jun 1999 02:17:41 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990628110251.B496@rz.uni-duesseldorf.de> Date: Mon, 28 Jun 1999 11:02:51 +0200 From: Andreas Beck To: #!/usr/bin/entropy --why-me Cc: mailing list GGI Subject: Re: Frames in SVGA Mail-Followup-To: #!/usr/bin/entropy --why-me , mailing list GGI References: <199906280206.WAA13968@csmctmto.interpoint.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <199906280206.WAA13968@csmctmto.interpoint.net>; from #!/usr/bin/entropy --why-me on Sun, Jun 27, 1999 at 10:06:07PM -0400 Resent-Message-ID: <"hZZLr2.0.gG2.pspTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13563 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I am trying to set ggi_mode.frames to 2 using display-svga. Is it > possible to havce multiple frames when using svga under linux? I am also > having problems with display-memory. When I write to display memory then > cross blit to display-vga it doesn't seem to work well. Sorry, I don't know much about the SVGA target, as I can't use it (won't work). I've forwarded your request to the mailing list. Hope the folks there remember to CC you on answers. Otherwise please check the ML archives, which are on http://www.ggi-project.org/ . CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 28 05:51:50 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id FAA26702 for ; Mon, 28 Jun 1999 05:51:49 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id CAA10889; Mon, 28 Jun 1999 02:38:40 -0700 Resent-Date: Mon, 28 Jun 1999 02:38:40 -0700 Date: Mon, 28 Jun 1999 11:38:34 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved In-Reply-To: <19990628110028.A496@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"uPdgB3.0.uf2.VAqTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13564 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Mon, 28 Jun 1999, Andreas Beck wrote: > > > DirectBuffer means direct access to the framebuffer. This is only > > > supported for the Glide target in recent snapshots. > > In ggi, xggi or glide? :) Just wondering which one I'm looking forward to > > downloading :) > GGI. IIRC you already are using Beta2.1 or newer, so xggi should be fine. > And AFAIk Glide was always up to that. You recalled correctly. But does that mean that I should be able to run xggi on the glide target? Cos xggi dies and complains that it can't access the framebuffer (or something like that, it is a framebuffer thing). > Note, that the VooDoos are not quite optimized for DB access. The hardware or glide or ggi? :) > > Also, I was wondering about a few other things... Can only root use the > > glide target? What about /dev/3dfx? I have it, but demos core dump(!) when > > I try to run them as me. > That's strange. This could be a problem with VT-switching or needing > root-access to use the keyboard. Could you run the core file through a > debugger to see where it dumps ? And/or make GGI_DEBUG=255 logs and strace > logs ? I'll have a look at it. BTW, is there some way to run quake fullscreen using GGI? I've tried squake, but that seems to be hardcoded to use the libc-version of libvga.so.1... Symlinking did not remedy this. Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Mon Jun 28 08:24:34 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA28177 for ; Mon, 28 Jun 1999 08:24:33 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA06826; Mon, 28 Jun 1999 05:14:50 -0700 Resent-Date: Mon, 28 Jun 1999 05:14:50 -0700 Date: Mon, 28 Jun 1999 08:14:41 -0400 (EDT) From: Billy Biggs To: ggi-develop@eskimo.com Subject: Release request Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vektor@dhp.com Resent-Message-ID: <"QcQj71.0.Og1.rSsTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13565 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com GGIers, I'd like to request that the GGI userspace graphics library please be released. I've gone again through the lets-try-to-find-a-decent-game library[1] routine again and once again determined that the only lib out there worthwhile for designing fullscreen games in the *NIX world is to write my own API on top of GGI directly. It seems to me that you guys are awful busy hacking KGI and stuff and forgetting that you're sitting on an awesome library for writing games on top of existing crap like DGA or xshm. Hell, we were writing demos on top of GGI last summer and it was working well enough, and now a year later we still don't have a stable release. I mean, I'd understand if my GGI apps were crashing left right and center, but quite frankly, I've never seen a bad GGI bug yet, at least not for the (very simple) stuff we've been trying to do with it. All we want to do is write a game. That said, here are some other problems we've had, maybe you guys could give me some advice: 1) The hwcursor seems to stick on the screen sometimes when I switch to DGA mode. I just started experiencing that recently, only with GGI programs, but possibly just out of luck. I tried doing an ugly hack to set the cursor myself, but GGI has no display-dependant code to give me, say, its X Display variable (shouldn't there be?). 2) Timing code has been a total bitch, partly because it appears that GGI uses setitimer using ITIMER_PROF, which fucks up all kinds of timing stuff. Is there any way of doing frame-rate limiting code portably? 3) Could someone maybe write a small tutorial on getting mouse input, especially in the context of DGA games? I haven't looked into this in detail, but grepping for 'mouse' in the docs gave surprisingly little hints on doing this at all. 4) Is there no way to do faster blits or let me myself have more control of video memory, especially when we're drawing to a display like DGA that does give reasonably direct access? 5) Any advice on syncing to refreshes? I've found it basically impossible, but I thought I'd ask anyways. Thanks, Billy Biggs vektor@div8.net [1] A worthy game library being: - one with a minimal API so I can do my own blit routines etc - one that doesn't require users to install strange libraries named after greek gods and related garb like mikmod - one that lets me do fullscreen games properly From ggi-develop-request@eskimo.com Mon Jun 28 20:07:30 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id UAA08694 for ; Mon, 28 Jun 1999 20:07:29 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id QAA12390; Mon, 28 Jun 1999 16:55:02 -0700 Resent-Date: Mon, 28 Jun 1999 16:55:02 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Portablility using printf Date: Mon, 28 Jun 1999 19:50:00 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99062819545700.04486@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"keKAQ1.0.G13.Ij0Ut"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13575 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Right now Im using printf to print to the background console that the GGI program was started in. Now Ive only done this in X and was wondering if there were any other targets that would not have a console running in the background that the printf's would output too. For example when I load a TGA and its in a bad format, I just print an error using printf and it comes up in a console that I can read behind the GGI app. Now is this bad if it gets ported to another target? -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Mon Jun 28 22:34:05 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA10590 for ; Mon, 28 Jun 1999 22:34:04 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA28491; Mon, 28 Jun 1999 19:19:37 -0700 Resent-Date: Mon, 28 Jun 1999 19:19:37 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990629031706.A2321@rz.uni-duesseldorf.de> Date: Tue, 29 Jun 1999 03:17:06 +0200 From: Andreas Beck To: mongoose@wpi.edu, mailing list GGI Cc: steve@ggi-project.org Subject: Re: Setting frame amounts Mail-Followup-To: mongoose@wpi.edu, mailing list GGI , steve@ggi-project.org References: <99062816472000.02626@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99062816472000.02626@mongoose>; from Garrett B on Mon, Jun 28, 1999 at 04:41:27PM -0500 Resent-Message-ID: <"me2nU.0.ux6.sq2Ut"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13576 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > If you call ggiSetMode and set the number of frames in the mode struct to 2, > will ggi return an error if it can only create one frame? or will it just > create the one frame and continue? You should not call SetMode without a prior positive response from Checkmode. But to answer your question by citing the manpage : For both ggiSetMode and ggiCheckMode, normal mode negotia- tion is performed, and if the given mode is not possible, modifications will be made to the passed structure to make it work. If GGI_AUTO (or GT_AUTO for the graphtype) is specified for any of the members of *tm, these are filled in with the ** Steve - something is missing here ... "appropriate values" ? ** Oh - I see the manpage source has "'recommended' parameters." ** there. Looks like this gets misdisplayed. Please fix. For ggiSetMode, if the mode cannot be set, a mode is sug- gested in *tm, but it will not be silently set. However, ** I think that answers your question. you'll probably want to use the convenience functions ggiSetTextMode and ggiSetGraphMode instead of ggiSetMode. > Also assuming it will fail if it only returns one frame, is there any > need to call ggiDBGetNumBuffers(vis) ? Because won't there always be a vis 0 > and 1? Note that the number of DirectBuffers has _nothing_ to do with the number of frames. A Directbuffer can contain pretty much anything, and you should always loop through all of them to find the one you are looking for. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Mon Jun 28 23:06:51 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA05956 for ; Mon, 28 Jun 1999 13:39:26 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA22107; Mon, 28 Jun 1999 10:25:58 -0700 Resent-Date: Mon, 28 Jun 1999 10:25:58 -0700 Date: Mon, 28 Jun 1999 13:25:53 -0400 (EDT) From: Billy Biggs To: ggi-develop@eskimo.com Subject: Re: Release request In-Reply-To: <19990628173643.B538@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vektor@dhp.com Resent-Message-ID: <"88wbj1.0.3P5.b0xTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13567 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Mon, 28 Jun 1999, Andreas Beck wrote: > > I'd like to request that the GGI userspace graphics library please be > > released. > > We are checking some minor issues. Maybe we are a bit too perfectionistic, > but actually where is the problem ? > > The Betas are pretty much as good as what others would call a release. > > > of GGI last summer and it was working well enough, and now a year later we > > still don't have a stable release. > > It's probably a matter of what one calls stable. I think The LibGGI Betas > are as stable as what others would call final release with fixpacks 1-5 > applied :-). Well, the main issue is getting the library installed in all the major Linux distributions. I'd also like a reasonable assurance that the API won't change significantly. I think I already have that assurance, but an official one would be nice. :) For example, friends of mine hesitate to install ggi because there isn't a stable version. This prevents me from releasing games. Ugh. Yes, this is somehow different from most other linux libraries. Like, please release something called, maybe, libggi-2.2 without the word 'beta' in there, and even if it still is a 'beta' release, more people will install it. Version it more like other linux software ? Mostly though, if I'm going to release a game, I'd like to have a stable library that users should already have installed. Thank you for your answers to my other questions, -- Billy Biggs bbiggs@div8.net From ggi-develop-request@eskimo.com Tue Jun 29 07:42:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA15641 for ; Tue, 29 Jun 1999 07:42:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA09917; Tue, 29 Jun 1999 04:28:56 -0700 Resent-Date: Tue, 29 Jun 1999 04:28:56 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990629131843.C534@rz.uni-duesseldorf.de> Date: Tue, 29 Jun 1999 13:18:43 +0200 From: Andreas Beck To: mongoose@wpi.edu Cc: mailing list GGI Subject: Re: Portablility using printf Mail-Followup-To: mongoose@wpi.edu, mailing list GGI References: <99062819545700.04486@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99062819545700.04486@mongoose>; from Garrett B on Mon, Jun 28, 1999 at 07:50:00PM -0500 Resent-Message-ID: <"fIyCZ.0.dQ2.rtAUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13578 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Right now Im using printf to print to the background console that the GGI > program was started in. Now Ive only done this in X and was wondering if > there were any other targets that would not have a console running in the > background that the printf's would output too. Well we can't destroy the filedescriptor of stdout, so there will usually always be a "somewhere" that such output is directed to. However this can have two possible side effects: 1. The output might be "eaten up" and never made visible, if not redirected. I don't know any such target yet, as Linux usually saves the background console. Other systems might differ. Redirecting it should help if you need the info. 2. The output might interfere with the graphical output. Try running a ggi demo on fbcon/kgicon when starting it from within mc. mc has it's shell attached through a pipe or something, so the tty cannot be put in "graphics mode" which initiates that "backgrounded console" behaviour. Again redirecting output helps. > For example when I load a TGA and its in a bad format, I just print an error > using printf and it comes up in a console that I can read behind the GGI app. > Now is this bad if it gets ported to another target? Well - if you can live with the 2 possible problems shown above, I'd say it's o.k. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 29 07:42:22 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA15640 for ; Tue, 29 Jun 1999 07:42:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA09915; Tue, 29 Jun 1999 04:28:56 -0700 Resent-Date: Tue, 29 Jun 1999 04:28:56 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990629131052.B534@rz.uni-duesseldorf.de> Date: Tue, 29 Jun 1999 13:10:52 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: XGGI & kdm Mail-Followup-To: ggi-develop@eskimo.com References: <3777FC76.465AD9EF@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <3777FC76.465AD9EF@fisicc-ufm.edu>; from Otto Solares on Mon, Jun 28, 1999 at 04:51:35PM -0600 Resent-Message-ID: <"xFF0n3.0.IQ2.ptAUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13577 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > Currently i have like 150 linux boxes for student > use at the internet labs and i found that XFree86 > have more overhead than XGGI so i decided to > install it (Currently i don't know if this observation > is wrong but i found XGGI faster in this 32Mb > boxes than any other X). Hmm - 32 MB ... that probably explains it. XGGI has a smaller memory footprint. Especially if the cards in the machines aren't heavily accelerated anyway, that will make XGGI faster. On machines with enough memory and heavy acceleration in the XFree server, I see a slowdown for font rendering which isn't acceled in XGGI right now. We are working on that. > The problem is that when > i start in runlevel 5 (is the default because we use > KDM for login purposes) X gives me an error: > display-fbdev: failed to open tty: Device not configured > L/vtswitch: open /dev/tty: Device not configured That's weird. That sounds like the TTY devices not being there ... ??? Can you enable debugging in GGI using GGI_DEBUG=255 and/or strace ? You might need to write a little script that wraps xdm for that. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 29 07:43:15 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA15653 for ; Tue, 29 Jun 1999 07:43:14 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA09983; Tue, 29 Jun 1999 04:29:05 -0700 Resent-Date: Tue, 29 Jun 1999 04:29:05 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990629133021.E534@rz.uni-duesseldorf.de> Date: Tue, 29 Jun 1999 13:30:21 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved Mail-Followup-To: ggi-develop@eskimo.com References: <19990628110028.A496@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Ketil Froyn on Mon, Jun 28, 1999 at 09:19:19PM +0200 Resent-Message-ID: <"b5lL03.0.kR2._tAUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13580 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > > Also, I was wondering about a few other things... Can only root use the > > > glide target? What about /dev/3dfx? I have it, but demos core dump(!) when > > > I try to run them as me. > > That's strange. This could be a problem with VT-switching or needing > > root-access to use the keyboard. Could you run the core file through a > > debugger to see where it dumps ? And/or make GGI_DEBUG=255 logs and strace > > logs ? > End of strace: > write(2, "LibGGI: ", 8LibGGI: ) = 8 > write(2, "GLIDE-lib starting\n", 19GLIDE-lib starting > ) = 19 Ah ... o.k. - located the code ... Great ... : /* YUCK! There's no way to determine if we are allowed to access the 3DFX hardware, and if we can't we get a segfault here. :-( */ grSstQueryBoards(&hwconf); > geteuid() = 500 > open("/dev/3dfx", > O_RDWR) = -1 ENOSYS (Function not implemented) > open("/dev/3dfx", O_RDWR) = -1 ENOSYS (Function not implemented) > open("/dev/3dfx", O_RDWR) = -1 ENODEV (No such device) > iopl(0x3) = -1 EPERM (Operation not permitted) > --- SIGSEGV (Segmentation fault) --- > +++ killed by SIGSEGV +++ So it happens exactly what is to be expected. It looks like the kernel driver doesn't let you in, and even if it would, calling iopl() will require root privs ... seems like you can't use Glide as non-root ... CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 29 07:44:41 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA15665 for ; Tue, 29 Jun 1999 07:44:41 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA09936; Tue, 29 Jun 1999 04:28:57 -0700 Resent-Date: Tue, 29 Jun 1999 04:28:57 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990629132348.D534@rz.uni-duesseldorf.de> Date: Tue, 29 Jun 1999 13:23:48 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved Mail-Followup-To: ggi-develop@eskimo.com References: <19990628110028.A496@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Ketil Froyn on Mon, Jun 28, 1999 at 11:38:34AM +0200 Resent-Message-ID: <"4Lds42.0.5R2.utAUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13579 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > > > DirectBuffer means direct access to the framebuffer. This is only > > > > supported for the Glide target in recent snapshots. > > > In ggi, xggi or glide? :) Just wondering which one I'm looking forward to > > > downloading :) > > GGI. IIRC you already are using Beta2.1 or newer, so xggi should be fine. > > And AFAIk Glide was always up to that. > You recalled correctly. But does that mean that I should be able to run > xggi on the glide target? After you updated LibGGI to a current snapshot I think. I don't have a Voodoo, so I can't check. Marcus ? > Cos xggi dies and complains that it can't access > the framebuffer (or something like that, it is a framebuffer thing). Yes. And if I got Marcus' reply correctly, I think that should now be solved. IIRC Marcus said something about having run XGGI on the glide target. At worst, one could probably emulate using the tile target, which can be told to emulate a DB. > > Note, that the VooDoos are not quite optimized for DB access. > The hardware or glide or ggi? :) The hardware. > BTW, is there some way to run quake fullscreen using GGI? I've tried > squake, but that seems to be hardcoded to use the libc-version of > libvga.so.1... Symlinking did not remedy this. You'd need to build a libc5 version of LibGGI and the SVGAlib wrapper. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 29 08:18:20 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA16007 for ; Tue, 29 Jun 1999 08:18:20 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA13979; Tue, 29 Jun 1999 04:52:44 -0700 Resent-Date: Tue, 29 Jun 1999 04:52:44 -0700 Date: Tue, 29 Jun 1999 13:52:35 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved In-Reply-To: <19990629132348.D534@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"JRXh-3.0.EQ3.BEBUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13581 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 29 Jun 1999, Andreas Beck wrote: > > BTW, is there some way to run quake fullscreen using GGI? I've tried > > squake, but that seems to be hardcoded to use the libc-version of > > libvga.so.1... Symlinking did not remedy this. > You'd need to build a libc5 version of LibGGI and the SVGAlib wrapper. Eeew... is this normal? Does everyone else do this? Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Tue Jun 29 08:43:52 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id IAA16230 for ; Tue, 29 Jun 1999 08:43:51 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id FAA24746; Tue, 29 Jun 1999 05:30:35 -0700 Resent-Date: Tue, 29 Jun 1999 05:30:35 -0700 Date: Tue, 29 Jun 1999 09:23:50 -0400 (EDT) From: "Brian S. Julin" To: ggi-develop@eskimo.com Subject: Re: XGGI & kdm In-Reply-To: <19990629131052.B534@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"6eO2x.0.R26.enBUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13582 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 29 Jun 1999, Andreas Beck wrote: > > display-fbdev: failed to open tty: Device not configured > > L/vtswitch: open /dev/tty: Device not configured > > That's weird. That sounds like the TTY devices not being there ... ??? This happened to me too. But it worked anyway, and I didn't have time to investigate. With me it was kernel v2.2.10, and I was running XGGI through /bin/open, so the output was on vc7 and XGGI on vc8. > Can you enable debugging in GGI using GGI_DEBUG=255 and/or strace ? Best to 2> /tmp/errs as the output will be huge and you won't have a scrollback buffer after switching back to the controlling VC. -- Brian From ggi-develop-request@eskimo.com Tue Jun 29 09:47:23 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id JAA17227 for ; Tue, 29 Jun 1999 09:47:22 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id GAA13026; Tue, 29 Jun 1999 06:30:56 -0700 Resent-Date: Tue, 29 Jun 1999 06:30:56 -0700 Date: Tue, 29 Jun 1999 15:30:49 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved In-Reply-To: <19990629133021.E534@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"zS2Zj3.0.NB3.FgCUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13583 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 29 Jun 1999, Andreas Beck wrote: > Ah ... o.k. - located the code ... Great ... : > > /* YUCK! There's no way to determine if we are allowed to access > the 3DFX hardware, and if we can't we get a segfault here. :-( > */ > grSstQueryBoards(&hwconf); > > So it happens exactly what is to be expected. It looks like the kernel > driver doesn't let you in, and even if it would, calling iopl() will require > root privs ... seems like you can't use Glide as non-root ... But that is the point of /dev/3dfx, no? I thought the deal was that with /dev/3dfx, you won't need the iopl(), so non-root users can use this... If not, what's even the point with /dev/3dfx? (Maybe I should ask 3dfx, not you, but I thought this was how it worked). BTW: I'm a little slow... can I run xggi on glide if I get the latest libggi snapshot? Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Tue Jun 29 11:10:41 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA05527 for ; Mon, 28 Jun 1999 13:21:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA13227; Mon, 28 Jun 1999 10:06:10 -0700 Resent-Date: Mon, 28 Jun 1999 10:06:10 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990628173643.B538@rz.uni-duesseldorf.de> Date: Mon, 28 Jun 1999 17:36:43 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Release request Mail-Followup-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Billy Biggs on Mon, Jun 28, 1999 at 08:14:41AM -0400 Resent-Message-ID: <"JUGeZ.0.QE3.0kwTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13566 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > I'd like to request that the GGI userspace graphics library please be > released. We are checking some minor issues. Maybe we are a bit too perfectionistic, but actually where is the problem ? The Betas are pretty much as good as what others would call a release. > of GGI last summer and it was working well enough, and now a year later we > still don't have a stable release. It's probably a matter of what one calls stable. I think The LibGGI Betas are as stable as what others would call final release with fixpacks 1-5 applied :-). > 1) The hwcursor seems to stick on the screen sometimes when I switch to > DGA mode. I just started experiencing that recently, only with GGI > programs, but possibly just out of luck. I tried doing an ugly hack > to set the cursor myself, but GGI has no display-dependant code to > give me, say, its X Display variable (shouldn't there be?). No. That's more or less the point of LibGGI. A LibGGI extension is allowed to know such stuff, to allow for doing such effects, but it is usually not recommended. > 2) Timing code has been a total bitch, partly because it appears that > GGI uses setitimer using ITIMER_PROF, That shouldn't be the case. The setitimer is only used if LibGGI is operated in SYNC mode. This is discouraged anyway. Use SYNC mode whenever possible. > Is there any way of doing frame-rate limiting code portably? You mean limiting in the sense of timing, not synchronizing to the CRT-ray ? Use the time argument for ggiEventPoll. > 3) Could someone maybe write a small tutorial on getting mouse input, > especially in the context of DGA games? ??? Mouse input should work the same no matter what target you have. The only difference is, that some targets have absolute mouse events, while others have relative ones. > 4) Is there no way to do faster blits or let me myself have more > control of video memory, especially when we're drawing to a display > like DGA that does give reasonably direct access? DirectBuffer ? > 5) Any advice on syncing to refreshes? I've found it basically > impossible, but I thought I'd ask anyways. If the underlying target supports it, you can do so via the ggimisc extension. CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 29 12:24:25 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id MAA02106 for ; Tue, 29 Jun 1999 12:24:24 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id JAA15451; Tue, 29 Jun 1999 09:10:15 -0700 Resent-Date: Tue, 29 Jun 1999 09:10:15 -0700 Date: Tue, 29 Jun 1999 18:10:09 +0200 (MET DST) From: Ketil Froyn To: Garrett B cc: ggi-develop@eskimo.com Subject: Re: switching color depth In-Reply-To: <99062911063100.02150@mongoose> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"VGUK7.0.Gn3.c_EUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13585 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 29 Jun 1999, Garrett B wrote: > when I run the slimy demo I get this > > slimy > LibGGI: Failed to set mode: [P8/8] > Error switching to 8bpp mode. > > Now Im in X and is there any way to allow X's color depth to be changed? Or > would I have to restart the X server at a new color depth each time I want to > change it? Check out the palemu and trueemu targets (I think). Look in doc/targets.txt in the libggi distribution. You should find what you need there. Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggi-develop-request@eskimo.com Tue Jun 29 13:33:56 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA03753 for ; Tue, 29 Jun 1999 13:33:55 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA06779; Tue, 29 Jun 1999 10:21:46 -0700 Resent-Date: Tue, 29 Jun 1999 10:21:46 -0700 Date: Tue, 29 Jun 1999 13:21:36 -0400 (EDT) From: Steve Cheng Sender: steve@sephiroth To: Garrett B cc: ggi-develop@eskimo.com Subject: Re: switching color depth In-Reply-To: <99062911063100.02150@mongoose> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"3eArG3.0.jf1.e2GUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13586 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 29 Jun 1999, Garrett B wrote: > Now Im in X and is there any way to allow X's color depth to be changed? Or > would I have to restart the X server at a new color depth each time I want to > change it? There's no way for a X client to change the X server's color depth. (XFree86 extensions only change the resolution.) -- Steve Cheng email: steve@ggi-project.org www: From ggi-develop-request@eskimo.com Tue Jun 29 13:39:16 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id NAA03868 for ; Tue, 29 Jun 1999 13:39:15 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id KAA08413; Tue, 29 Jun 1999 10:28:07 -0700 Resent-Date: Tue, 29 Jun 1999 10:28:07 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Direct Buffering was: Re: switching color depth Date: Tue, 29 Jun 1999 13:27:51 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: MIME-Version: 1.0 Message-Id: <99062913232800.02949@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"11bTF3.0.F32.c8GUt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13587 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 29 Jun 1999, you wrote: > > when I run the slimy demo I get this > > > slimy > > LibGGI: Failed to set mode: [P8/8] > > Error switching to 8bpp mode. > > > > Now Im in X and is there any way to allow X's color depth to be changed? Or > > would I have to restart the X server at a new color depth each time I want to > > change it? > > Check out the palemu and trueemu targets (I think). Look in > doc/targets.txt in the libggi distribution. You should find what you need > there. That brings up something else from targets.txt, it says x-lib doesn't support direct buffering but X does. Whats the difference between the X target and x-lib target? And if I use Direct Buffering in my program then thats going to limit the portability of my program. -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Tue Jun 29 16:02:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA07737 for ; Tue, 29 Jun 1999 16:02:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA20970; Tue, 29 Jun 1999 12:48:09 -0700 Resent-Date: Tue, 29 Jun 1999 12:48:09 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990629215007.A1749@rz.uni-duesseldorf.de> Date: Tue, 29 Jun 1999 21:50:07 +0200 From: Andreas Beck To: mongoose@wpi.edu Cc: mailing list GGI Subject: Re: switching color depth Mail-Followup-To: mongoose@wpi.edu, mailing list GGI References: <99062911063100.02150@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99062911063100.02150@mongoose>; from Garrett B on Tue, Jun 29, 1999 at 11:02:27AM -0500 Resent-Message-ID: <"DO4Ig1.0.k65.rBIUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13588 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > when I run the slimy demo I get this > > slimy > LibGGI: Failed to set mode: [P8/8] > Error switching to 8bpp mode. > Now Im in X and is there any way to allow X's color depth to be changed? AFAIK not. I restart the server for that. And I _HATE_ it. But it's probably impossible to change it, as the clients request the visual configuration and use it, so if we changed it beneath the clients, they would be very unhappy probably. > Or would I have to restart the X server at a new color depth each time > I want to change it? Yes. Though you can use the palemu and trueemu targets to circumvent the problem for LibGGI apps. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 29 16:46:45 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA08644 for ; Tue, 29 Jun 1999 16:46:44 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA01481; Tue, 29 Jun 1999 13:35:19 -0700 Resent-Date: Tue, 29 Jun 1999 13:35:19 -0700 Date: Tue, 29 Jun 1999 16:36:21 -0400 From: tentacle tentacle boat To: ggi-develop@eskimo.com Subject: Re: switching color depth Message-ID: <19990629163621.A4136@greenbytes.greenbytes.cx> References: <99062911063100.02150@mongoose> <19990629215007.A1749@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990629215007.A1749@rz.uni-duesseldorf.de>; from Andreas Beck on Tue, Jun 29, 1999 at 09:50:07PM +0200 Resent-Message-ID: <"TQK4z2.0.-M.6uIUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13589 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, Jun 29, 1999 at 09:50:07PM +0200, Andreas Beck wrote: > > > when I run the slimy demo I get this > > > slimy > > LibGGI: Failed to set mode: [P8/8] > > Error switching to 8bpp mode. > > > Now Im in X and is there any way to allow X's color depth to be changed? > > AFAIK not. I restart the server for that. And I _HATE_ it. But it's probably > impossible to change it, as the clients request the visual configuration and > use it, so if we changed it beneath the clients, they would be very unhappy > probably. > This will be changed in v 4.0 of Xfree, they plan to support on the fly depth switching :) john From ggi-develop-request@eskimo.com Tue Jun 29 17:26:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA09454 for ; Tue, 29 Jun 1999 17:26:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA14107; Tue, 29 Jun 1999 14:13:49 -0700 Resent-Date: Tue, 29 Jun 1999 14:13:49 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990629221928.B1776@rz.uni-duesseldorf.de> Date: Tue, 29 Jun 1999 22:19:28 +0200 From: Andreas Beck To: mongoose@wpi.edu Cc: mailing list GGI Subject: Re: Direct Buffering was: Re: switching color depth Mail-Followup-To: mongoose@wpi.edu, mailing list GGI References: <99062913232800.02949@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99062913232800.02949@mongoose>; from Garrett B on Tue, Jun 29, 1999 at 01:27:51PM -0500 Resent-Message-ID: <"XWtNM3.0.BR3.9SJUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13590 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > That brings up something else from targets.txt, it says x-lib doesn't support > direct buffering but X does. Whats the difference between the X target and > x-lib target? The X target basically allocates a bit pixmap (shared if possible) and always transfers it to the server completely. This is how it achieves to have a DirectBuffer. While this is o.k. for local displaying (best if it has MITSHM extension, as you can then bypass sending the the bitmap through the network connection, but o.k. as well if it hasn't, as the local loopback device is usually fast), but slow for remote displays. Xlib thus uses direct calls to X drawing functions to be faster. What exactly is faster depends on what the program does. Stars (which sets only a few points each frame) is faster on Xlib, others that draw the whole screen will probably be faster on X. > And if I use Direct Buffering in my program then thats going to > limit the portability of my program. Yes. You should always have a fallback. At worst use a memory-visual and CrossBlit each frame or use a PutBox based approach. CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Tue Jun 29 17:40:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA09701 for ; Tue, 29 Jun 1999 17:40:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA18877; Tue, 29 Jun 1999 14:27:01 -0700 Resent-Date: Tue, 29 Jun 1999 14:27:01 -0700 Sender: marcus@e.kth.se Message-ID: <37793A1E.157C8D41@stacken.kth.se> Date: Tue, 29 Jun 1999 21:26:54 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.10-ac3 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Direct Buffering was: Re: switching color depth References: <99062913232800.02949@mongoose> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"tAJy11.0.kc4.aeJUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13591 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B wrote: > That brings up something else from targets.txt, it says x-lib doesn't support > direct buffering but X does. Whats the difference between the X target and > x-lib target? X-target ======== Description +++++++++++ Displays in an X window. Emulates a linear framebuffer which is blitted to the Xserver with the XPutImage() function. In ASYNC mode this is done when ggiFlush() is called, and in SYNC mode it's done periodicly in the background (typicly 20 times/s). The MITSHM extension is used when available for maximum speed. =========== Xlib-target =========== Description +++++++++++ Displays in an X window. Uses Xlib primitives to do drawing. Faster than X-target when using drawing- primitives on on accelerated X-server. Blitting is slower when running local. > And if I use Direct Buffering in my program then thats going to > limit the portability of my program. No it wont. Not supporting non-DirectBuffer will though, but of course you will support that, right? ;) //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 29 17:56:02 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA10160 for ; Tue, 29 Jun 1999 17:56:01 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA25540; Tue, 29 Jun 1999 14:43:45 -0700 Resent-Date: Tue, 29 Jun 1999 14:43:45 -0700 Sender: marcus@e.kth.se Message-ID: <37793E0B.3A713C5C@stacken.kth.se> Date: Tue, 29 Jun 1999 21:43:39 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.10-ac3 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved References: <19990628110028.A496@rz.uni-duesseldorf.de> <19990629133021.E534@rz.uni-duesseldorf.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"Y5jtW2.0.pE6.GuJUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13592 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck wrote: > > geteuid() = 500 > > open("/dev/3dfx", > > O_RDWR) = -1 ENOSYS (Function not implemented) > > open("/dev/3dfx", O_RDWR) = -1 ENOSYS (Function not implemented) > > open("/dev/3dfx", O_RDWR) = -1 ENODEV (No such device) You do not have the 3dfx driver loaded. > > iopl(0x3) = -1 EPERM (Operation not permitted) So Glide will try to hit the hardware directly. > > --- SIGSEGV (Segmentation fault) --- But because you are not root that fails too. > > +++ killed by SIGSEGV +++ > > So it happens exactly what is to be expected. It looks like the kernel > driver doesn't let you in, and even if it would, calling iopl() will require > root privs ... seems like you can't use Glide as non-root ... Sure you can. It works just fine here with Device3Dfx. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Tue Jun 29 18:53:07 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA11312 for ; Tue, 29 Jun 1999 18:53:06 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA16066; Tue, 29 Jun 1999 15:40:55 -0700 Resent-Date: Tue, 29 Jun 1999 15:40:55 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Re: Direct Buffering was: Re: switching color depth Date: Tue, 29 Jun 1999 18:35:20 -0500 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <37793A1E.157C8D41@stacken.kth.se> MIME-Version: 1.0 Message-Id: <99062918403800.00630@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"1qWhk3.0.Ov3.ejKUt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13593 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Tue, 29 Jun 1999, Marcus Sundberg wrote: > > And if I use Direct Buffering in my program then thats going to > > limit the portability of my program. > > No it wont. Not supporting non-DirectBuffer will though, but of course > you will support that, right? ;) Well say Im loading an image from a file. Whats the best way to get the picture from the file to into a visual so I can blt it around? Just do ALOT of ggiPutPixel's? -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggi-develop-request@eskimo.com Tue Jun 29 22:49:23 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA14584 for ; Tue, 29 Jun 1999 22:49:22 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA24802; Tue, 29 Jun 1999 19:35:40 -0700 Resent-Date: Tue, 29 Jun 1999 19:35:40 -0700 From: Andrew Apted Message-ID: <19990630124118.28639@ajax.netspace.net.au> Date: Wed, 30 Jun 1999 12:41:18 +1000 To: ggi-develop@eskimo.com Subject: Re: Direct Buffering was: Re: switching color depth Reply-To: ggi-develop@eskimo.com References: <37793A1E.157C8D41@stacken.kth.se> <99062918403800.00630@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <99062918403800.00630@mongoose>; from Garrett B on Tue, Jun 29, 1999 at 06:35:20PM -0500 Resent-Message-ID: <"rUsce2.0.736.q9OUt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13594 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Garrett B writes: > Well say Im loading an image from a file. Whats the best way to get the > picture from the file to into a visual so I can blt it around? Just do ALOT of > ggiPutPixel's? If it is a memory visual, and image-load speed is not a problem, then yeah ggiPutPixel() is the easiest way. A faster alternative it to build one whole line at a time, and then ggiPutHLine() it. There is only 4 cases to cover -- 1, 2, 3 or 4 bytes-per-pixel. This is what flying-ggis does. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Tue Jun 29 22:53:49 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA14646 for ; Tue, 29 Jun 1999 22:53:48 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id TAA28249; Tue, 29 Jun 1999 19:41:21 -0700 Resent-Date: Tue, 29 Jun 1999 19:41:21 -0700 From: Andrew Apted Message-ID: <19990630124708.26874@ajax.netspace.net.au> Date: Wed, 30 Jun 1999 12:47:08 +1000 To: ggi-develop@eskimo.com Subject: Re: XGGI & kdm Reply-To: ggi-develop@eskimo.com References: <3777FC76.465AD9EF@fisicc-ufm.edu> <19990629131052.B534@rz.uni-duesseldorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <19990629131052.B534@rz.uni-duesseldorf.de>; from Andreas Beck on Tue, Jun 29, 1999 at 01:10:52PM +0200 Resent-Message-ID: <"cfa6H2.0.4v6.GFOUt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13595 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck writes: > > The problem is that when > > i start in runlevel 5 (is the default because we use > > KDM for login purposes) X gives me an error: > > > display-fbdev: failed to open tty: Device not configured > > L/vtswitch: open /dev/tty: Device not configured > > That's weird. That sounds like the TTY devices not being there ... ??? Perhaps his boot script doesn't start any getty's on /dev/tty* ? The "-novt" option of display-fbdev might help. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggi-develop-request@eskimo.com Wed Jun 30 00:42:55 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id AAA16190 for ; Wed, 30 Jun 1999 00:42:54 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id VAA23301; Tue, 29 Jun 1999 21:27:51 -0700 Resent-Date: Tue, 29 Jun 1999 21:27:51 -0700 Sender: peter@lime.idonex.se To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved References: Content-Transfer-Encoding: 8BIT X-Face: #.`T$>|mFxfHna0Wy-(\k3d5TWne~qr.cVHv(ye95XPctC&SXXcZJOPdbqzjWOsgO9AK"/9 unLFS+cdbl&EIVhO2yVW ~z8*h(Rbpng{9B+,_gj+OM{%8O|h5~'Lo=N6jPvwp.vp240Z"`&I(\(#s5[:`y%MIX,%[L=vQJi[S, `B:!}As%w97=Ut[9Eg<(*(^LDD8g Content-Type: TEXT/PLAIN; charset=ISO-8859-1 From: Peter Bortas Date: 30 Jun 1999 06:27:24 +0200 In-Reply-To: Ketil Froyn's message of "Tue, 29 Jun 1999 13:52:35 +0200 (MET DST)" Message-ID: <76oghyl3df.fsf@lime.idonex.se> Lines: 18 User-Agent: Gnus/5.070088 (Pterodactyl Gnus v0.88) XEmacs/21.1 (20 Minutes to Nikko) MIME-Version: 1.0 Resent-Message-ID: <"OwyCS3.0.ch5.5pPUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13596 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn writes: > On Tue, 29 Jun 1999, Andreas Beck wrote: > > > > BTW, is there some way to run quake fullscreen using GGI? I've tried > > > squake, but that seems to be hardcoded to use the libc-version of > > > libvga.so.1... Symlinking did not remedy this. > > You'd need to build a libc5 version of LibGGI and the SVGAlib wrapper. > > Eeew... is this normal? Does everyone else do this? Yup, or no, we run Quake3test instead. If someone could convince id to let someone publicize a recompiled version of Quake there would be no such problem, but that is not likely to happen right now. -- Peter Bortas http://peter.bortas.org Idonex AB http://www.idonex.com From ggi-develop-request@eskimo.com Wed Jun 30 04:57:17 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA18822 for ; Wed, 30 Jun 1999 04:57:16 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA08540; Wed, 30 Jun 1999 01:43:31 -0700 Resent-Date: Wed, 30 Jun 1999 01:43:31 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990630104634.B496@rz.uni-duesseldorf.de> Date: Wed, 30 Jun 1999 10:46:34 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: Direct Buffering was: Re: switching color depth Mail-Followup-To: ggi-develop@eskimo.com References: <37793A1E.157C8D41@stacken.kth.se> <99062918403800.00630@mongoose> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <99062918403800.00630@mongoose>; from Garrett B on Tue, Jun 29, 1999 at 06:35:20PM -0500 Resent-Message-ID: <"v3ZDf3.0.G52.mYTUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13597 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > No it wont. Not supporting non-DirectBuffer will though, but of course > > you will support that, right? ;) > Well say Im loading an image from a file. Whats the best way to get the > picture from the file to into a visual so I can blt it around? Just do ALOT of > ggiPutPixel's? That's what I do. Loading the image is slow anyway (io-limited), so speed shouldn't be critical there anyway. Example raw-ppm loader below. CU, Andy /* Helper. Read line ignoring comments. */ char *fgetsnoc(char *buffer,size_t size,FILE *inf){ char *rc; while(1) { rc=fgets(buffer,size,inf); if (rc&&*rc!='#') return rc; } } int loadppm(ggi_visual_t vis,int x,int y,char *name) { struct rgb{ unsigned char r,g,b; } rgb; ggi_color col; FILE *inf; int w,h,xx,yy; char buffer[256]; if (NULL==(inf=fopen(name,"r"))) return 1; fgetsnoc(buffer,sizeof(buffer),inf); if (strcmp(buffer,"P6\n")) return 1; fgetsnoc(buffer,sizeof(buffer),inf); w=h=0; sscanf(buffer,"%d %d",&w,&h); fgetsnoc(buffer,sizeof(buffer),inf); for(yy=0;yy = From ggi-develop-request@eskimo.com Wed Jun 30 04:58:14 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id EAA18845 for ; Wed, 30 Jun 1999 04:58:13 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id BAA08578; Wed, 30 Jun 1999 01:43:38 -0700 Resent-Date: Wed, 30 Jun 1999 01:43:38 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990630104147.A496@rz.uni-duesseldorf.de> Date: Wed, 30 Jun 1999 10:41:47 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved Mail-Followup-To: ggi-develop@eskimo.com References: <19990628110028.A496@rz.uni-duesseldorf.de> <19990629133021.E534@rz.uni-duesseldorf.de> <37793E0B.3A713C5C@stacken.kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <37793E0B.3A713C5C@stacken.kth.se>; from Marcus Sundberg on Tue, Jun 29, 1999 at 09:43:39PM +0000 Resent-Message-ID: <"UivzE3.0.o52.uYTUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13598 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > > > open("/dev/3dfx", > > > O_RDWR) = -1 ENOSYS (Function not implemented) > > > open("/dev/3dfx", O_RDWR) = -1 ENOSYS (Function not implemented) > > > open("/dev/3dfx", O_RDWR) = -1 ENODEV (No such device) > You do not have the 3dfx driver loaded. Hmm - out of curiosity: Why does one get twice ENOSYS, and then once ENODEV when doing three times the same call ? I had assumed it is the driver somehow actively rejecting access, but if it is like you say, and the driver isn't loaded, I wonder why the errorcode changes. > > root privs ... seems like you can't use Glide as non-root ... > Sure you can. It works just fine here with Device3Dfx. Ah - GOOOD ! Hmm - can we "pretest" that condition ? It seems Glide doesn't give helpful error messages ... I assume we could check if we are root. If we are not, we can try to open /dev/3dfx. If that fails, we know that Glide won't work either and issue an error message ... ? CU, ANdy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Wed Jun 30 07:27:15 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id HAA19774 for ; Wed, 30 Jun 1999 07:27:14 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id EAA00613; Wed, 30 Jun 1999 04:13:46 -0700 Resent-Date: Wed, 30 Jun 1999 04:13:46 -0700 Message-ID: <19990630111432.3888.rocketmail@web115.yahoomail.com> Date: Wed, 30 Jun 1999 04:14:32 -0700 (PDT) From: Kien Pham Subject: C++ namespace infringement "feature." To: ggi-develop@eskimo.com MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-846930886-930741272=:3619" Resent-Message-ID: <"7mPx82.0.v8.elVUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13599 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com --0-846930886-930741272=:3619 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi. One of the extension structs has a member "private" which is a reserved C++ keyword. Simple patch is attached. ~K.P. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com --0-846930886-930741272=:3619 Content-Type: text/plain; name="patch.txt" Content-Description: patch.txt Content-Disposition: inline; filename="patch.txt" *** structs.h Tue Jun 22 11:25:07 1999 --- /usr/local/include/ggi/internal/structs.h Tue Jun 22 11:25:49 1999 *************** *** 126,130 **** typedef struct { int attachcount; ! void *private; } ggi_extlist; --- 126,130 ---- typedef struct { int attachcount; ! void *priv; } ggi_extlist; --0-846930886-930741272=:3619-- From ggi-develop-request@eskimo.com Wed Jun 30 15:20:11 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA29136 for ; Wed, 30 Jun 1999 15:20:10 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA14562; Wed, 30 Jun 1999 12:05:36 -0700 Resent-Date: Wed, 30 Jun 1999 12:05:36 -0700 Sender: becka@rz.uni-duesseldorf.de Message-ID: <19990630180839.A512@rz.uni-duesseldorf.de> Date: Wed, 30 Jun 1999 18:08:39 +0200 From: Andreas Beck To: ggi-develop@eskimo.com Subject: Re: C++ namespace infringement "feature." Mail-Followup-To: ggi-develop@eskimo.com References: <19990630111432.3888.rocketmail@web115.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <19990630111432.3888.rocketmail@web115.yahoomail.com>; from Kien Pham on Wed, Jun 30, 1999 at 04:14:32AM -0700 Resent-Message-ID: <"u7pKc.0.8Y3.wfcUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13600 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com > One of the extension structs has a member "private" which > is a reserved C++ keyword. Simple patch is attached. Thanks for making me have a look again ... I found occurences in quite a few files ... : ./libggi3d/lib/3d_int.h: void *private; ./libggi3d/include/ggi3d/module.h: void *private; ./libggi3d/modules/debug.c: modinfo->private = priv; ./libggi3d/modules/ggivis.c: modinfo->private = priv; ./libggi3d/modules/phong_light.c: modinfo->private = priv; ./libggi3d/modules/pipeline.c: modinfo->private = priv; ./libggi3d/modules/renderworld.c: modinfo->private = priv; ./libggi3d/modules/tesselate.c: modinfo->private = priv; ./libggi3d/modules/zbuffer.c: modinfo->private = priv; Jon ? ./libwmh/ggiwmh/wmh_int.h: void *private; I fixed that. ./libggi/display/xf86dga/visual.c: XFree(priv->dgamodes[i]->private); ./libggi/display/xf86dga/XF86VMode.c: modelines[i]->private = NULL; We can't do anything about those they are in XFree ... GRR. It's not too bad, as LibGGI is C-only and thus hides away that problem, but ... CU, Andy -- = Andreas Beck | Email : = From ggi-develop-request@eskimo.com Wed Jun 30 17:43:40 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id RAA02518 for ; Wed, 30 Jun 1999 17:43:38 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id OAA01254; Wed, 30 Jun 1999 14:31:18 -0700 Resent-Date: Wed, 30 Jun 1999 14:31:18 -0700 Date: Wed, 30 Jun 1999 14:30:55 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: C++ namespace infringement "feature." In-Reply-To: <19990630180839.A512@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"EB8LD.0.AJ.UoeUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13601 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com On Wed, 30 Jun 1999, Andreas Beck wrote: > > One of the extension structs has a member "private" which > > is a reserved C++ keyword. Simple patch is attached. > > Thanks for making me have a look again ... I found occurences in quite a > few files ... : > > ./libggi3d/lib/3d_int.h: void *private; > ./libggi3d/include/ggi3d/module.h: void *private; > ./libggi3d/modules/debug.c: modinfo->private = priv; > ./libggi3d/modules/ggivis.c: modinfo->private = priv; > ./libggi3d/modules/phong_light.c: modinfo->private = priv; > ./libggi3d/modules/pipeline.c: modinfo->private = priv; > ./libggi3d/modules/renderworld.c: modinfo->private = priv; > ./libggi3d/modules/tesselate.c: modinfo->private = priv; > ./libggi3d/modules/zbuffer.c: modinfo->private = priv; > > Jon ? Fixed and committed. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggi-develop-request@eskimo.com Wed Jun 30 18:15:32 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA03033 for ; Wed, 30 Jun 1999 18:15:31 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA18229; Wed, 30 Jun 1999 15:02:55 -0700 Resent-Date: Wed, 30 Jun 1999 15:02:55 -0700 Sender: marcus@e.kth.se Message-ID: <377A933D.18CADA86@stacken.kth.se> Date: Wed, 30 Jun 1999 21:59:25 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.10-ac3 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: Accelleration (Was: Re: TNT benchmark) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"x1YlC3.0.2S4.8GfUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13602 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Jon M. Taylor wrote: > You do realize that (in principle anyway) there is no need for one > single universal method of implementing acceleration in a KGI driver? The > existing Dali kgicommand API explicitly defines a set of 2D accels > (ACCEL_DRAWBOX, etc) which for the most part works OK, Note that using one ioctl() per accel operation is definitely not recommended for anything else than initial testing, even for 2D. Using ioctl()s are almost one order of magnitude slower than using direct access. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 30 18:15:32 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA03036 for ; Wed, 30 Jun 1999 18:15:32 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA18520; Wed, 30 Jun 1999 15:03:24 -0700 Resent-Date: Wed, 30 Jun 1999 15:03:24 -0700 Sender: marcus@e.kth.se Message-ID: <377A920E.CE5A57D@stacken.kth.se> Date: Wed, 30 Jun 1999 21:54:22 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.10-ac3 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"AbVLZ2.0.gT4.IGfUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13605 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn wrote: > > On Tue, 29 Jun 1999, Andreas Beck wrote: > > > > BTW, is there some way to run quake fullscreen using GGI? I've tried > > > squake, but that seems to be hardcoded to use the libc-version of > > > libvga.so.1... Not really. It's hardcoded to use libc.so.5, libvga has nothing to do with it. > > > Symlinking did not remedy this. > > You'd need to build a libc5 version of LibGGI and the SVGAlib wrapper. > > Eeew... is this normal? Does everyone else do this? Yes. Note that qwcl and quake2 also come in glibc flavors, so it's only squake that requires libc5. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 30 18:17:37 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA03081 for ; Wed, 30 Jun 1999 18:17:34 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA18471; Wed, 30 Jun 1999 15:03:30 -0700 Resent-Date: Wed, 30 Jun 1999 15:03:30 -0700 Sender: marcus@e.kth.se Message-ID: <377A916F.74C9A241@stacken.kth.se> Date: Wed, 30 Jun 1999 21:51:43 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.10-ac3 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"-3WgJ3.0.TS4.9GfUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13603 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Ketil Froyn wrote: > But that is the point of /dev/3dfx, no? I thought the deal was that with > /dev/3dfx, you won't need the iopl(), so non-root users can use this... > If not, what's even the point with /dev/3dfx? (Maybe I should ask 3dfx, > not you, but I thought this was how it worked). Glide only tries to use iopl() because you haven't loaded the 3dfx kernel module. > BTW: I'm a little slow... can I run xggi on glide if I get the latest > libggi snapshot? Yes. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 30 18:17:43 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA03086 for ; Wed, 30 Jun 1999 18:17:42 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA18505; Wed, 30 Jun 1999 15:03:21 -0700 Resent-Date: Wed, 30 Jun 1999 15:03:21 -0700 Sender: marcus@e.kth.se Message-ID: <377A9119.401C598A@stacken.kth.se> Date: Wed, 30 Jun 1999 21:50:17 +0000 From: Marcus Sundberg X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.10-ac3 i586) MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved References: <19990628110028.A496@rz.uni-duesseldorf.de> <19990629133021.E534@rz.uni-duesseldorf.de> <37793E0B.3A713C5C@stacken.kth.se> <19990630104147.A496@rz.uni-duesseldorf.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Resent-Message-ID: <"vWNWE.0.aS4.AGfUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13604 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Andreas Beck wrote: > > > > > open("/dev/3dfx", > > > > O_RDWR) = -1 ENOSYS (Function not implemented) > > > > open("/dev/3dfx", O_RDWR) = -1 ENOSYS (Function not implemented) > > > > open("/dev/3dfx", O_RDWR) = -1 ENODEV (No such device) > > You do not have the 3dfx driver loaded. > > Hmm - out of curiosity: Why does one get twice ENOSYS, and then once ENODEV > when doing three times the same call ? At first I thought it was glibc doing something special, but then I found out that doing int 0x80 directly also produces the same three open() entries per call in strace logs. Strange... > I had assumed it is the driver somehow actively rejecting access, but if it > is like you say, and the driver isn't loaded, I wonder why the errorcode > changes. After further testing it appears that when the 3dfx module is not loaded you get: open("/dev/3dfx", O_RDONLY) = -1 ENOSYS (Function not implemented) open("/dev/3dfx", O_RDONLY) = -1 ENOSYS (Function not implemented) open("/dev/3dfx", O_RDONLY) = 3 but subsequent open()s will give just the last strace entry. Apparently it has something to do with kmod. > > > root privs ... seems like you can't use Glide as non-root ... > > Sure you can. It works just fine here with Device3Dfx. > > Ah - GOOOD ! Hmm - can we "pretest" that condition ? It seems Glide doesn't > give helpful error messages ... I assume we could check if we are root. If > we are not, we can try to open /dev/3dfx. If that fails, we know that Glide > won't work either and issue an error message ... ? Not very nice in case Glide changes in some strange way. Seems better to use a temporary SIGSEGV handler and longjmp() out of the handler after setting an error flag. //Marcus -- -------------------------------+------------------------------------ Marcus Sundberg | http://www.stacken.kth.se/~mackan/ Royal Institute of Technology | Phone: +46 707 295404 Stockholm, Sweden | E-Mail: mackan@stacken.kth.se From ggi-develop-request@eskimo.com Wed Jun 30 22:02:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id WAA06156 for ; Wed, 30 Jun 1999 22:02:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id SAA27055; Wed, 30 Jun 1999 18:48:36 -0700 Resent-Date: Wed, 30 Jun 1999 18:48:36 -0700 Date: Wed, 30 Jun 1999 21:47:32 -0400 (EDT) From: James Simmons X-Sender: jsimmons@elmwood.afterfive.com To: ggi-develop Subject: mono to any depth mapping Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"a09l.0.gb6.RZiUt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13606 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com hi! Anyone know where I can get really fast code for mapping a bitmap (just 1 and 0) to any color depth? Thank you alot. From ggi-develop-request@eskimo.com Wed Jun 30 23:21:18 1999 Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id XAA07318 for ; Wed, 30 Jun 1999 23:21:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id UAA21244; Wed, 30 Jun 1999 20:03:52 -0700 Resent-Date: Wed, 30 Jun 1999 20:03:52 -0700 From: Andrew Apted Message-ID: <19990701130933.34411@ajax.netspace.net.au> Date: Thu, 1 Jul 1999 13:09:33 +1000 To: ggi-develop@eskimo.com Subject: Re: mono to any depth mapping Reply-To: ggi-develop@eskimo.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from James Simmons on Wed, Jun 30, 1999 at 09:47:32PM -0400 Resent-Message-ID: <"56uzF2.0.VB5.MgjUt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13607 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com James Simmons writes: > Anyone know where I can get really fast code for mapping a bitmap (just > 1 and 0) to any color depth? Thank you alot. Perhaps Allegro ? http://www.talula.demon.co.uk/allegro/ Or the HERMES library, but sorry I've lost the URL. Cheers, ___________________________________________________ \ / Andrew Apted \/ From ggiweb@metalab.unc.edu Mon Jun 28 15:09:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA00471 for ; Mon, 28 Jun 1999 15:09:36 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id LAA00092; Mon, 28 Jun 1999 11:57:02 -0700 Resent-Date: Mon, 28 Jun 1999 11:57:02 -0700 Date: Mon, 28 Jun 1999 15:49:52 -0400 (EDT) From: "Brian S. Julin" To: Jos Hulzink cc: ggi-develop@eskimo.com Subject: Re: Accelleration (Was: Re: TNT benchmark) In-Reply-To: Message-ID: MIME-Version: 1.0 Resent-Message-ID: <"YO5SZ2.0.11.xLyTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13568 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 625 On Mon, 28 Jun 1999, Jos Hulzink wrote: > I'm implementing 3D accelleration for the ViRGE now, > but to get this working, I have to hack libggi. I thought the idea of a > driver was that software doesn't have to deal with driver-specific code > anymore ? I have to recompile libggi if I change from the nvriva driver to > the S3 virge driver... Nice... :( Umm..... Why? Care to be more specific as to what made you have to recompile, rather than just adding a display-s3-virge target library? Even adding new 3d functions you should be able to do this by making an extension and not have to recompile LibGGI. -- Brian From ggiweb@metalab.unc.edu Mon Jun 28 15:33:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id PAA01550 for ; Mon, 28 Jun 1999 15:33:28 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id MAA05596; Mon, 28 Jun 1999 12:19:31 -0700 Resent-Date: Mon, 28 Jun 1999 12:19:31 -0700 Date: Mon, 28 Jun 1999 21:19:19 +0200 (MET DST) From: Ketil Froyn To: ggi-develop@eskimo.com Subject: Re: ggi acting up solved In-Reply-To: <19990628110028.A496@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Resent-Message-ID: <"lk7Ss3.0.iM1.0hyTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13569 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1889 On Mon, 28 Jun 1999, Andreas Beck wrote: > > Also, I was wondering about a few other things... Can only root use the > > glide target? What about /dev/3dfx? I have it, but demos core dump(!) when > > I try to run them as me. > That's strange. This could be a problem with VT-switching or needing > root-access to use the keyboard. Could you run the core file through a > debugger to see where it dumps ? And/or make GGI_DEBUG=255 logs and strace > logs ? Backtrace: Program received signal SIGSEGV, Segmentation fault. 0x4018f854 in pioOutLongLinux () (gdb) bt #0 0x4018f854 in pioOutLongLinux () #1 0x0 in ?? () End of strace: write(2, "LibGGI: ", 8LibGGI: ) = 8 write(2, "GLIDE-lib starting\n", 19GLIDE-lib starting ) = 19 geteuid() = 500 open("/dev/3dfx", O_RDWR) = -1 ENOSYS (Function not implemented) open("/dev/3dfx", O_RDWR) = -1 ENOSYS (Function not implemented) open("/dev/3dfx", O_RDWR) = -1 ENODEV (No such device) iopl(0x3) = -1 EPERM (Operation not permitted) --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ GGI_DEBUG=255: LibGII: Debugging=255 LibGGI: Debugging=255 LibGGI: ggiOpen("glide") called LibGGI: Loading driver glide LibGGI: _ggiAddDL(0x8050fb8, "glide", "(null)", 0x1) called LibGGI: _ggiLoadDL("/usr/local/lib/ggi/display/glide.so", 0x1) called LibGGI: hand.handle=0x8051308 LibGGI: hand.init=0x400213f0 LibGGI: hand.cleanup=0x40021880 LibGGI: _ggiLoadDL returned 0x80518a8 LibGGI: GLIDE-lib starting Segmentation fault (core dumped) I used libggi-2.0b2.1/programs/demos/flying_ggis in all the cases, except I had to run libggi-2.0b2.1/programs/demos/.libs/lt-flying_ggis in debug. For once I hope this wasn't all my mistake :) Ketil Froyn -- He who Laughs, Lasts. http://www.ifi.uio.no/~ketilf/ mailto:ketilf@ifi.uio.no From ggiweb@metalab.unc.edu Mon Jun 28 16:17:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA02791 for ; Mon, 28 Jun 1999 16:17:24 -0400 (EDT) Received: (from smartlst@localhost) by mx2.eskimo.com (8.9.1a/8.8.8) id NAA15278; Mon, 28 Jun 1999 13:00:02 -0700 (PDT) Resent-Date: Mon, 28 Jun 1999 13:00:02 -0700 (PDT) Date: Mon, 28 Jun 1999 15:56:39 -0400 (EDT) From: Steve Cheng Sender: steve@sephiroth To: mailing list GGI Subject: Re: Frames in SVGA In-Reply-To: <19990628110251.B496@rz.uni-duesseldorf.de> Message-ID: MIME-Version: 1.0 Resent-Message-ID: <"CAlbI3.0.Nh3.3GzTt"@mx2> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13570 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 552 On Mon, 28 Jun 1999, Andreas Beck wrote: > > I am trying to set ggi_mode.frames to 2 using display-svga. Is it > > possible to havce multiple frames when using svga under linux? I am also A quick look at degas/lib/libggi/display/svgalib/mode.c shows that it is not possible. > > having problems with display-memory. When I write to display memory then > > cross blit to display-vga it doesn't seem to work well. What do you mean "doesn't seem to work well"? -- Steve Cheng email: steve@ggi-project.org www: From ggiweb@metalab.unc.edu Mon Jun 28 16:58:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA03840 for ; Mon, 28 Jun 1999 16:58:48 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA09161; Mon, 28 Jun 1999 13:46:46 -0700 Resent-Date: Mon, 28 Jun 1999 13:46:46 -0700 Date: Mon, 28 Jun 1999 13:46:39 -0700 (PDT) From: "Jon M. Taylor" To: ggi-develop@eskimo.com Subject: Re: Accelleration (Was: Re: TNT benchmark) In-Reply-To: Message-ID: MIME-Version: 1.0 Resent-Message-ID: <"PDQAC.0.rE2.pyzTt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13571 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2542 On Mon, 28 Jun 1999, Jos Hulzink wrote: > On Mon, 28 Jun 1999, Denis Oliver Kropp wrote: > > > Hi, > > > > I ran the same tests except that the card is a TNT now. > > > Cool, running benchmarks on unaccellerated drivers and comparing them with > Direct X... The only KGICON drivers that support accelleration AFAIK are > the Matrox drivers and the S3 ViRGE drivers on my machine :) > > In one thing Linus is right: Some parts of the GGI project have no clear > goal. In my eyes, there has been no good thinking about the > accelleration of drivers. You do realize that (in principle anyway) there is no need for one single universal method of implementing acceleration in a KGI driver? The existing Dali kgicommand API explicitly defines a set of 2D accels (ACCEL_DRAWBOX, etc) which for the most part works OK, but 3D features vary much more widely between chipsets. For the Savage4 KGI driver, I defined my own set of 3D-related kgicommands: * DrawPrimitive (draw triangle/strip/fan/quad) * SetGlobalState (clipping, zbuffer/stencil/alpha, etc) * SetLocalState (Texture blendmode/type, etc) * FlushState (flush command FIFOs, flush vertex buffer, etc) Don't be afraid to roll your own, especially when you are developing the driver. As long as you write a customized display-S3-virge type of target for LibGGI/GGIMesa/whatever, your accel interface can be whatever you want it to be. And it should not affect the rest of the library code. > I'm implementing 3D accelleration for the ViRGE now, > but to get this working, I have to hack libggi. Um... why are you doing 3D accels through LibGGI and not GGIMesa? > I thought the idea of a > driver was that software doesn't have to deal with driver-specific code > anymore ? Yes, but the KGI driver is only part of the total "driver" code. Each individual LibGGI-family target is also a driver. So after you get your KGI driver working, you still need to code up a target for each library that will be making use of features that are specific to your driver. Most 2D features are common across KGI drivers so no customized targets are necessary, but when you get into the weirder 2D features (STREAMS, etc) or 3D features, you have to write your own target code. > I have to recompile libggi if I change from the nvriva driver to > the S3 virge driver... Nice... :( This should not be necessary. Can you give us some more details? Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed From ggiweb@metalab.unc.edu Mon Jun 28 16:58:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id QAA03844 for ; Mon, 28 Jun 1999 16:58:50 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id NAA09518; Mon, 28 Jun 1999 13:47:29 -0700 Resent-Date: Mon, 28 Jun 1999 13:47:29 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: Setting frame amounts Date: Mon, 28 Jun 1999 16:41:27 -0500 X-Mailer: KMail [version 1.0.17] MIME-Version: 1.0 Message-Id: <99062816472000.02626@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"0GM0c.0.DK2.UzzTt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13572 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Content-Type: text/plain Content-Length: 503 If you call ggiSetMode and set the number of frames in the mode struct to 2, will ggi return an error if it can only create one frame? or will it just create the one frame and continue? Also assuming it will fail if it only returns one frame, is there any need to call ggiDBGetNumBuffers(vis) ? Because won't there always be a vis 0 and 1? -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain From ggiweb@metalab.unc.edu Mon Jun 28 18:27:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id SAA05827 for ; Mon, 28 Jun 1999 18:27:40 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA07798; Mon, 28 Jun 1999 15:14:44 -0700 Resent-Date: Mon, 28 Jun 1999 15:14:44 -0700 Date: Mon, 28 Jun 1999 18:13:39 -0400 (EDT) From: Steve Cheng Sender: steve@sephiroth To: Garrett B cc: ggi-develop@eskimo.com Subject: Re: Setting frame amounts In-Reply-To: <99062816472000.02626@mongoose> Message-ID: MIME-Version: 1.0 Resent-Message-ID: <"JMqs-2.0.of1.bE_Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13573 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 908 On Mon, 28 Jun 1999, Garrett B wrote: > If you call ggiSetMode and set the number of frames in the mode struct to 2, > will ggi return an error if it can only create one frame? or will it just > create the one frame and continue? The frames value in the ggi_mode will be changed to 1, and both ggiSetMode() and ggiCheckMode() will fail. If you want the one frame mode, just call ggiSetMode() again. See the LibGGI API docs at the web site or ftp site for the details of mode negotiation. > Also assuming it will fail if it only returns one frame, is there any > need to call ggiDBGetNumBuffers(vis) ? Because won't there always be a vis 0 > and 1? It's still possible in that case that there can be more than 1 DirectBuffer. One example is two different pointers to the framebuffer with different endianness. -- Steve Cheng email: steve@ggi-project.org www: From ggiweb@metalab.unc.edu Mon Jun 28 19:00:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id TAA07492 for ; Mon, 28 Jun 1999 19:00:21 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id PAA22004; Mon, 28 Jun 1999 15:47:44 -0700 Resent-Date: Mon, 28 Jun 1999 15:47:44 -0700 Sender: solca@fisicc-ufm.edu Message-ID: <3777FC76.465AD9EF@fisicc-ufm.edu> Date: Mon, 28 Jun 1999 16:51:35 -0600 From: Otto Solares Organization: FISICC-UFM X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10-ac4 i586) X-Accept-Language: en MIME-Version: 1.0 To: ggi-develop@eskimo.com Subject: XGGI & kdm Content-Transfer-Encoding: 7bit Resent-Message-ID: <"nSHEw1.0.NN5.Fk_Tt"@mx1> Resent-From: ggi-develop@eskimo.com Reply-To: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13574 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Content-Type: text/plain; charset=us-ascii Content-Length: 656 Hi guys! I am the network administrator in a University at Guatemala and i am using GGI some time along. Currently i have like 150 linux boxes for student use at the internet labs and i found that XFree86 have more overhead than XGGI so i decided to install it (Currently i don't know if this observation is wrong but i found XGGI faster in this 32Mb boxes than any other X). The problem is that when i start in runlevel 5 (is the default because we use KDM for login purposes) X gives me an error: display-fbdev: failed to open tty: Device not configured L/vtswitch: open /dev/tty: Device not configured Any idea to solve this problem? Otto Solares From ggiweb@metalab.unc.edu Tue Jun 29 11:49:00 1999 -0400 Status: X-Status: X-Keywords: Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by luna.oit.unc.edu (8.8.6/8.8.6/rchk1.19) with ESMTP id LAA01226 for ; Tue, 29 Jun 1999 11:49:17 -0400 (EDT) Received: (from smartlst@localhost) by mx1.eskimo.com (8.9.1a/8.8.8) id IAA16114; Tue, 29 Jun 1999 08:06:35 -0700 Resent-Date: Tue, 29 Jun 1999 08:06:35 -0700 From: Garrett B Reply-To: mongoose@wpi.edu To: ggi-develop@eskimo.com Subject: switching color depth Date: Tue, 29 Jun 1999 11:02:27 -0500 X-Mailer: KMail [version 1.0.17] MIME-Version: 1.0 Message-Id: <99062911063100.02150@mongoose> Content-Transfer-Encoding: 8bit Resent-Message-ID: <"4ZTd8.0.Wx3.t3EUt"@mx1> Resent-From: ggi-develop@eskimo.com X-Mailing-List: archive/latest/13584 X-Loop: ggi-develop@eskimo.com Precedence: list Resent-Sender: ggi-develop-request@eskimo.com Content-Type: text/plain Content-Length: 435 when I run the slimy demo I get this > slimy LibGGI: Failed to set mode: [P8/8] Error switching to 8bpp mode. Now Im in X and is there any way to allow X's color depth to be changed? Or would I have to restart the X server at a new color depth each time I want to change it? -Mongoose, WPI student majoring in Computer Science. "Whenever you find yourself on the side of the majority, it's time to pause and reflect." -Mark Twain