Chameleon

Chameleon Commit Details

Date:2010-09-04 09:49:30 (8 years 10 months ago)
Author:Azimutz
Commit:489
Parents: 488
Message:Doc edit.
Changes:
M/branches/azimutz/Chazi/doc-azi/Modules.txt

File differences

branches/azimutz/Chazi/doc-azi/Modules.txt
11
22
33
4
45
56
6
7
8
79
8
9
10
1011
12
1113
12
13
14
1514
15
16
17
1618
1719
1820
21
1922
2023
2124
2225
2326
2427
25
2628
29
2730
28
29
3031
32
33
34
35
3136
37
3238
3339
3440
......
4147
4248
4349
44
50
4551
4652
4753
......
4955
5056
5157
58
5259
5360
5461
The possible info at the moment:
Installation:
- get the source, compile; find modules at /sym/i386, with .dylib file extension.
- copy the .dylib files to a Modules folder created on your favorite Extra folder.
- create a /Extra/modules folder, copy Symbols.dylib (mandatory) to modules folder,
plus any other module you wish to load.
- update boot file or reinstall the booter completely in case it's too old;
"old" in RC5 world means before rev 168 (atm).
- update boot file or reinstall the booter completely, as needed.
How to use?
- Check if a key is needed to activate the module you pretend to use.
Modules are loaded at startup, before the Gui loads, providing they are located in
the right place (check Issues below).
- Just check if a key is needed to activate the module you pretend to use. Otherwise
modules are loaded at startup by the booter from default location. (check Issues below).
---------------//---------------//---------------
What are modules?
- good question! Well, can't add much on the "geek" side... need to study the stuff so
i don't start dumping bs. The easy answer is they are like plugins, adding/replacing
booter functionality. For instance: the Kernel Patcher (Kptchr) is around for some time,
integrated on boot file like any other Chameleon function; with Modules support Kptchr
can now live as a module, freeing the space it occupied on boot file
(one of module's advantages).
The booter will still perform as usual if a module fails to load.
Featured modules:
- Symbols.dylib: first and always loaded. No key is foreseen for this module.
No other module will work if this one fails to load.
- Symbols.dylib: always needed to load other modules! It's the first one to load and no
other module will work if this one fails to load. The booter will still perform as
usual, if it fails to load.
- KernelPatcher.dylib:
- "will" need PatchKernel=y to be enabled.
Note:*** this is still under consideration/testing so, for now the patcher is enabled by default***
will benefit of the same treatment!
Let's just say that the only patch needed by the 925 on Legacy Mode(*) is cpuid_set!
- HelloWorld.dylib: just a notifier, i guess :P
- HelloWorld.dylib: just a notifier (not needed).
(*) For those who "missed" the lesson, Legacy Mode is the mode 32 bit only cpu's run on OS X.
---------------//---------------//---------------
Issues:
- modules may fail to load, if you have the booter on a separate device/partition and try
to load modules from selected volume. Confirmed on MBR/boot0hfs install only.

Archive Download the corresponding diff file

Revision: 489