Re: 2D Acceleration not used using ATI Rage Mobility P/M AGP 2x

2003-11-07 Thread Alex Deucher 
try removing the videoram line from your config.  the driver will
detect videoram fine.

Alex

--- Salvio Sergi <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I posted this on dri-users and have been suggested to post here...
> 
> Everything starts fine with no errors (as you can see from the logs).
> 
> The problem I have is that I don't think I have 2D acceleration.
> 
> The simple test I do is to just drag a window on the screen... the
> redraw is extremely slow and the CPU is maxed out (only when I move
> the windows)
> 
> This means (I guess) that I do not have 2D acceleration. You can
> actually see the redraw happening... really slow.
> 
> To add to that, at the time I had windows 2000 server installed on
> that machine (Laptop Dell Latitude CPxj, now a Linux only system)
> the windows could be moved around really fast so it can't be a
> limitation of the hardware.
> 
> CPU is a pentium 3 some 600Mhz - 512 MB memory - less than 200MB
> used by the system, no swap space used.
> 
> I have also tried other colour depths as well as different screen
> resolutions (I think I tried all possible permutations): always
> with the same results.
> 
> I finally tried "Accel" "on" and "off" with no apparent consequence
> (same speed)
> 
> 
> Thanks,
> Salvio
> > # XFree86 4 configuration created by redhat-config-xfree86
> 
> Section "ServerLayout"
>   Identifier "Default Layout"
>   Screen  0  "Screen0" 0 0
>   InputDevice"Mouse0" "CorePointer"
>   InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
> 
> Section "Files"
> 
> # RgbPath is the location of the RGB database.  Note, this is the
> name of the 
> # file minus the extension (like ".txt" or ".db").  There is normally
> # no need to change the default.
> # Multiple FontPath entries are allowed (they are concatenated
> together)
> # By default, Red Hat 6.0 and later now use a font server independent
> of
> # the X server to render fonts.
>   RgbPath  "/usr/X11R6/lib/X11/rgb"
>   FontPath "unix/:7100"
> EndSection
> 
> Section "Module"
>   Load  "dbe"
>   Load  "extmod"
>   Load  "fbdevhw"
>   Load  "glx"
>   Load  "record"
>   Load  "freetype"
>   Load  "type1"
>   Load  "dri"
> EndSection
> 
> Section "InputDevice"
> 
> # Specify which keyboard LEDs can be user-controlled (eg, with
> xset(1))
> # Option  "Xleds" "1 2 3"
> # To disable the XKEYBOARD extension, uncomment XkbDisable.
> # Option  "XkbDisable"
> # To customise the XKB settings to suit your keyboard, modify the
> # lines below (which are the defaults).  For example, for a non-U.S.
> # keyboard, you will probably want to use:
> # Option  "XkbModel"  "pc102"
> # If you have a US Microsoft Natural keyboard, you can use:
> # Option  "XkbModel"  "microsoft"
> #
> # Then to change the language, change the Layout setting.
> # For example, a german layout can be obtained with:
> # Option  "XkbLayout" "de"
> # or:
> # Option  "XkbLayout" "de"
> # Option  "XkbVariant""nodeadkeys"
> #
> # If you'd like to switch the positions of your capslock and
> # control keys, use:
> # Option  "XkbOptions""ctrl:swapcaps"
> # Or if you just want both to be control, use:
> # Option  "XkbOptions""ctrl:nocaps"
> #
>   Identifier  "Keyboard0"
>   Driver  "keyboard"
>   Option  "XkbRules" "xfree86"
>   Option  "XkbModel" "pc105"
>   Option  "XkbLayout" "gb"
> EndSection
> 
> Section "InputDevice"
>   Identifier  "Mouse0"
>   Driver  "mouse"
>   Option  "Protocol" "PS/2"
>   Option  "Device" "/dev/input/mice"
>   Option  "ZAxisMapping" "4 5"
>   Option  "Emulate3Buttons" "no"
> EndSection
> 
> Section "InputDevice"
> 
> # If the normal CorePointer mouse is not a USB mouse then
> # this input device can be used in AlwaysCore mode to let you
> # also use USB mice at the same time.
>   Identifier  "DevInputMice"
>   Driver  "mouse"
>   Option  "Protocol" "IMPS/2"
>   Option  "Device" "/dev/input/mice"
>   Option  "ZAxisMapping" "4 5"
>   Option  "Emulate3Buttons" "no"
> EndSection
> 
> Section "Monitor"
>   Identifier   "Monitor0"
>   VendorName   "Monitor Vendor"
>   ModelName"Unknown monitor"
>   HorizSync31.5 - 37.9
>   VertRefresh  50.0 - 70.0
>   Option  "dpms"
> EndSection
> 
> Section "Device"
>   Identifier  "Videocard0"
>   Driver  "ati"
>   VendorName  "Videocard vendor"
>   BoardName   "ATI Rage Mobility"
>   VideoRam8192
> EndSection
> 
> Section "Screen"
>   Identifier "Screen0"
>   Device "Videocard0"
>   Monitor"Monitor0"
>   DefaultDepth 16
>   SubSection "Display"
>   Depth 16
>   Modes"1024x768"
>   EndSubSection
> EndSection
> 
> Section "DRI"
>   Group0
>   Mode 0666
> EndSection
> 


