<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - PowerPC e5500, kernel crash, GT520, GT610" href="https://bugs.freedesktop.org/show_bug.cgi?id=88868#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - PowerPC e5500, kernel crash, GT520, GT610" href="https://bugs.freedesktop.org/show_bug.cgi?id=88868">bug 88868</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Dmitriy from <a href="show_bug.cgi?id=88868#c8">comment #8</a>) > ) Thank you very much for your answer. > > I spent a lot of time to get out how the driver works. Yes, powerpc e5500 it > is BE arch. Of course byteswaps can be the reason of error but I think it > isn't in this case. [fwiw, ppc le is becoming a thing] > > Could you please clearify two moments. And I'll try to find the problem by > myself. > 1.Why does the variable "boot" have byteswap but the variable "strap" has > the correct value? I don't see anywhere in your kernel log where boot0 is correct. (boot0 is mmio register 0) > 2.Why can't the driver read on the address 0x700000 and 0x700001? Probably because it doesn't do the if (device->card_type >= NV_50) bits which set up instmem to point to the right place. 0x700000 isn't some magical thing... it's a view into vram, and it doesn't get set up because the card gets detected as a NV1A which is *considerably* different from NVD9. (pre-nv50 I think vram always fit into the 0x700000 range so the prefix wasn't a thing... or something.) > > Please tell me what first steps should I take to find out how to correct the > error. In case Ben's patch doesn't fix it, try to figure out what's going on. Until boot0 is read out properly, you can ignore any of the later failures.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>