Re: [Xpert]Support for S3 Savage4 in 4.2.0

[Alexey Dokuchaev]

On Wed, Aug 21, 2002 at 09:34:14PM -0400, Kevin Brosius wrote:
> Alexey Dokuchaev wrote:
> > 
> > 
> > On Tue, Aug 20, 2002 at 06:45:34PM -0400, Kevin Brosius wrote:
> > > Alexey Dokuchaev wrote:
> > > >
> > > >
> > > > Hi, Xperts!
> > > >
> > > > I've build XFree86 4.2.0 from FreeBSD ports, nice and clean, however,
> > > > all I was able to get on my S3 Savage4 card is 640x480.  This is kinda
> > > > frustrating, not to say more.
> > > >
> > > > What is current situation with support of this chip in X?  I think there
> > > > should really be no problems, since specs are generally available (are
> > > > they?).
> > > >
> > > > Thanks.
> > >
> > > What makes you say that?  Presently, S3 specs are available under NDA
> > > only, although they allow source code release of drivers developed using
> > > them.
> > 
> > Uhm, so what is this stuff: http://keithp.com/~keithp/download/savage/ ?
> > I haven't take a look at it, but it looks like some specs to me.
> > 
> > ./danfe
> 
> Good question.  I'm presently unable to open that link.  Is it correct?

It's probably because Keith made those files inaccessible.

./danfe

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

Re: [Xpert]Re: Savage4 Specs (Was: Support for S3 Savage4 in 4.2.0)

[Kevin Brosius]

Keith Packard wrote:
> 
> 
> 
> Around 12 o'clock on Aug 21, =?iso-8859-1?Q?Jos=E9?= Fonseca wrote:
> 
> > Keith, I assume that you have received permission to redistribute these
> > documents. Do you think that the BCI tech ref could be also
> > redistributable? (Max Lingua already has that one).
> 
> I really don't recall where those documents came from; it was long before I
> joined the XFree86 project, so I'm sure I didn't sign any kind of NDA for
> them.  Given what I now know about S3's policy, I suspect they were
> inappropriately redistributed at the time, so I've made them inaccessible
> again.
> 
> I'd forgotten they were on my web site.  Too much disk space can be a
> dangerous thing.  I was under the impression that XFree86 had an NDA with
> S3 covering this documentation.  If so, you need only apply for
> "membership" in XFree86.  "Membership" is a formal relationship with
> XFree86 which permits the redistribution of material covered by various
> old NDAs that XFree86 used to have with hardware manufacturers; most
> current vendors use other methods to keep their designs private.
> 
> Keith PackardXFree86 Core TeamHP Cambridge Research Lab


Hi Keith,
  Sounds reasonable.  Personally, I have documents from S3 (prior to
their being purchased by Via) which I acquired outside an NDA.  I
consider them to be freely redistributable.  Since that time I contacted
S3Graphics/Via and was informed that an NDA was required, but that
source code was distributable (the NDA is _a lot_ more wordy than
this!)  So, anything acquired after that date I consider only sharable
with people under an S3Graphics NDA, or those who signed an S3 NDA and
still consider it binding (xfree86.)

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

[Xpert]Re: [I18n]drawing keysyms on screen

[Bharathi S]

On 22 Aug 2002, Mohammed Sameer wrote:

> if so please direct me to the correct one
  
  List:  [EMAIL PROTECTED]

> for example when it receives the key A it should convert it to a "0x05c"
> That's nt the problem but the problem is how to convert the "0x05c" to a

 In the X-Window system, X server generates either KeyPressed or
 KeyRelease event when user presses the key or releases the
 key and send the event to the application. The generated events
 contains keycodes and keysyms. For translating meaningful
 characters from the keycode generated by the keyboard envoles mainly 
 two steps.

 The first step involves translating the keycodes which is hardware
 DEPENDENT to a symbolic name known as keysym which is hardware 
 INDEPENENT. * The second step involves converting the keysym to an 
 ASCII code that can be used for displaying, saving in files or buffers.

 In order to provide Native language support, we can add one more step
 to the above to steps to convert Eng to Native.

Bye :)
-- 
--==| Bharathi S | BSB-364 DONLab | IIT-Madras |==--
Leaving ripe fruits the raw he eats
Who speaks harsh when sweet words suits.
*In Tirukkural of Holy Tamil poet Tiruvalluvar.

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

Re: [Xpert]Support for S3 Savage4 in 4.2.0

[Kevin Brosius]

Alexey Dokuchaev wrote:
> 
> 
> On Tue, Aug 20, 2002 at 06:45:34PM -0400, Kevin Brosius wrote:
> > Alexey Dokuchaev wrote:
> > >
> > >
> > > Hi, Xperts!
> > >
> > > I've build XFree86 4.2.0 from FreeBSD ports, nice and clean, however,
> > > all I was able to get on my S3 Savage4 card is 640x480.  This is kinda
> > > frustrating, not to say more.
> > >
> > > What is current situation with support of this chip in X?  I think there
> > > should really be no problems, since specs are generally available (are
> > > they?).
> > >
> > > Thanks.
> >
> > What makes you say that?  Presently, S3 specs are available under NDA
> > only, although they allow source code release of drivers developed using
> > them.
> 
> Uhm, so what is this stuff: http://keithp.com/~keithp/download/savage/ ?
> I haven't take a look at it, but it looks like some specs to me.
> 
> ./danfe

Good question.  I'm presently unable to open that link.  Is it correct?

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

Re: [Xpert]X return segmentation fault when trying to start it

[pcpa]

Quoting Tino Keitel <[EMAIL PROTECTED]>:

  I suggest compiling XFree86 with the optimization flags, but also with
-g, and run it under the custom gdb at ftp://ftp.xfree86.org/pub/xpert/gdb
  Do it from a remote computer.

  It is dependant on your compiler version, snapshots may have bugs. But
most times I found this sort of problem and could figure out what was wrong
(sometimes I just find the chunk of code that is breaking and rewrite it...),
it was some program error, like writting past the start/end of a stack
buffer, uninitialized data that happens to have the same contents after
some time (anything that was left in the heap after malloc/free calls), etc.

