On Sat, Mar 03, 2001 at 01:26:28AM -0500, Brian S. Julin wrote:
>
> I've made a new LibGGIMisc:
>
> http://mojo.calyx.net/~bri/projects/GGI/libggimisc.tar.bz2
>
> Changes:
> -- moved from libggi/extensions to own directory
> -- updated structure to match libedemo
> -- added docbook/manpages and retrace thread from 1998 list archives
> -- added fbdev target (TOTALLY UNTESTED)
>
>
> I'd commit this, but since I moved its location, I want to make sure
> the removal of the one in lib/libggi/extensions goes smoothly
> and whatever can be done to preserve old changelog entries is done,
> which is above my head CVS-wise.
It'd be nice to install a perl script to generate a ChangeLog from
the commit-messages while doing the other CVS-surgery
btw, the last three packages uploaded to ftp.ggi-project.org
(OVL, GCP and BSE) do not seem to be world readable. Got them
from SF, but have not looked at them yet..
>
> Also, it could probably use a few testers first. I'll probably
> be trying it on my matrox card tomorrow. It won't work on any
> other fbdev because matroxfb is the only one that implements
> the GETVSYNC IOCTL. The only thing I know works is display-X's
> splitline implementation.
>
> P.S. I use pretty recent utils/kernel, so if you're one of those
> install-from-cd-and-never-change-your-underwear type of guys,
> no guarantee as to whether it will compile. But please try,
> because making it autoconf right is as important as it actually
> working these days.
I did not try it yet, but will ASAP. Changes i made while
reading the doc included.
Back to fighting against mesa_3_4 texture stuff :-/
Jon? is e.g. _mesa_null_texformat only me? anyone?
How heavyly has the texture subsys changed wrt 3_2?
I Never looked at Mesa's tex-proxy before...
>
> --
> Brian
>
-- b
diff -Ndur libggimisc.orig/README libggimisc/README
--- libggimisc.orig/README Fri Mar 2 18:16:50 2001
+++ libggimisc/README Mon Mar 5 23:46:40 2001
@@ -7,7 +7,7 @@
============
LibGGIMisc is a place to put support for graphics target features
-which are not desrving of their own special extensions. Right
+which are not deserving their own special extensions. Right
now this means basically some VGA adaptor features --
getting and waiting for the raster position, using a hardware
horizontal splitline feature, and loading/unloading font data
diff -Ndur libggimisc.orig/display/fbdev/funcs.c libggimisc/display/fbdev/funcs.c
--- libggimisc.orig/display/fbdev/funcs.c Sat Mar 3 01:48:49 2001
+++ libggimisc/display/fbdev/funcs.c Tue Mar 6 01:50:55 2001
@@ -66,7 +66,7 @@
is a sync or blank is not established.
The interworking between the interfaces is even
- worse -- GGI sheilds the user from knowing about
+ worse -- GGI shields the user from knowing about
scandoubling/pixeldoubling. Luckily we have
the fbcon fix info. Unluckily we don't know
for sure how the counter relates to the fix info,
@@ -120,7 +120,7 @@
/* Now it gets ugly. */
/* Punt!
We're going to assume that counter is in pixels for now.
- Which, is most likely wrong. But to use the timing
+ Which is most likely wrong. But to use the timing
info, we would have to do lots of math because fbdev
keeps timings in -- uh -- time units. Those nerds! :)
*/
diff -Ndur libggimisc.orig/doc/docbook/.cvsignore libggimisc/doc/docbook/.cvsignore
--- libggimisc.orig/doc/docbook/.cvsignore Thu Jan 1 01:00:00 1970
+++ libggimisc/doc/docbook/.cvsignore Fri Mar 2 18:16:48 2001
@@ -0,0 +1 @@
+Makefile.in
diff -Ndur libggimisc.orig/doc/docbook/libggimisc-book.sgml
libggimisc/doc/docbook/libggimisc-book.sgml
--- libggimisc.orig/doc/docbook/libggimisc-book.sgml Sat Mar 3 01:52:53 2001
+++ libggimisc/doc/docbook/libggimisc-book.sgml Tue Mar 6 01:38:23 2001
@@ -39,7 +39,7 @@
<title/Introduction/
<para>
-<firstterm>LibGGIMisc</firstterm> is a a LibGGI extension implementing
+<firstterm>LibGGIMisc</firstterm> is a LibGGI extension implementing
support for a range of hard to categorize features.
</para>
@@ -137,7 +137,7 @@
<title>Description</title>
<para>
-Though currently only implented via matroxfb, this function
+Though currently only implemented via matroxfb, this function
will retrieve the current position of the raster beam on a display
that uses a cathode ray tube, or resembles such internally. Because
it has not been implemented and put into widespread use, there may
@@ -216,9 +216,10 @@
<title>Return value</title>
<para><ReturnValue/0/ for OK, otherwise an error code. In the event that
there is an error, it is most likely that the implementation on the
-given target is limited. In this case, the parameters <parameter/x/,<parameter/y/
will be assigned values equal to one of the above macros, which should
-work on the target, supposing using those values actually accomplishes what
-you want to do.
+given target is limited. In this case, the parameters
+<parameter/x/,<parameter/y/ will be assigned values equal to one of the above
+macros, which should work on the target, supposing using those values actually
+accomplishes what you want to do.
</para>
</refsect1>
diff -Ndur libggimisc.orig/doc/ggimisc.txt libggimisc/doc/ggimisc.txt
--- libggimisc.orig/doc/ggimisc.txt Fri Mar 2 23:41:13 2001
+++ libggimisc/doc/ggimisc.txt Mon Mar 5 23:48:52 2001
@@ -1,5 +1,5 @@
-LibGGIMisc is a a LibGGI extension implementing
+LibGGIMisc is a LibGGI extension implementing
support for a range of hard to categorize features.
LibGGIMisc consists of a main library (<filename/libggimisc.so/) and a few
diff -Ndur libggimisc.orig/doc/man/.cvsignore libggimisc/doc/man/.cvsignore
--- libggimisc.orig/doc/man/.cvsignore Thu Jan 1 01:00:00 1970
+++ libggimisc/doc/man/.cvsignore Fri Mar 2 18:16:48 2001
@@ -0,0 +1 @@
+Makefile.in
diff -Ndur libggimisc.orig/doc/retrace.txt libggimisc/doc/retrace.txt
--- libggimisc.orig/doc/retrace.txt Fri Mar 2 18:16:48 2001
+++ libggimisc/doc/retrace.txt Tue Mar 6 01:31:28 2001
@@ -24,10 +24,10 @@
3. If using the RTC, it has to be set up for one-shot mode and reset
on every trigger, as well as calibrated with the hardware, the way
the PC speaker driver does it, but fortunately at a much lower
- frequency :-). The periodic RTC freqs don't yeild good results
+ frequency :-). The periodic RTC freqs don't yield good results
because they are not flexible enough.
- 4. Very few cards seem to allow you to read the CRTC address counter
+ 4. Very few cards seem to allow to read the CRTC address counter
back out of the card. This being the case, the only way to know
when blanking is asserted is to calibrate with the vsync pulse via
polling the "retrace active" registers, and calculate the amount of
@@ -88,7 +88,7 @@
Anyway, using the vertical non-display has all but eliminated this
last little problem. I think the main reason for this is the huge
amount of extra time you get to write out your data. Here are the
- timing comparrisons on a VGA, according to Wilton:
+ timing comparisons on a VGA, according to Wilton:
Vertical Retrace: 0.064 Milliseconds
@@ -97,7 +97,7 @@
(timings based on 640x480)
In computer terms, that's a big difference!!! 1.366 Milliseconds extra
- for writing out that doublebuffer - awsome.
+ for writing out that doublebuffer - awesome.
The price comes in the form of more complex code. This is because
unlike the vertical retrace, there is no VGA status register that we
@@ -113,8 +113,8 @@
This means all we have to do is time how long it takes for a
horizontal retrace to occur, and store this value as a trigger. When
- the the Display Enable is disabled (1) for longer than our trigger
- value (which we double -just to be sure) then we know that the
+ the Display Enable is disabled (1) for longer than our trigger
+ value (which we double - just to be sure) then we know that the
Vertical Non-display has occurred, and can safely write to video
memory without risk of getting caught in the middle of a redraw. Cool
eh?
diff -dur libggi.orig/programs/check/speed.c libggi/programs/check/speed.c
--- libggi.orig/programs/check/speed.c Mon Dec 18 07:11:44 2000
+++ libggi/programs/check/speed.c Mon Mar 5 23:03:28 2001
@@ -19,7 +19,11 @@
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
+
#include <sys/times.h>
+#ifndef CLK_TCK
+#include <time.h>
+#endif
#include <ggi/ggi.h>
unlike glibc-2.1.x, glibc-2.2(.2-1) has switched from C99 to POSIX times.
Did not try the AC_HEADER_TIME dance yet.
