View Single Post
  #540 (permalink)  
Old 12-04-2010, 08:00 PM
[ACL]'s Avatar
[ACL]
VIP Member
Offline
Location: NY
 
Join Date: Feb 2010
Posts: 1,534
Reputation: 6350
[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 11-29: New Framebuffer, gralloc, and libGLES

Quote:
Originally Posted by natemcnutty View Post
I flashed stock ROM to do some testing, and I'm wondering if this is even the right memory address. I am getting random results for 0xBA0811D4. Most of the time it stays what I have below:
Code:
HaRET(16)# vdump 0xBA0811D4 16
ba0811d4 | 3a2a52bb 00200000 00600000 52d00400 | .R*:.. ...`....R
After letting it sit for 5 minutes, it has changed to this:
Code:
HaRET(18)# vdump 0xBA0811D4 16
ba0811d4 | 3a2a5457 00200000 00600000 52d00400 | WT*:.. ...`....R
HaRET(19)# vdump 0xBA0811D4 16
ba0811d4 | 3a2a548e 00200000 00600000 52d00400 | .T*:.. ...`....R
And it is now staying as 3a2a548e

I just dumped the entire MMU while the screen was dimmed, off, and on full brightness. I'm creating diffs between them, but holy crap is there a lot of junk in there.
Thanks dood.. also fee free to update the wiki. All this research is helpfull.
__________________
Reply With Quote
This post has been thanked 1 times.