__

Re: "nv" driver obscurities...

2003-11-07 Thread Mark Vojkovich 
On Fri, 7 Nov 2003, Mike A. Harris wrote:

> Everywhere 
> in the driver hex values are given premultiplied by 4 it seems, 
> and specified as VALUE/4.

   The register pointers are dword pointers.  The register offsets
are byte offsets.  They are written as VALUE/4 so that I can grep
for VALUE.  This is done so that it's easier for me to maintain.
Converting everything to dword offsets will make my job more
difficult.

   I'm not sure why you are bringing this up.  I would think it
would be obvious that since I am maintaining it, it would be in
the form that is easiest for me to maintain.

Mark.


___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: Xfbdev error

2003-11-07 Thread David Dawes 
On Fri, Nov 07, 2003 at 04:39:43PM -, jassi  brar wrote:
>Hi all,
>I m building kdrive/Xfbdev,Xipaq (XFree86-4.3.99.14) server. I just amaze why its 
>size is so big(Xfbdev-3.2MB, Xipaq-3.3MB)... when it is supposed to be light-weight.

Does your target platform have shared libraries?  I find Xfbdev to be less
than 1MB on platforms with shared libraries.  Check the sizes of the pieces
that get linked together to make Xfbdev.

David
-- 
David Dawes X-Oz Technologies
www.XFree86.org/~dawes  www.x-oz.com
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: *Need* to upgrade fontconfig in XFree86 cvs.

2003-11-07 Thread David Dawes 
On Fri, Nov 07, 2003 at 07:48:35PM -0600, Boris wrote:
>The latest fontconfig in cvs is old and has problems. After reading posts in reguard 
>to the fontconfig in cvs, It has problems with some truetype fonts and fc-cache 
>segmentation faults during startup on systems. Fontconfig in cvs is 1.0.2 while the 
>latest is 2.2.0. Could we please update fontconfig in the xfree cvs?

