From: <fh...@at...> - 2000-10-22 04:06:37
|
In <Pine.LNX.4.10.10010181211150.841-100000@cassiopeia.home>, on 10/18/00 at 12:46 PM, Geert Uytterhoeven <ge...@li...> said: >On Tue, 17 Oct 2000 fh...@at... wrote: >> In <Pine.LNX.4.10.10010171602340.394-100000@cassiopeia.home>, on 10/17/00 >> at 04:09 PM, Geert Uytterhoeven <ge...@li...> said: >> >> >On Tue, 17 Oct 2000 fh...@at... wrote: >> >> So, have I got this right? Setup has: >> >To find out that unknown location, you can replace the `7' by some easy >> >to find unique value (whatever that may mean, e.g. 0xdeadbeef or >> >0xdeadcode or 0xfAedbeef (looks like Fredbeef :-)) and search for it in >> >memory after running the DSP script. >> >> How to I search the memory? grep deadcode /dev/kmem ? >No, you search from 0xc0000000 to 0xc4000000 in your driver. Never did figure out out to search memory by address in the driver. Could you use a for loop with a readl() in it? I got the driver to pass the cache test finally. I also found out something interesting: There is a limit as to how many printks you can have in a driver. :) Now hopefully I can get to more of the "fun" stuff. Fred |