Difference between revisions of "Category:Modules"

From Syslinux Wiki
Jump to: navigation, search
m (Revert redirect. Since v5.00, "Modules" is a more adequate name than "Comboot".)
(Mention .cbt modules. Link to Doc/comboot. Wiki formatting.)
 
Line 1: Line 1:
Comboot modules utilize the Syslinux [[Comboot API]] to provide features to a few niche cases.  These are loaded using the ''kernel'' option with a special ending of '''.com''' or '''.c32'''. Comboot modules are special as they don't actually leave the PXE stack, and instead just invoke the [[Comboot API]] enabling items like DMI parsing, evaluating CPU flags, scanning the PCI bus, staging up multiple images at once, etc!  If the module fails to load properly, then you are still in the syslinux stack and things are returned to the original syslinux state (for the most part).
+
Comboot modules utilize the Syslinux [[Comboot API]] to provide features to a few niche cases.   
 +
These are loaded using the <tt>KERNEL</tt> directive with a special ending of:
 +
* "<tt>.com</tt>" <small>{{v|-4.xx}}</small> or;
 +
* "<tt>.cbt</tt>" <small>{{v|-4.xx}}</small> or;
 +
* "<tt>.c32</tt>".
 +
 
 +
Comboot modules are special as they don't actually leave the PXE stack,  
 +
and instead just invoke the [[Comboot API]] enabling items like  
 +
DMI parsing, evaluating CPU flags, scanning the PCI bus, staging up multiple images at once, etc!   
 +
If the module fails to load properly, then you are still in the Syslinux stack  
 +
and things are returned to the original Syslinux state (for the most part).
 +
 
 +
See also [[Doc/comboot|doc/comboot.txt]].
  
 
Below are the currently documented comboot modules.
 
Below are the currently documented comboot modules.
 +
<br />

Latest revision as of 18:01, 22 December 2018

Comboot modules utilize the Syslinux Comboot API to provide features to a few niche cases. These are loaded using the KERNEL directive with a special ending of:

  • ".com" [-4.xx] or;
  • ".cbt" [-4.xx] or;
  • ".c32".

Comboot modules are special as they don't actually leave the PXE stack, and instead just invoke the Comboot API enabling items like DMI parsing, evaluating CPU flags, scanning the PCI bus, staging up multiple images at once, etc! If the module fails to load properly, then you are still in the Syslinux stack and things are returned to the original Syslinux state (for the most part).

See also doc/comboot.txt.

Below are the currently documented comboot modules.