Re: Accelerated DGA with i810 ?
I've just committed a fix for this. The driver was incorrectly testing for acceleration being enabled when the DGA capabilities get initialised. That's great news! Thanks for that. Do I have to compile the whole CVS tree or there is a way to patch the i810 driver for 4.2.0? Cheerz, Max ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.2.99.902 (4.3.0 RC2) tagged
David Dawes wrote: Have we achieved code freeze? Are there major outstanding issues that are holding us up for the tag date of 27 Feb 2003? There's nothing standing in the way of it at the moment. May I suggest that you (the maintainer, that is) update the PCI ID's once again before a code freeze? The file in use is 4 months old and I added the ID's for the last generation SiS chips one month ago. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Centralize XXXCopyMungedData
Egbert Eich wrote: Just my $0.02: Watch out when centralizing the memory allocation routines, different hardware (ie drivers) use different granularities. Yes. Any functions provided by the core server will have the status of helper functions. Therefore it they don't meet your needs you can replace them with your own. Erm, I know that... :) What I actually meant was if Björn starts patching *drivers* (and that's what his statements sounded like) he'd better take care. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
xrandr status
I've been trying in vain to play with RandR. I posted this to the general XFree list and received no replies, so I'm trying my luck here. I've downloaded CVS, and compiled the Xvesa server, which in theory should support RandR. Here's what I get when I run xrandr: [EMAIL PROTECTED] yan]$ xrandr -q SZ:Pixels Physical Refresh 0320 x 200( 217mm x 163mm ) 1640 x 200( 217mm x 163mm ) 2640 x 350( 217mm x 163mm ) *3640 x 480( 217mm x 163mm ) 4800 x 600( 217mm x 163mm ) 5 1024 x 768( 217mm x 163mm ) 6 1280 x 1024 ( 217mm x 163mm ) Current rotation - normal Current reflection - none Rotations possible - normal left inverted right Reflections possible - X Axis Y Axis OK, so I should be able to do reflections. But when I run [EMAIL PROTECTED] yan]$ xrandr -x -v Server reports RandR version 1.1 The screen goes black for a second, then returns to normal. No reflection. No errors, no unusual happenings. Nothing in the log files anywhere that I can find. Any ideas on what is happening? How do I get reflection working? Any way to generate verbose output to tell me where to start looking? The resize part works fine. I can resize the screen with no problems. I'm not a developer - just an end user, but I need this so I don't mind mucking with code for a bit. If someone can give me some pointers, I'll see what I can do to test/fix it. --Yan -- o /\ /_ o__ o* ~(_) ,/'_ o__ Yan Seiner, PE (_)\(_) ,/'_ o__ o__ Cardinal Engineering, Inc. (_)\(_) ,/'_ ,/'_ http://www.cardinalengineering.com (_)\(_) (_)\(_) spam killer code kpwq1jkcsEzdx39gnkVvgycd15ayqq ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
ATI with cvs
hello, im using the cvs version with the ati driver for my laptop with a ATI mobility 9000 and ( of course ;) i have a few questions.. is the ati driver the correct driver to be using? i know ati support is best for these cards in the cvs version but i best check the basics first. (dont scream at me for this one) can i get accel 3d working? is it currently possible to use the laptops(/gfx cards) monitor out? with the aim of expanding my desktop onto it. thanks dunk fordyce -- http://www.dunkfordyce.co.uk Tagline for Wednesday, February 26, 2003 I'd love to, but there's a disturbance in the Force. dunk fordyce is d1223m @ #linuxhelp @ irc.freenode.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: ATI with cvs
thanks for the speeedy reply *grin* (dont scream at me for this one) can i get accel 3d working? Yes, but you need a recent DRM, either from CVS or from a 2.5 kernel. do you mean from the xfree cvs? or am i completely wrong - i dont think im familiar with DRM /me gets itchy to try a 2.5 kernel -- http://www.dunkfordyce.co.uk Tagline for Wednesday, February 26, 2003 I'd love to go out with you, but I have to floss my cat. dunk fordyce is d1223m @ #linuxhelp @ irc.freenode.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Centralize XXXCopyMungedData
Thomas Winischhofer writes: Egbert Eich wrote: Erm, I know that... :) What I actually meant was if Björn starts patching *drivers* (and that's what his statements sounded like) he'd better take care. OK, sorry, I misunderstood you. Patching individual drivers should be left to their maintainers or at least to somebody who has got HW to test. Egbert. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Centralize XXXCopyMungedData
On Wed, Feb 26, 2003 at 04:30:44PM +0100, Egbert Eich wrote: Thomas Winischhofer writes: Egbert Eich wrote: Erm, I know that... :) What I actually meant was if Björn starts patching *drivers* (and that's what his statements sounded like) he'd better take care. OK, sorry, I misunderstood you. Patching individual drivers should be left to their maintainers or at least to somebody who has got HW to test. And a nice documentation of the new function would help a lot for that. BTW, is there any such documentation for the Render extension, and more precisely the XAA functions. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.2.99.902 (4.3.0 RC2) tagged
Just noticed; The RELNOTES need to have the line FreeType2 updated to version 2.0.6. under Client and Library Updates section removed, since the current FreeType version included is 2.1.1, and this is mentioned under the I18N and Font updates. Ar an 26ú lá de mí 2, scríobh Thomas Winischhofer : [..] -- I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet. -- T. Samant, 29 June 1997 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
Yitzhak, I too am interested in this. I have only seen ":hacks" that require two X servers (one normal and one modified) plus a modified kernel. This is not a very pretty sight to say the least. Please copy myself if you receive any "private" replies as it sounds like we are looking for the same thing. Take care, KJohn - Original Message - From: Yitzhak Bar Geva To: [EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 10:03 AM Subject: Multiple video consoles What is the status of simultaneous multiple video console operation for full multiuser X on one machine?
Re: XFree86 4.2.99.902 (4.3.0 RC2) tagged
On Wed, Feb 26, 2003 at 03:34:04PM +, Aidan Kehoe wrote: Just noticed; The RELNOTES need to have the line FreeType2 updated to version 2.0.6. under Client and Library Updates section removed, since the current FreeType version included is 2.1.1, and this is mentioned under the I18N and Font updates. Thanks, I've just removed the out of date duplicate. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Accelerated DGA with i810 ?
On Wed, Feb 26, 2003 at 10:16:24AM +0100, Max Zaitsev wrote: I've just committed a fix for this. The driver was incorrectly testing for acceleration being enabled when the DGA capabilities get initialised. That's great news! Thanks for that. Do I have to compile the whole CVS tree or there is a way to patch the i810 driver for 4.2.0? The 4.2.0 i810 driver doesn't even support the 845G, so I'm not sure what you mean. I'm assuming you're using the CVS version, and that's where the fix is. If you're not using the CVS version, then you can probably find the patch via cvsweb.xfree86.org. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Accelerated DGA with i810 (works now!)
Hi! first good news: it works! At least vmware does not complain and scrolling is indeed fast. However, I've just started the new X for the first time and did not do much testing. Shall I expect some bugs/issues to appear or RC2 is already reasonably clean? The 4.2.0 i810 driver doesn't even support the 845G, so I'm not sure what you mean. Nope, I was using 4.2.0 from SuSE, which was capable to work with my 845G (probably suse 4.2.0 is patched or whatever), but I've also tried one of the binary releases of 4.2.99. I'm assuming you're using the CVS version, and that's where the fix is. If you're not using the CVS version, then you can probably find the patch via cvsweb.xfree86.org. I did the complete cvs pull and compiled everything from scratch. Took a while :-) Best regards, Max ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Wed, 26 Feb 2003, Yitzhak Bar Geva wrote: What is the status of simultaneous multiple video console operation for full multiuser X on one machine? Someone reported that X works with the multi-head console support in Linux 2.5 kernels. As far as I am concerned, that is the right way to go: get multi-heads working on the console, then run X on top of that. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: Multiple video consoles
Greatly encouraged by your response, thanks! Someone reported that X works with the multi-head console support in Linux 2.5 kernels. I did some searching for multi-head consoles under 2.5 kernel, but didn't see anything. I would be highly appreciative if you could give me some pointers. As far as I could see, the Linux Console Project is defunct, but there is definitely work on multiple input devices going on. Yitzhak -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dr Andrew C Aitchison Sent: Wednesday, February 26, 2003 8:40 PM To: [EMAIL PROTECTED] Subject: Re: Multiple video consoles On Wed, 26 Feb 2003, Yitzhak Bar Geva wrote: What is the status of simultaneous multiple video console operation for full multiuser X on one machine? Someone reported that X works with the multi-head console support in Linux 2.5 kernels. As far as I am concerned, that is the right way to go: get multi-heads working on the console, then run X on top of that. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Wed, Feb 26, 2003 at 06:40:07PM +, Dr Andrew C Aitchison wrote: On Wed, 26 Feb 2003, Yitzhak Bar Geva wrote: What is the status of simultaneous multiple video console operation for full multiuser X on one machine? Someone reported that X works with the multi-head console support in Linux 2.5 kernels. As far as I am concerned, that is the right way to go: get multi-heads working on the console, then run X on top of that. Does it really work ? With 2.4 multi-headed console, X blanks the second head when it launches, even if i don't display anything on the second head. I tried tailing the /var/log/XFree86.0.log on it, but to no avail. BTW, i suppose you mean dual head as in one X on one head, and another X (with another user, keyboard and mouse) on the second head. How do you imagine this would work when both head are using a shared accel (XAA or DRI) engine ? Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Wed, Feb 26, 2003 at 09:27:50PM +0200, Yitzhak Bar Geva wrote: Greatly encouraged by your response, thanks! Someone reported that X works with the multi-head console support in Linux 2.5 kernels. I did some searching for multi-head consoles under 2.5 kernel, but didn't see anything. I would be highly appreciative if you could give me some pointers. As far as I could see, the Linux Console Project is defunct, but there is definitely work on multiple input devices going on. The correct place is the linux-fbdev project on sourceforge, especially their mailing list, James Simmon is the main developper of the new console code, and you have to look into the late 2.5.5x at least to get working stuff. That said, XFree86 people don't like fbdev much, and anyway, i don't think you can handle the dual head/one accel engine this way. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
Absolutely right, but ... This can be done if two servers are used. The point I was making earlier in this thread was that used hacked kernels and servers are a bad thing. If two consoles (including keyboards) could be operated on a single box, then two separate X servers could also be run. The biggest problem is not the display, but rather that both X and Linux have a single console keyboard ingrained in their code. Any thoughts on how this might be circumvented using existing pieces? Take care, KJohn - Original Message - From: Sven Luther [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 2:25 PM Subject: Re: Multiple video consoles On Wed, Feb 26, 2003 at 09:27:50PM +0200, Yitzhak Bar Geva wrote: Greatly encouraged by your response, thanks! Someone reported that X works with the multi-head console support in Linux 2.5 kernels. I did some searching for multi-head consoles under 2.5 kernel, but didn't see anything. I would be highly appreciative if you could give me some pointers. As far as I could see, the Linux Console Project is defunct, but there is definitely work on multiple input devices going on. The correct place is the linux-fbdev project on sourceforge, especially their mailing list, James Simmon is the main developper of the new console code, and you have to look into the late 2.5.5x at least to get working stuff. That said, XFree86 people don't like fbdev much, and anyway, i don't think you can handle the dual head/one accel engine this way. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: ATI with cvs
On Mit, 2003-02-26 at 16:00, [EMAIL PROTECTED] wrote: (dont scream at me for this one) can i get accel 3d working? Yes, but you need a recent DRM, either from CVS or from a 2.5 kernel. do you mean from the xfree cvs? Yes. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XRENDER extension docs?
Kurt Wall [EMAIL PROTECTED] wrote: Feigning erudition, Kendall Bennett wrote: % Hi Guys, % % Is thete any documentation on the XRENDER extension and more specifically % the Matrox implementation of it? Do any other drivers other than the % Matrox driver implement this extension? http://www.xfree86.org/~keithp/render/ $XFREE86ROOT/lib/X11/doc/render-protocol.txt Awesome, thanks! That gives a bit more information, but it doesn't really describe how the XAA drivers can accelerate the XRENDER extension. It seems the Matrox driver is the only one that can do this so far, so I guess we will just look at the Matrox driver source code. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Stepping outside the box with XAA drivers?
Hi Guys, I am trying to work out if it is possible to 'step outside the box' so to speak when writing an XAA driver module for XFree86 4.0. Basically there are some functions that we think we can implement faster if we hooked them at a higher level in the X server than to implement them via just the XAA provided hooks. Say for something like the text rendering functions. Is there a way to directly hook into the rendering model above the XAA layer so we can accelerate some things with a more efficient model than just XAA? Back in the old days of XFree86 3.x it was easy because everything was in a single server binary, but with the loadable module system I am not sure if this is possible or not. Any insight would be greatly appreciated. Thanks! --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Stepping outside the box with XAA drivers?
On Wed, 26 Feb 2003, Kendall Bennett wrote: Hi Guys, I am trying to work out if it is possible to 'step outside the box' so to speak when writing an XAA driver module for XFree86 4.0. Basically there are some functions that we think we can implement faster if we hooked them at a higher level in the X server than to implement them via just the XAA provided hooks. Say for something like the text rendering functions. Is there a way to directly hook into the rendering model above the XAA layer so we can accelerate some things with a more efficient model than just XAA? Back in the old days of XFree86 3.x it was easy because everything was in a single server binary, but with the loadable module system I am not sure if this is possible or not. There isn't anything above the XAA layer. XAA lets drivers hook things at 2 or 3 different levels. It's just not documented. Watch the LOW, MID and GC level in xaaInitAccel.c. LOW is the documented interface. XAA builds MID from LOW, builds GC from MID. GC is the top level. Of course, you don't have to use XAA at all if you don't want to, but XAA is an all or nothing thing. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xmag segv's
The background reports Depth: 0 with xwininfo. That looks like a
problem.
The x,y,... to the GetImage seem good, 1103,302,64,64.
--
Kevin
Mark Vojkovich wrote:
Are there depth 32 windows or something? If not
GetImageAndAttributes should call XGetImage on the
root window. It looks like the checks in there are OK.
Can you check the x,y,width,height to that first XGetImage
in GetImageAndAttributes?
Mark.
On Tue, 25 Feb 2003, Kevin Brosius wrote:
Of course, that's not what causes the X_GetImage failure... That
happens here:
in DragEH()
case ButtonRelease: /* end drag mode */
if (event-xbutton.button == Button1) { /* get image */
/* Problem: You can't get bits with XGetImage outside of its
window.
* xmag will only do a GetImage on the actual window in
the case
* where the depth of the window does not match the depth
of
* the root window.
*/
GetImageAndAttributes(FindWindow(event-xmotion.x_root,
event-xmotion.y_root),
event-xbutton.x_root,
event-xbutton.y_root,
srcWidth, srcHeight, data);
the GetImage call above generates the BadMatch. The embedded
FindWindow() calls seem to succeed.
Kevin Brosius wrote:
Latest CVS xmag (yesterday, changelog at 948.) No, there's no overlay,
this is on an ATI Mach64 at depth 16. I do think e17 uses a virtual
root window however. Here's the problem:
(gdb) r
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73 (X_GetImage)
Serial number of failed request: 2375
Current serial number in output stream: 2375
Program received signal SIGSEGV, Segmentation fault.
0x0804b48d in GetMinIntensity (data=0x805b5b8) at xmag.c:908
(gdb) bt
#0 0x0804b48d in GetMinIntensity (data=0x805b5b8) at xmag.c:908
#1 0x0804b7cf in PopupNewScale (data=0x805b5b8) at xmag.c:975
#2 0x0804a909 in DragEH (w=0x805fc38, closure=0x805b5b8,
event=0xb460, continue_to_dispatch=0xb38f
\001`ôÿ¿8ü\005\bdf\005\b8·\005\b\a) at xmag.c:664
#3 0x400accf4 in XtDispatchEventToWidget () from
/usr/X11R6/lib/libXt.so.6
#4 0x400ad767 in _XtDefaultDispatcher () from /usr/X11R6/lib/libXt.so.6
#5 0x400ad944 in XtDispatchEvent () from /usr/X11R6/lib/libXt.so.6
#6 0x400adea2 in XtAppMainLoop () from /usr/X11R6/lib/libXt.so.6
#7 0x0804bd43 in main (argc=1, argv=0xb554) at xmag.c:1105
#8 0x402204a2 in __libc_start_main () from /lib/libc.so.6
(gdb) l
static Pixel
GetMinIntensity(hlPtr data)
{
XColor *colors = NULL, *mptr, *tptr;
int i, ncolors;
if (data-win_info.colormap == DefaultColormap(dpy, scr))
return BlackPixel(dpy, scr);
ncolors = Get_XColors(data-win_info, colors);
mptr = tptr = colors; tptr++;
903 for (i=1; incolors; i++) {
904 if ((int)Intensity(mptr) (int)Intensity(tptr))
905 mptr = tptr;
906 tptr++;
907 }
908 return mptr-pixel;
909 }
910
(gdb) p ncolors
$1 = 0
I pasted some extra lines from the function in question. Get_XColors
returns 0 in my case, and since mptr was set to NULL already, the return
segv's when hit (the for loop falls through.) What should happen in
this case? Can we just return BlackPixel like the previous test?
--
Kevin
Mark Vojkovich wrote:
I don't see how the window manager could be involved. How
current of CVS? The last thing in the CHANGELOG on my machine is
862 and I don't see this problem.
I think BadMatch can happen with GetImage only if the app
trys to grab outside of the window. I think xmag grabs on the
root window to avoid this, but can only do this when the depth
of the window in question is the root depth. You don't have
different depth windows do you (overlay, depth 32 windows).
It looks like it knows how to clamp to the window dimensions.
Maybe you can get a backtrace with a debug xmag?
Maybe it has something to do with RandR?
Mark.
On Mon, 24 Feb 2003, Kevin Brosius wrote:
I've noticed the following xmag segv with current CVS when trying to
view part of the background in the development version of e (e17). Is
this an xmag or a window manager problem? (Or both?)
(gdb) r
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73 (X_GetImage)
Serial number of failed request: 668
Current serial number in output stream: 668
Program received signal SIGSEGV, Segmentation fault.
0x0804afbf in GetMinIntensity ()
This only occurs when the start point of the xmag selection window is
Re: Stepping outside the box with XAA drivers?
Mark Vojkovich [EMAIL PROTECTED] wrote: There isn't anything above the XAA layer. XAA lets drivers hook things at 2 or 3 different levels. It's just not documented. Watch the LOW, MID and GC level in xaaInitAccel.c. LOW is the documented interface. XAA builds MID from LOW, builds GC from MID. GC is the top level. Of course, you don't have to use XAA at all if you don't want to, but XAA is an all or nothing thing. Ok great! I knew there was probably a way to do this. I have looked at xaaInitAccel.c and I can now see exactly what we need to do. Thanks! Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
NVidia driver (open source) on Apple Powerbook G4 12
Hello XFree developer team, I recently got the new Apple Powerbook G4 12. GPU is a Geforce4 440 Go 64M (lspci -vv attached). I'm running X 4.3 for Debian from http://penguinppc.org/~daniels/. It works so far, but the framebuffer (openfirmware framebuffer) doesn't get restored correctly if I quit X or change with ctrl-alt-F1 back to console. The screen stays black but I can do everything as normal (type reboot blindly or switch back to X, ...). Perhaps the nvidia driver does not handle the console switch correctly... or there is a bug within the openfirmware framebuffer driver. best regards, Christoph00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 16, cache line size 08 Capabilities: [80] AGP version 1.0 Status: RQ=8 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none 00:10.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 440 Go 64M] (rev a3) (prog-if 00 [VGA]) Subsystem: nVidia Corporation: Unknown device 0010 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 248 (1250ns min, 250ns max) Interrupt: pin A routed to IRQ 48 Region 0: Memory at 9100 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at 9400 (32-bit, prefetchable) [size=64M] Region 2: Memory at f100 (32-bit, prefetchable) [size=512K] Expansion ROM at 9000 [disabled] [size=128K] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [44] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none 10:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0035 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 16, cache line size 08 10:12.0 Network controller: Broadcom Corporation: Unknown device 4320 (rev 02) Subsystem: Apple Computer Inc.: Unknown device 004e Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 16 Interrupt: pin A routed to IRQ 52 Region 0: Memory at 80084000 (32-bit, non-prefetchable) [disabled] [size=8K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=2 PME- 10:17.0 Class ff00: Apple Computer Inc.: Unknown device 003e Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 16, cache line size 08 Region 0: Memory at 8000 (32-bit, non-prefetchable) [size=512K] 10:18.0 USB Controller: Apple Computer Inc.: Unknown device 003f (prog-if 10 [OHCI]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 16 (750ns min, 21500ns max), cache line size 08 Interrupt: pin A routed to IRQ 27 Region 0: Memory at 80082000 (32-bit, non-prefetchable) [size=4K] 10:19.0 USB Controller: Apple Computer Inc.: Unknown device 003f (prog-if 10 [OHCI]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 16 (750ns min, 21500ns max), cache line size 08 Interrupt: pin A routed to IRQ 28 Region 0: Memory at 80081000 (32-bit, non-prefetchable) [size=4K] 10:1a.0 USB Controller: Apple Computer Inc.: Unknown device 003f (prog-if 10 [OHCI]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 16 (750ns min, 21500ns max), cache line
Re: xmag segv's
On Wed, 26 Feb 2003, Kevin Brosius wrote:
The background reports Depth: 0 with xwininfo. That looks like a
problem.
The x,y,... to the GetImage seem good, 1103,302,64,64.
What does xwininfo say the Class is? It should be InputOnly.
Depth 0 windows are InputOnly.
Can you poke around in xmag's FindWindow? Maybe the logic
in there is busted. I'm not really following what it's supposed
to be doing. Looks like it starts at the root and works it's way
towards the pointer (out of the screen) until the last InputOutput
window, which is the only type it can grab from. I would guess it
wants the frontmost InputOutput window under the pointer.
Mark.
--
Kevin
Mark Vojkovich wrote:
Are there depth 32 windows or something? If not
GetImageAndAttributes should call XGetImage on the
root window. It looks like the checks in there are OK.
Can you check the x,y,width,height to that first XGetImage
in GetImageAndAttributes?
Mark.
On Tue, 25 Feb 2003, Kevin Brosius wrote:
Of course, that's not what causes the X_GetImage failure... That
happens here:
in DragEH()
case ButtonRelease: /* end drag mode */
if (event-xbutton.button == Button1) { /* get image */
/* Problem: You can't get bits with XGetImage outside of its
window.
* xmag will only do a GetImage on the actual window in
the case
* where the depth of the window does not match the depth
of
* the root window.
*/
GetImageAndAttributes(FindWindow(event-xmotion.x_root,
event-xmotion.y_root),
event-xbutton.x_root,
event-xbutton.y_root,
srcWidth, srcHeight, data);
the GetImage call above generates the BadMatch. The embedded
FindWindow() calls seem to succeed.
Kevin Brosius wrote:
Latest CVS xmag (yesterday, changelog at 948.) No, there's no overlay,
this is on an ATI Mach64 at depth 16. I do think e17 uses a virtual
root window however. Here's the problem:
(gdb) r
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73 (X_GetImage)
Serial number of failed request: 2375
Current serial number in output stream: 2375
Program received signal SIGSEGV, Segmentation fault.
0x0804b48d in GetMinIntensity (data=0x805b5b8) at xmag.c:908
(gdb) bt
#0 0x0804b48d in GetMinIntensity (data=0x805b5b8) at xmag.c:908
#1 0x0804b7cf in PopupNewScale (data=0x805b5b8) at xmag.c:975
#2 0x0804a909 in DragEH (w=0x805fc38, closure=0x805b5b8,
event=0xb460, continue_to_dispatch=0xb38f
\001`ôÿ¿8ü\005\bdf\005\b8·\005\b\a) at xmag.c:664
#3 0x400accf4 in XtDispatchEventToWidget () from
/usr/X11R6/lib/libXt.so.6
#4 0x400ad767 in _XtDefaultDispatcher () from /usr/X11R6/lib/libXt.so.6
#5 0x400ad944 in XtDispatchEvent () from /usr/X11R6/lib/libXt.so.6
#6 0x400adea2 in XtAppMainLoop () from /usr/X11R6/lib/libXt.so.6
#7 0x0804bd43 in main (argc=1, argv=0xb554) at xmag.c:1105
#8 0x402204a2 in __libc_start_main () from /lib/libc.so.6
(gdb) l
static Pixel
GetMinIntensity(hlPtr data)
{
XColor *colors = NULL, *mptr, *tptr;
int i, ncolors;
if (data-win_info.colormap == DefaultColormap(dpy, scr))
return BlackPixel(dpy, scr);
ncolors = Get_XColors(data-win_info, colors);
mptr = tptr = colors; tptr++;
903 for (i=1; incolors; i++) {
904 if ((int)Intensity(mptr) (int)Intensity(tptr))
905 mptr = tptr;
906 tptr++;
907 }
908 return mptr-pixel;
909 }
910
(gdb) p ncolors
$1 = 0
I pasted some extra lines from the function in question. Get_XColors
returns 0 in my case, and since mptr was set to NULL already, the return
segv's when hit (the for loop falls through.) What should happen in
this case? Can we just return BlackPixel like the previous test?
--
Kevin
Mark Vojkovich wrote:
I don't see how the window manager could be involved. How
current of CVS? The last thing in the CHANGELOG on my machine is
862 and I don't see this problem.
I think BadMatch can happen with GetImage only if the app
trys to grab outside of the window. I think xmag grabs on the
root window to avoid this, but can only do this when the depth
of the window in question is the root depth. You don't have
different depth windows do you (overlay, depth 32 windows).
It looks like it knows how to clamp to the window dimensions.
Maybe you can get a backtrace with a debug xmag?
Maybe it has something to do with RandR?
Mark.
On
Re: xmag segv's
On Wed, 26 Feb 2003 20:41:40 -0500 Kevin Brosius [EMAIL PROTECTED] babbled:
The background reports Depth: 0 with xwininfo. That looks like a
problem.
The x,y,... to the GetImage seem good, 1103,302,64,64.
naughty xmag. it's assuming it can do XGetImage on an InputOnlyWindow :) naughty
naughty.
Mark Vojkovich wrote:
Are there depth 32 windows or something? If not
GetImageAndAttributes should call XGetImage on the
root window. It looks like the checks in there are OK.
Can you check the x,y,width,height to that first XGetImage
in GetImageAndAttributes?
Mark.
On Tue, 25 Feb 2003, Kevin Brosius wrote:
Of course, that's not what causes the X_GetImage failure... That
happens here:
in DragEH()
case ButtonRelease: /* end drag mode */
if (event-xbutton.button == Button1) { /* get image */
/* Problem: You can't get bits with XGetImage outside of its
window.
* xmag will only do a GetImage on the actual window in
the case
* where the depth of the window does not match the depth
of
* the root window.
*/
GetImageAndAttributes(FindWindow(event-xmotion.x_root,
event-xmotion.y_root),
event-xbutton.x_root,
event-xbutton.y_root,
srcWidth, srcHeight, data);
the GetImage call above generates the BadMatch. The embedded
FindWindow() calls seem to succeed.
Kevin Brosius wrote:
Latest CVS xmag (yesterday, changelog at 948.) No, there's no overlay,
this is on an ATI Mach64 at depth 16. I do think e17 uses a virtual
root window however. Here's the problem:
(gdb) r
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73 (X_GetImage)
Serial number of failed request: 2375
Current serial number in output stream: 2375
Program received signal SIGSEGV, Segmentation fault.
0x0804b48d in GetMinIntensity (data=0x805b5b8) at xmag.c:908
(gdb) bt
#0 0x0804b48d in GetMinIntensity (data=0x805b5b8) at xmag.c:908
#1 0x0804b7cf in PopupNewScale (data=0x805b5b8) at xmag.c:975
#2 0x0804a909 in DragEH (w=0x805fc38, closure=0x805b5b8,
event=0xb460, continue_to_dispatch=0xb38f
\001`ôÿ¿8ü\005\bdf\005\b8·\005\b\a) at xmag.c:664
#3 0x400accf4 in XtDispatchEventToWidget () from
/usr/X11R6/lib/libXt.so.6
#4 0x400ad767 in _XtDefaultDispatcher () from /usr/X11R6/lib/libXt.so.6
#5 0x400ad944 in XtDispatchEvent () from /usr/X11R6/lib/libXt.so.6
#6 0x400adea2 in XtAppMainLoop () from /usr/X11R6/lib/libXt.so.6
#7 0x0804bd43 in main (argc=1, argv=0xb554) at xmag.c:1105
#8 0x402204a2 in __libc_start_main () from /lib/libc.so.6
(gdb) l
static Pixel
GetMinIntensity(hlPtr data)
{
XColor *colors = NULL, *mptr, *tptr;
int i, ncolors;
if (data-win_info.colormap == DefaultColormap(dpy, scr))
return BlackPixel(dpy, scr);
ncolors = Get_XColors(data-win_info, colors);
mptr = tptr = colors; tptr++;
903 for (i=1; incolors; i++) {
904 if ((int)Intensity(mptr) (int)Intensity(tptr))
905 mptr = tptr;
906 tptr++;
907 }
908 return mptr-pixel;
909 }
910
(gdb) p ncolors
$1 = 0
I pasted some extra lines from the function in question. Get_XColors
returns 0 in my case, and since mptr was set to NULL already, the return
segv's when hit (the for loop falls through.) What should happen in
this case? Can we just return BlackPixel like the previous test?
--
Kevin
Mark Vojkovich wrote:
I don't see how the window manager could be involved. How
current of CVS? The last thing in the CHANGELOG on my machine is
862 and I don't see this problem.
I think BadMatch can happen with GetImage only if the app
trys to grab outside of the window. I think xmag grabs on the
root window to avoid this, but can only do this when the depth
of the window in question is the root depth. You don't have
different depth windows do you (overlay, depth 32 windows).
It looks like it knows how to clamp to the window dimensions.
Maybe you can get a backtrace with a debug xmag?
Maybe it has something to do with RandR?
Mark.
On Mon, 24 Feb 2003, Kevin Brosius wrote:
I've noticed the following xmag segv with current CVS when trying to
view part of the background in the development version of e (e17).
Is this an xmag or a window manager problem? (Or both?)
(gdb) r
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73
Re: xmag segv's
On Thu, 27 Feb 2003, Carsten Haitzler wrote: On Wed, 26 Feb 2003 20:41:40 -0500 Kevin Brosius [EMAIL PROTECTED] babbled: The background reports Depth: 0 with xwininfo. That looks like a problem. The x,y,... to the GetImage seem good, 1103,302,64,64. naughty xmag. it's assuming it can do XGetImage on an InputOnlyWindow :) naughty naughty. No it's got checks in there to prevent that. Either the logic is broken or it's something else. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xmag segv's
On Wed, 26 Feb 2003 21:15:57 -0500 (EST) Mark Vojkovich [EMAIL PROTECTED] babbled: On Thu, 27 Feb 2003, Carsten Haitzler wrote: On Wed, 26 Feb 2003 20:41:40 -0500 Kevin Brosius [EMAIL PROTECTED] babbled: The background reports Depth: 0 with xwininfo. That looks like a problem. The x,y,... to the GetImage seem good, 1103,302,64,64. naughty xmag. it's assuming it can do XGetImage on an InputOnlyWindow :) naughty naughty. No it's got checks in there to prevent that. Either the logic is broken or it's something else. i'd guess the logic. i know prop and xiwininfo don't work right with :click on the window to query for properies/info. they dont walk the window tree right. so i'd guess xmag would have something too. -- --- Codito, ergo sum - I code, therefore I am The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] [EMAIL PROTECTED] Mobile Phone: +61 (0)413 451 899Home Phone: 02 9698 8615 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Wed, Feb 26, 2003 at 09:25:21PM +0100, Sven Luther wrote: On Wed, Feb 26, 2003 at 09:27:50PM +0200, Yitzhak Bar Geva wrote: Greatly encouraged by your response, thanks! Someone reported that X works with the multi-head console support in Linux 2.5 kernels. I did some searching for multi-head consoles under 2.5 kernel, but didn't see anything. I would be highly appreciative if you could give me some pointers. As far as I could see, the Linux Console Project is defunct, but there is definitely work on multiple input devices going on. The correct place is the linux-fbdev project on sourceforge, especially their mailing list, James Simmon is the main developper of the new console code, and you have to look into the late 2.5.5x at least to get working stuff. That said, XFree86 people don't like fbdev much, and anyway, i don't Not necessarily :-) I recently wrote an fbdev driver for Intel 830M and later chipsets (www.xfree86.org/~dawes/intelfb.html, and it should be in new -ac kernels). It was fun doing some graphics stuff outside of XFree86 for a change. It's basically a 2.4.x driver right now, and still needs to be ported to the latest 2.5.6x fbdev interfaces. think you can handle the dual head/one accel engine this way. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
XFree86 4.3.0 release tagged
I've tagged the XFree86 4.3.0 release. The tag is xf-4_3_0, and the branch tag associated with this release is xf-4_3-branch. This should all be visible from the anoncvs repository soon. This marks the closing of the 4.3.0 release, and I'd like to thank all who have contributed to it. We've had a lot of great testing and bug reporting feedback over the last few weeks. Online documentation will be available soon at http://www.xfree86.org/4.3.0/. Check the README, Release Notes and Installation Notes there before downloading. Source tarballs and patches will be available over the next day or so from our ftp site ftp://ftp.xfree86.org/pub/XFree86/4.3.0/. Some binary distributions will be available over the next week or so. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
