Chameleon Svn Source Tree


  • Property svn:executable set to
1TODO List for Chameleon Boot Loader
3- Integrate Prasys current work on options and quick shortcut modified version of 18seven
5- Add auto detection of efistring algorithm to enable graphics enabler to be enabled by default while not
6 conflicting with other efi string overriden content
7 (original idea of Galaxy)
9- Add a more sophisticated acpi loading mechanism to enable loading custom acpi tables when dsdtdrop=y
10 Here's a specification to think about:
11 First we must care about if a forced DSDT full path has been specified (was the pb smith had in
12 his first tries) and take it for the DSDT path as is.
13 Then we have the case where no DSDT path was set where we run our usual DSDT search algorithm to find this file.
14 In the latter case, the file has to be named DSDT.aml and be in one of the / /Extra or bt(0,0)/Extra directory.
16 Now a first idea to implement correctly the acpi tables loading would be:
18 Whatever the path was hardcoded in the DSDT option or was automatically found, we extract the path part of
19 the DSDT file that has been successfully found and we run a loop to enumerate all other acpi files in the same directory.
20 Now for each acpi file found, we should compare the name with an existing acpi table found in the system that
21 we would normally load and replace this usual injection by the content of the file.
23 Once DropDSDT=y is set, no other acpi table than dsdt is loaded, then it is the responsibility of user
24 to provide any other acpi table.
26- Add a new module capable of writing proprietary Chameleon data to ioreg:
27 Using the DT__xxx() API, we will create a set of functions to write
28 to log info, chameleon boot info to be retrieved by helper applications...
29 the only public function for log info purpose of this module would be:
30 logMessageToIOREG(...); // var args printf style format
31 flushLogToIOREG(); // store a unique log info property to the ioreg
33 The preferred internal behavior of the log info ioreg buffer
34 would be to store the messages in a consolidated buffer then only write once,
35 this buffer (i.e just before call the kernel) with flushLogToIOREG();
36 The other public function for writing chameleon boot info data would be:
38 verbose() should incorporate a call to logMessageToIOREG()
39 to permit helper applications to extract
40 this log info (i.e: the chameleon system pref pane)
42- Add API for displaying and logging messages like:
44 void verbose(...)
45 {
46 ...
47 logMessageToIOREG("%s: %sn", title, s);
49 }
51 void display_and_log( const char* title, const char* msg)
52 {
53 printf("%s: %sn", title, s);
54 logMessageToIOREG(title,s);
55 }
57 void deprecated(const char * s)
58 {
59 display_and_log("WARNING: Deprecated option",s);
60 sleep(1);
61 }
63 void error_message(const char * s)
64 {
65 display_and_log("ERROR",s);
66 getc();
67 }
69 - Case unsensitive parsing for the bootConfig options:
70 should help the common/novice user to setup more easily.

Archive Download this file

Revision: HEAD