If you read my previous reply (you are subscribed to this list
aren't you?), you'd see that the fontconfig in the current XFree86
CVS is 2.1.0.  I committed a fix today for the segfault caused by
the return value of getenv("HOME") not being checked.  If you have
other specific bugs that need to be fixed, please post details so
that the fixes for them can be identified and included.

We are too far into our release cycle to be importing a new version
without separating out bug fixes from other stuff.  The time for that
was over three weeks ago.

David
-- 
David Dawes
developer/release engineer  The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

"nv" driver obscurities...

2003-11-07 Thread Mike A. Harris 
I'm curious about some of the obscurity in the "nv" driver.  In 
particular, almost everywhere in the driver, registers are 
addressed numerically, and not by symbolic names.  That on it's 
own is obscure enough to make things difficult to tell what's 
going on, but we know the deal with Nvidia documentation well 
enough, so I won't bother to worry about that much...

Various people have commented though about certian obscurities 
like the following being rather odd:

chip->Rop= (RivaRop   *)&(chip->FIFO[0x/4]);

Why "0x/4" and not just plain "0x"?  Everywhere 
in the driver hex values are given premultiplied by 4 it seems, 
and specified as VALUE/4.

Was that done just to intentionally obfuscate the driver source 
further?  Or was the original driver (or current driver for that 
matter) actually maintained elsewhere with real symbolic names 
and whatnot, and then obfuscation scripts ran over them prior to 
committing to the XFree86 tree?

Would cleanups that remove this obfuscation and make the driver 
more readable be considered useful, and potentially accepted?  Or 
is there some other reason I'm missing as to why the driver is so 
obfuscated?


-- 
Mike A. Harris

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

*Need* to upgrade fontconfig in XFree86 cvs.

2003-11-07 Thread Boris 



The latest fontconfig in cvs is old and has 
problems. After reading posts in reguard to the fontconfig in cvs, It has 
problems with some truetype fonts and fc-cache segmentation faults during 
startup on systems. Fontconfig in cvs is 1.0.2 while the latest is 2.2.0. Could 
we please update fontconfig in the xfree cvs?

2D Acceleration not used using ATI Rage Mobility P/M AGP 2x

2003-11-07 Thread Salvio Sergi 
Hi,

I posted this on dri-users and have been suggested to post here...

Everything starts fine with no errors (as you can see from the logs).

The problem I have is that I don't think I have 2D acceleration.

The simple test I do is to just drag a window on the screen... the
redraw is extremely slow and the CPU is maxed out (only when I move
the windows)
This means (I guess) that I do not have 2D acceleration. You can
actually see the redraw happening... really slow.
To add to that, at the time I had windows 2000 server installed on
that machine (Laptop Dell Latitude CPxj, now a Linux only system)
the windows could be moved around really fast so it can't be a
limitation of the hardware.
CPU is a pentium 3 some 600Mhz - 512 MB memory - less than 200MB
used by the system, no swap space used.
I have also tried other colour depths as well as different screen
resolutions (I think I tried all possible permutations): always
with the same results.
I finally tried "Accel" "on" and "off" with no apparent consequence
(same speed)
Thanks,
Salvio
# XFree86 4 configuration created by redhat-config-xfree86

Section "ServerLayout"
Identifier "Default Layout"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "Files"

# RgbPath is the location of the RGB database.  Note, this is the name of the 
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath  "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection

Section "Module"
Load  "dbe"
Load  "extmod"
Load  "fbdevhw"
Load  "glx"
Load  "record"
Load  "freetype"
Load  "type1"
Load  "dri"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#   Option  "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#   Option  "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#   Option  "XkbModel"  "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#   Option  "XkbModel"  "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#   Option  "XkbLayout" "de"
# or:
#   Option  "XkbLayout" "de"
#   Option  "XkbVariant""nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#   Option  "XkbOptions""ctrl:swapcaps"
# Or if you just want both to be control, use:
#   Option  "XkbOptions""ctrl:nocaps"
#
Identifier  "Keyboard0"
Driver  "keyboard"
Option  "XkbRules" "xfree86"
Option  "XkbModel" "pc105"
Option  "XkbLayout" "gb"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "PS/2"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5"
Option  "Emulate3Buttons" "no"
EndSection

Section "InputDevice"

# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier  "DevInputMice"
Driver  "mouse"
Option  "Protocol" "IMPS/2"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5"
Option  "Emulate3Buttons" "no"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Unknown monitor"
HorizSync31.5 - 37.9
VertRefresh  50.0 - 70.0
Option  "dpms"
EndSection

Section "Device"
Identifier  "Videocard0"
Driver  "ati"
VendorName  "Videocard vendor"
BoardName   "ATI Rage Mobility"
VideoRam8192
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor"Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes"1024x768"
EndSubSection
EndSection

Section "DRI"
Group0
Mode 0666
EndSection


XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2)
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] 
Build Date: 27 February 2003
Build Host: porky.devel.redhat.com
 
Before reporting problems, check http://www.XFree86.Org/
to make sure that you

Viewport behaviour

2003-11-07 Thread David Dawes 
I've just committed fixes to make the initial viewport behaviour match
the documented behaviour.  This affects the initial viewport position
when the initial physical screen resolution is different from the virtual
resolution.  The documented behaviour (from XF86Config(5)) is:

   ViewPort  x0 y0
  This  optional  entry sets the upper left corner of
  the initial display.  This is  only  relevant  when
  the virtual screen resolution is different from the
  resolution of the  initial  video  mode.   If  this
  entry  is  not given, then the initial display will
  be centered in the virtual display area.


