[Xpert]Re: Various SiS driver items

2002-02-09 Thread Egbert Eich




  
  So it seems some change to the accel code that occured between 
  4.1.0 and 4.2.0 is overwriting the hardware mouse cursor image in 
  video memory.  That's my best guess anyway.  Any comments from 
  someone who has worked on the code previously would be greatly 
  appreciated.
  

Look at sis530_accel.c, locate the line:
topFB = (pSiS-maxxfbmem = pSiS-FbMapSize - offset) ?
change the = to 

  (--) SIS(0): Unofficial driver (16.01.02) by Thomas Winischhofer
  
  When looking at the source code for the driver I see:
  
  /* TW: ---EGBERT: Remove this before committing !*/
  xf86DrvMsg(pScrn-scrnIndex, X_PROBED,
 Unofficial driver (16.01.02) by Thomas Winischhofer\n);
  
  
  So those lines should probably be removed from sis_driver.c and
  committed to xf-4_2-branch and head also.  Might even be a good
  idea to have Thomas just not include such string at all.  If the
  purpose is to distinguish between official XFree86 driver
  releases and non official, it isn't doing well.  ;o)
  

Indeed I didn't notice this line in the rush to get this driver
out. This can happen - can't it? 

  
  Another minor issue:
  With swcursor enabled, and the problem gone, the output of the X 
  server shows:
  
  (==) SIS(0): Silken mouse enabled
  (II) SIS(0): direct rendering disabled
  (WW) SIS(0): Option swsursor is not used
  (II) Setting vga for screen 0.
  (II) Initializing built-in extension MIT-SHM
  
  So it says swcursor is used, then later that it isn't used.  I 
  couldn't find anywhere in the entire source tree under Xserver 
  with a quick grep that displays the string with the warning, or 
  anything close to it, which was odd.  I presume whatever it is, 
  it builds up the string.  I looked in the code and found the 
  logic that looks for HWcursoe/SWcursor options is setting 
  HWcursor variable internally and not the swcursor variable.  My 
  guess without further examination, is that the driver is only 
  setting the HWcursor variable, and leaving SWcursor variable 
  uninitialized, so when it later prints the various options that 
  are unset - swcursor shows as unset.  A patch is attached which 
  attempts to fix that minor issue, but is untested.
  

There is a very simple answer:
The driver doesn't know an option swsursor only swcursor.

  ===
  
  Another thing I noticed is:
  
  (--) SIS(0): Video BIOS version ËVer  1 detected
  

This is a string returned by the BIOS. 
As this part of the code works well for almost
everybody else I suspect that the driver doesn't
stick to the  VESA conventions.
If anybody feels bothered he/she should complain to
the BIOS Vendor.

Egbert.

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]RE: Xpert -- confirmation of subscription -- request 903874

2002-02-09 Thread Ray-Hon Sun



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 11:16 AM
To: Ray-Hon Sun
Subject: Xpert -- confirmation of subscription -- request 903874


Xpert -- confirmation of subscription -- request 903874

We have received a request from 216.52.27.231 for subscription of your
email address, [EMAIL PROTECTED], to the [EMAIL PROTECTED] mailing
list.  To confirm the request, please send a message to
[EMAIL PROTECTED], and either:

- maintain the subject line as is (the reply's additional Re: is
ok),

- or include the following line - and only the following line - in the
message body: 

confirm 903874

(Simply sending a 'reply' to this message should work from most email
interfaces, since that usually leaves the subject line in the right
form.)

If you do not wish to subscribe to this list, please simply disregard
this message.  Send questions to [EMAIL PROTECTED]
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]NVIDIA drivers on PowerPC

2002-02-09 Thread Isreal Packard



   I hope this is an appropriate question to direct here. I saw a reference 
on Usenet that indicates I might get some direction here. Basically, as a 
complete novice, I'd like to know how to get the display working on my 
GeForce 2?
   Thanks, in advance.

_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Xfree 4.2 and S3 Trio64V2-DX/GX

2002-02-09 Thread Frédéric LE FAUCHEUR

