Provided by: vboot-utils_0~20121212-3_amd64 bug

NAME

       crossystem - Chrome OS firmware/system interface utility

DESCRIPTION

   Usage:
              crossystem [--all]

              Prints all parameters with descriptions and current values.  If --all is specified,
              prints even normally hidden fields.

              crossystem [param1 [param2 [...]]]

              Prints the current value(s) of the parameter(s).

              crossystem [param1=value1] [param2=value2 [...]]]

              Sets the parameter(s) to the specified value(s).

              crossystem [param1?value1] [param2?value2 [...]]]

              Checks if the parameter(s) all contain the specified value(s).

       Stops at the first error.  Valid parameters:

       arch   Platform architecture

       clear_tpm_owner_request
              Clear TPM owner on next boot

       clear_tpm_owner_done
              Clear TPM owner done

       cros_debug
              OS should allow debug features

       dbg_reset
              Debug reset mode request (writable)

       ddr_type
              Type of DDR RAM

       disable_dev_request
              Disable virtual dev-mode on next boot

       dev_boot_usb
              Enable developer mode boot from USB/SD (writable)

       dev_boot_legacy
              Enable developer mode boot Legacy OSes (writable)

       dev_boot_signed_only
              Enable developer mode boot only from official kernels (writable)

       devsw_boot
              Developer switch position at boot

       devsw_cur
              Developer switch current position

       ecfw_act
              Active EC firmware

       fmap_base
              Main firmware flashmap physical address

       fwb_tries
              Try firmware B count (writable)

       fwid   Active firmware ID

       fwupdate_tries
              Times to try OS firmware update (writable, inside kern_nv)

       hwid   Hardware ID

       kern_nv
              Non-volatile field for kernel use

       kernkey_vfy
              Type of verification done on kernel key block

       loc_idx
              Localization index for firmware screens (writable)

       mainfw_act
              Active main firmware

       mainfw_type
              Active main firmware type

       nvram_cleared
              Have NV settings been lost?  Write 0 to clear

       oprom_needed
              Should we load the VGA Option ROM at boot?

       platform_family
              Platform family type

       recovery_reason
              Recovery mode reason for current boot

       recovery_request
              Recovery mode request (writable)

       recoverysw_boot
              Recovery switch position at boot

       recoverysw_cur
              Recovery switch current position

       recoverysw_ec_boot
              Recovery switch position at EC boot

       ro_fwid
              Read-only firmware ID

       savedmem_base
              RAM debug data area physical address

       savedmem_size
              RAM debug data area size in bytes

       sw_wpsw_boot
              Firmware write protect software setting enabled at boot

       tpm_fwver
              Firmware version stored in TPM

       tpm_kernver
              Kernel version stored in TPM

       tried_fwb
              Tried firmware B before A this boot

       vdat_flags
              Flags from VbSharedData

       vdat_lfdebug
              LoadFirmware() debug data (not in print-all)

       vdat_lkdebug
              LoadKernel() debug data (not in print-all)

       vdat_timers
              Timer values from VbSharedData

       wpsw_boot
              Firmware write protect hardware switch position at boot

       wpsw_cur
              Firmware write protect hardware switch current position

SEE ALSO

       The full documentation for crossystem is maintained as a Texinfo manual.  If the info  and
       crossystem programs are properly installed at your site, the command

              info crossystem

       should give you access to the complete manual.