Difference between revisions of "Creating A devicetree.cb"
Eocallaghan (talk | contribs) (Initial.) |
Eocallaghan (talk | contribs) (Outline) |
||
Line 1: | Line 1: | ||
− | This article should help people who are writting a devicetree.cb for their system. | + | This article should help people who are writting a '''devicetree.cb''' for their system. |
== What you will need == | == What you will need == | ||
− | + | * '''lspci -nvvv''' output | |
== Introduction == | == Introduction == | ||
Line 12: | Line 12: | ||
When a device in '''devicetree.cb''' is found during the coreboot PCI/system scan process the functions to do customized initialization are called via the '''device_operations''' and the '''chip_operations''' structures. You will find these structures in the devices source files. | When a device in '''devicetree.cb''' is found during the coreboot PCI/system scan process the functions to do customized initialization are called via the '''device_operations''' and the '''chip_operations''' structures. You will find these structures in the devices source files. | ||
+ | |||
+ | == Keywords == | ||
+ | |||
+ | .. | ||
+ | |||
+ | == Syntax == | ||
+ | |||
+ | .. | ||
+ | |||
+ | == Grammar == | ||
+ | |||
+ | .. | ||
+ | |||
+ | == Examples == | ||
+ | |||
+ | === NorthBridge === | ||
+ | |||
+ | .. | ||
+ | |||
+ | === Super I/O === | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | {{Cc-by-2.5}} |
Revision as of 09:21, 18 February 2014
This article should help people who are writting a devicetree.cb for their system.
Contents
What you will need
- lspci -nvvv output
Introduction
The mainboard's devicetree.cb file contains many build and platform configuration settings. One of the most important items is the mainboard device list.
A device needs to be listed in the mainboard devicetree.cb if it requires more setup than standard PCI initialization (resource allocation). Typically, that includes the CPU, northbridge, southbridge, and Super I/O. These devices are usually required for system specific configuration as well as indicate the system bus structure (pci_domain).
When a device in devicetree.cb is found during the coreboot PCI/system scan process the functions to do customized initialization are called via the device_operations and the chip_operations structures. You will find these structures in the devices source files.
Keywords
..
Syntax
..
Grammar
..
Examples
NorthBridge
..
Super I/O
![]() ![]() |
This file is licensed under Creative Commons Attribution 2.5 License. In short: you are free to distribute and modify the file as long as you attribute its author(s) or licensor(s). |