I've installed the new XFree 4.2 on my Linux box (kernel 2.4.17). Before I used the 
XFree 4.1 with the XFree 3.x S3 driver.
My computer is dual boot Windows 98 / Slackware Linux 8.0. When I cold boot the 
machine on Linux, the video screen is divided in many vertical portions. If I boot on 
Windows first and then warm reboot on Linux, the screen is OK. 
I think is about initilisation of the chip but I can't figure it out. 

Fred. 

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]NVIDIA drivers on PowerPC

2002-02-09 Thread Derrik Pates

On Fri, 8 Feb 2002, Isreal Packard wrote:

I hope this is an appropriate question to direct here. I saw a reference
 on Usenet that indicates I might get some direction here. Basically, as a
 complete novice, I'd like to know how to get the display working on my
 GeForce 2?

Well, the complexity of that is going to afffected by a few things. What
type of display are you trying to drive? VGA, or a DVI flat panel? What
version of XFree86 do you have installed? What kernel?

Derrik Pates  |   Sysadmin, Douglas School   |#linuxOS on EFnet
[EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Trident 9397DVD on Gateway Solo 9100

2002-02-09 Thread Vincent Meyer, MD

Hello,

Any progress on the driver for the Trident chip in Gateway laptops?
I saw some posts where it looked like the cause of the problem was 
pinpointed, but haven't seen anything in the changelogs.

It does work with the 4.1.0 driver to some degree with the 4.2.0 
server and related files.

V.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Various SiS driver items

2002-02-09 Thread Thomas Winischhofer


Hi,

could you please send our patches to me?

Thanks.

About the line Unofficial driver by...:

I need to do this for testing, to see what version the people are using
when sending me their logs.

We had a time issue when committing the code to Xfree86 before the
deadline for 4.2, Egbert Eich (who commits on my behalf) seems to have
missed this.

Egbert had to make some minor changes to the accel code for (global)
memory management reasons introduced by my MaxXFbMem option. As soon as
I have received your patches, I will take care of this.

As for the unused options:


 (**) SIS(0): Option SWcursor
 (**) SIS(0): Using SW cursor
 (==) SIS(0): PCI retry enabled
 (==) SIS(0): Fast VRAM enabled
 (==) SIS(0): TurboQueue disabled ...  

 Then later on: (==) SIS(0): Silken mouse enabled
 (II) SIS(0): direct rendering disabled
 (WW) SIS(0): Option swsursor is not used

You see the difference...? sw_S_ursor...

(--) SIS(0): Video BIOS version ËVer  1 detected

This is fixed in my development version, which will be committed soon.
The driver does no more use the BIOS. 


Thomas

-- 
Thomas Winischhofer
Vienna/Austria
mailto:[EMAIL PROTECTED]  *** http://www.webit.com/tw
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]signal handlers SIGALRM

2002-02-09 Thread Garold Scantlen

I'm using 4.1.0
I'm calling XDrawPoint inside a SIGALRM handler
If I do extensive XDraws in main app. while processing SIGALRM
I get a lockup, not a crash or exit, just seems busy running endless loop.
I found no info. stating XDraws were not to be called in sinal handlers.
Is this the case or should I keep debugging ?

Gary
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]signal handlers SIGALRM

2002-02-09 Thread Mark Vojkovich

On Sat, 9 Feb 2002, Garold Scantlen wrote:

 I'm using 4.1.0
 I'm calling XDrawPoint inside a SIGALRM handler
 If I do extensive XDraws in main app. while processing SIGALRM
 I get a lockup, not a crash or exit, just seems busy running endless loop.
 I found no info. stating XDraws were not to be called in sinal handlers.
 Is this the case or should I keep debugging ?
 

   There is a protocol stream.  If the app is putting commands into
the stream and a signal interrupts it and the single handler puts
commands into the stream, this is an error.  You cannot do this.  
If you really need to draw something from the signal handler
you should use a separate display connection to do that so that
it doesn't trash the other one.


Mark.

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert