Re: *** xf86BiosREAD, IA64, Multi-card Init ***

2003-08-27 Thread Mark Vojkovich
On 27 Aug 2003, John Dennis wrote: > > Mark, is there a hardware engineer at nvidia that would be familar with > the VGA timing? Is it possible your VGA is running near or beyond the > limits of the PCI timing requirements? My understanding is the ZX1 is a > very aggressive chipset tuned for high

[XFree86] XFree86 Segmentation Fault (extract problem?)

2003-08-27 Thread L e a n d r o S a l e s
Hi! I'm using Debian woody(unstable version) and I'm trying to install XFree86 4.3. I downloaded Xinstall.sh and run: # sh Xinstall sh -check Checking which OS you're running... uname reports 'Linux' version '2.4.18', architecture 'i686' Object format is 'ELF'. libc version is '6.3.2' (6.3).

Re: *** xf86BiosREAD, IA64, Multi-card Init ***

2003-08-27 Thread John Dennis
On Wed, 2003-08-27 at 06:15, Egbert Eich wrote: > Appearantly there are still issues with VGA framebuffer and emulated > PIO register writes when saving and restoring fonts. These problems > only affect certain cards (so far I've only heared of Nvidia cards). > Mark Vojkovich is sure that these are

Re: RENDER question

2003-08-27 Thread Thomas Winischhofer
Carsten Haitzler (The Rasterman) wrote: > please please please PLEASE! accelerate everythig you can :) > > http://www.rasterman.com/files/render_bench.tar.gz Is it correct to assume, that the image I see over a rainbow-like background is the result of RENDER, and over a grey-shaded background fr

Re: XInput: The device type in XListInputDevices comes up again...

2003-08-27 Thread Claus Matthiesen
On Wed, 2003-08-27 at 19:52, Bryan W. Headley wrote: > Claus Matthiesen wrote: > > Weee! Device interface designing is fun! > > > > As a side note - isn't it rater a failure of the extended input thingy > > in X when neither the application programmer nor the device driver > > programmer think it'

Re: XInput: The device type in XListInputDevices comes up again...

2003-08-27 Thread Bryan W. Headley
Claus Matthiesen wrote: Weee! Device interface designing is fun! As a side note - isn't it rater a failure of the extended input thingy in X when neither the application programmer nor the device driver programmer think it's good enough? La la la la. I can't read you :-) -- .:.

Re: XInput: The device type in XListInputDevices comes up again...

2003-08-27 Thread Claus Matthiesen
Weee! Device interface designing is fun! As a side note - isn't it rater a failure of the extended input thingy in X when neither the application programmer nor the device driver programmer think it's good enough? On Wed, 2003-08-27 at 17:03, Bryan W. Headley wrote: > Claus Matthiesen wrote: > >

Re: XInput: The device type in XListInputDevices comes up again...

2003-08-27 Thread Bryan W. Headley
Claus Matthiesen wrote: - Original Message - From: "Bryan W. Headley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, August 26, 2003 9:43 PM Subject: Re: XInput: The device type in XListInputDevices comes up again... > The problem is, there's a type field and a name field. The

Re: XInput: The device type in XListInputDevices comes up again...

2003-08-27 Thread Egbert Eich
Bryan W. Headley writes: > Egbert Eich wrote: > > That is correct. However Claus was talking about the future - once > > that is fixed. Appearantly toolkits like gnome already do make use > > of the name field. > > Sure, albeit dangerously. They had best not be making decisions based on >

Re: XInput: The device type in XListInputDevices comes up again...

2003-08-27 Thread Claus Matthiesen
- Original Message - From: "Bryan W. Headley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, August 26, 2003 9:43 PM Subject: Re: XInput: The device type in XListInputDevices comes up again... > > > The problem is, there's a type field and a name field. They're not > > > p

Re: *** xf86BiosREAD, IA64, Multi-card Init ***

2003-08-27 Thread Egbert Eich
John Dennis writes: > > I will confess my understanding is weak when it comes to low level bus > interactions, but I'm learning more eveytime I have to tackle these > issues ;-) > > Correct me if I'm wrong, but I thought things like caching and > write-combining are not properties of the P

Re: *** xf86BiosREAD, IA64, Multi-card Init ***

2003-08-27 Thread Egbert Eich
Hi John, thanks on following up on this. John Dennis writes: > > Anytime in the XServer when MMIO was specified as a mapping flag the > ia64 code would have requested non-cached, this is done for all register > mappings and the VGA framebuffer (because write combining was avoided on > banke

Re: RENDER question

2003-08-27 Thread Thomas Winischhofer
Carsten Haitzler (The Rasterman) wrote: > please please please PLEASE! accelerate everythig you can :) > > http://www.rasterman.com/files/render_bench.tar.gz > http://www.rasterman.com/files/imlib2-1.1.0.tar.gz > this might be handy for you as a way of 1. measuring correctness (well so it > "look

Re: Core pointer / keyboard device with 4.3.99.11

2003-08-27 Thread Andrew Bevitt
> There's a bug there that's resulting in them being ignored. The fix is > attached, and I'll commit it tonight. Thanks a bunch it works now, after being built with that patch. > It might be possible to work around it by removing the input devices > from the Layout section and instead specifying

Re: Core pointer / keyboard device with 4.3.99.11

2003-08-27 Thread David Dawes
On Wed, Aug 27, 2003 at 09:01:32AM +1000, Andrew Bevitt wrote: >Hi > >Im working on trying to get the latest snapshot to work after compilation, >I have updated to total cvs and still experience the same problem. > >It seems that update 397 (see below) has made the user incapable of >specifying wh

Re: RENDER question

2003-08-27 Thread The Rasterman
On Tue, 26 Aug 2003 15:50:46 +0200 Thomas Winischhofer <[EMAIL PROTECTED]> babbled: > Since I recently found out that SiS hardware _does_ support per-pixel > alpha-blended bitblits, I could finish the (yet disabled) render > acceleration. > > The only problem I encountered: