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