On Tue, 4 Mar 2003, Kendall Bennett wrote:
I know I have asked this before, but I can't seem to find my emails and
the mailing list archive does not seem to be responding.
What sort of back/forward compatibility is there with the XFree86 driver
modules? From memory last time I tested this,
Jonathan,
could you also post your XF86Config file? I have some ideas on how
to extend this. It's still kind of a hack, but here goes:
add an option to the radeon driver, say MergedFB or something like
that. when that option is set to TRUE, it would skip the sections of
code that you have
Mike A. Harris [EMAIL PROTECTED] wrote:
I am trying to debug XFree86 at the source code level on Red Hat 8.0 but
not having much like. I force installed gdb-5.1.1-2.0xfree from the RPM
file from Red Hat's site, but when I do 'gdb X' gdb crashes with a
segmentation fault.
gdb-xfree is
On Wed, 5 Mar 2003, Kendall Bennett wrote:
I am trying to debug XFree86 at the source code level on Red Hat 8.0 but
not having much like. I force installed gdb-5.1.1-2.0xfree from the RPM
file from Red Hat's site, but when I do 'gdb X' gdb crashes with a
segmentation fault.
gdb-xfree
On Wed, 5 Mar 2003, Marc Aurele La France wrote:
On Wed, 5 Mar 2003, Kendall Bennett wrote:
Is that the correct approach? Or should we be building modules for each
released version of XFree86 (ie: 4.1.0, 4.1.2, 4.1.3, 4.2.0, 4.2.1 etc)?
The compatibility we strive for (but
I have a patch that updates the Logitech PS/2++ protocol to support
their mice with up to 10 buttons (currently they're only using 8 on the
MX500 and MX700). The PS/2++ protocol now uses 6 bits to identify a
packet instead of 4 as before. Apparently, there's a touchpad protocol
that also used it
Marc Aurele La France [EMAIL PROTECTED] wrote:
The binaries you provide for your driver should be generated against the
earliest (public) XFree86 version that provides the functionality your
driver depends on. If that means 4.1.0, then that means 4.1.0. This does
not absolve you of the
On Wed, 5 Mar 2003, Kendall Bennett wrote:
Marc Aurele La France [EMAIL PROTECTED] wrote:
The binaries you provide for your driver should be generated against the
earliest (public) XFree86 version that provides the functionality your
driver depends on. If that means 4.1.0, then that
On Mon, 3 Mar 2003 10:54:16 -0600
jkjellman [EMAIL PROTECTED] wrote:
I am working on modifying an input driver (or two :-) and am having a
little trouble. I cannot find man pages or other documentation on
internal X calls. For example, xf86Msg, xf86OpenSerial, etc. I have
figured out some
Feigning erudition, Kendall Bennett wrote:
% Marc Aurele La France [EMAIL PROTECTED] wrote:
%
% The binaries you provide for your driver should be generated against the
% earliest (public) XFree86 version that provides the functionality your
% driver depends on. If that means 4.1.0, then
Around 21 o'clock on Mar 5, Mark Vojkovich wrote:
So am I right that when pGC-miTranslate is true, the caller needs
to add the drawable origin to FillSpans, SetSpans and PushPixels?
Yes, the drawable origin must be added into all of the parameters to these
functions when the top-most such
On Wed, 5 Mar 2003, Keith Packard wrote:
Around 21 o'clock on Mar 5, Mark Vojkovich wrote:
So am I right that when pGC-miTranslate is true, the caller needs
to add the drawable origin to FillSpans, SetSpans and PushPixels?
Yes, the drawable origin must be added into all of the
Kendall,
You should also test against different distributions, different
compilers (gcc 3.2.x versus 2.95) and different C libraries.
In particular, modules compiled with gcc 2.95 might not work with
XFree86 compiled with gcc 3.2.x and vice versa..
best
Around 23 o'clock on Mar 5, Mark Vojkovich wrote:
Offscreen pixmaps don't so this has been broken since 3.9.x.
It's obviously not a common case if I'm just seeing this now for
the first time.
The core cursors are all 16x16, which is presumably smaller than the pixmap
code would put in
Around 0 o'clock on Mar 6, Mark Vojkovich wrote:
You don't understand. The shadow framebuffer SetSpans, FillSpans
and PushPixels ARE CURRENTLY TRANSLATING.
Ah. Yes, I was confused. the miext/shadow code doesn't translate the
data on the way to the underlying code (I thought you were
15 matches
Mail list logo
