build_config

type ChromeOSConfig struct {
	Identity        *ChromeOSConfig_Identity        `protobuf:"bytes,1,opt,name=identity,proto3" json:"identity,omitempty"`
	Arc             *ChromeOSConfig_Arc             `protobuf:"bytes,2,opt,name=arc,proto3" json:"arc,omitempty"`
	Firmware        *ChromeOSConfig_Firmware        `protobuf:"bytes,3,opt,name=firmware,proto3" json:"firmware,omitempty"`
	FirmwareSigning *ChromeOSConfig_FirmwareSigning `protobuf:"bytes,4,opt,name=firmware_signing,json=firmware-signing,proto3" json:"firmware_signing,omitempty"`
	// Unique name for the given model.
	Name string `protobuf:"bytes,5,opt,name=name,proto3" json:"name,omitempty"`
	// Brand code of the model (also called RLZ code).
	BrandCode string `protobuf:"bytes,6,opt,name=brand_code,json=brand-code,proto3" json:"brand_code,omitempty"`
	// contains filtered or unexported fields
}

type ChromeOSConfig_Arc struct {
	BuildProperties *ChromeOSConfig_Arc_BuildProperties `protobuf:"bytes,1,opt,name=build_properties,json=build-properties,proto3" json:"build_properties,omitempty"`
	// contains filtered or unexported fields
}

type ChromeOSConfig_Arc_BuildProperties struct {

	// Device name to report in ‘ro.product.device’. This is often
	// ‘{product}_cheets’ but it can be something else if desired.
	Device string `protobuf:"bytes,1,opt,name=device,proto3" json:"device,omitempty"`
	// The first Android API level that this model shipped with.
	FirstApiLevel string `protobuf:"bytes,2,opt,name=first_api_level,json=first-api-level,proto3" json:"first_api_level,omitempty"`
	// Name of this model as it is called in the market, reported in
	// ‘ro.product.model’. This often starts with ‘{oem}’.
	MarketingName string `protobuf:"bytes,3,opt,name=marketing_name,json=marketing-name,proto3" json:"marketing_name,omitempty"`
	// Tag to use to track metrics for this model. The tag can be shared
	// across many devices if desired, but this will result in larger
	// granularity for metrics reporting. Ideally the metrics system should
	// support collation of metrics with different tags into groups, but if
	// this is not supported, this tag can be used to achieve the same end.
	// This is reported in ‘ro.product.metrics.tag’.
	MetricsTag string `protobuf:"bytes,4,opt,name=metrics_tag,json=metrics-tag,proto3" json:"metrics_tag,omitempty"`
	// Original Equipment Manufacturer for this model. This generally means
	// the OEM name printed on the device.
	Oem        string `protobuf:"bytes,5,opt,name=oem,proto3" json:"oem,omitempty"`
	PaiRegions string `protobuf:"bytes,6,opt,name=pai_regions,json=pai-regions,proto3" json:"pai_regions,omitempty"`
	// Product name to report in ‘ro.product.name’. This may be the device
	// name, or it can be something else, to allow several devices to be
	// grouped into one product.
	Product string `protobuf:"bytes,7,opt,name=product,proto3" json:"product,omitempty"`
	// contains filtered or unexported fields
}

type ChromeOSConfig_Firmware struct {

	// BCS overlay path used to determine BCS file path for binary firmware
	// downloads.
	BcsOverlay string `protobuf:"bytes,1,opt,name=bcs_overlay,json=bcs-overlay,proto3" json:"bcs_overlay,omitempty"`
	// The name of the firmware build. Typically the device name, but can differ
	// when a device may have two or more different firmware builds.
	BuildName    string                                `protobuf:"bytes,2,opt,name=build_name,json=build-name,proto3" json:"build_name,omitempty"`
	BuildTargets *ChromeOSConfig_Firmware_BuildTargets `protobuf:"bytes,3,opt,name=build_targets,json=build-targets,proto3" json:"build_targets,omitempty"`
	// Name of the file located in BCS under the respective bcs-overlay.
	EcRoImage string `protobuf:"bytes,4,opt,name=ec_ro_image,json=ec-ro-image,proto3" json:"ec_ro_image,omitempty"`
	// Name of the file located in BCS under the respective bcs-overlay.
	MainRoImage string `protobuf:"bytes,5,opt,name=main_ro_image,json=main-ro-image,proto3" json:"main_ro_image,omitempty"`
	// Name of the file located in BCS under the respective bcs-overlay.
	MainRwImage string `protobuf:"bytes,6,opt,name=main_rw_image,json=main-rw-image,proto3" json:"main_rw_image,omitempty"`
	// This is a human-recognizable name used to refer to the firmware. It will
	// be used when generating the shellball via firmware packer. Mainly, this
	// is only for compatibility testing with device tree (since DT allowed
	// firmwares to be named).
	Name string `protobuf:"bytes,7,opt,name=name,proto3" json:"name,omitempty"`
	// If present this indicates that this model has no firmware at present.
	// This means that it will be omitted from the firmware updater
	// (chromeos-firmware- ebuild) and it will not be included in the signer
	// instructions file sent to the signer. This option is often useful when a
	// model is first added, since it may not have firmware at that point.
	NoFirmware bool `protobuf:"varint,8,opt,name=no_firmware,json=no-firmware,proto3" json:"no_firmware,omitempty"`
	// Name of the file located in BCS under the respective bcs-overlay.
	PdRoImage string `protobuf:"bytes,9,opt,name=pd_ro_image,json=pd-ro-image,proto3" json:"pd_ro_image,omitempty"`
	// contains filtered or unexported fields
}

