diff options
author | Sylvestre Ledru <sylvestre.ledru@scilab.org> | 2011-04-04 18:04:46 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2011-04-04 20:51:47 -0400 |
commit | f65e51d740688b8a0ad15cbde34974e6c4559972 (patch) | |
tree | 73c1d7b91d2c222ae310529003bbc88fb281ae3c /Documentation/devicetree | |
parent | 44a4dcf75c58157a5d036ff783dfb2254703b93e (diff) |
Documentation: fix minor typos/spelling
Fix some minor typos:
* informations => information
* there own => their own
* these => this
Signed-off-by: Sylvestre Ledru <sylvestre.ledru@scilab.org>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/devicetree')
-rw-r--r-- | Documentation/devicetree/booting-without-of.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/devicetree/booting-without-of.txt b/Documentation/devicetree/booting-without-of.txt index 55fd2623445b..50619a0720a8 100644 --- a/Documentation/devicetree/booting-without-of.txt +++ b/Documentation/devicetree/booting-without-of.txt | |||
@@ -138,7 +138,7 @@ and properties to be present. This will be described in detail in | |||
138 | section III, but, for example, the kernel does not require you to | 138 | section III, but, for example, the kernel does not require you to |
139 | create a node for every PCI device in the system. It is a requirement | 139 | create a node for every PCI device in the system. It is a requirement |
140 | to have a node for PCI host bridges in order to provide interrupt | 140 | to have a node for PCI host bridges in order to provide interrupt |
141 | routing informations and memory/IO ranges, among others. It is also | 141 | routing information and memory/IO ranges, among others. It is also |
142 | recommended to define nodes for on chip devices and other buses that | 142 | recommended to define nodes for on chip devices and other buses that |
143 | don't specifically fit in an existing OF specification. This creates a | 143 | don't specifically fit in an existing OF specification. This creates a |
144 | great flexibility in the way the kernel can then probe those and match | 144 | great flexibility in the way the kernel can then probe those and match |
@@ -385,7 +385,7 @@ struct boot_param_header { | |||
385 | among others, by kexec. If you are on an SMP system, this value | 385 | among others, by kexec. If you are on an SMP system, this value |
386 | should match the content of the "reg" property of the CPU node in | 386 | should match the content of the "reg" property of the CPU node in |
387 | the device-tree corresponding to the CPU calling the kernel entry | 387 | the device-tree corresponding to the CPU calling the kernel entry |
388 | point (see further chapters for more informations on the required | 388 | point (see further chapters for more information on the required |
389 | device-tree contents) | 389 | device-tree contents) |
390 | 390 | ||
391 | - size_dt_strings | 391 | - size_dt_strings |
@@ -553,7 +553,7 @@ looks like in practice. | |||
553 | 553 | ||
554 | This tree is almost a minimal tree. It pretty much contains the | 554 | This tree is almost a minimal tree. It pretty much contains the |
555 | minimal set of required nodes and properties to boot a linux kernel; | 555 | minimal set of required nodes and properties to boot a linux kernel; |
556 | that is, some basic model informations at the root, the CPUs, and the | 556 | that is, some basic model information at the root, the CPUs, and the |
557 | physical memory layout. It also includes misc information passed | 557 | physical memory layout. It also includes misc information passed |
558 | through /chosen, like in this example, the platform type (mandatory) | 558 | through /chosen, like in this example, the platform type (mandatory) |
559 | and the kernel command line arguments (optional). | 559 | and the kernel command line arguments (optional). |