View Single Post
  #1169 (permalink)  
Old 02-10-2011, 10:30 AM
[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 - 01-07: Panel power on/off fixes

Quote:
Originally Posted by Lmiller1708 View Post
Yes JooJooBee666 from PPCK is looking into this for us.
He thinks the partition start offsets are hard coded.
He will hopefully have something later on in the day.


@ACL,
With your partition table are you able to get the data to stick?
It seems our XIP RAM should be starting out in the same location for both Partition 0 and Partition 1. (Just a guess though)
Cant boot. Moving the imgfs to tinboot put a size restriction on us. Vogue had the same issue so they had to implement lzma compression on the kernel (which we dont have). I can port it over tonight, for now i just need to know if we can shrink down the initrd.gz to around 1.1mb. Harder than i thought. I erased the sbin , modem stuff and logo and still to big. May need to wipe a few symlinks too?

This line is the one causing issues when trying to make the xip with the gz file.

.org XIP_END-0x20000,0xff

The only good news here is that i didnt brick myself with the partition table.
__________________
Reply With Quote
This post has been thanked 1 times.