type ChromeOSConfig_FirmwareSigning struct {

	// Key ID from the signer key set that is used to sign the given firmware
	// image.
	KeyId string `protobuf:"bytes,1,opt,name=key_id,json=key-id,proto3" json:"key_id,omitempty"`
	//   Indicates that this model cannot be decoded by the mapping table.
	//   Instead the model is stored in the VPD (Vital Product Data) region in
	//   the customization_id property. This allows us to determine the model to
	//   use in the factory during the finalization stage. Note that if the VPD
	//   is wiped then the model will be lost. This may mean that the device
	//   will revert back to a generic model, or may not work. It is not
	//   possible in general to test whether the model in the VPD is correct at
	//   run-time. We simply assume that it is. The advantage of using this
	//   property is that no hardware changes are needed to change one model
	//   into another. For example we can create 20 different whitelabel boards,
	//   all with the same hardware, just by changing the customization_id that
	//   is written into SPI flash.
	SigIdInCustomizationId bool `` /* 138-byte string literal not displayed */
	// ID used to generate keys/keyblocks in the firmware signing output. This
	// is also the value provided to mosys platform signature for the
	// updater4.sh script.
	SignatureId string `protobuf:"bytes,3,opt,name=signature_id,json=signature-id,proto3" json:"signature_id,omitempty"`
	// contains filtered or unexported fields
}

type ChromeOSConfig_Firmware_BuildTargets struct {

	// Build target of the base EC firmware for a detachable device, that will
	// be considered dirty when building/testing
	Base string `protobuf:"bytes,1,opt,name=base,proto3" json:"base,omitempty"`
	// Build target that will be considered dirty when building/testing
	// locally.
	Coreboot string `protobuf:"bytes,2,opt,name=coreboot,proto3" json:"coreboot,omitempty"`
	// Build target that will be considered dirty when building/testing
	// locally.
	Cr50 string `protobuf:"bytes,3,opt,name=cr50,proto3" json:"cr50,omitempty"`
	// Build target that will be considered dirty when building/testing
	// locally.
	Depthcharge string `protobuf:"bytes,4,opt,name=depthcharge,proto3" json:"depthcharge,omitempty"`
	// Build target that will be considered dirty when building/testing
	// locally.
	Ec string `protobuf:"bytes,5,opt,name=ec,proto3" json:"ec,omitempty"`
	// Extra EC build targets to build within chromeos-ec.
	EcExtras []string `protobuf:"bytes,6,rep,name=ec_extras,json=ecExtras,proto3" json:"ec_extras,omitempty"`
	// Build target that will be considered dirty when building/testing
	// locally.
	Ish string `protobuf:"bytes,7,opt,name=ish,proto3" json:"ish,omitempty"`
	// Build target that will be considered dirty when building/testing
	// locally.
	Libpayload string `protobuf:"bytes,8,opt,name=libpayload,proto3" json:"libpayload,omitempty"`
	// Build target that will be considered dirty when building/testing
	// locally.
	UBoot string `protobuf:"bytes,9,opt,name=u_boot,json=u-boot,proto3" json:"u_boot,omitempty"`
	// contains filtered or unexported fields
}

type ChromeOSConfig_Identity struct {

	// ‘customization_id’ value set in the VPD for non-unibuild Zergs and
	// Whitelabels. Deprecated for use in new products since 2017/07/26.
	CustomizationId string `protobuf:"bytes,1,opt,name=customization_id,json=customization-id,proto3" json:"customization_id,omitempty"`
	// Defines the name that is reported by ‘mosys platform name’ This is
	// typically the reference design name with the first letter capitalized.
	PlatformName string `protobuf:"bytes,2,opt,name=platform_name,json=platform-name,proto3" json:"platform_name,omitempty"`
	// SKU/Board strapping pins configured during board manufacturing. Minimum
	// value: -0x1. Maximum value: 0x7fffffff.
	SkuId int64 `protobuf:"varint,3,opt,name=sku_id,json=sku-id,proto3" json:"sku_id,omitempty"`
	// [x86] Firmware name built into the firmware and reflected back out in the
	// SMBIOS tables.
	SmbiosNameMatch string `protobuf:"bytes,4,opt,name=smbios_name_match,json=smbios-name-match,proto3" json:"smbios_name_match,omitempty"`
	// [ARM] String pattern (partial) that is matched against the contents of
	// /proc/device-tree/compatible on ARM devices.
	DeviceTreeCompatibleMatch string `` /* 143-byte string literal not displayed */
	// ‘whitelabel_tag’ value set in the VPD, to add Whitelabel branding over an
	// unbranded base model.
	WhitelabelTag string `protobuf:"bytes,6,opt,name=whitelabel_tag,json=whitelabel-tag,proto3" json:"whitelabel_tag,omitempty"`
	// contains filtered or unexported fields
}

type ChromeOSConfigs struct {
	Configs []*ChromeOSConfig `protobuf:"bytes,1,rep,name=configs,proto3" json:"configs,omitempty"`
	// contains filtered or unexported fields
}