TODO List for Chameleon Boot Loader
====================================
31.01.2011 Slice
- linux detection
- proper bootArgs when starting from CD

27.12.2010 Slice
- numerous errors, mistakes, reservation, non-finished codes... Spaghetti sources!
- kernelcache never used (adler32 is wrong?)  -- resolved
- more careful CPU detection
- readNVRAM is wrong  -- resolved
- graphicsEnabler for X3100 is not good
- ATI Radeon enabler is not perfect


16.12.2010 Slice
- I want to implement NVRAM for use with nvram, bless, StartupDisk.prefPane, and with VoodooHDA in future. 
1. Write a script rc.shutdown.local and place it into /etc
<--------------
#!/bin/sh
nvram -p >nvram.inf
echo Hello! NVRAM is saved!
-------------->
2. Read and interpret nvram.inf to place variables into /options node
3. Prepare some other boot-time variables in the node (platform-uuid, BootOrder, FirmwareFeatures, efi-boot-device and so on)
4. Implement boot flag -c to clear growing amount of nvram savings.

- ATI GraphicsEnabler is not perfect. 
1. ATY,SCLK, ATY,MCLK, ATY,RefCLK must be read from VideoBIOS but not constant values. Excluded!
2. FakeDeviceID needed

- Intel GraphicsEnabler needs to be corrected by calculating LCD info. Done!
--------------------------------------------------------------------------------------------------------
- Integrate Prasys current work on options and quick shortcut modified version of 18seven

- Add autodetection of efistring algorythm to enabke graphics enabler to beanbled by default while not conflicting whith other efi string overriden content
  (original idea of Galaxy)

- Add a more sophisticated acpi loading mechanism to enable loading custom acpi tables when dsdtdrop=y
    Here's a specification to think about:
    First we must care about if a forced DSDT full path has been specified (was the pb smith had in
     his first tries) and take it for the DSDT path as is.
    Then we have the case where no DSDT path was set where we run our usual DSDT search algorithm to find this file.
    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.
    
    Now a first idea to implement correctly the acpi tables loading would be:
    
    Whatever the path was hardcoded in the DSDT option or was automatically found, we extract the path part of 
    the DSDT file that has been successfully found and we run a loop to enumerate all other acpi files in the same directory.
    Now for each acpi file found, we should compare the name with an existing acpi table found in the system that
     we would normally load and replace this usual injection by the content of the file.
    
    Once DropDSDT=y is set, no other acpi table than dsdt is loaded, then it is the responsability of user
    to provide any other acpi table.

- Add a new module capable of writing proprietary Chameleon data to ioreg:
  Using the DT__xxx() API, we will create a set of functions to write
  to log info, chameleon boot info to be retrieved by helper applications...
  the only public function for log info purpose of this module would be:
  logMessageToIOREG(...); // var args printf style format
  flushLogToIOREG(); // store a unique log info property to the ioreg

  The preferred internal behavior of the log info ioreg buffer
  would be to store the messages in a consolidated buffer then only write once,
 this buffer (i.e just before call the kernel) with flushLogToIOREG();
  The other public function for writing chameleon boot info data would be:
   
  verbose() should incorporate a call to logMessageToIOREG() 
  to permit helper applications to extract
  this log info (i.e: the chameleon system pref pane)

- Add API for displaying and logging messages like:

    void verbose(...)
    {
     ...
       logMessageToIOREG("%s: %sn", title, s);

    }

    void display_and_log( const char* title, const char* msg) 
    {
       printf("%s: %sn", title, s);
       logMessageToIOREG(title,s);
    }

    void deprecated(const char * s)
    {
       display_and_log("WARNING: Deprecated option",s); 
       sleep(1);    
    }

    void error_message(const char * s)
    {
       display_and_log("ERROR",s); 
       getc();
    }

 - Case unsensitive parsing for the bootConfig options:
   should help the common/novice user to setup more easily.