This parameter was being ignored, and the initial display viewport
always set to (0,0).

If the (0,0) default is preferable to a centred viewport, I can switch
that back and update the man page accordingly.  Given that it has been
working like that for a while, it might be.

David
-- 
David Dawes
developer/release engineer  The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: Upgrade fontconfig in cvs.

2003-11-07 Thread David Dawes 
On Thu, Nov 06, 2003 at 12:27:44PM -0500, David Dawes wrote:
>On Thu, Nov 06, 2003 at 10:28:37AM -0600, Boris wrote:
>>It seems the fontconfig in cvs is very old (1.0.2) and needs to be upgraded to 
>>2.2.0. Reading varios emails and posts, it seems the older fontconfig has problems 
>>with some TrueType fonts and the 2.2.xx files the problem. Also the fc-cache v1.0.2 
>>crashes (segmentation fault) when run during system startup where as 2.2.0 does not 
>>have that problem. Any possible way we could get the latest fontconfig into the 
>>xfree86 cvs?
>
>The fontconfig version in the current XFree86 CVS is 2.1.0.  For
>whatever reason, various version strings were not updated when the
>version got bumped from 1.x to 2.x.
>
>Bug fixes are welcome, but the feature freeze date was about three weeks
>ago.

I have found/fixed/committed what is likely the segfault cause -- the
result of getenv("HOME") not being checked before being dereferenced.

David
-- 
David Dawes
developer/release engineer  The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Xfbdev error

2003-11-07 Thread jassi brar 
Hi all,
I m building kdrive/Xfbdev,Xipaq (XFree86-4.3.99.14) server. I just amaze why its size 
is so big(Xfbdev-3.2MB, Xipaq-3.3MB)... when it is supposed to be light-weight.

here are my host.def and cross.def file.

host.def

#define KDriveXServer YES

#define XiPAQH3500Server YES

#define KdriveServerExtraDefines -DITSY -DMAXSCREENS=2

#define TinyXServerYES

#define CrossCompilingYES

#define TouchScreenYES

#define ItsyCompilerBugYES

#undef  BuildRandR

#define BuildRandRYES

#define BuildXInputLibYES

#define ProjectRoot/usr/X11R6

#define EtcX11DirectoryProjectRoot/etc

#define Freetype2Dir  $(TOP)/extras/freetype2

#define Freetype2LibDir$(TOP)/exports/lib

#define BuildXTrueTypeYES

#define BuildScreenSaverExtYES

#define BuildScreenSaverLibraryYES

#define SharedLibXss  YES

#define ServerXdmcpDefines

#define XfbdevServer  YES

#define XipaqServerYES

#define HasLibpng NO





cross.def
*
#undef i386Architecture

#define Arm32Architecture

#undef OptimizedCDebugFlags

#define OptimizedCDebugFlags-O2 -g

#define ServerCDebugFlags  -O2 -g

#undef StandardDefines

#define StandardDefines -Dlinux -D__arm__ -D_POSIX_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE 
-DX_LOCALE

#define StdIncDir /opt/host/armv4l/armv4l-unknown-linux/include

#define PreIncDir

#undef PostIncDir

#define PostIncDir /opt/host/armv4l/lib/gcc-lib/armv4l-unknown-linux/2.95.2/include

#undef CcCmd

#define CcCmd /opt/host/armv4l/bin/armv4l-unknown-linux-gcc -pipe

#define DoRanlibCmd YES

#define RanlibCmd  /opt/host/armv4l/bin/armv4l-unknown-linux-ranlib

#define HasCplusplus YES

#undef CplusplusCmd

#define CplusplusCmd /opt/host/armv4l/bin/armv4l-unknown-linux-g++ -pipe

#undef ExtraLoadFlags

#define ExtraLoadFlags

#define FbNoPixelAddrCode

#undef TermcapLibrary

#define TermcapLibrary -ltermcap

#undef LdPostLib

