Re: rs480 + r300 driver fun..
On 4/9/07, Alex Jackson awj_in_japan-at-hotmail.com |rivatv-devel| ... wrote: What has to be done now? Where can look to start hacking Mesa to support it? (I've spent all of my time so far in DRM.. (radeon_cp.c) ) Does setting tcl_mode=0 in .drirc make it work? I tested this with my Xpress 200M (128M video RAM, no system RAM). glxgears runs, and even exits cleanly when I press Esc; however, it displays an utterly corrupted window instead of the lovely spinning gears we all want to see. --Noah --AWJ-- _ Don't waste time standing in line—try shopping online. Visit Sympatico / MSN Shopping today! http://shopping.sympatico.msn.ca - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: ATI Radeon XPRESS 200M
On 11/22/06, Phillip Ezolt phillipezolt-at-. |rivatv-devel| ... wrote: Alright. I don't have an interleaved options in my BIOS. I only have: Sideport_Only (128M) Sideport(128M)+UMA(0M) Sideport(128M)+UMA(32M) Sideport(128M)+UMA(64M) Sideport(128M)+UMA(128M) According to what little I understand of the system, interleaving is handled automagically by the chipset whenever the size of the Sideport and UMA RAM areas are the same. So in this case, the Sideport(128M)+UMA(128M) case would be automatically interleaved. I don't know if it is interleaved. There is no option for me to change the interleaving settings. I don't think there is one, I think this is somehow detected by the hardware. --Phil - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: PCI Express command paths?
Adam Jackson ajax-at-nwnk.net |rivatv-devel| wrote: On Wednesday 22 March 2006 09:55, [EMAIL PROTECTED] wrote: The thought occurred to me that if the kernel provides the functionality to call the bus, then perhaps there is a slim chance that if I hack the kernel and intercept the command stream, I can learn how fglrx sets up the video card. Maybe I'm totally off on my DRI theory here; if so, please correct me. The r300 project has already done this. - ajax Perhaps they have, but the Xpress 200 chipsets have a different setup that I thought this reverse-engineering could work on. I'm just trying to figure out the best way to get these cards to work properly. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Xpress 200M + Thunderbird = GPF
No. I know DRI is non-functional on it. Also, I figured out that it's not just Thunderbird, though it is the application that routinely and regularly causes the lockup. There was an instance where launching Firefox did cause problems. René Rebe rene-at-exactcode.de |rivatv-devel| wrote: Hi, On Wednesday 08 February 2006 00:10, [EMAIL PROTECTED] wrote: Hey all, After a message from this list telling me that turning color tiling off was the key to avoiding lockups on the r300 driver, I tried it and was delighted to find that it worked. Well, mostly. Using Thunderbird causes my kernel to oops with a general protection fault. It appears to be the *only* program on my system that causes the problem. No errors are reported in my /var/log/Xorg.0.log; all I get (if anything) is a kernel oops that sometimes hard-locks my system, sometimes doesn't. How can I go about debugging this problem? Do you claim that, aside Thunderbird 2D usage pattern result in a lockup, you can use DRI / DRM on the 200M ? Yours, -- Prone to wander, Lord, I feel it Prone to leave the God I love Here's my heart, Lord, take and seal it Seal it for Thy courts above. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Xpress 200M + Thunderbird = GPF
I went back and disabled the glx, drm, and dri Xorg extensions. Same result. Alex Deucher alexdeucher-at-gmail.com |rivatv-devel| wrote: On 2/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: No. I know DRI is non-functional on it. Also, I figured out that it's not just Thunderbird, though it is the application that routinely and regularly causes the lockup. There was an instance where launching Firefox did cause problems. Is the radeon drm loaded? make sure it's not. Alex René Rebe rene-at-exactcode.de |rivatv-devel| wrote: Hi, On Wednesday 08 February 2006 00:10, [EMAIL PROTECTED] wrote: Hey all, After a message from this list telling me that turning color tiling off was the key to avoiding lockups on the r300 driver, I tried it and was delighted to find that it worked. Well, mostly. Using Thunderbird causes my kernel to oops with a general protection fault. It appears to be the *only* program on my system that causes the problem. No errors are reported in my /var/log/Xorg.0.log; all I get (if anything) is a kernel oops that sometimes hard-locks my system, sometimes doesn't. How can I go about debugging this problem? Do you claim that, aside Thunderbird 2D usage pattern result in a lockup, you can use DRI / DRM on the 200M ? Yours, -- Prone to wander, Lord, I feel it Prone to leave the God I love Here's my heart, Lord, take and seal it Seal it for Thy courts above. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Radeon X1600?
Actually, I've been having trouble with my Xpress 200M locking up in 2D mode. I'm still trying to determine what the cause of the lockup is. If you're looking for something supported by other than the fglrx driver, I would steer clear of the 200M for a while. Roland Scheidegger rscheidegger_lists-at-hispeed.ch |rivatv-devel| wrote: John Clemens wrote: There was a post on this list at the end of december(?) indicating that ATI was not interested in helping open source with 3D specs anymore.. I'm guessing they didn't do much with the r300 line either.. but does anyone know anything or have any official word on whether the r500 series of radeon cards will ever be supported by anything other than fglrx for 3D? Any official word from ATI? Is anything known about these cards? I ask because my ibook g3 is getting a bit long in the tooth, and since my non-x86 options for laptops are fast approaching 0, I'm looking for a turion notebook with a supported chipset. I'm debating about going cheaper with a radeon 200M (which i think has an undocumented memory controller and thus doesn't work even though it's an r300 core?), or the MSI-1029 with an X700 (which is supported by r300, right?). But, the 1029 is about to be replaced with the 1039 which comes with the new X1600, so I'd like to know if I have to move before the 1029 disappears, or if i can wait a little while. Both xpress 200m and x700 should at least work for 2d, and the x700 hopefully for 3d too (some people still don't have luck with them it seems). There is not much hope of getting the X1xxx chips to work anytime soon, even for 2d, as they are believed to be much different (especially as far as modesetting/2d is concerned, radeon 7200 to radeon x850 are nearly identical there). You can always use vesa driver, which of course totally sucks, and there's a high probability you couldn't even use the display's native resolution with that. Fglrx should support it at some point, but an ATI employee stated it will take a couple of driver revisions, which I interpret as something up to half a year. Roland --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Xpress 200M + Thunderbird = GPF
Hey all, After a message from this list telling me that turning color tiling off was the key to avoiding lockups on the r300 driver, I tried it and was delighted to find that it worked. Well, mostly. Using Thunderbird causes my kernel to oops with a general protection fault. It appears to be the *only* program on my system that causes the problem. No errors are reported in my /var/log/Xorg.0.log; all I get (if anything) is a kernel oops that sometimes hard-locks my system, sometimes doesn't. How can I go about debugging this problem? --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Xpress 200M register dumps
That makes sense, because (from my understanding) this chipset is basically an ATI northbridge with an attached Radeon x300 GPU. This is what enables them to do their UMA+Sideport interleaving technology, I guess; since the Xpress chip *is* the northbridge, it has direct access to system memory and to the Sideport dedicated memory. Hope this helps. Dave Airlie airlied-at-linux.ie |rivatv-devel| wrote: Hey all, I took these register dumps from my Radeon Xpress 200M using the hw_script program and the read_radeon_pcie.scp script. One is from a clean startup, and the other one was taken from an X session. If there's anything else I can do, let me know, I'm eager to help. So these chips have a completly different memory controller than the real PCIE chips, so they aren't going to work with my driver changes for PCIE, I have some info on them but I've no idea how the hell to set them up correctly at all, they appear to be some sort of AGP based chipset... I'm going to see one at LCA, but looking at the info I have it might be a bit of work to get DRI going on it .. Dave. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Xpress 200M register dumps
Hey all, I took these register dumps from my Radeon Xpress 200M using the hw_script program and the read_radeon_pcie.scp script. One is from a clean startup, and the other one was taken from an X session. If there's anything else I can do, let me know, I'm eager to help. pcie_reg_dumps.tgz Description: GNU Unix tar archive
Re: Status of Xpress chips support
I played with the latest CVS version some last week and managed to get X to at least start with DRI enabled on the radeon driver. It doesn't start any applications, and if I leave it alone long enough it goes to a black screen and soft-locks; killing X hard-locks. Attached is the log, or at least, the interesting part of it. The last four lines repeat several hundred thousand times in the full log. ;) I was unable to repeat the hard-lock condition with debugging enabled, unfortunately. I hope this helps. Dec 23 14:29:23 snorlax [drm] Initialized drm 1.0.1 20051102 Dec 23 14:29:23 snorlax [drm:drm_init] Dec 23 14:29:23 snorlax [drm:drm_get_dev] Dec 23 14:29:23 snorlax [drm:radeon_driver_load] PCIE card detected Dec 23 14:29:23 snorlax [drm:drm_ctxbitmap_next] drm_ctxbitmap_next bit : 0 Dec 23 14:29:23 snorlax [drm:drm_ctxbitmap_init] drm_ctxbitmap_init : 0 Dec 23 14:29:23 snorlax [drm:drm_get_head] Dec 23 14:29:23 snorlax [drm:drm_get_head] new minor assigned 0 Dec 23 14:29:23 snorlax [drm] Initialized radeon 1.20.0 20050911 on minor 0: Dec 23 14:29:23 snorlax [drm:drm_stub_open] Dec 23 14:29:23 snorlax [drm:drm_open_helper] pid = 5392, minor = 0 Dec 23 14:29:23 snorlax [drm:radeon_driver_open] Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0xb010, size = 0x0001, type = 1 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0xc000, size = 0x1000, type = 0 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0x, size = 0x2000, type = 2 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] 8192 13 c2017000 Dec 23 14:29:23 snorlax [drm:drm_setup] Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0106407, nr=0x07, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0106401, nr=0x01, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0106401, nr=0x01, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0106407, nr=0x07, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0286415, nr=0x15, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0x, size = 0x2000, type = 2 Dec 23 14:29:23 snorlax [drm:drm_mmap] start = 0x2aaab14dc000, end = 0x2aaab14de000, offset = 0x1000 Dec 23 14:29:23 snorlax [drm:drm_vm_open] 0x2aaab14dc000,0x2000 Dec 23 14:29:23 snorlax [drm:drm_do_vm_shm_nopage] shm_nopage 0x2aaab14dc000 Dec 23 14:29:23 snorlax [drm:drm_do_vm_shm_nopage] shm_nopage 0x2aaab14dd000 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0286415, nr=0x15, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0xc000, size = 0x03ef8000, type = 0 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] Matching maps of type 0 with mismatched sizes, (66027520 vs 268435456) Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0106426, nr=0x26, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0106426, nr=0x26, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0x40106438, nr=0x38, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_sg_alloc] drm_sg_alloc Dec 23 14:29:23 snorlax [drm:drm_sg_alloc] sg size=8388608 pages=2048 Dec 23 14:29:23 snorlax [drm:drm_sg_alloc] sg alloc handle = 10265200 Dec 23 14:29:23 snorlax [drm:drm_sg_alloc] sg alloc virtual = c20010269000 Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0286415, nr=0x15, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0x, size = 0x00101000, type = 4 Dec 23 14:29:23 snorlax [drm:drm_mmap] start = 0x2aaab14de000, end = 0x2aaab15df000, offset = 0x10001000 Dec 23 14:29:23 snorlax [drm:drm_vm_open] 0x2aaab14de000,0x00101000 Dec 23 14:29:23 snorlax [drm:drm_do_vm_sg_nopage] Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0286415, nr=0x15, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0x00101000, size = 0x1000, type = 4 Dec 23 14:29:23 snorlax [drm:drm_mmap] start = 0x2aaab15df000, end = 0x2aaab15e, offset = 0x10002000 Dec 23 14:29:23 snorlax [drm:drm_vm_open] 0x2aaab15df000,0x1000 Dec 23 14:29:23 snorlax [drm:drm_do_vm_sg_nopage] Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0286415, nr=0x15, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0x00102000, size = 0x0020, type = 4 Dec 23 14:29:23 snorlax [drm:drm_mmap] start = 0x2aaab15e, end = 0x2aaab17e, offset = 0x10003000 Dec 23 14:29:23 snorlax [drm:drm_vm_open] 0x2aaab15e,0x0020 Dec 23 14:29:23 snorlax [drm:drm_do_vm_sg_nopage] Dec 23 14:29:23 snorlax [drm:drm_ioctl] pid=5392, cmd=0xc0286415, nr=0x15, dev 0xe200, auth=1 Dec 23 14:29:23 snorlax [drm:drm_addmap_core] offset = 0x00302000,
Status of Xpress chips support
Hey all. This is my first time sending to a public mailing list, so don't eat me alive, please. :) Anyhow, I was wanting to volunteer my services and my Radeon Xpress 200M for development work on this project. I have some kernel hacking/driver development experience, but that was on a device with open specifications, so I wanted to ask the following questions: 1) What do we currently know about these chipsets? 2) What more information do I need to bring this aspect of the driver up to par with the older cards/chipsets? 3) How do I go about gathering this information? Thanks for your help and the great work, and I hope I can be of some help. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
