|
||||
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
I guess that would be fine. If the ten cars just sat there a lot of times, why not waste 2? Or am I still missing one other key factor? (which is entirely possible, I'm sure...hell, it's probably more than one...)
__________________
|
This post has been thanked 1 times. |
|
||||
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
Quote:
The point is there is a fixed amount of memory over which to distribute stuff and optimal division of your resources will give you the maximum gain. You will not gain additional RAM by xipping (analogous to adding an 11th car). Overallocating and then pointing out the gain of moving from one area to the over allocated area is a poor example of gain compared to allocating efficiently in the first place. Your original statement was that you save 4MB approx. of memory by moving igo to xip region. Now you're saying it's ok to waste some space because you have so much. These are competing ideas - either you are trying to maximize or you are not, but being wasteful in one area and then trying to maximize your wastefullness is not an optimum strategy.
__________________
Grammar: The difference between knowing your shit and knowing you're shit.
Last edited by gguruusa; 04-24-2009 at 09:22 AM. |
This post has been thanked 2 times. |
|
||||
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
Quote:
This is based from this: "When execute in place (XIP) DLLs are loaded, they are loaded from the top of the 64 MB space down. Each XIP DLL is based (positioned in the address space) when the ROM is created. When a non XIP DLL is loaded, it is positioned below the 32 MB boundary. Non-XIP DLLs, also called RAM-based DLLs, are those that are loaded from the object store, decompressed from ROM or loaded from an external file system such as a Compact Flash card. The upper 32 MB of the applications virtual memory space is only used for XIP DLLs." But of course, I may be interpreting it wrong. Please don't assume I am saying you are wrong at all. I am just trying to gain a better understanding and appreciate all of your feedback thus far Last edited by joojoobee666; 04-24-2009 at 09:39 AM. |
This post has been thanked 1 times. |
|
||||
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
Quote:
So final analysis of what you are saying sir, is we could just get skewed overly too excited moduling everything including what stays more beneficial in the overall interest as a file? |
|
||||
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
Quote:
I have studied the SYS from 21159 till 21501 and found out that most SYS folders that were files in 21159 and 21169, were either partially or completely converted into modules form 2117+ and above. So does this not account for the speed of subsequent builds and improved memory management and efficiency? |
|
||||
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
Quote:
Last edited by joojoobee666; 04-24-2009 at 10:26 AM. |
This post has been thanked 1 times. |
|
||||
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
Quote:
|
|
||||
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
Hey, I've been reading this thread for a while, and I've been trying to port over the 21501 SYS to the i910. I've been cooking for WM6.1, so I understand enough to get a decent WM6.1 rom out, but I would really like to get 6.5 on the device. Through trial and error, I've gotten the device to the second boot screen. For a while it would boot, and the screen would turn off, and be frozen at the Welcome screen(when I hit a button, the backlight would turn back on). Now when it boots, it gets through 5-8 loops of the second boot screen and then the screen goes out of sync (doesn't take up the whole screen, lines are fuzzy). This leads me to think it's either not loading the correct driver for something. Has anyone run into this problem and can shed some light on what my next step in attempting to get a working rom should be?
|
|
|
|