![Old](images/statusicon/post_old.gif)
01-21-2009, 08:30 AM
|
![lllboredlll's Avatar](customavatars/avatar45468_13.gif) |
VIP Member
Offline
Location: NC
|
|
Join Date: Dec 2007
Posts: 1,545
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
|
Re: New XIP for 21109 sys with working encryption
Quote:
Originally Posted by gguruusa
You do know you can patch up any kitchen to work, right? It can be done easiest, however using PPCkitchen.
ok, I've "stopped realizing that the PPCK is NOT FOR EVERYONE". Now I'm onto it IS for everyone.
lol - You realize that you are trying to argue in favor of using tools that even the author acknowledges as being antiquated? Essentially, you're arguing that using ancient versions of software is "innovative and progressive". Nice logic.
------------------------------
Back to the thread subject, you guys completely lost me in your xip discussion, and if I'm confused I'm sure everyone else is too.
Things are taken out of xip for two reasons: not enough xip space allocated (ram problem), or, xip partition isn't sized large enough (rom problem). Both are resizeable, but it's just plain easier to work within the existing layout than restructure stuff - so that's what most people do. Most of the older tools don't react well to non-standard layouts, anyway.
Things execute faster when they are in XIP form because they don't have to be rebased on load (rebasing is where you change all the jump tables to reflect where the module was actually loaded in memory). They also only load once (obviously, since they only load at a single fixed address). Unfortunately, nothing is free - not everything is pure and reentrant (which you must be to work right in xip form), and xip modules aren't unloadable - they permanently consume resources.
|
Well unless things have changed ALOT since I last used PPCKitchen I will have to say it's NOT for everyone. You can argue that point all day long til you are blue in the face and I will not agree with you. One of the biggest problems with the kitchen is the poorly compiled OEM Pack. Vague descriptions as well as dependencies that are not identified unless you do trial and error ROM building, which is a bunch of BS. I dont have all day to test a compilation because someone was too lazy to author their packages correctly. Last but not least, you guys make it a pain in the a$$ to compile a ROM for the kitchen. Constant changes get annoying after awhile. Especially when you supply NO resource for the cooks to use in order to integrate their ROM's into "Your" kitchen. It's personally traded information based on who kisses who's a$$. Plus I never have cared for "Glamware" and the kitchen is exactly that. Tell me your kitchen can give me the resources that Ervius's Kitchen supplies me and I'll tell you that you're full of ****. I can cook my ROM with the "Caveman" style kitchen and get more stability, less bugs and better ram performance but as always anything you support is perfect and you the only one that knows anything. We're just a bunch of dumb sob's.
__________________
Accepted NOT Expected
|