path: root/Documentation/devicetree/booting-without-of.txt
AgeCommit message (Collapse)AuthorFilesLines
2016-03-17sh: add device tree support and generic board using device treeRich Felker1-0/+13
Add a new pseudo-board, within the existing SH boards/machine-vectors framework, which does not represent any actual hardware but instead requires all hardware to be described by the device tree blob provided by the boot loader. Changes made are thus non-invasive and do not risk breaking support for legacy boards. New hardware, including the open-hardware J2 and associated SoC devices, will use device free from the outset. Legacy SH boards can transition to device tree once all their hardware has device tree bindings, driver support for device tree, and a dts file for the board. It is intented that, once all boards are supported in the new framework, the existing machine-vectors framework should be removed and the new device tree setup code integrated directly. Signed-off-by: Rich Felker <>
2015-05-08ARM: 8354/1: Documentation: devicetree: root node serial-number property ↵Paul Kocialkowski1-0/+4
documentation Open firmware is already using the serial-number property for passing the device's serial number from the bootloader to the kernel. In addition, lshw already has support for scanning this property. The serial number is a string that somewhat represents the device's serial number. It might come from some form of storage (e.g. an eeprom) and be programmed at factory-time by the manufacturer or come from identification bits available in e.g. the SoC (note that the soc_id property in the SoC bus should hold a full account of those bits). The serial number is taken as-is from the bootloader, so it is up to the bootloader to define where the serial number comes from and what length it should be. Some use cases for the serial number require it to have a maximum length (e.g. for USB serial number) and some other cases imply more restrictions on what the serial number should look like (e.g. in Android, the ro.serialno property is usually a 16-bytes (plus one null byte) representation of a 64 bit number). Signed-off-by: Paul Kocialkowski <> Acked-by: Rob Herring <> Signed-off-by: Russell King <>
2015-04-01MIPS: BMIPS: Document the firmware->kernel DTB interfaceKevin Cernekee1-0/+28
Add a new section covering the Generic BMIPS machine type. Signed-off-by: Kevin Cernekee <> Cc: Cc: Cc: Cc: Cc: Cc: Cc: Cc: Cc: Cc: Cc: Patchwork: Signed-off-by: Ralf Baechle <>
2014-09-26dt/documentation: add specification of dma bus informationSantosh Shilimkar1-0/+53
Recently we introduced the generic device tree infrastructure for couple of DMA bus parameter, dma-ranges and dma-coherent. Update the documentation so that its useful for future users. The "dma-ranges" property is intended to be used for describing the configuration of DMA bus RAM addresses and its offset w.r.t CPU addresses. The "dma-coherent" property is intended to be used for identifying devices supported coherent DMA operations. Cc: Arnd Bergmann <> Cc: Grant Likely <> Cc: Rob Herring <> Cc: Pawel Moll <> Cc: Mark Rutland <> Cc: Ian Campbell <> Cc: Kumar Gala <> Acked-by: Shawn Guo <> Signed-off-by: Grygorii Strashko <> Signed-off-by: Santosh Shilimkar <> Signed-off-by: Rob Herring <>
2014-01-16dt/bindings: Remove all references to device_type "ethernet-phy"Grant Likely1-3/+0
The device_type property is deprecated for the flattened device tree and the value "ethernet-phy" has never been defined as having a useful meaning. Neither the kernel nor u-boot depend on it. It should never have appeared in PHY bindings. This patch removes all references to "ethernet-phy" as a device_type value from the documentation and the .dts files. This patch was generated mechanically with the following command and then verified by looking at the diff. sed -i '/"ethernet-phy"/d' `git grep -l '"ethernet-phy"'` Signed-off-by: Grant Likely <> Acked-by: Srinivas Kandagatla <> Cc: Rob Herring <> Cc: Pawel Moll <> Cc: Mark Rutland <> Cc: Ian Campbell <> Cc: Kumar Gala <> Cc: Florian Fainelli <> Cc: Benjamin Herrenschmidt <> documentation fixesChristian Kujau1-1/+1
After I came across a help text for SUNGEM mentioning a broken URL, I felt like fixing those up, as they are now pointing to URLs. Signed-off-by: Christian Kujau <> Acked-by: David S. Miller <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
2012-05-19dt/documentation: Fix value format descriptionRoland Stigge1-27/+28
Numeric values in dts files can be specified in decimal and hex (the latter prefixed 0x). The current documentation is updated with this patch to prevent confusion about what is meant with values without "0x" (previously hex, now dec). Signed-off-by: Roland Stigge <> Acked-by: Rob Landley <> Signed-off-by: Grant Likely <>
2012-03-07Documentation: Fix multiple typo in DocumentationMasanari Iida1-1/+1
Signed-off-by: Masanari Iida <> Acked-by: Randy Dunlap <> Signed-off-by: Jiri Kosina <>
2011-05-23dt: add documentation of ARM dt boot interfaceGrant Likely1-4/+44
v6: typo fixes v5: clarified that dtb should be aligned on a 64 bit boundary in RAM. v3: added details to Documentation/arm/Booting Acked-by: Tony Lindgren <> Acked-by: Nicolas Pitre <> Acked-by: Russell King <> Signed-off-by: Grant Likely <>
2011-04-04Documentation: fix minor typos/spellingSylvestre Ledru1-3/+3
Fix some minor typos: * informations => information * there own => their own * these => this Signed-off-by: Sylvestre Ledru <> Signed-off-by: Randy Dunlap <> Signed-off-by: Linus Torvalds <>
2011-02-23x86: Add device tree supportSebastian Andrzej Siewior1-0/+20
This patch adds minimal support for device tree on x86. The device tree blob is passed to the kernel via setup_data which requires at least boot protocol 2.09. Memory size, restricted memory regions, boot arguments are gathered the traditional way so things like cmd_line are just here to let the code compile. The current plan is use the device tree as an extension and to gather information which can not be enumerated and would have to be hardcoded otherwise. This includes things like - which devices are on this I2C/SPI bus? - how are the interrupts wired to IO APIC? - where could my hpet be? Signed-off-by: Sebastian Andrzej Siewior <> Signed-off-by: Dirk Brandewie <> Acked-by: Grant Likely <> Cc: Cc: LKML-Reference: <> Signed-off-by: Thomas Gleixner <>
2011-02-14Revert "dt: add documentation of ARM dt boot interface"Grant Likely1-40/+0
This reverts commit 9830fcd6f6a4781d8b46d2b35c13b39f30915c63. The ARM dt support has not been merged yet; this documentation update was premature. Signed-off-by: Grant Likely <>
2011-01-31dt: add documentation of ARM dt boot interfaceGrant Likely1-0/+40
v3: added details to Documentation/arm/Booting Signed-off-by: Grant Likely <>
2011-01-31dt: Remove obsolete description of powerpc boot interfaceGrant Likely1-111/+54
32 and 64 bit powerpc support has been merged for a while now, but the booting-without-of.txt document still describes 32 bit as not supporting multiplatform, which is no longer true. This patch fixes the documentation. Also remove references to powerpc-specific details outside of section I in preparation to add details for other architectures. v3: cleaned up a lot more powerpc-isms and updated text to reflect current usage conventions. Signed-off-by: Grant Likely <>
2011-01-31dt: Move device tree documentation out of powerpc directoryGrant Likely1-0/+1447
The device tree is used by more than just PowerPC. Make the documentation directory available to all. v2: reorganized files while moving to create arch and driver specific directories. Signed-off-by: Grant Likely <> Acked-by: Josh Boyer <>