diff options
Diffstat (limited to 'docs/git/index.html')
| -rw-r--r-- | docs/git/index.html | 127 |
1 files changed, 0 insertions, 127 deletions
diff --git a/docs/git/index.html b/docs/git/index.html index aaa2ff58..3f3894c6 100644 --- a/docs/git/index.html +++ b/docs/git/index.html @@ -266,133 +266,6 @@ <div class="section"> - <h1 id="config">Configuring libreboot</h1> - - <p> - Before building a ROM in libreboot (or coreboot, for that matter), you need to configure it. - Configuration files should already be included, so you don't need to do anything. This information - is only for reference. If you are updating or modifying coreboot-libre, and need to update the configs - in any way, refer to <a href="../maintain/index.html#newboard_libreboot">../maintain/index.html#newboard_libreboot</a>. - </p> - - <p> - If you've already built a kernel before, you know how to use this interface. - </p> - - <div class="subsection"> - <h2 id="config_dmidecode"> - dmidecode - </h2> - <p> - There is certain information that can be useful to enter in particular: - </p> - <ul> - <li>Local version string</li> - <li>SMBIOS Serial Number</li> - <li>SMBIOS Manufacturer</li> - <li>SMBIOS Version</li> - <li>SMBIOS Product name</li> - </ul> - <p> - This information can be obtained using:<br/> - <b>$ sudo dmidecode</b><br/> - <b># dmidecode</b> - </p> - <p> - Specifically, it's good practise to enter the same information for libreboot that you found when running this - with the original BIOS or firmware. <b>libreboot has already done this for you. This information is for reference, - in the hope that it will be useful.</b> - </p> - <p> - In practise, this information is useless and you can - just leave it on the defaults that coreboot uses (this - is what libreboot does, on most boards). - </p> - </div> - - <h2 id="config">GRUB payload</h2> - - <p> - GRUB is one of the payloads that libreboot targets. - </p> - - <p> - Configurations are then saved as files called <b>".config"</b>. Copies of each configuration used - for each system type by the libreboot build scripts are stored in resources/libreboot/config/grub/ - </p> - - <div class="subsection"> - <h3 id="config_x86"> - Generic configuration file (file: resources/libreboot/config/payload/board/config) - </h3> - <ul> - <li>General setup / Expert mode = <i>enable</i></li> - <li>General / Use CMOS for configuration values = <i>enable</i></li> - <li>Mainboard / Mainboard vendor = <i>Name of manufacturer</i></li> - <li>Mainboard / Mainboard model = <i>Model name</i></li> - <li>Mainboard / ROM chip size = <i>size of flash chip</i></li> - <li>Chipset / Include CPU microcode in CBFS = <i>Do not include microcode updates</i></li> - <li>Devices / Use native graphics initialization = <i>enable</i></li> - <li> - Display / Keep VESA framebuffer = <i>disable</i> (disable for text-mode graphics, enable for coreboot vesa framebuffer) - <ul> - <li>Libreboot provides this with text-mode enabled by default, but it automatically patches a copy of the config at build time - to enable coreboot framebuffer for a separate set of ROM images, in each system.</li> - </ul> - </li> - <li>Generic Drivers / USB 2.0 EHCI debug dongle support = <i>Enable</i></li> - <li>Generic Drivers / Enable early (pre-RAM) usbdebug = <i>Enable</i></li> - <li>Generic Drivers / Type of dongle = <i>Net20DC or compatible</i></li> - <li>Generic Drivers / Digitizer = <i>Present</i></li> - - <li>Console / USB dongle console output = <i>enable</i></li> - <li>Payload / Add a payload = <i>An ELF executable payload</i></li> - <li>Payload / Payload path and filename = <i>grub.elf</i></li> - </ul> - <p> - Now go back into Devices: - </p> - <ul> - <li>Devices / Run VGA Option ROMs = <i>disable</i></li> - <li>Devices / Run Option ROMs on PCI devices = <i>disable</i></li> - </ul> - <p> - The resulting .config file was saved as resources/libreboot/config/<b>payload/board/config</b> and is used by the build - scripts for this system. - </p> - </div> - - <h2 id="config_chromebook">Configuring libreboot for chromebooks</h2> - <p> - Depthcharge is one of the payloads that libreboot targets. - </p> - <p> - Configurations are then saved as files called <b>".config"</b>. Copies of each configuration used - for each system type by the libreboot build scripts are stored in resources/libreboot/config/depthcharge/ - </p> - <div class="subsection"> - <h3 id="config_arm"> - Generic configuration file (file: resources/libreboot/config/depthcharge/board/config) - </h3> - <ul> - <li>Mainboard / Mainboard vendor = <i>Google</i></li> - <li>Mainboard / Mainboard model = <i>name of model</i></li> - <li>Chipset / ChromeOS / Build for ChromeOS = <i>enable</i></li> - <li>Chipset / ChromeOS / Verify firmware with vboot. = <i>disable</i></li> - <li>Payload / Add a payload = <i>An ELF executable payload</i></li> - <li>Payload / Payload path and filename = <i>depthcharge.elf</i></li> - </ul> - <p> - The resulting .config file was saved as resources/libreboot/config/<b>depthcharge/board/config</b> and is used by the build - scripts for this system. - </p> - </div> - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - <h1 id="build">How to build the ROM images</h1> <p>You don't need to do much, as there are scripts already written for you that can build everything automatically.</p> |