[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 20:49 --- (In reply to comment #11) > (In reply to comment #9) > > (In reply to comment #4) > > > > > > Is bitblt secure? > > > > I don't think so - it could be used to view system memory, > > so a check is needed. > > See comment #6. Thing is the patch switches BITBLT to use a r300 raw packet, so this would bypass usual radeon checks. I am not certain why this patch affects things at all, as I would have expected packets inherited from radeon driver to work fine - certainly Xserver should use BITBLT quite often. Perhaps, there is some subtle issue that I am missing ? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 18:46 --- (In reply to comment #9) > (In reply to comment #4) > > > > Is bitblt secure? > > I don't think so - it could be used to view system memory, > so a check is needed. See comment #6. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 17:45 --- I may have spoken a little too soon. Now instead of an immediate hard lock after some time the machine locks. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 17:44 --- (In reply to comment #4) > Created an attachment (id=2966) --> (https://bugs.freedesktop.org/attachment.cgi?id=2966&action=view) [edit] > drm side of the proposed fix > > Is bitblt secure? I don't think so - it could be used to view system memory, so a check is needed. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: r300 + FreeBSD -CURRENT?
And so on, through /dev/dri/card254 Mind you, /dev/dri/card0 exists: [ [EMAIL PROTECTED] - ~ ]: ls -la /dev/dri total 1 dr-xr-xr-x 2 root wheel 512 Aug 21 18:37 . dr-xr-xr-x 5 root wheel 512 Dec 31 1969 .. crw-rw-rw- 1 root wheel0, 162 Aug 21 18:35 card0 Any ideas? Is the major ok ? On my (linux) system I get: crw-rw-rw- 1 root root 226, 0 Aug 21 19:07 card0 I would expect a difference, but, it might have changed.. Also, check that the DRM driver knows your PCI id. best Vladimir Dergachev Adam --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 16:44 --- I can confirm that the r300 driver patch works. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
r300 + FreeBSD -CURRENT?
I'm curious if anyone has gotten r300 working on FreeBSD now that the driver has been merged with Mesa and the DRM cvs tree? I managed to get Mesa CVS to build on FreeBSD with some help from Adam Jackson and Daniel Stone on irc today. DRM from the cvs tree compiled as well. The kernel module loads when I start X: drm0: port 0xa000-0xa0ff mem 0xc000-0xcfff,0xe900-0xe900 irq 10 at device 0.0 on pci1 info: [drm] AGP at 0xe000 128MB info: [drm] Initialized radeon 1.17.0 20050720 Xorg gives me the standard warning about DRM on r300: (WW) RADEON(0): Enabling DRM support *** Direct rendering support is highly experimental for Radeon 9500 *** and newer cards. The 3d mesa driver is not provided in this tree. *** A very experimental (and incomplete) version is available from Mesa CVS. *** Additional information can be found on http://r300.sourceforge.net *** This message has been last modified on 2005-08-07. But Direct Rendering is disabled. I get: drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 6, (OK) drmOpenByBusid: drmOpenMinor returns 6 drmOpenByBusid: drmGetBusid reports drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -1013 And so on, through /dev/dri/card254 Mind you, /dev/dri/card0 exists: [ [EMAIL PROTECTED] - ~ ]: ls -la /dev/dri total 1 dr-xr-xr-x 2 root wheel 512 Aug 21 18:37 . dr-xr-xr-x 5 root wheel 512 Dec 31 1969 .. crw-rw-rw- 1 root wheel0, 162 Aug 21 18:35 card0 Any ideas? Adam --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: PCI, AGP, PCI-E
> My understanding of bus operation is that it's sole function is to > provide memory mapped IO, IO ports, and interrupt control, after these > features are configured -- by the BIOS -- software only has to worry > about the device at the other end... After this initial configuration, > so I thought, the bus was invisible and mostly irrelevant... You need to get a better understanding of bus operation... if all you want to do with an AGP card is use it as a basic PCI card you might be in the ballpark, but AGP does a lot more than simple PCI so the X server needs to configure it (faster speeds, special write cycles, etc..) > >From the trafic on this list it seems that not only are there > performance considerations but vital operational charactoristics of > these busses that require software support. Can someone please explain > this to me? Also with AGP you have a thing called a GART, which is built into your chipset, with non-AGP (PCI/PCIe) this isn't available, and manufacturers put them on the GPU, these need to be configured by the drivers to enable accelerated operations, however currently ATI have only provided information for their PCI GART, their PCIE GART is undocumented as of yet (beyond basic register information - which is probably enough, I just need to write more test code..) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R430 (Radeon X800 XL AGP)
Now the bad stuff: - Some programs run without acceleration. LIBGL_DEBUG=verbose reports things like: libGL error: dlopen .../r300_dri.so failed (.../r300_dri.so: undefined symbol: _glapi_add_dispatch) Did you install Mesa from CVS ? There were quite a few big change in CVS and one now needs to install the library as well, not just the drivers. best Vladimir Dergachev strace shows it opening the right versions of libGL and r300_dri, and libGL does have that symbol, and of course glxinfo and glxgears do run with direct rendering. So this is a mystery. - Software GL consistently segfaults the X server whenever certain operations (such as a window resize) are attempted. For example one of my test programs that does _not_ run with direct rendering does a glutReshapeWindow on startup and it segfaults X.org every time. The good news is that the server seems to restart easily and e.g. the machine has not completely locked up on me yet. - The "Building" page on the wiki seems to be out of date. Mesa now requires libdrm to be installed and registered with pkg-config. -Dave Dodge --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R430 (Radeon X800 XL AGP)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Dodge wrote: | libGL error: dlopen .../r300_dri.so failed (.../r300_dri.so: undefined symbol: _glapi_add_dispatch) Hmm.. you have LD_LIBRARY_PATH pointing to a libGL from CVS, right? That's the problem I had, but it sounds like everything else is working for you. | - The "Building" page on the wiki seems to be out of date. Mesa now | requires libdrm to be installed and registered with pkg-config. That just changed a couple of days ago, so it might take a little bit for somebody to update it. Did you? Thanks, Donnie -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDCQXbXVaO67S1rtsRAgCCAJ954F7NFn4GplHANR6r0sZgn2wD2ACgpuTe gmNNUrcay2PN4sanGbTqAFQ= =+1Ko -END PGP SIGNATURE- --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
R430 (Radeon X800 XL AGP)
I picked up an X800 XL a few days ago. Apparently ATI is using a different chipset than the previously-tested X800 board mentioned on the r300 website; this one has an R430 in it. 01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 554d 01:00.1 Display controller: ATI Technologies Inc: Unknown device 556d To see if I could get it working, I threw "R430" stuff into the Mesa and drm source pretty much wherever I found "R420" mentioned. I used the 0x554d ID. [drm] Initialized radeon 1.17.0 20050720 on minor 0: PCI device 1002:554d (ATI Technologies Inc) mtrr: 0xd000,0x1000 overlaps existing 0xd000,0x800 mtrr: 0xd000,0x1000 overlaps existing 0xd000,0x800 mtrr: 0xd000,0x1000 overlaps existing 0xd000,0x800 agpgart: Found an AGP 2.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 1x mode agpgart: Putting AGP V2 device at :01:00.0 into 1x mode [drm] Loading R300 Microcode X.org seems to recognize the board, though it incorrectly claims it's PCIE: (--) RADEON(0): Chipset: "ATI Radeon X800 XL (R430) (PCIE)" (ChipID = 0x554d) I'm using kernel 2.6.11 plus some distribution-specific (GoboLinux) patches. I believe the Gobo patches are mainly for the filesystem and shouldn't be impacting DRI. The good news is that it does at least enable DRI, and I do seem to get stable 2D support (although in some cases it seems slower than the old Voodoo3 it replaced). $ glxinfo name of display: :0.0 *WARN_ONCE* File r300_state.c function r300Enable line 456 TODO - double side stencil ! *** No ctx->FragmentProgram._Current!! display: :0 screen: 0 direct rendering: Yes ... $ glxgears *WARN_ONCE* File r300_state.c function r300Enable line 456 TODO - double side stencil ! *** No ctx->FragmentProgram._Current!! *WARN_ONCE* File r300_render.c function r300_get_num_verts line 188 user error: Need more than 2 vertices to draw primitive QS ! *** 4587 frames in 5.0 seconds = 917.248 FPS 4605 frames in 5.0 seconds = 920.863 FPS ... If the FPS seems low, note that the test machine is an old P3-500MHz. Now the bad stuff: - Some programs run without acceleration. LIBGL_DEBUG=verbose reports things like: libGL error: dlopen .../r300_dri.so failed (.../r300_dri.so: undefined symbol: _glapi_add_dispatch) strace shows it opening the right versions of libGL and r300_dri, and libGL does have that symbol, and of course glxinfo and glxgears do run with direct rendering. So this is a mystery. - Software GL consistently segfaults the X server whenever certain operations (such as a window resize) are attempted. For example one of my test programs that does _not_ run with direct rendering does a glutReshapeWindow on startup and it segfaults X.org every time. The good news is that the server seems to restart easily and e.g. the machine has not completely locked up on me yet. - The "Building" page on the wiki seems to be out of date. Mesa now requires libdrm to be installed and registered with pkg-config. -Dave Dodge --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #2966 is|0 |1 obsolete|| --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 11:39 --- Created an attachment (id=2968) --> (https://bugs.freedesktop.org/attachment.cgi?id=2968&action=view) Whops... :) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 11:34 --- (In reply to comment #4) > Created an attachment (id=2966) --> (https://bugs.freedesktop.org/attachment.cgi?id=2966&action=view) [edit] > drm side of the proposed fix > > Is bitblt secure? Not as-is. But it's a type3 packet so that's already handled by radeon_check_and_fixup_packet3. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 11:28 --- Created an attachment (id=2967) --> (https://bugs.freedesktop.org/attachment.cgi?id=2967&action=view) r300 driver side of the proposed fix -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 11:24 --- Created an attachment (id=2966) --> (https://bugs.freedesktop.org/attachment.cgi?id=2966&action=view) drm side of the proposed fix Is bitblt secure? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
PCI, AGP, PCI-E
The few sources I've read have said that the hardware for AGP, and PCI-E was designed to emulate the software interface of PCI so that the underlying hardware would be transparent to software. This can be seen in the output of lspci, where my marginally supported R200 (Where's 6.2.2 when you need it?) is reported as two PCI devices... The purpose of the second device entry is obscure. (On a side note, I have a spare 6326 which I'm willing to donate for the price of shipping, I intend to offer one of my two R128s to a dumb-terminal using friend of mine.. If he declines, I'll offer that too, but only after the R200 driver stabilizes to the point where it Does Not Crash(tm)). My understanding of bus operation is that it's sole function is to provide memory mapped IO, IO ports, and interrupt control, after these features are configured -- by the BIOS -- software only has to worry about the device at the other end... After this initial configuration, so I thought, the bus was invisible and mostly irrelevant... >From the trafic on this list it seems that not only are there performance considerations but vital operational charactoristics of these busses that require software support. Can someone please explain this to me? -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! Non-sequiter item: Charleston, South Carolina --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
r300_dri compiling
hi! i'm not too experienced in programming, but here it goes: but i've been able to check out the Mesa cvs and the r300 cvs. i've been trying for quite a long time, to compile r300 Mesa drivers. the drm works fine from r300 cvs, but i cant get mesa to compile. if i try to compile the r300 code from Mesa cvs the compile finishes cleanly, but I get no direct 3D acceleration. libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering display: :0 screen: 0 direct rendering: No if I lndir the r300 code from r300 cvs, the build doesn't finish: output in attached file. i think it's just me, but i would like to be shure i can't help you guys! THANX for the hard work (i got it to compile about one month ago, once, but am still using that driver!) In file included from r200_context.h:51, from radeon_screen.c:48: radeon_context.h:199: error: syntax error before âPFNGLXGETUSTPROCâ radeon_context.h:199: warning: no semicolon at end of struct or union radeon_context.h:207: error: syntax error before â}â token In file included from radeon_screen.c:48: r200_context.h:759: error: field âradeonâ has incomplete type In file included from radeon_screen.c:49: r300_context.h:813: error: field âradeonâ has incomplete type radeon_screen.c: In function âradeonCreateScreenâ: radeon_screen.c:502: warning: pointer targets in assignment differ in signedness radeon_screen.c:586: warning: implicit declaration of function âglXGetProcAddressâ radeon_screen.c: In function âradeonCreateContextâ: radeon_screen.c:765: warning: control reaches end of non-void function radeon_screen.c: In function âradeonDestroyContextâ: radeon_screen.c:774: error: dereferencing pointer to incomplete type radeon_screen.c: At top level: radeon_screen.c:809: error: syntax error before â*â token radeon_screen.c: In function â__driCreateScreenâ: radeon_screen.c:814: warning: implicit declaration of function â__driUtilCreateScreenâ radeon_screen.c:814: error: âdpyâ undeclared (first use in this function) radeon_screen.c:814: error: (Each undeclared identifier is reported only once radeon_screen.c:814: error: for each function it appears in.) radeon_screen.c:814: error: âscrnâ undeclared (first use in this function) radeon_screen.c:814: error: âpscâ undeclared (first use in this function) radeon_screen.c:814: error: ânumConfigsâ undeclared (first use in this function) radeon_screen.c:814: error: âconfigâ undeclared (first use in this function) radeon_screen.c:814: warning: assignment makes pointer from integer without a cast radeon_screen.c: In function âgetSwapInfoâ: radeon_screen.c:890: error: dereferencing pointer to incomplete type radeon_screen.c:891: error: dereferencing pointer to incomplete type radeon_screen.c:892: error: dereferencing pointer to incomplete type radeon_screen.c:895: error: dereferencing pointer to incomplete type make[6]: *** [radeon_screen.o] Error 1 make[6]: Leaving directory `/home/jano/DRIcvs/Xorg/Mesa/src/mesa/drivers/dri/r300' make[5]: *** [subdirs] Error 1 make[5]: Leaving directory `/home/jano/DRIcvs/Xorg/Mesa/src/mesa/drivers/dri' make[4]: *** [drivers-dri] Error 2 make[4]: Leaving directory `/home/jano/DRIcvs/Xorg/Mesa/src/mesa' make[3]: *** [default] Error 2 make[3]: Leaving directory `/home/jano/DRIcvs/Xorg/Mesa/src/mesa' make[2]: *** [subdirs] Error 1 make[2]: Leaving directory `/home/jano/DRIcvs/Xorg/Mesa/src' make[1]: *** [default] Error 1 make[1]: Leaving directory `/home/jano/DRIcvs/Xorg/Mesa' make: *** [linux-dri-x86] Error 2 pgpXQBv1D2G1m.pgp Description: PGP signature
Re: Kernel / user interface for new memory manager
Ian Romanick a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There's been quite a bit of discussion about this on #dri-devel the past few days. I thought I'd write up a quick summary and post it to the list. I know that there are a lot of interested parties that are on the list, but who don't hang out in #dri-devel. :) As described in an old message[1], the new memory manager will be partially in the kernel and partially in user space. The discussions in IRC have focused on the interface between the two. Listed below are the functions that have been discussed. The names are just made up. initialize_pool - Initialze a new memory pool. This will be called once for each memory pool (e.g., on-card, AGP, PCI, etc.). get_pool_state - When a new process starts up it needs to know the state of a pool. That is, it needs to know which regions are allocated or not allocated. Since all allocations / frees are written to a log that is stored in a circular buffer, it is possible for the log to wrap around between times when a given processes the log. In that case the process will also need to use this function. force_log_update - The kernel updates its view of memory periodically when processes call into it. It is possible (though very unlikely) that a process could wrap the log between these occurances. The process can detect this and, before wrapping the log, call this function so that the kernel can update its view of memory. backup_region - Regions can be marked with a "preserve" bit. This means that the contents have to be saved before the memory can be reclaimed. backup_region instructs the kernel to do this for a specified portion of a region. restore_region - Restores the contents of a previously backed-up region to a new location. Depending on how backup_region is implemented, this function may not be necessary. As you said on IRC, this might not be needed. alloc_id_block - Each region is tracked by a unique ID. This function allocates a block of these IDs to a process. They will be automatically reclaimed if the process dies. release_id_block - Releases a block of previously allocated IDs. Now, there is one question that sounds to me like it will have implications over the whole memory manager design : do we want to enforce video memory ownership ? Stephane --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: r300_dri compiling
On Sun, 21 Aug 2005, john wrote: hi! i'm not too experienced in programming, but here it goes: but i've been able to check out the Mesa cvs and the r300 cvs. i've been trying for quite a long time, to compile r300 Mesa drivers. the drm works fine from r300 cvs, but i cant get mesa to compile. if i try to compile the r300 code from Mesa cvs the compile finishes cleanly, but I get no direct 3D acceleration. libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering display: :0 screen: 0 direct rendering: No Take a look in /var/log/Xorg.0.log - I bet it says direct rendering disabled. You need to use DRM from DRI CVS - it has proper version number that Xorg Xserver recognizes. The reason for the check is that previous DRM versions provided 2d acceleration only and using Mesa driver with them will not work. if I lndir the r300 code from r300 cvs, the build doesn't finish: output in attached file. No, it is not supposed to - there had been significant changes in Mesa. best Vladimir Dergachev i think it's just me, but i would like to be shure i can't help you guys! THANX for the hard work (i got it to compile about one month ago, once, but am still using that driver!) --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] patches wanted !
> > nope a working PCIEGART isn't the same as a working PCIGART, I have > > all the information I think I need (though an R42x 2D programmers guide as > > opposed to the R42x regref would help a bit), I just can't connect the > > dots... I also suffer from the fact that fglrx doesn't work on my PCIE > > system either (though I've talked to ATI engineers about those issues) > > Hangs your box when X starts up? I noticed if I start the stock > xorg server without fglrx once, and then restart with it, it > works. Otherwise my box hangs hard. This is straight after boot. > Michel let me know about the new fglrx version and it seems to fix my issues with 1GB RAM and PCIE cards on the r300 front I've stopped the NMI from happening by allocing the PCIGART table down in GFP_DMA as opposed to GFP_KERNEL, the drm now goes into an infinite loop on the first access to the ring buffer.. I'd bet the ring buffer or DMA setups aren't correct... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 2754] ATI Technologies Inc Radeon Mobility M6 LY in DRM/DRI mode locks up if CPU frequency changes on battery power
http://bugzilla.kernel.org/show_bug.cgi?id=2754 --- Additional Comments From [EMAIL PROTECTED] 2005-08-21 02:54 --- Sorry, i can't test it. I changed notebook model and vendor, so i can't help with report in future. Thanks -- sign: Josef Rysanek (ailas) <[EMAIL PROTECTED]> www:http://www.ailas.net/ -- Odchozi zprava neobsahuje viry, protoze nepouzivam MS Windows --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [R300] patches wanted !
On Sat, 20 Aug 2005, Dave Airlie wrote: > > > In for a penny in for a pound, (old saying..) i.e. if I could do that I > > > would have working 3D... the CP crashes on startup... > > > > I assume that you have a version of PCIGART working, right ? You can test > > this > > using MMIO by doing bitblt from GART memory to video memory, for example. > > nope a working PCIEGART isn't the same as a working PCIGART, I have > all the information I think I need (though an R42x 2D programmers guide as > opposed to the R42x regref would help a bit), I just can't connect the > dots... I also suffer from the fact that fglrx doesn't work on my PCIE > system either (though I've talked to ATI engineers about those issues) Hangs your box when X starts up? I noticed if I start the stock xorg server without fglrx once, and then restart with it, it works. Otherwise my box hangs hard. This is straight after boot. New version of fglrx came out the other day, have to re-test with that. --j --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
