View Single Post
  #1415 (permalink)  
Old 03-01-2011, 12:51 PM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 01-07: Panel power on/off fixes

Quote:
Originally Posted by Lmiller1708 View Post
Where do you get 64MB?

Also we can change and remove these MTDParts as need be... Maybe just leave it up to the cooks.
If we want to add the cache we can with no problem.

Edit: I think ACL has plans for the Root...
I get 64 MB by this:

0x04000000 (base 16) = 67,108,864 (base 10)
67,108,864 (bytes) / 1024 = 65,536 (kb) / 1024 = 64 (MB)

The kernel and tinboot code only occupy the first 6 MB or so of NAND. I think we could safely shrink the starting point to 16 MB without any fear of overwriting stuff. How does this look:

mtdparts=msm_nand:
0x20000000@0x0(nand) - 512 MB total
0x00800000@0x01000000(root) - 8 MB of space
0x0A000000@0x01800000(system) - 160 MB of space
0x14800000@0x0B800000(userdata) - 328 MB of space

I think 160 MB might be a bit much for system, but that does give the chefs a lot of space to work with. 328 MB for user data will really be 310 MB of usable space since we are eating up 18 MB with modules.
Reply With Quote