Ticket #2980: docs_typos.patch

File docs_typos.patch, 4.3 KB (added by Jesper Dangaard Brouer <hawk@…>, 10 years ago)

Trivial typo fix for docs

  • docs/bugs.tex

     
    4545\item the problem cannot be reproduced by the developers (worksforme) 
    4646\end{itemize} 
    4747 
    48 A the same time, the reporter may want to get the ticket closed since he is not  
     48At the same time, the reporter may want to get the ticket closed since he is not  
    4949longer able to trigger the bug, or found it invalid by himself. 
    5050 
    5151When a ticket is closed by a developer and marked as "fixed", the comment contains  
  • docs/adding.tex

     
    1515 
    1616This is one of the reasons why OpenWrt and other firmware exists: providing a  
    1717version independent, and tools independent firmware, that can be run on various  
    18 platforms, known to be running Linux originaly. 
     18platforms, known to be running Linux originally. 
    1919 
    2020\subsection{Which Operating System does this device run?} 
    2121 
     
    135135 
    136136By using a serial port and a level shifter, you may reach the console that is being shown by the device 
    137137for debugging or flashing purposes. By analysing the output of this device, you can 
    138 easily notice if the device uses a Linux kenrel or something different. 
     138easily notice if the device uses a Linux kernel or something different. 
    139139 
    140140\subsection{Finding and using the manufacturer SDK} 
    141141 
     
    238238may not always be relevant, so that you have to clean up those patches to only  
    239239let the "must have" code into them. 
    240240 
    241 The fist patch will contain all the code that is needed by the board to be  
     241The first patch will contain all the code that is needed by the board to be  
    242242initialized at startup, as well as processor detection and other boot time  
    243243specific fixes. 
    244244 
    245 The second patch will contain all useful definitions for that board: adresses,  
     245The second patch will contain all useful definitions for that board: addresses,  
    246246kernel granularity, redefinitions, processor family and features ... 
    247247 
    248248The third patch may contain drivers for: serial console, ethernet NIC, wireless  
     
    256256The bootloader is the first program that is started right after your device has  
    257257been powered on. This program, can be more or less sophisticated, some do let you  
    258258do network booting, USB mass storage booting ... The bootloader is device and  
    259 architeture specific, some bootloaders were designed to be universal such as  
     259architecture specific, some bootloaders were designed to be universal such as  
    260260RedBoot or U-Boot so that you can meet those loaders on totally different  
    261261platforms and expect them to behave the same way. 
    262262 
     
    331331of running a custom firmware on your device, because this is sometimes a blocking 
    332332part of the flashing process. 
    333333 
    334 A firmare format is most of the time composed of the following fields: 
     334A firmware format is most of the time composed of the following fields: 
    335335 
    336336\begin{itemize} 
    337 \item header, containing a firmare version and additional fields: Vendor, Hardware version ... 
     337\item header, containing a firmware version and additional fields: Vendor, Hardware version ... 
    338338\item CRC32 checksum on either the whole file or just part of it 
    339339\item Binary and/or compressed kernel image 
    340340\item Binary and/or compressed root filesystem image 
     
    342342\end{itemize} 
    343343 
    344344Once you have figured out how the firmware format is partitioned, you will have  
    345 to write your own tool that produces valid firmare binaries. One thing to be very 
     345to write your own tool that produces valid firmware binaries. One thing to be very 
    346346careful here is the endianness of either the machine that produces the binary  
    347347firmware and the device that will be flashed using this binary firmware. 
    348348 
     
    418418               return -EIO; 
    419419       } 
    420420 
    421            // Initlialise the device map 
     421           // Initialize the device map 
    422422       simple_map_init(&device_map); 
    423423 
    424424           /* MTD informations are closely linked to the flash map device 
     
    474474module_exit(device_mtd_cleanup); 
    475475 
    476476 
    477 // Macros defining licence and author, parameters can be defined here too. 
     477// Macros defining license and author, parameters can be defined here too. 
    478478MODULE_LICENSE("GPL"); 
    479479MODULE_AUTHOR("Me, myself and I <memyselfandi@domain.tld"); 
    480480\end{verbatim}