> > Seem strange to me that a software like XFree86 cannot use
> optimization 
> > FLAGS durring compile time. Here is what I used as optimization -->
> "-O2 
> > -march=i686 -funroll-loops" and XFree86 fail. Again without the
> previous 
> > optimization FLAGS, all run ok.
> > 
> > For me, this mean that XFree86 cannot be compiled to get advantage of
> i686 
> > CPU architecture :((
> 
> I would think about this in a different way. In my point of view, this
> is a code generation bug in the compiler (gcc?). In a perfect world,
> any piece of source code should compile and work perfectly even with
> the most exotic optimization flags turned on.
> 
> I also had this problem with other software. Most of the time I could
> determine _one_ source file that will be broken with _one_ certain
> optimization option. I would at first try to build without the
> -funroll-loops option.
> 
> Regards,
> Tino
> 
> -- 
> [EMAIL PROTECTED]
> dipl.-inf.Innominate Security Technologies AG
> software engineer   networking people
> tel: +49.30.6392-3308  http://www.innominate.com/
> ___
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert

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

Re: [Xpert]Possible bug in xf86bigfont.c

[Marc Aurele La France]

On 20 Aug 2002, Christopher Keller wrote:

> I've tracked down a situation which I believe to be a bug in XFree86.
> I'm using RedHat 7.3, version 4.2.0-8.

> The gist is a null pointer exception in line 667 & 668 of xf86bigfont.c.

> pFont->info.props is null and it's being assigned without checking
> whether it's null or not. I'm not sure if the simple answer is to wrap
> the assign statements in a null pointer check or if it's more complex
> than that.

> I'm not an X developer, but I'd love to assist in the confirmation and
> patch of this particular error, as it's causing me a huge headache right
> now. I've been hanging out on #xfree86-devel, but I see no traffic.

> (gdb) list xf86bigfont.c:667
> 662 xFontProp* prFP;
> 663 int i;
> 664 for (i = 0, pFP = pFont->info.props, prFP =
> (xFontProp *) p;
> 665  i < nfontprops;
> 666  i++, pFP++, prFP++) {
> 667 prFP->name = pFP->name;
> 668 prFP->value = pFP->value;
> 669 if (client->swapped) {
> 670 char tmp;
> 671 swapl(&prFP->name, tmp);
> (gdb) print *pFont
> $5 = {refcnt = 142373721, info = {firstCol = 57392, lastCol = 16914,
> firstRow = 0, lastRow = 0, defaultCh = 0, noOverlap = 0, terminalFont =
> 0, constantMetrics = 0, constantWidth = 0, inkInside = 0, inkMetrics =
> 0, allExist = 0, drawDirection = 0, cachable = 1, anamorphic = 0,
> maxOverlap = 0, pad = 0, maxbounds = { leftSideBearing = 2,
> rightSideBearing = 18, characterWidth = 18, ascent = 18, descent = 4,
> attributes = 0}, minbounds = {leftSideBearing = -3, rightSideBearing =
> 1, characterWidth = 4, ascent = -2, descent = -11, attributes = 0},
> ink_maxbounds = {leftSideBearing = 2, rightSideBearing = 18,
> characterWidth = 18, ascent = 18, descent = 4, attributes = 0},
> ink_minbounds = {leftSideBearing = -3, rightSideBearing = 1,
> characterWidth = 4, ascent = -2, descent = -11, attributes = 0},
> fontAscent = 16, fontDescent = 4, nprops = 27, props = 0x0, isStringProp
> = 0x8a439a8 "\001\001\001\001\001\001"}, bit = 0 '\0', byte = 0 '\0',
> glyph = 4 '\004', scan = 1 '\001', format = 512, get_glyphs = 0x8121ee8
> <_fs_get_glyphs>, get_metrics = 0x8122418 <_fs_get_metrics>, unload_font
> = 0x8122726 <_fs_unload_font>, unload_glyphs = 0, fpe = 0x873f2a0,
> svrPrivate = 0x0, fontPrivate = 0x87d32b0, fpePrivate = 0x87d32c0,
> maxPrivate = 1, devPrivates = 0x8a43724}
> (gdb) quit

Humm.  Perhaps a better question to ask is why nprops is non-zero when
props is NULL.  With that in mind, I've gone through the source to ensure
both are kept in sync.  In the process, I tripped over what looks like a
memory leak in the PCF code.  The resulting patch is attached.  Please try
it and report back whether or not it fixes the problem (or creates new
ones).

Thanks.

Marc.

+--+---+
|  Marc Aurele La France   |  work:   1-780-492-9310   |
|  Computing and Network Services  |  fax:1-780-492-1729   |
|  352 General Services Building   |  email:  [EMAIL PROTECTED]  |
|  University of Alberta   +---+
|  Edmonton, Alberta   |   |
|  T6G 2H1 | Standard disclaimers apply|
|  CANADA  |   |
+--+---+
XFree86 Core Team member.  ATI driver and X server internals.



font.diff.gz
Description: Binary data

Re: [Xpert]xfree86-4.2.0 problems on a sony vaio fxa59

[Marc Aurele La France]

On Tue, 20 Aug 2002, Mike Labriola wrote:

> i just compiled xfree86-4.2.0 on my brand new sony vaio fxa59 and i'm having
> some strange issues getting x to start correctly.  here's the quick rundown.

> everything compiled and installed fine, and i'm using the attached XF86Config.
> as you can see from the attached XFree86.0.log file, there are no obvious error
> messages popping up on me...  but instead of getting a nice x screen when i
> 'startx', i get a jagged lined (almost like chain links) and speckled grey
> screen with a little white box in the upper left corner (about 1" square).  this
> is not the "x is running but there's no wm" screen...

> the specs sheet that came with the laptop says it has an ATI 3D RAGE MOBILITY-M1
> and a 15.0" SXGA TFT screen that's supposed to run at 1400x1050.

> now i was completely stumped for a while, but i've actually made a positive
> discovery...  oddly enough, if i plug a monitor into the vga out on the laptop
> and switch the display over to it (which works) and then switch it back to the
> lcd, the lcd works correctly.  now, this is a good thing...  but having to plug
> the thing into a monitor whenever i want to use x kinda defeats the entire
> purpose of a laptop...  ;-)  baby steps in the right direction, though.

Try 'Option "NoCompositeSync"' in the device section.

Marc.

+--+---+
|  Marc Aurele La France   |  work:   1-780-492-9310   |
|  Computing and Network Services  |  fax:1-780-492-1729   |
|  352 General Services Building   |  email:  [EMAIL PROTECTED]  |
|  University of Alberta   +---+
|  Edmonton, Alberta   |   |
|  T6G 2H1 | Standard disclaimers apply|
|  CANADA  |   |
+--+---+
XFree86 Core Team member.  ATI driver and X server internals.

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

Re: [Xpert]Fbdev Server, Matrox card and ARM CATS board problems.

[Michel Dänzer]

On Wed, 2002-08-21 at 11:15, Matthew Allum wrote: 
> 
> I have a framebuffer running fine on top of an old Matrox PCI card (
> mellenium? ) on an ARM based machine with a Linux 2.4.18 kernel and
> Debian unstable.
> 
> Unfortunately when I run either X4.2 with the fbdev driver or a TinyX
> ( kdrive ) server, The X Server comes up but the screen fills with
> garbage.

Can you try to be a bit more specific? Is it random, or a distortion of
how it should look?


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Re: [Xpert]Trident TGUI 9680-1 cannot be used with Jaton nvidia geforce2-MX

[Paul Pikowsky]

I've tried compiling this driver and I am getting errors.  The last line in 
the error messages I get is:

make:***[i810_dma.o] Error 1

My kernel is Red Hat 2.4.18-5

Paul


Original Message Follows
From: Alan Hourihane <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Xpert]Trident TGUI 9680-1 cannot be used with Jaton nvidia 
geforce2-MX
Date: Tue, 20 Aug 2002 08:38:10 +0100
MIME-Version: 1.0
Received: from [204.152.184.37] by hotmail.com (3.2) with ESMTP id 
MHotMailBF2B3E9B002640042A15CC98B82511D80; Tue, 20 Aug 2002 00:45:46 -0700
Received: from public.XFree86.Org (localhost [127.0.0.1])by 
public.xfree86.org (Postfix) with ESMTPid ED1792766E; Tue, 20 Aug 2002 
03:45:17 -0400 (EDT)
Received: from fairlite.demon.co.uk (fairlite.demon.co.uk 
[158.152.52.252])by public.xfree86.org (8.11.6/8.11.6) with ESMTP id 
g7K7cHw43620for <[EMAIL PROTECTED]>; Tue, 20 Aug 2002 00:38:17 -0700 
(PDT)(envelope-from [EMAIL PROTECTED])
Received: (from alanh@localhost)by fairlite.demon.co.uk (8.11.6/8.11.6) id 
g7K7cAg01109for [EMAIL PROTECTED]; Tue, 20 Aug 2002 08:38:10 +0100
>From [EMAIL PROTECTED] Tue, 20 Aug 2002 00:47:34 -0700
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.3.27i
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.0.9
Precedence: bulk
List-Help: 
List-Post: 
List-Subscribe: 
,
List-Id: General X Discussion 
List-Unsubscribe: 
,
List-Archive: 

Try using the trident driver from http://www.xfree86.org/~alanh

Alan.

On Mon, Aug 19, 2002 at 04:43:51 -0700, Paul Pikowsky wrote:
 > This is using XFree86 4.2
 >
 > The monitor light quits flashing as though it is about to get a screen, 
but
 > the screen stays dark.  And, if I try to log on as another user, the 
system
 > hangs and I have to reboot.
 >
 > Paul Pikowsky, [EMAIL PROTECTED]
 > ___
 > Xpert mailing list
 > [EMAIL PROTECTED]
 > http://XFree86.Org/mailman/listinfo/xpert
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Paul Pikowsky1850 Hanover Dr. #43, Davis, CA, 95616, USA 
530-753-6513 [EMAIL PROTECTED] 






_
Send and receive Hotmail on your mobile device: http://mobile.msn.com

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

[Xpert]Re: Savage4 Specs (Was: Support for S3 Savage4 in 4.2.0)

[Keith Packard]

Around 12 o'clock on Aug 21, =?iso-8859-1?Q?Jos=E9?= Fonseca wrote:

> Keith, I assume that you have received permission to redistribute these
> documents. Do you think that the BCI tech ref could be also
> redistributable? (Max Lingua already has that one).

I really don't recall where those documents came from; it was long before I
joined the XFree86 project, so I'm sure I didn't sign any kind of NDA for
them.  Given what I now know about S3's policy, I suspect they were
inappropriately redistributed at the time, so I've made them inaccessible
again.

I'd forgotten they were on my web site.  Too much disk space can be a 
dangerous thing.  I was under the impression that XFree86 had an NDA with 
S3 covering this documentation.  If so, you need only apply for 
"membership" in XFree86.  "Membership" is a formal relationship with 
XFree86 which permits the redistribution of material covered by various 
old NDAs that XFree86 used to have with hardware manufacturers; most 
current vendors use other methods to keep their designs private.

Keith PackardXFree86 Core TeamHP Cambridge Research Lab


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

Re: [Xpert]X return segmentation fault when trying to start it

[Juliusz Chroboczek]

TK> I would think about this in a different way. In my point of view, this
TK> is a code generation bug in the compiler (gcc?). In a perfect world,
TK> any piece of source code should compile and work perfectly even with
TK> the most exotic optimization flags turned on.

Not necessarily.  C9X allows a compiler to make a number of
assumptions about aliasing (about whether two distinct pointers point
at the same data in memory) which older C standards do not allow.

X does a lot of pointer aliasing, and it wouldn't surprise me at all
if it violated some of the restrictions on aliasing in C9X.  Recent
versions of gcc do enable -fstrict-aliasing at higher optimisation
levels.

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

[Xpert]Embedding the JVM into XFree86

[Michael Michael]

Hello all I'm working on embbeding the JVM into
XFree86 previously I embbedded Java int the 3X series
by compiling X as a shared library and loading it into
the JVM. For the 4.X series I'm trying to use it as a
module.

Does the 4.x series support a threaded X server under
Linux ? 

I've tried compiling with the thread switches and it
crashes in the signal handler I can give more detail
later but I'm hoping to get some info on a threaded X
server on linux.

If the module approach does not work I'll go back to a
shared lib X11 which may be useful to other people its
fairly trivial set of changes to the build.

On the Java side I've ported the AWT on top of Swing
so there are no motif dependenices etc. It runs
directly on top of Xlib and in the 3.X series
XServers.

Mike



__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Re: [Xpert]X return segmentation fault when trying to start it

[John Baldwin]

On 20-Aug-2002 Wahib Nackad wrote:
>>What if you use only some of those flags?
> It doesn't work, I've tried the following flags without success:
> -O2 -march=i686 -funroll-loops -pipe
> -O2 -march=i686 -pipe
> -O2 -pipe
> 
> The *only* way to make it work is with "-pipe" only. Binaries and libraries 
> are *not* striped at all.

What about using -O instead of -O2?  In FreeBSD land we have seen some bugs on
i386 with -O2 with both gcc 3.1 and gcc 2.95.x.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

[Xpert]Problem with the mga driver on a G400 and Xv

[Bernd Ernesti]

Hi,

I have a problem to play some divx avis with mplayer on a Matrox G400.

Mplayer uses the Xv extension and that has some problems to display
a few avi, there is no problem when I use the plain x11 interface,
but thats too slow.

Now, I replaced my mga_drv.o with the 4.2.0 one from the matrox ftp server
and the problem  is now gone, so I guess there is a problem with the
mga driver in the xfree cvs tree. Oh, and I also copied the mga_hal_drv.o
to my modules directory, so maybe this could als be a reason why it is
fixed now.

I'm currently using a xfree current source checked out on July, 31st.

If someone wants the avi which cause this problem, then I can put
a few MB of it up on a http server.

Regards,
Bernd

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

[Xpert]Savage4 Specs (Was: Support for S3 Savage4 in 4.2.0)

[José Fonseca]

On Wed, Aug 21, 2002 at 01:33:43PM +0700, Alexey Dokuchaev wrote:
> On Tue, Aug 20, 2002 at 06:45:34PM -0400, Kevin Brosius wrote:
> > Alexey Dokuchaev wrote:
> > > 
> > > Hi, Xperts!
> > > 
> > > I've build XFree86 4.2.0 from FreeBSD ports, nice and clean, however,
> > > all I was able to get on my S3 Savage4 card is 640x480.  This is kinda
> > > frustrating, not to say more.
> > > 
> > > What is current situation with support of this chip in X?  I think there
> > > should really be no problems, since specs are generally available (are
> > > they?).
> > > 
> > > Thanks.
> > 
> > What makes you say that?  Presently, S3 specs are available under NDA
> > only, although they allow source code release of drivers developed using
> > them.
> 
> Uhm, so what is this stuff: http://keithp.com/~keithp/download/savage/ ?
> I haven't take a look at it, but it looks like some specs to me.

These are the specs, all right. I've been trying to get these from S3
for so long that I already had lost hope to ever get them. The only
thing missing is the BCI (Batch Command Interface) programming which is 
addressed in another document.

Keith, I assume that you have received permission to redistribute these
documents. Do you think that the BCI tech ref could be also
redistributable? (Max Lingua already has that one).

José Fonseca
__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

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

Re: [Xpert]X return segmentation fault when trying to start it

[Tino Keitel]

On Tue, Aug 20, 2002 at 20:15:17 +, Wahib Nackad wrote:
> Hello Michel,
> 
> Sorry for the long time before replaying to your message. I was busy to 
> found the problem related to X and finaly found it. It was related to the 
> fact that I've used the following optimization FLAGS to compile it and it 
> look like X don't like it at all. More than that, I cannot compile X with 
> optimization FLAGS and if I do it, then it will segmenfault on the binary. 
> Seem strange to me that a software like XFree86 cannot use optimization 
> FLAGS durring compile time. Here is what I used as optimization --> "-O2 
> -march=i686 -funroll-loops" and XFree86 fail. Again without the previous 
> optimization FLAGS, all run ok.
> 
> For me, this mean that XFree86 cannot be compiled to get advantage of i686 
> CPU architecture :((

I would think about this in a different way. In my point of view, this
is a code generation bug in the compiler (gcc?). In a perfect world,
any piece of source code should compile and work perfectly even with
the most exotic optimization flags turned on.

I also had this problem with other software. Most of the time I could
determine _one_ source file that will be broken with _one_ certain
optimization option. I would at first try to build without the
-funroll-loops option.

Regards,
Tino

-- 
[EMAIL PROTECTED]
dipl.-inf.Innominate Security Technologies AG
software engineer   networking people
tel: +49.30.6392-3308  http://www.innominate.com/
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

[Xpert]Fbdev Server, Matrox card and ARM CATS board problems.

[Matthew Allum]

Hi;

I have a framebuffer running fine on top of an old Matrox PCI card (
mellenium? ) on an ARM based machine with a Linux 2.4.18 kernel and
Debian unstable.

Unfortunately when I run either X4.2 with the fbdev driver or a TinyX
( kdrive ) server, The X Server comes up but the screen fills with
garbage. Id sort of assumed that X running on top of the framebuffer
should just 'work'. Am I missing something ?

I have used fbset in the console to switch between various modes
and all seems fine there. 

Any help greatly appreciated. 

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