#define LdPostLib  -L /opt/host/armv4l/lib

#undef ExtensionOSDefines

#define ExtensionOSDefines

#define ServerXdmcpDefines  /**/

#define ModuleArCmd  /opt/host/armv4l/bin/armv4l-unknown-linux-ar

#define ModuleAsCmd /opt/host/armv4l/bin/armv4l-unknown-linux-as

#define ModuleLdCmd  /opt/host/armv4l/bin/armv4l-unknown-linux-ld

#define LdCmd   /opt/host/armv4l/bin/armv4l-unknown-linux-ld

#define CppCmd   /opt/host/armv4l/bin/armv4l-unknown-linux-cpp

#include "cross.rules"


Can anybody suggest me where am i missing(overdoing) something?

Regards,
Jassi

(no subject)

2003-11-07 Thread guillelx 
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: SPLIT_WC_REGIONS - anyone out there?

2003-11-07 Thread Egbert Eich 
Alexander Stohr writes:
 > Hello,
 > 
 > i stumbled across the above mentioned define and
 > related code in the XFree86 sources (lnx_video.c).
 > 
 > comparing X4.1.0 and X4.3.0 i found that the
 > condtitnal coding of "if (base % size)" has
 > vanished at some point in time and the handling
 > is now hardcoded at this code location.

The old code was broken. It created to many split areas which
were unnecessary.

 > 
 > to my best knowledge that coding is related to
 > maybe the 3Dfx PCI memory regions layout with
 > a single mixed framebuffer and register mapping.

No, this code is entirely generic.
A WC region needs to be a power of 2. If it is not the range
has to be split up and subdevided.

 > 
 > is any developer out there that is willing to
 > describe the main points of that design in a
 > few words. i am asking for that because i have
 > had a case where the split code went into action
 > despite any need and even the PCI range was a
 > power of two. so in theory it should not happen.

Can you give an example please?

 > 
 > before popping up with any general solution
 > i just wanted to make sure that i got the right
 > idea of that code. to my understanding current
 > mtrr implementations might be more flexible 
 > than it is assumed in the existing code.
 > 

I thought I had the most general solution. If you
show me an example where the code doesn't do the
right thing I'll investiagte.

Egbert.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Doubt in X11

2003-11-07 Thread Kumar P. 
Hello All,
  My apologies, if this is not the forum to
ask this question. I created a window using
XCreateWindow and set attributes.event_mask to
ButtonReleaseMask alone. But the window is not
receiving the ButtonRelease events. It is receiving
the ButtonRelease event, if ButtonPressMask is also
selected (or) its parent window has
OwnerGrabButtonMask. Is there any other way to receive
ButtonRelease event alone? 

Thanks,
Arun


__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: Upgrade fontconfig in cvs.

2003-11-07 Thread Mike A. Harris 
On Thu, 6 Nov 2003, Boris wrote:

>Date: Thu, 6 Nov 2003 10:28:37 -0600
>From: Boris <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Reply-To: [EMAIL PROTECTED]
>Content-Type: multipart/alternative;
>   boundary="=_NextPart_000_0005_01C3A450.BD38C8A0"
>Subject: Upgrade fontconfig in cvs.
>
>It seems the fontconfig in cvs is very old (1.0.2) and needs to
>be upgraded to 2.2.0. Reading varios emails and posts, it seems
>the older fontconfig has problems with some TrueType fonts and
>the 2.2.xx files the problem. Also the fc-cache v1.0.2 crashes
>(segmentation fault) when run during system startup where as
>2.2.0 does not have that problem. Any possible way we could get
>the latest fontconfig into the xfree86 cvs?

To avoid the SEGV, run fc-cache as: HOME=/ fc-cache

>btw. I downloading it from anoncvs and then "make World".

I recommend just using the upstream fontconfig instead.  It's 
easier to stay current that way, and to update it separately.

Wouldn't hurt of course though to update the included fontconfig 
also, it does have many stability, performance and other 
improvements.  Might be considered too late at this point though, 
but most Linux and other OS distributions I think ship the newer 
fontconfigs for quite a while now, so it shouldn't be too hard to 
find prebuilt packages for many OS's also.

Take care,
TTYL



-- 
Mike A. Harris

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel