Re: 64-bit kernel with 32-bit userspace app.
Egbert Eich wrote a patch to handle this that's pending review: https://bugs.freedesktop.org/show_bug.cgi?id=943 To work on this stuff my advice is to have a 32-bit machine and a 64-bit machine and have XFree86 4.3 and latest Xorg and make sure all the backwards combinations works or at least find out which ones don't and see if anyone cares... I'm going to get time to check Egberts patch at some stage soon, but I think it might break backways 64-bit to 64-bit.. which may be the only option (apart from moving to a brand new interface and leaving the old one as is...).. Dave -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Modified Linux 2.6 drm initializes multiple R350's
ACPI: PCI interrupt :17:00.0[A]: no GSI [drm:radeon_stub_register] [drm:radeon_stub_register] calling inter_module_register agpgart: agp_backend_acquire: pdev = 0xe2307bfc0800, acquired bridge = 0xe13003934800 [drm:radeon_ctxbitmap_next] drm_ctxbitmap_next bit : 0 [drm:radeon_ctxbitmap_init] drm_ctxbitmap_init : 0 [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc R350 NK [Fire GL X2] [drm:radeon_probe] ACPI: PCI interrupt :1b:00.0[A]: no GSI [drm:radeon_stub_register] [drm:radeon_stub_register] already registered agpgart: agp_backend_acquire: pdev = 0xe2307bfc, acquired bridge = 0xe13003934700 [drm:radeon_ctxbitmap_next] drm_ctxbitmap_next bit : 0 [drm:radeon_ctxbitmap_init] drm_ctxbitmap_init : 0 [drm] Initialized radeon 1.11.0 20020828 on minor 1: ATI Technologies Inc R350 NK [Fire GL X2] (#2) --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-users] miniglx and radeon r200
You're more likely to get help on the DRI list. I'm cc'ing it. -Brian Daniel Sperka wrote: I'm having problems getting miniglx to render anything with my Radeon9000. I saw a post about this from some time back, but no replies to it. I start up simple_server and get this reponse: [EMAIL PROTECTED] Mesa]# ./progs/miniglx/sample_server [2] 4176 [miniglx] probed chipset 0x4966 got MMIOAddress 0xf3071000 offset 67108864 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmGetBusid returned '' [drm] added 8192 byte SAREA at 0x1385c000 [drm] mapped SAREA 0x1385c000 to 0xf305c000, size 8192 [drm] framebuffer handle = 0xe800 [drm] register handle = 0xf69f [gart] AGP enabled at 2x [gart] 8192 kB allocated with handle 0x0001 [gart] ring handle = 0xf000 [gart] ring read ptr handle = 0xf0101000 [gart] vertex/indirect buffers handle = 0xf0102000 [gart] AGP texture map handle = 0xf0302000 Using 8 MB AGP aperture Using 1 MB for the ring buffer Using 2 MB for vertex/indirect buffers Using 1 MB for AGP textures Will use back buffer at offset 0x30 Will use depth buffer at offset 0x60 Will use 56320 kb for textures at offset 0x90 [drm] Added 32 65536 byte vertex/indirect buffers [drm] dma control initialized, using IRQ 11 [drm] Initialized kernel gart heap manager, 5111808 page flipping disabled [miniglx] Setting mode: visible 1024x768 virtual 1024x768x32 [miniglx] Readback mode: visible 1024x768 virtual 1024x768x32 RADEONEngineRestore I'm not certain, but this looks OK to me (I am investigating the page flipping disabled message). After this I run miniglxsample, but I do not get the rotating square. The glClear(GL_COLOR_BIT) does work - I can make the background any color I wish. The rectangle just doesn't show up. I do have a black box in the lower left corner of the screen - looks like the size of a cursor, however. It is NOT the color the rectangle is supposed to be. I've messed with the coordinates, moved the rectangle around, tried gluOrtho2D, all to no avail. Has anyone made this work with an r200? If so, can you post your procedures and/or example program(s)? Dan --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Mesa3d-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mesa3d-users --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: via.o build problem with 2.6.10-rc2-mm2
On Mer, 2004-11-24 at 02:28, Dave Airlie wrote: That is due to the new remap_pfn_range stuff, I'm not sure we can put checks for it into our CVS tree, as -mm trees don't have different KERNEL_VERSION than Linus trees, you could try building the linux-core tree rather than the linux-2.6 tree... If that stuff is in Linus's tree we need to put the checks in but not until then... Its in 10rc as well. The change fixes various things like remapping pages high up. Also btw heading this way and it broke AGP and seems to break DRI is Linux x86 using the Xen paravirtualizer. This correctly implements virt_to_bus/dma_alloc and friends but being virt_to_bus/virt_to_phys are no longer randomly the same as they are on generic x86, and two adjacent kernel virtual addresses may not have the adjacent bus addresses. Right now i810 with acceleration explodes in this configuration. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: HyperZ for IGP320M
On Thu, Nov 25, 2004 at 03:53:17PM +0100, Stephane Marchesin wrote: Btw, we're looking for people that could do some hacking on r200 now, since we don't have access to these cards. I can do r200 (well, rv280). How much hackery is involved? Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[1/34 submit] Reenable MGA DRI on x86-64
Reenable MGA DRI on x86-64 Has been reported as working. Signed-off-by: Andi Kleen [EMAIL PROTECTED] Index: linux/drivers/char/drm/Kconfig === --- linux.orig/drivers/char/drm/Kconfig 2004-10-19 01:55:10.%N +0200 +++ linux/drivers/char/drm/Kconfig 2004-11-02 17:55:41.%N +0100 @@ -81,7 +81,7 @@ config DRM_MGA tristate Matrox g200/g400 - depends on DRM AGP (!X86_64 || BROKEN) + depends on DRM AGP help Choose this option if you have a Matrox G200, G400 or G450 graphics card. If M is selected, the module will be called mga. AGP --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: 64-bit kernel with 32-bit userspace app.
Egbert Eich wrote a patch to handle this that's pending review: https://bugs.freedesktop.org/show_bug.cgi?id=943 To work on this stuff my advice is to have a 32-bit machine and a 64-bit machine and have XFree86 4.3 and latest Xorg and make sure all the backwards combinations works or at least find out which ones don't and see if anyone cares... I'm going to get time to check Egberts patch at some stage soon, but I think it might break backways 64-bit to 64-bit.. which may be the only option (apart from moving to a brand new interface and leaving the old one as is...).. Dave Thanks. My concern was not to introduce any new code that would break a possibly existing 32-64 bit compatibility. /Thomas -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: HyperZ for IGP320M
Philip Armstrong wrote: On Thu, Nov 25, 2004 at 03:53:17PM +0100, Stephane Marchesin wrote: Btw, we're looking for people that could do some hacking on r200 now, since we don't have access to these cards. I can do r200 (well, rv280). How much hackery is involved? For once, that's not the same. It should work just fine on rv280, since I have a rv250 (though I might have broken it on rv100 when I optimized it for rv250). The r200 supports hierarchical-z though, which isn't working yet. I'm still looking at the pictures people submitted, and try to come up with a new solution. I also have a version which works for r100, though there's no patch available yet. Roland --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
tvout support for mach64
Is the tvout support for mach64 supposed to go into the tree? There was a patch running around some time ago that added the tvout support (from gatos I believe). Just added it to the code and its still working and I was wondering why it never made it in. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: via.o build problem with 2.6.10-rc2-mm2
Its in 10rc as well. The change fixes various things like remapping pages high up. and the DRM in 10rc works but I really only want to add checks to CVS for released kernels, supporting -mm and -rcs in our CVS tree isn't really something I'd like to spend time on... (I know via isn't in the kernel and I'm still thinking of how to resolve this .. when 2.6.10 is released I'll push the core/split stuff to Linus and then start addressing some of the other issues... Also btw heading this way and it broke AGP and seems to break DRI is Linux x86 using the Xen paravirtualizer. This correctly implements virt_to_bus/dma_alloc and friends but being virt_to_bus/virt_to_phys are no longer randomly the same as they are on generic x86, and two adjacent kernel virtual addresses may not have the adjacent bus addresses. Ah crap... this sorta stuff always happens when I'm busy, I think the DRM has some major issues in this area of mappings and abusing addresses that there may be a rethink needed about some areas of it ... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Unresolved symbols in X.org modules with Savage IX
Hi there, I'm trying to get my Savage IX running with DRI. I'm precisely following the instructions supplied at http://dri.sourceforge.net/cgi-bin/moin.cgi/Building. After everything is compiled, X.org starts fine, but when I review Xorg.0.log, it turns out that something's screwed up. Here's a snippet: Symbol printf from module /usr/X11R6/lib/modules/linux/libdrm.a is unresolved! Symbol puts from module /usr/X11R6/lib/modules/fonts/libtype1.a is unresolved! Symbol printf from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! Each of these errors is printed out a few times. Before it happens, X.org tells me that DRI was successfully initialized (DRI is enabled). When I run glxinfo (or any other OpenGL application) afterwards, it crashes my Xserver telling me that An undefined function has been called. What's even more frustrating, the same thing happens for me both when I update the X.org version installed from a Slackware package (6.7.0) and when I compile the whole X.org source tree from scratch! I'm more than confused by the contents of those messages - unresolved symbol *printf*? Or puts? Even such a newbie as me knows these are standard C I/O functions so I sense something weird in here... Got any clues? Could this be a CVS error? Or maybe something's wrong with my configuration? I'm using a self-compiled 2.4.27 kernel and Slackware 10.0 as I mentioned before. gcc version 3.3.4, glibc version 2.3.2. Is anything else worth mentioning? Dunno. If you'd like to review my whole Xorg.0.log, here it is: http://kempniu.no-ip.com/files/Xorg.0.log I'd be grateful for any clues as I already saw posts about successful DRI installations using Savage IX and I can't wait to get my very own working :) Best regards, Michal Kepien --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: tvout support for mach64
It's more of an Xorg thing than a dri thing, I'd ask on the Xorg lists, I'd be happy to see it go in , it has worked quite well for me ... I think now that Vladimir has merged in the radeon stuff there should be no reason for the tvout to be a separate patch... when I get my laptop fixed I might get time to update the patch to Xorg if you haven't done it ... no idea how long it will take for the replacements bits for my laptop to arrive though.. Dave. On Fri, 26 Nov 2004, Micha Feigin wrote: Is the tvout support for mach64 supposed to go into the tree? There was a patch running around some time ago that added the tvout support (from gatos I believe). Just added it to the code and its still working and I was wondering why it never made it in. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
