README 113 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587158815891590159115921593159415951596159715981599160016011602160316041605160616071608160916101611161216131614161516161617161816191620162116221623162416251626162716281629163016311632163316341635163616371638163916401641164216431644164516461647164816491650165116521653165416551656165716581659166016611662166316641665166616671668166916701671167216731674167516761677167816791680168116821683168416851686168716881689169016911692169316941695169616971698169917001701170217031704170517061707170817091710171117121713171417151716171717181719172017211722172317241725172617271728172917301731173217331734173517361737173817391740174117421743174417451746174717481749175017511752175317541755175617571758175917601761176217631764176517661767176817691770177117721773177417751776177717781779178017811782178317841785178617871788178917901791179217931794179517961797179817991800180118021803180418051806180718081809181018111812181318141815181618171818181918201821182218231824182518261827182818291830183118321833183418351836183718381839184018411842184318441845184618471848184918501851185218531854185518561857185818591860186118621863186418651866186718681869187018711872187318741875187618771878187918801881188218831884188518861887188818891890189118921893189418951896189718981899190019011902190319041905190619071908190919101911191219131914191519161917191819191920192119221923192419251926192719281929193019311932193319341935193619371938193919401941194219431944194519461947194819491950195119521953195419551956195719581959196019611962196319641965196619671968196919701971197219731974197519761977197819791980198119821983198419851986198719881989199019911992199319941995199619971998199920002001200220032004200520062007200820092010201120122013201420152016201720182019202020212022202320242025202620272028202920302031203220332034203520362037203820392040204120422043204420452046204720482049205020512052205320542055205620572058205920602061206220632064206520662067206820692070207120722073207420752076207720782079208020812082208320842085208620872088208920902091209220932094209520962097209820992100210121022103210421052106210721082109211021112112211321142115211621172118211921202121212221232124212521262127212821292130213121322133213421352136213721382139214021412142214321442145214621472148214921502151215221532154215521562157215821592160216121622163216421652166216721682169217021712172217321742175217621772178217921802181218221832184218521862187218821892190219121922193219421952196219721982199220022012202220322042205220622072208220922102211221222132214221522162217221822192220222122222223222422252226222722282229223022312232223322342235223622372238223922402241224222432244224522462247224822492250225122522253225422552256225722582259226022612262226322642265226622672268226922702271227222732274227522762277227822792280228122822283228422852286228722882289229022912292229322942295229622972298229923002301230223032304230523062307230823092310231123122313231423152316231723182319232023212322232323242325232623272328232923302331233223332334233523362337233823392340234123422343234423452346234723482349235023512352235323542355235623572358235923602361236223632364236523662367236823692370237123722373237423752376237723782379238023812382238323842385238623872388238923902391239223932394239523962397239823992400240124022403240424052406240724082409241024112412241324142415241624172418241924202421242224232424242524262427242824292430243124322433243424352436243724382439244024412442244324442445244624472448244924502451245224532454245524562457245824592460246124622463246424652466246724682469247024712472247324742475247624772478247924802481248224832484248524862487248824892490249124922493249424952496249724982499250025012502250325042505250625072508250925102511251225132514251525162517251825192520252125222523252425252526252725282529253025312532253325342535253625372538253925402541254225432544254525462547254825492550255125522553255425552556255725582559256025612562256325642565256625672568256925702571257225732574257525762577257825792580258125822583258425852586258725882589259025912592259325942595259625972598259926002601260226032604260526062607260826092610261126122613261426152616261726182619262026212622262326242625262626272628262926302631263226332634263526362637263826392640264126422643264426452646264726482649265026512652265326542655265626572658265926602661266226632664266526662667266826692670267126722673267426752676267726782679268026812682268326842685268626872688268926902691269226932694269526962697269826992700270127022703270427052706270727082709271027112712271327142715271627172718271927202721272227232724272527262727272827292730273127322733273427352736273727382739274027412742274327442745274627472748274927502751275227532754275527562757275827592760276127622763276427652766276727682769277027712772277327742775277627772778277927802781278227832784278527862787278827892790279127922793279427952796279727982799280028012802280328042805280628072808280928102811281228132814281528162817281828192820282128222823282428252826282728282829283028312832283328342835283628372838283928402841284228432844284528462847284828492850285128522853285428552856285728582859286028612862286328642865286628672868286928702871287228732874287528762877287828792880288128822883288428852886288728882889289028912892289328942895289628972898289929002901290229032904290529062907290829092910291129122913291429152916291729182919292029212922292329242925292629272928292929302931293229332934293529362937293829392940294129422943294429452946294729482949295029512952295329542955295629572958295929602961296229632964296529662967296829692970297129722973297429752976297729782979298029812982298329842985298629872988298929902991299229932994299529962997299829993000300130023003300430053006300730083009301030113012301330143015301630173018301930203021302230233024302530263027302830293030303130323033303430353036303730383039304030413042304330443045304630473048304930503051305230533054305530563057305830593060306130623063306430653066306730683069307030713072307330743075307630773078307930803081308230833084308530863087308830893090309130923093309430953096309730983099310031013102310331043105310631073108310931103111311231133114311531163117311831193120312131223123312431253126312731283129313031313132313331343135313631373138313931403141314231433144314531463147314831493150315131523153315431553156315731583159316031613162316331643165316631673168316931703171317231733174317531763177317831793180318131823183318431853186318731883189319031913192319331943195319631973198319932003201320232033204320532063207320832093210321132123213321432153216321732183219322032213222322332243225322632273228322932303231323232333234323532363237323832393240324132423243324432453246324732483249325032513252325332543255325632573258325932603261326232633264326532663267326832693270327132723273327432753276327732783279328032813282328332843285328632873288328932903291329232933294329532963297329832993300330133023303330433053306330733083309331033113312331333143315331633173318331933203321332233233324332533263327332833293330333133323333333433353336333733383339334033413342334333443345334633473348334933503351335233533354335533563357335833593360336133623363336433653366336733683369337033713372337333743375337633773378337933803381338233833384338533863387338833893390339133923393339433953396339733983399340034013402340334043405340634073408340934103411341234133414341534163417341834193420342134223423342434253426342734283429343034313432343334343435343634373438343934403441344234433444
  1. #
  2. # (C) Copyright 2000 - 2005
  3. # Wolfgang Denk, DENX Software Engineering, wd@denx.de.
  4. #
  5. # See file CREDITS for list of people who contributed to this
  6. # project.
  7. #
  8. # This program is free software; you can redistribute it and/or
  9. # modify it under the terms of the GNU General Public License as
  10. # published by the Free Software Foundation; either version 2 of
  11. # the License, or (at your option) any later version.
  12. #
  13. # This program is distributed in the hope that it will be useful,
  14. # but WITHOUT ANY WARRANTY; without even the implied warranty of
  15. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  16. # GNU General Public License for more details.
  17. #
  18. # You should have received a copy of the GNU General Public License
  19. # along with this program; if not, write to the Free Software
  20. # Foundation, Inc., 59 Temple Place, Suite 330, Boston,
  21. # MA 02111-1307 USA
  22. #
  23. Summary:
  24. ========
  25. This directory contains the source code for U-Boot, a boot loader for
  26. Embedded boards based on PowerPC, ARM, MIPS and several other
  27. processors, which can be installed in a boot ROM and used to
  28. initialize and test the hardware or to download and run application
  29. code.
  30. The development of U-Boot is closely related to Linux: some parts of
  31. the source code originate in the Linux source tree, we have some
  32. header files in common, and special provision has been made to
  33. support booting of Linux images.
  34. Some attention has been paid to make this software easily
  35. configurable and extendable. For instance, all monitor commands are
  36. implemented with the same call interface, so that it's very easy to
  37. add new commands. Also, instead of permanently adding rarely used
  38. code (for instance hardware test utilities) to the monitor, you can
  39. load and run it dynamically.
  40. Status:
  41. =======
  42. In general, all boards for which a configuration option exists in the
  43. Makefile have been tested to some extent and can be considered
  44. "working". In fact, many of them are used in production systems.
  45. In case of problems see the CHANGELOG and CREDITS files to find out
  46. who contributed the specific port.
  47. Where to get help:
  48. ==================
  49. In case you have questions about, problems with or contributions for
  50. U-Boot you should send a message to the U-Boot mailing list at
  51. <u-boot-users@lists.sourceforge.net>. There is also an archive of
  52. previous traffic on the mailing list - please search the archive
  53. before asking FAQ's. Please see
  54. http://lists.sourceforge.net/lists/listinfo/u-boot-users/
  55. Where we come from:
  56. ===================
  57. - start from 8xxrom sources
  58. - create PPCBoot project (http://sourceforge.net/projects/ppcboot)
  59. - clean up code
  60. - make it easier to add custom boards
  61. - make it possible to add other [PowerPC] CPUs
  62. - extend functions, especially:
  63. * Provide extended interface to Linux boot loader
  64. * S-Record download
  65. * network boot
  66. * PCMCIA / CompactFLash / ATA disk / SCSI ... boot
  67. - create ARMBoot project (http://sourceforge.net/projects/armboot)
  68. - add other CPU families (starting with ARM)
  69. - create U-Boot project (http://sourceforge.net/projects/u-boot)
  70. Names and Spelling:
  71. ===================
  72. The "official" name of this project is "Das U-Boot". The spelling
  73. "U-Boot" shall be used in all written text (documentation, comments
  74. in source files etc.). Example:
  75. This is the README file for the U-Boot project.
  76. File names etc. shall be based on the string "u-boot". Examples:
  77. include/asm-ppc/u-boot.h
  78. #include <asm/u-boot.h>
  79. Variable names, preprocessor constants etc. shall be either based on
  80. the string "u_boot" or on "U_BOOT". Example:
  81. U_BOOT_VERSION u_boot_logo
  82. IH_OS_U_BOOT u_boot_hush_start
  83. Versioning:
  84. ===========
  85. U-Boot uses a 3 level version number containing a version, a
  86. sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2",
  87. sub-version "34", and patchlevel "4".
  88. The patchlevel is used to indicate certain stages of development
  89. between released versions, i. e. officially released versions of
  90. U-Boot will always have a patchlevel of "0".
  91. Directory Hierarchy:
  92. ====================
  93. - board Board dependent files
  94. - common Misc architecture independent functions
  95. - cpu CPU specific files
  96. - 74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs
  97. - arm720t Files specific to ARM 720 CPUs
  98. - arm920t Files specific to ARM 920 CPUs
  99. - at91rm9200 Files specific to Atmel AT91RM9200 CPU
  100. - imx Files specific to Freescale MC9328 i.MX CPUs
  101. - s3c24x0 Files specific to Samsung S3C24X0 CPUs
  102. - arm925t Files specific to ARM 925 CPUs
  103. - arm926ejs Files specific to ARM 926 CPUs
  104. - arm1136 Files specific to ARM 1136 CPUs
  105. - i386 Files specific to i386 CPUs
  106. - ixp Files specific to Intel XScale IXP CPUs
  107. - mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs
  108. - mips Files specific to MIPS CPUs
  109. - mpc5xx Files specific to Freescale MPC5xx CPUs
  110. - mpc5xxx Files specific to Freescale MPC5xxx CPUs
  111. - mpc8xx Files specific to Freescale MPC8xx CPUs
  112. - mpc8220 Files specific to Freescale MPC8220 CPUs
  113. - mpc824x Files specific to Freescale MPC824x CPUs
  114. - mpc8260 Files specific to Freescale MPC8260 CPUs
  115. - mpc85xx Files specific to Freescale MPC85xx CPUs
  116. - nios Files specific to Altera NIOS CPUs
  117. - nios2 Files specific to Altera Nios-II CPUs
  118. - ppc4xx Files specific to IBM PowerPC 4xx CPUs
  119. - pxa Files specific to Intel XScale PXA CPUs
  120. - s3c44b0 Files specific to Samsung S3C44B0 CPUs
  121. - sa1100 Files specific to Intel StrongARM SA1100 CPUs
  122. - disk Code for disk drive partition handling
  123. - doc Documentation (don't expect too much)
  124. - drivers Commonly used device drivers
  125. - dtt Digital Thermometer and Thermostat drivers
  126. - examples Example code for standalone applications, etc.
  127. - include Header Files
  128. - lib_arm Files generic to ARM architecture
  129. - lib_generic Files generic to all architectures
  130. - lib_i386 Files generic to i386 architecture
  131. - lib_m68k Files generic to m68k architecture
  132. - lib_mips Files generic to MIPS architecture
  133. - lib_nios Files generic to NIOS architecture
  134. - lib_ppc Files generic to PowerPC architecture
  135. - net Networking code
  136. - post Power On Self Test
  137. - rtc Real Time Clock drivers
  138. - tools Tools to build S-Record or U-Boot images, etc.
  139. Software Configuration:
  140. =======================
  141. Configuration is usually done using C preprocessor defines; the
  142. rationale behind that is to avoid dead code whenever possible.
  143. There are two classes of configuration variables:
  144. * Configuration _OPTIONS_:
  145. These are selectable by the user and have names beginning with
  146. "CONFIG_".
  147. * Configuration _SETTINGS_:
  148. These depend on the hardware etc. and should not be meddled with if
  149. you don't know what you're doing; they have names beginning with
  150. "CFG_".
  151. Later we will add a configuration tool - probably similar to or even
  152. identical to what's used for the Linux kernel. Right now, we have to
  153. do the configuration by hand, which means creating some symbolic
  154. links and editing some configuration files. We use the TQM8xxL boards
  155. as an example here.
  156. Selection of Processor Architecture and Board Type:
  157. ---------------------------------------------------
  158. For all supported boards there are ready-to-use default
  159. configurations available; just type "make <board_name>_config".
  160. Example: For a TQM823L module type:
  161. cd u-boot
  162. make TQM823L_config
  163. For the Cogent platform, you need to specify the cpu type as well;
  164. e.g. "make cogent_mpc8xx_config". And also configure the cogent
  165. directory according to the instructions in cogent/README.
  166. Configuration Options:
  167. ----------------------
  168. Configuration depends on the combination of board and CPU type; all
  169. such information is kept in a configuration file
  170. "include/configs/<board_name>.h".
  171. Example: For a TQM823L module, all configuration settings are in
  172. "include/configs/TQM823L.h".
  173. Many of the options are named exactly as the corresponding Linux
  174. kernel configuration options. The intention is to make it easier to
  175. build a config tool - later.
  176. The following options need to be configured:
  177. - CPU Type: Define exactly one of
  178. PowerPC based CPUs:
  179. -------------------
  180. CONFIG_MPC823, CONFIG_MPC850, CONFIG_MPC855, CONFIG_MPC860
  181. or CONFIG_MPC5xx
  182. or CONFIG_MPC8220
  183. or CONFIG_MPC824X, CONFIG_MPC8260
  184. or CONFIG_MPC85xx
  185. or CONFIG_IOP480
  186. or CONFIG_405GP
  187. or CONFIG_405EP
  188. or CONFIG_440
  189. or CONFIG_MPC74xx
  190. or CONFIG_750FX
  191. ARM based CPUs:
  192. ---------------
  193. CONFIG_SA1110
  194. CONFIG_ARM7
  195. CONFIG_PXA250
  196. MicroBlaze based CPUs:
  197. ----------------------
  198. CONFIG_MICROBLAZE
  199. Nios-2 based CPUs:
  200. ----------------------
  201. CONFIG_NIOS2
  202. - Board Type: Define exactly one of
  203. PowerPC based boards:
  204. ---------------------
  205. CONFIG_ADCIOP CONFIG_GEN860T CONFIG_PCI405
  206. CONFIG_ADS860 CONFIG_GENIETV CONFIG_PCIPPC2
  207. CONFIG_AMX860 CONFIG_GTH CONFIG_PCIPPC6
  208. CONFIG_AR405 CONFIG_gw8260 CONFIG_pcu_e
  209. CONFIG_BAB7xx CONFIG_hermes CONFIG_PIP405
  210. CONFIG_c2mon CONFIG_hymod CONFIG_PM826
  211. CONFIG_CANBT CONFIG_IAD210 CONFIG_ppmc8260
  212. CONFIG_CCM CONFIG_ICU862 CONFIG_QS823
  213. CONFIG_CMI CONFIG_IP860 CONFIG_QS850
  214. CONFIG_cogent_mpc8260 CONFIG_IPHASE4539 CONFIG_QS860T
  215. CONFIG_cogent_mpc8xx CONFIG_IVML24 CONFIG_RBC823
  216. CONFIG_CPCI405 CONFIG_IVML24_128 CONFIG_RPXClassic
  217. CONFIG_CPCI4052 CONFIG_IVML24_256 CONFIG_RPXlite
  218. CONFIG_CPCIISER4 CONFIG_IVMS8 CONFIG_RPXsuper
  219. CONFIG_CPU86 CONFIG_IVMS8_128 CONFIG_rsdproto
  220. CONFIG_CRAYL1 CONFIG_IVMS8_256 CONFIG_sacsng
  221. CONFIG_CSB272 CONFIG_JSE CONFIG_Sandpoint8240
  222. CONFIG_CU824 CONFIG_LANTEC CONFIG_Sandpoint8245
  223. CONFIG_DASA_SIM CONFIG_lwmon CONFIG_sbc8260
  224. CONFIG_DB64360 CONFIG_MBX CONFIG_sbc8560
  225. CONFIG_DB64460 CONFIG_MBX860T CONFIG_SM850
  226. CONFIG_DU405 CONFIG_MHPC CONFIG_SPD823TS
  227. CONFIG_DUET_ADS CONFIG_MIP405 CONFIG_STXGP3
  228. CONFIG_EBONY CONFIG_MOUSSE CONFIG_SXNI855T
  229. CONFIG_ELPPC CONFIG_MPC8260ADS CONFIG_TQM823L
  230. CONFIG_ELPT860 CONFIG_MPC8540ADS CONFIG_TQM8260
  231. CONFIG_ep8260 CONFIG_MPC8560ADS CONFIG_TQM850L
  232. CONFIG_ERIC CONFIG_MUSENKI CONFIG_TQM855L
  233. CONFIG_ESTEEM192E CONFIG_MVS1 CONFIG_TQM860L
  234. CONFIG_ETX094 CONFIG_NETPHONE CONFIG_TTTech
  235. CONFIG_EVB64260 CONFIG_NETTA CONFIG_UTX8245
  236. CONFIG_FADS823 CONFIG_NETVIA CONFIG_V37
  237. CONFIG_FADS850SAR CONFIG_NX823 CONFIG_W7OLMC
  238. CONFIG_FADS860T CONFIG_OCRTC CONFIG_W7OLMG
  239. CONFIG_FLAGADM CONFIG_ORSG CONFIG_WALNUT
  240. CONFIG_FPS850L CONFIG_OXC CONFIG_ZPC1900
  241. CONFIG_FPS860L CONFIG_ZUMA
  242. ARM based boards:
  243. -----------------
  244. CONFIG_AT91RM9200DK, CONFIG_CERF250, CONFIG_DNP1110,
  245. CONFIG_EP7312, CONFIG_H2_OMAP1610, CONFIG_HHP_CRADLE,
  246. CONFIG_IMPA7, CONFIG_INNOVATOROMAP1510, CONFIG_INNOVATOROMAP1610,
  247. CONFIG_LART, CONFIG_LPD7A400 CONFIG_LUBBOCK,
  248. CONFIG_OSK_OMAP5912, CONFIG_OMAP2420H4, CONFIG_SHANNON,
  249. CONFIG_P2_OMAP730, CONFIG_SMDK2400, CONFIG_SMDK2410,
  250. CONFIG_TRAB, CONFIG_VCMA9
  251. MicroBlaze based boards:
  252. ------------------------
  253. CONFIG_SUZAKU
  254. Nios-2 based boards:
  255. ------------------------
  256. CONFIG_PCI5441 CONFIG_PK1C20
  257. - CPU Module Type: (if CONFIG_COGENT is defined)
  258. Define exactly one of
  259. CONFIG_CMA286_60_OLD
  260. --- FIXME --- not tested yet:
  261. CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
  262. CONFIG_CMA287_23, CONFIG_CMA287_50
  263. - Motherboard Type: (if CONFIG_COGENT is defined)
  264. Define exactly one of
  265. CONFIG_CMA101, CONFIG_CMA102
  266. - Motherboard I/O Modules: (if CONFIG_COGENT is defined)
  267. Define one or more of
  268. CONFIG_CMA302
  269. - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
  270. Define one or more of
  271. CONFIG_LCD_HEARTBEAT - update a character position on
  272. the lcd display every second with
  273. a "rotator" |\-/|\-/
  274. - Board flavour: (if CONFIG_MPC8260ADS is defined)
  275. CONFIG_ADSTYPE
  276. Possible values are:
  277. CFG_8260ADS - original MPC8260ADS
  278. CFG_8266ADS - MPC8266ADS
  279. CFG_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
  280. CFG_8272ADS - MPC8272ADS
  281. - MPC824X Family Member (if CONFIG_MPC824X is defined)
  282. Define exactly one of
  283. CONFIG_MPC8240, CONFIG_MPC8245
  284. - 8xx CPU Options: (if using an MPC8xx cpu)
  285. CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if
  286. get_gclk_freq() cannot work
  287. e.g. if there is no 32KHz
  288. reference PIT/RTC clock
  289. CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK
  290. or XTAL/EXTAL)
  291. - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
  292. CFG_8xx_CPUCLK_MIN
  293. CFG_8xx_CPUCLK_MAX
  294. CONFIG_8xx_CPUCLK_DEFAULT
  295. See doc/README.MPC866
  296. CFG_MEASURE_CPUCLK
  297. Define this to measure the actual CPU clock instead
  298. of relying on the correctness of the configured
  299. values. Mostly useful for board bringup to make sure
  300. the PLL is locked at the intended frequency. Note
  301. that this requires a (stable) reference clock (32 kHz
  302. RTC clock or CFG_8XX_XIN)
  303. - Linux Kernel Interface:
  304. CONFIG_CLOCKS_IN_MHZ
  305. U-Boot stores all clock information in Hz
  306. internally. For binary compatibility with older Linux
  307. kernels (which expect the clocks passed in the
  308. bd_info data to be in MHz) the environment variable
  309. "clocks_in_mhz" can be defined so that U-Boot
  310. converts clock data to MHZ before passing it to the
  311. Linux kernel.
  312. When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
  313. "clocks_in_mhz=1" is automatically included in the
  314. default environment.
  315. CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
  316. When transfering memsize parameter to linux, some versions
  317. expect it to be in bytes, others in MB.
  318. Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
  319. - Serial Ports:
  320. CFG_PL010_SERIAL
  321. Define this if you want support for Amba PrimeCell PL010 UARTs.
  322. CFG_PL011_SERIAL
  323. Define this if you want support for Amba PrimeCell PL011 UARTs.
  324. CONFIG_PL011_CLOCK
  325. If you have Amba PrimeCell PL011 UARTs, set this variable to
  326. the clock speed of the UARTs.
  327. CONFIG_PL01x_PORTS
  328. If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
  329. define this to a list of base addresses for each (supported)
  330. port. See e.g. include/configs/versatile.h
  331. - Console Interface:
  332. Depending on board, define exactly one serial port
  333. (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
  334. CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
  335. console by defining CONFIG_8xx_CONS_NONE
  336. Note: if CONFIG_8xx_CONS_NONE is defined, the serial
  337. port routines must be defined elsewhere
  338. (i.e. serial_init(), serial_getc(), ...)
  339. CONFIG_CFB_CONSOLE
  340. Enables console device for a color framebuffer. Needs following
  341. defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)
  342. VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
  343. (default big endian)
  344. VIDEO_HW_RECTFILL graphic chip supports
  345. rectangle fill
  346. (cf. smiLynxEM)
  347. VIDEO_HW_BITBLT graphic chip supports
  348. bit-blit (cf. smiLynxEM)
  349. VIDEO_VISIBLE_COLS visible pixel columns
  350. (cols=pitch)
  351. VIDEO_VISIBLE_ROWS visible pixel rows
  352. VIDEO_PIXEL_SIZE bytes per pixel
  353. VIDEO_DATA_FORMAT graphic data format
  354. (0-5, cf. cfb_console.c)
  355. VIDEO_FB_ADRS framebuffer address
  356. VIDEO_KBD_INIT_FCT keyboard int fct
  357. (i.e. i8042_kbd_init())
  358. VIDEO_TSTC_FCT test char fct
  359. (i.e. i8042_tstc)
  360. VIDEO_GETC_FCT get char fct
  361. (i.e. i8042_getc)
  362. CONFIG_CONSOLE_CURSOR cursor drawing on/off
  363. (requires blink timer
  364. cf. i8042.c)
  365. CFG_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
  366. CONFIG_CONSOLE_TIME display time/date info in
  367. upper right corner
  368. (requires CFG_CMD_DATE)
  369. CONFIG_VIDEO_LOGO display Linux logo in
  370. upper left corner
  371. CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
  372. linux_logo.h for logo.
  373. Requires CONFIG_VIDEO_LOGO
  374. CONFIG_CONSOLE_EXTRA_INFO
  375. addional board info beside
  376. the logo
  377. When CONFIG_CFB_CONSOLE is defined, video console is
  378. default i/o. Serial console can be forced with
  379. environment 'console=serial'.
  380. When CONFIG_SILENT_CONSOLE is defined, all console
  381. messages (by U-Boot and Linux!) can be silenced with
  382. the "silent" environment variable. See
  383. doc/README.silent for more information.
  384. - Console Baudrate:
  385. CONFIG_BAUDRATE - in bps
  386. Select one of the baudrates listed in
  387. CFG_BAUDRATE_TABLE, see below.
  388. CFG_BRGCLK_PRESCALE, baudrate prescale
  389. - Interrupt driven serial port input:
  390. CONFIG_SERIAL_SOFTWARE_FIFO
  391. PPC405GP only.
  392. Use an interrupt handler for receiving data on the
  393. serial port. It also enables using hardware handshake
  394. (RTS/CTS) and UART's built-in FIFO. Set the number of
  395. bytes the interrupt driven input buffer should have.
  396. Leave undefined to disable this feature, including
  397. disable the buffer and hardware handshake.
  398. - Console UART Number:
  399. CONFIG_UART1_CONSOLE
  400. IBM PPC4xx only.
  401. If defined internal UART1 (and not UART0) is used
  402. as default U-Boot console.
  403. - Boot Delay: CONFIG_BOOTDELAY - in seconds
  404. Delay before automatically booting the default image;
  405. set to -1 to disable autoboot.
  406. See doc/README.autoboot for these options that
  407. work with CONFIG_BOOTDELAY. None are required.
  408. CONFIG_BOOT_RETRY_TIME
  409. CONFIG_BOOT_RETRY_MIN
  410. CONFIG_AUTOBOOT_KEYED
  411. CONFIG_AUTOBOOT_PROMPT
  412. CONFIG_AUTOBOOT_DELAY_STR
  413. CONFIG_AUTOBOOT_STOP_STR
  414. CONFIG_AUTOBOOT_DELAY_STR2
  415. CONFIG_AUTOBOOT_STOP_STR2
  416. CONFIG_ZERO_BOOTDELAY_CHECK
  417. CONFIG_RESET_TO_RETRY
  418. - Autoboot Command:
  419. CONFIG_BOOTCOMMAND
  420. Only needed when CONFIG_BOOTDELAY is enabled;
  421. define a command string that is automatically executed
  422. when no character is read on the console interface
  423. within "Boot Delay" after reset.
  424. CONFIG_BOOTARGS
  425. This can be used to pass arguments to the bootm
  426. command. The value of CONFIG_BOOTARGS goes into the
  427. environment value "bootargs".
  428. CONFIG_RAMBOOT and CONFIG_NFSBOOT
  429. The value of these goes into the environment as
  430. "ramboot" and "nfsboot" respectively, and can be used
  431. as a convenience, when switching between booting from
  432. ram and nfs.
  433. - Pre-Boot Commands:
  434. CONFIG_PREBOOT
  435. When this option is #defined, the existence of the
  436. environment variable "preboot" will be checked
  437. immediately before starting the CONFIG_BOOTDELAY
  438. countdown and/or running the auto-boot command resp.
  439. entering interactive mode.
  440. This feature is especially useful when "preboot" is
  441. automatically generated or modified. For an example
  442. see the LWMON board specific code: here "preboot" is
  443. modified when the user holds down a certain
  444. combination of keys on the (special) keyboard when
  445. booting the systems
  446. - Serial Download Echo Mode:
  447. CONFIG_LOADS_ECHO
  448. If defined to 1, all characters received during a
  449. serial download (using the "loads" command) are
  450. echoed back. This might be needed by some terminal
  451. emulations (like "cu"), but may as well just take
  452. time on others. This setting #define's the initial
  453. value of the "loads_echo" environment variable.
  454. - Kgdb Serial Baudrate: (if CFG_CMD_KGDB is defined)
  455. CONFIG_KGDB_BAUDRATE
  456. Select one of the baudrates listed in
  457. CFG_BAUDRATE_TABLE, see below.
  458. - Monitor Functions:
  459. CONFIG_COMMANDS
  460. Most monitor functions can be selected (or
  461. de-selected) by adjusting the definition of
  462. CONFIG_COMMANDS; to select individual functions,
  463. #define CONFIG_COMMANDS by "OR"ing any of the
  464. following values:
  465. #define enables commands:
  466. -------------------------
  467. CFG_CMD_ASKENV * ask for env variable
  468. CFG_CMD_AUTOSCRIPT Autoscript Support
  469. CFG_CMD_BDI bdinfo
  470. CFG_CMD_BEDBUG * Include BedBug Debugger
  471. CFG_CMD_BMP * BMP support
  472. CFG_CMD_BSP * Board specific commands
  473. CFG_CMD_BOOTD bootd
  474. CFG_CMD_CACHE * icache, dcache
  475. CFG_CMD_CONSOLE coninfo
  476. CFG_CMD_DATE * support for RTC, date/time...
  477. CFG_CMD_DHCP * DHCP support
  478. CFG_CMD_DIAG * Diagnostics
  479. CFG_CMD_DOC * Disk-On-Chip Support
  480. CFG_CMD_DTT * Digital Therm and Thermostat
  481. CFG_CMD_ECHO * echo arguments
  482. CFG_CMD_EEPROM * EEPROM read/write support
  483. CFG_CMD_ELF * bootelf, bootvx
  484. CFG_CMD_ENV saveenv
  485. CFG_CMD_FDC * Floppy Disk Support
  486. CFG_CMD_FAT * FAT partition support
  487. CFG_CMD_FDOS * Dos diskette Support
  488. CFG_CMD_FLASH flinfo, erase, protect
  489. CFG_CMD_FPGA FPGA device initialization support
  490. CFG_CMD_HWFLOW * RTS/CTS hw flow control
  491. CFG_CMD_I2C * I2C serial bus support
  492. CFG_CMD_IDE * IDE harddisk support
  493. CFG_CMD_IMI iminfo
  494. CFG_CMD_IMLS List all found images
  495. CFG_CMD_IMMAP * IMMR dump support
  496. CFG_CMD_IRQ * irqinfo
  497. CFG_CMD_ITEST Integer/string test of 2 values
  498. CFG_CMD_JFFS2 * JFFS2 Support
  499. CFG_CMD_KGDB * kgdb
  500. CFG_CMD_LOADB loadb
  501. CFG_CMD_LOADS loads
  502. CFG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
  503. loop, loopw, mtest
  504. CFG_CMD_MISC Misc functions like sleep etc
  505. CFG_CMD_MMC * MMC memory mapped support
  506. CFG_CMD_MII * MII utility commands
  507. CFG_CMD_NAND * NAND support
  508. CFG_CMD_NET bootp, tftpboot, rarpboot
  509. CFG_CMD_PCI * pciinfo
  510. CFG_CMD_PCMCIA * PCMCIA support
  511. CFG_CMD_PING * send ICMP ECHO_REQUEST to network host
  512. CFG_CMD_PORTIO * Port I/O
  513. CFG_CMD_REGINFO * Register dump
  514. CFG_CMD_RUN run command in env variable
  515. CFG_CMD_SAVES * save S record dump
  516. CFG_CMD_SCSI * SCSI Support
  517. CFG_CMD_SDRAM * print SDRAM configuration information
  518. (requires CFG_CMD_I2C)
  519. CFG_CMD_SETGETDCR Support for DCR Register access (4xx only)
  520. CFG_CMD_SPI * SPI serial bus support
  521. CFG_CMD_USB * USB support
  522. CFG_CMD_VFD * VFD support (TRAB)
  523. CFG_CMD_BSP * Board SPecific functions
  524. CFG_CMD_CDP * Cisco Discover Protocol support
  525. -----------------------------------------------
  526. CFG_CMD_ALL all
  527. CONFIG_CMD_DFL Default configuration; at the moment
  528. this is includes all commands, except
  529. the ones marked with "*" in the list
  530. above.
  531. If you don't define CONFIG_COMMANDS it defaults to
  532. CONFIG_CMD_DFL in include/cmd_confdefs.h. A board can
  533. override the default settings in the respective
  534. include file.
  535. EXAMPLE: If you want all functions except of network
  536. support you can write:
  537. #define CONFIG_COMMANDS (CFG_CMD_ALL & ~CFG_CMD_NET)
  538. Note: Don't enable the "icache" and "dcache" commands
  539. (configuration option CFG_CMD_CACHE) unless you know
  540. what you (and your U-Boot users) are doing. Data
  541. cache cannot be enabled on systems like the 8xx or
  542. 8260 (where accesses to the IMMR region must be
  543. uncached), and it cannot be disabled on all other
  544. systems where we (mis-) use the data cache to hold an
  545. initial stack and some data.
  546. XXX - this list needs to get updated!
  547. - Watchdog:
  548. CONFIG_WATCHDOG
  549. If this variable is defined, it enables watchdog
  550. support. There must be support in the platform specific
  551. code for a watchdog. For the 8xx and 8260 CPUs, the
  552. SIU Watchdog feature is enabled in the SYPCR
  553. register.
  554. - U-Boot Version:
  555. CONFIG_VERSION_VARIABLE
  556. If this variable is defined, an environment variable
  557. named "ver" is created by U-Boot showing the U-Boot
  558. version as printed by the "version" command.
  559. This variable is readonly.
  560. - Real-Time Clock:
  561. When CFG_CMD_DATE is selected, the type of the RTC
  562. has to be selected, too. Define exactly one of the
  563. following options:
  564. CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
  565. CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
  566. CONFIG_RTC_MC146818 - use MC146818 RTC
  567. CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
  568. CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
  569. CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
  570. CONFIG_RTC_DS164x - use Dallas DS164x RTC
  571. CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
  572. Note that if the RTC uses I2C, then the I2C interface
  573. must also be configured. See I2C Support, below.
  574. - Timestamp Support:
  575. When CONFIG_TIMESTAMP is selected, the timestamp
  576. (date and time) of an image is printed by image
  577. commands like bootm or iminfo. This option is
  578. automatically enabled when you select CFG_CMD_DATE .
  579. - Partition Support:
  580. CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
  581. and/or CONFIG_ISO_PARTITION
  582. If IDE or SCSI support is enabled (CFG_CMD_IDE or
  583. CFG_CMD_SCSI) you must configure support for at least
  584. one partition type as well.
  585. - IDE Reset method:
  586. CONFIG_IDE_RESET_ROUTINE - this is defined in several
  587. board configurations files but used nowhere!
  588. CONFIG_IDE_RESET - is this is defined, IDE Reset will
  589. be performed by calling the function
  590. ide_set_reset(int reset)
  591. which has to be defined in a board specific file
  592. - ATAPI Support:
  593. CONFIG_ATAPI
  594. Set this to enable ATAPI support.
  595. - LBA48 Support
  596. CONFIG_LBA48
  597. Set this to enable support for disks larger than 137GB
  598. Also look at CFG_64BIT_LBA ,CFG_64BIT_VSPRINTF and CFG_64BIT_STRTOUL
  599. Whithout these , LBA48 support uses 32bit variables and will 'only'
  600. support disks up to 2.1TB.
  601. CFG_64BIT_LBA:
  602. When enabled, makes the IDE subsystem use 64bit sector addresses.
  603. Default is 32bit.
  604. - SCSI Support:
  605. At the moment only there is only support for the
  606. SYM53C8XX SCSI controller; define
  607. CONFIG_SCSI_SYM53C8XX to enable it.
  608. CFG_SCSI_MAX_LUN [8], CFG_SCSI_MAX_SCSI_ID [7] and
  609. CFG_SCSI_MAX_DEVICE [CFG_SCSI_MAX_SCSI_ID *
  610. CFG_SCSI_MAX_LUN] can be adjusted to define the
  611. maximum numbers of LUNs, SCSI ID's and target
  612. devices.
  613. CFG_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
  614. - NETWORK Support (PCI):
  615. CONFIG_E1000
  616. Support for Intel 8254x gigabit chips.
  617. CONFIG_EEPRO100
  618. Support for Intel 82557/82559/82559ER chips.
  619. Optional CONFIG_EEPRO100_SROM_WRITE enables eeprom
  620. write routine for first time initialisation.
  621. CONFIG_TULIP
  622. Support for Digital 2114x chips.
  623. Optional CONFIG_TULIP_SELECT_MEDIA for board specific
  624. modem chip initialisation (KS8761/QS6611).
  625. CONFIG_NATSEMI
  626. Support for National dp83815 chips.
  627. CONFIG_NS8382X
  628. Support for National dp8382[01] gigabit chips.
  629. - NETWORK Support (other):
  630. CONFIG_DRIVER_LAN91C96
  631. Support for SMSC's LAN91C96 chips.
  632. CONFIG_LAN91C96_BASE
  633. Define this to hold the physical address
  634. of the LAN91C96's I/O space
  635. CONFIG_LAN91C96_USE_32_BIT
  636. Define this to enable 32 bit addressing
  637. CONFIG_DRIVER_SMC91111
  638. Support for SMSC's LAN91C111 chip
  639. CONFIG_SMC91111_BASE
  640. Define this to hold the physical address
  641. of the device (I/O space)
  642. CONFIG_SMC_USE_32_BIT
  643. Define this if data bus is 32 bits
  644. CONFIG_SMC_USE_IOFUNCS
  645. Define this to use i/o functions instead of macros
  646. (some hardware wont work with macros)
  647. - USB Support:
  648. At the moment only the UHCI host controller is
  649. supported (PIP405, MIP405, MPC5200); define
  650. CONFIG_USB_UHCI to enable it.
  651. define CONFIG_USB_KEYBOARD to enable the USB Keyboard
  652. and define CONFIG_USB_STORAGE to enable the USB
  653. storage devices.
  654. Note:
  655. Supported are USB Keyboards and USB Floppy drives
  656. (TEAC FD-05PUB).
  657. MPC5200 USB requires additional defines:
  658. CONFIG_USB_CLOCK
  659. for 528 MHz Clock: 0x0001bbbb
  660. CONFIG_USB_CONFIG
  661. for differential drivers: 0x00001000
  662. for single ended drivers: 0x00005000
  663. - MMC Support:
  664. The MMC controller on the Intel PXA is supported. To
  665. enable this define CONFIG_MMC. The MMC can be
  666. accessed from the boot prompt by mapping the device
  667. to physical memory similar to flash. Command line is
  668. enabled with CFG_CMD_MMC. The MMC driver also works with
  669. the FAT fs. This is enabled with CFG_CMD_FAT.
  670. - Journaling Flash filesystem support:
  671. CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
  672. CONFIG_JFFS2_NAND_DEV
  673. Define these for a default partition on a NAND device
  674. CFG_JFFS2_FIRST_SECTOR,
  675. CFG_JFFS2_FIRST_BANK, CFG_JFFS2_NUM_BANKS
  676. Define these for a default partition on a NOR device
  677. CFG_JFFS_CUSTOM_PART
  678. Define this to create an own partition. You have to provide a
  679. function struct part_info* jffs2_part_info(int part_num)
  680. If you define only one JFFS2 partition you may also want to
  681. #define CFG_JFFS_SINGLE_PART 1
  682. to disable the command chpart. This is the default when you
  683. have not defined a custom partition
  684. - Keyboard Support:
  685. CONFIG_ISA_KEYBOARD
  686. Define this to enable standard (PC-Style) keyboard
  687. support
  688. CONFIG_I8042_KBD
  689. Standard PC keyboard driver with US (is default) and
  690. GERMAN key layout (switch via environment 'keymap=de') support.
  691. Export function i8042_kbd_init, i8042_tstc and i8042_getc
  692. for cfb_console. Supports cursor blinking.
  693. - Video support:
  694. CONFIG_VIDEO
  695. Define this to enable video support (for output to
  696. video).
  697. CONFIG_VIDEO_CT69000
  698. Enable Chips & Technologies 69000 Video chip
  699. CONFIG_VIDEO_SMI_LYNXEM
  700. Enable Silicon Motion SMI 712/710/810 Video chip. The
  701. video output is selected via environment 'videoout'
  702. (1 = LCD and 2 = CRT). If videoout is undefined, CRT is
  703. assumed.
  704. For the CT69000 and SMI_LYNXEM drivers, videomode is
  705. selected via environment 'videomode'. Two diferent ways
  706. are possible:
  707. - "videomode=num" 'num' is a standard LiLo mode numbers.
  708. Following standard modes are supported (* is default):
  709. Colors 640x480 800x600 1024x768 1152x864 1280x1024
  710. -------------+---------------------------------------------
  711. 8 bits | 0x301* 0x303 0x305 0x161 0x307
  712. 15 bits | 0x310 0x313 0x316 0x162 0x319
  713. 16 bits | 0x311 0x314 0x317 0x163 0x31A
  714. 24 bits | 0x312 0x315 0x318 ? 0x31B
  715. -------------+---------------------------------------------
  716. (i.e. setenv videomode 317; saveenv; reset;)
  717. - "videomode=bootargs" all the video parameters are parsed
  718. from the bootargs. (See drivers/videomodes.c)
  719. CONFIG_VIDEO_SED13806
  720. Enable Epson SED13806 driver. This driver supports 8bpp
  721. and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
  722. or CONFIG_VIDEO_SED13806_16BPP
  723. - Keyboard Support:
  724. CONFIG_KEYBOARD
  725. Define this to enable a custom keyboard support.
  726. This simply calls drv_keyboard_init() which must be
  727. defined in your board-specific files.
  728. The only board using this so far is RBC823.
  729. - LCD Support: CONFIG_LCD
  730. Define this to enable LCD support (for output to LCD
  731. display); also select one of the supported displays
  732. by defining one of these:
  733. CONFIG_NEC_NL6448AC33:
  734. NEC NL6448AC33-18. Active, color, single scan.
  735. CONFIG_NEC_NL6448BC20
  736. NEC NL6448BC20-08. 6.5", 640x480.
  737. Active, color, single scan.
  738. CONFIG_NEC_NL6448BC33_54
  739. NEC NL6448BC33-54. 10.4", 640x480.
  740. Active, color, single scan.
  741. CONFIG_SHARP_16x9
  742. Sharp 320x240. Active, color, single scan.
  743. It isn't 16x9, and I am not sure what it is.
  744. CONFIG_SHARP_LQ64D341
  745. Sharp LQ64D341 display, 640x480.
  746. Active, color, single scan.
  747. CONFIG_HLD1045
  748. HLD1045 display, 640x480.
  749. Active, color, single scan.
  750. CONFIG_OPTREX_BW
  751. Optrex CBL50840-2 NF-FW 99 22 M5
  752. or
  753. Hitachi LMG6912RPFC-00T
  754. or
  755. Hitachi SP14Q002
  756. 320x240. Black & white.
  757. Normally display is black on white background; define
  758. CFG_WHITE_ON_BLACK to get it inverted.
  759. - Splash Screen Support: CONFIG_SPLASH_SCREEN
  760. If this option is set, the environment is checked for
  761. a variable "splashimage". If found, the usual display
  762. of logo, copyright and system information on the LCD
  763. is suppressed and the BMP image at the address
  764. specified in "splashimage" is loaded instead. The
  765. console is redirected to the "nulldev", too. This
  766. allows for a "silent" boot where a splash screen is
  767. loaded very quickly after power-on.
  768. - Compression support:
  769. CONFIG_BZIP2
  770. If this option is set, support for bzip2 compressed
  771. images is included. If not, only uncompressed and gzip
  772. compressed images are supported.
  773. NOTE: the bzip2 algorithm requires a lot of RAM, so
  774. the malloc area (as defined by CFG_MALLOC_LEN) should
  775. be at least 4MB.
  776. - MII/PHY support:
  777. CONFIG_PHY_ADDR
  778. The address of PHY on MII bus.
  779. CONFIG_PHY_CLOCK_FREQ (ppc4xx)
  780. The clock frequency of the MII bus
  781. CONFIG_PHY_GIGE
  782. If this option is set, support for speed/duplex
  783. detection of Gigabit PHY is included.
  784. CONFIG_PHY_RESET_DELAY
  785. Some PHY like Intel LXT971A need extra delay after
  786. reset before any MII register access is possible.
  787. For such PHY, set this option to the usec delay
  788. required. (minimum 300usec for LXT971A)
  789. CONFIG_PHY_CMD_DELAY (ppc4xx)
  790. Some PHY like Intel LXT971A need extra delay after
  791. command issued before MII status register can be read
  792. - Ethernet address:
  793. CONFIG_ETHADDR
  794. CONFIG_ETH2ADDR
  795. CONFIG_ETH3ADDR
  796. Define a default value for ethernet address to use
  797. for the respective ethernet interface, in case this
  798. is not determined automatically.
  799. - IP address:
  800. CONFIG_IPADDR
  801. Define a default value for the IP address to use for
  802. the default ethernet interface, in case this is not
  803. determined through e.g. bootp.
  804. - Server IP address:
  805. CONFIG_SERVERIP
  806. Defines a default value for theIP address of a TFTP
  807. server to contact when using the "tftboot" command.
  808. - BOOTP Recovery Mode:
  809. CONFIG_BOOTP_RANDOM_DELAY
  810. If you have many targets in a network that try to
  811. boot using BOOTP, you may want to avoid that all
  812. systems send out BOOTP requests at precisely the same
  813. moment (which would happen for instance at recovery
  814. from a power failure, when all systems will try to
  815. boot, thus flooding the BOOTP server. Defining
  816. CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
  817. inserted before sending out BOOTP requests. The
  818. following delays are insterted then:
  819. 1st BOOTP request: delay 0 ... 1 sec
  820. 2nd BOOTP request: delay 0 ... 2 sec
  821. 3rd BOOTP request: delay 0 ... 4 sec
  822. 4th and following
  823. BOOTP requests: delay 0 ... 8 sec
  824. - DHCP Advanced Options:
  825. CONFIG_BOOTP_MASK
  826. You can fine tune the DHCP functionality by adding
  827. these flags to the CONFIG_BOOTP_MASK define:
  828. CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
  829. serverip from a DHCP server, it is possible that more
  830. than one DNS serverip is offered to the client.
  831. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
  832. serverip will be stored in the additional environment
  833. variable "dnsip2". The first DNS serverip is always
  834. stored in the variable "dnsip", when CONFIG_BOOTP_DNS
  835. is added to the CONFIG_BOOTP_MASK.
  836. CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
  837. to do a dynamic update of a DNS server. To do this, they
  838. need the hostname of the DHCP requester.
  839. If CONFIG_BOOP_SEND_HOSTNAME is added to the
  840. CONFIG_BOOTP_MASK, the content of the "hostname"
  841. environment variable is passed as option 12 to
  842. the DHCP server.
  843. - CDP Options:
  844. CONFIG_CDP_DEVICE_ID
  845. The device id used in CDP trigger frames.
  846. CONFIG_CDP_DEVICE_ID_PREFIX
  847. A two character string which is prefixed to the MAC address
  848. of the device.
  849. CONFIG_CDP_PORT_ID
  850. A printf format string which contains the ascii name of
  851. the port. Normally is set to "eth%d" which sets
  852. eth0 for the first ethernet, eth1 for the second etc.
  853. CONFIG_CDP_CAPABILITIES
  854. A 32bit integer which indicates the device capabilities;
  855. 0x00000010 for a normal host which does not forwards.
  856. CONFIG_CDP_VERSION
  857. An ascii string containing the version of the software.
  858. CONFIG_CDP_PLATFORM
  859. An ascii string containing the name of the platform.
  860. CONFIG_CDP_TRIGGER
  861. A 32bit integer sent on the trigger.
  862. CONFIG_CDP_POWER_CONSUMPTION
  863. A 16bit integer containing the power consumption of the
  864. device in .1 of milliwatts.
  865. CONFIG_CDP_APPLIANCE_VLAN_TYPE
  866. A byte containing the id of the VLAN.
  867. - Status LED: CONFIG_STATUS_LED
  868. Several configurations allow to display the current
  869. status using a LED. For instance, the LED will blink
  870. fast while running U-Boot code, stop blinking as
  871. soon as a reply to a BOOTP request was received, and
  872. start blinking slow once the Linux kernel is running
  873. (supported by a status LED driver in the Linux
  874. kernel). Defining CONFIG_STATUS_LED enables this
  875. feature in U-Boot.
  876. - CAN Support: CONFIG_CAN_DRIVER
  877. Defining CONFIG_CAN_DRIVER enables CAN driver support
  878. on those systems that support this (optional)
  879. feature, like the TQM8xxL modules.
  880. - I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C
  881. These enable I2C serial bus commands. Defining either of
  882. (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will
  883. include the appropriate I2C driver for the selected cpu.
  884. This will allow you to use i2c commands at the u-boot
  885. command line (as long as you set CFG_CMD_I2C in
  886. CONFIG_COMMANDS) and communicate with i2c based realtime
  887. clock chips. See common/cmd_i2c.c for a description of the
  888. command line interface.
  889. CONFIG_HARD_I2C selects the CPM hardware driver for I2C.
  890. CONFIG_SOFT_I2C configures u-boot to use a software (aka
  891. bit-banging) driver instead of CPM or similar hardware
  892. support for I2C.
  893. There are several other quantities that must also be
  894. defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.
  895. In both cases you will need to define CFG_I2C_SPEED
  896. to be the frequency (in Hz) at which you wish your i2c bus
  897. to run and CFG_I2C_SLAVE to be the address of this node (ie
  898. the cpu's i2c node address).
  899. Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)
  900. sets the cpu up as a master node and so its address should
  901. therefore be cleared to 0 (See, eg, MPC823e User's Manual
  902. p.16-473). So, set CFG_I2C_SLAVE to 0.
  903. That's all that's required for CONFIG_HARD_I2C.
  904. If you use the software i2c interface (CONFIG_SOFT_I2C)
  905. then the following macros need to be defined (examples are
  906. from include/configs/lwmon.h):
  907. I2C_INIT
  908. (Optional). Any commands necessary to enable the I2C
  909. controller or configure ports.
  910. eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
  911. I2C_PORT
  912. (Only for MPC8260 CPU). The I/O port to use (the code
  913. assumes both bits are on the same port). Valid values
  914. are 0..3 for ports A..D.
  915. I2C_ACTIVE
  916. The code necessary to make the I2C data line active
  917. (driven). If the data line is open collector, this
  918. define can be null.
  919. eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
  920. I2C_TRISTATE
  921. The code necessary to make the I2C data line tri-stated
  922. (inactive). If the data line is open collector, this
  923. define can be null.
  924. eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
  925. I2C_READ
  926. Code that returns TRUE if the I2C data line is high,
  927. FALSE if it is low.
  928. eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
  929. I2C_SDA(bit)
  930. If <bit> is TRUE, sets the I2C data line high. If it
  931. is FALSE, it clears it (low).
  932. eg: #define I2C_SDA(bit) \
  933. if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
  934. else immr->im_cpm.cp_pbdat &= ~PB_SDA
  935. I2C_SCL(bit)
  936. If <bit> is TRUE, sets the I2C clock line high. If it
  937. is FALSE, it clears it (low).
  938. eg: #define I2C_SCL(bit) \
  939. if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
  940. else immr->im_cpm.cp_pbdat &= ~PB_SCL
  941. I2C_DELAY
  942. This delay is invoked four times per clock cycle so this
  943. controls the rate of data transfer. The data rate thus
  944. is 1 / (I2C_DELAY * 4). Often defined to be something
  945. like:
  946. #define I2C_DELAY udelay(2)
  947. CFG_I2C_INIT_BOARD
  948. When a board is reset during an i2c bus transfer
  949. chips might think that the current transfer is still
  950. in progress. On some boards it is possible to access
  951. the i2c SCLK line directly, either by using the
  952. processor pin as a GPIO or by having a second pin
  953. connected to the bus. If this option is defined a
  954. custom i2c_init_board() routine in boards/xxx/board.c
  955. is run early in the boot sequence.
  956. CONFIG_I2CFAST (PPC405GP|PPC405EP only)
  957. This option enables configuration of bi_iic_fast[] flags
  958. in u-boot bd_info structure based on u-boot environment
  959. variable "i2cfast". (see also i2cfast)
  960. - SPI Support: CONFIG_SPI
  961. Enables SPI driver (so far only tested with
  962. SPI EEPROM, also an instance works with Crystal A/D and
  963. D/As on the SACSng board)
  964. CONFIG_SPI_X
  965. Enables extended (16-bit) SPI EEPROM addressing.
  966. (symmetrical to CONFIG_I2C_X)
  967. CONFIG_SOFT_SPI
  968. Enables a software (bit-bang) SPI driver rather than
  969. using hardware support. This is a general purpose
  970. driver that only requires three general I/O port pins
  971. (two outputs, one input) to function. If this is
  972. defined, the board configuration must define several
  973. SPI configuration items (port pins to use, etc). For
  974. an example, see include/configs/sacsng.h.
  975. - FPGA Support: CONFIG_FPGA_COUNT
  976. Specify the number of FPGA devices to support.
  977. CONFIG_FPGA
  978. Used to specify the types of FPGA devices. For example,
  979. #define CONFIG_FPGA CFG_XILINX_VIRTEX2
  980. CFG_FPGA_PROG_FEEDBACK
  981. Enable printing of hash marks during FPGA configuration.
  982. CFG_FPGA_CHECK_BUSY
  983. Enable checks on FPGA configuration interface busy
  984. status by the configuration function. This option
  985. will require a board or device specific function to
  986. be written.
  987. CONFIG_FPGA_DELAY
  988. If defined, a function that provides delays in the FPGA
  989. configuration driver.
  990. CFG_FPGA_CHECK_CTRLC
  991. Allow Control-C to interrupt FPGA configuration
  992. CFG_FPGA_CHECK_ERROR
  993. Check for configuration errors during FPGA bitfile
  994. loading. For example, abort during Virtex II
  995. configuration if the INIT_B line goes low (which
  996. indicated a CRC error).
  997. CFG_FPGA_WAIT_INIT
  998. Maximum time to wait for the INIT_B line to deassert
  999. after PROB_B has been deasserted during a Virtex II
  1000. FPGA configuration sequence. The default time is 500
  1001. mS.
  1002. CFG_FPGA_WAIT_BUSY
  1003. Maximum time to wait for BUSY to deassert during
  1004. Virtex II FPGA configuration. The default is 5 mS.
  1005. CFG_FPGA_WAIT_CONFIG
  1006. Time to wait after FPGA configuration. The default is
  1007. 200 mS.
  1008. - Configuration Management:
  1009. CONFIG_IDENT_STRING
  1010. If defined, this string will be added to the U-Boot
  1011. version information (U_BOOT_VERSION)
  1012. - Vendor Parameter Protection:
  1013. U-Boot considers the values of the environment
  1014. variables "serial#" (Board Serial Number) and
  1015. "ethaddr" (Ethernet Address) to be parameters that
  1016. are set once by the board vendor / manufacturer, and
  1017. protects these variables from casual modification by
  1018. the user. Once set, these variables are read-only,
  1019. and write or delete attempts are rejected. You can
  1020. change this behviour:
  1021. If CONFIG_ENV_OVERWRITE is #defined in your config
  1022. file, the write protection for vendor parameters is
  1023. completely disabled. Anybody can change or delete
  1024. these parameters.
  1025. Alternatively, if you #define _both_ CONFIG_ETHADDR
  1026. _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
  1027. ethernet address is installed in the environment,
  1028. which can be changed exactly ONCE by the user. [The
  1029. serial# is unaffected by this, i. e. it remains
  1030. read-only.]
  1031. - Protected RAM:
  1032. CONFIG_PRAM
  1033. Define this variable to enable the reservation of
  1034. "protected RAM", i. e. RAM which is not overwritten
  1035. by U-Boot. Define CONFIG_PRAM to hold the number of
  1036. kB you want to reserve for pRAM. You can overwrite
  1037. this default value by defining an environment
  1038. variable "pram" to the number of kB you want to
  1039. reserve. Note that the board info structure will
  1040. still show the full amount of RAM. If pRAM is
  1041. reserved, a new environment variable "mem" will
  1042. automatically be defined to hold the amount of
  1043. remaining RAM in a form that can be passed as boot
  1044. argument to Linux, for instance like that:
  1045. setenv bootargs ... mem=\$(mem)
  1046. saveenv
  1047. This way you can tell Linux not to use this memory,
  1048. either, which results in a memory region that will
  1049. not be affected by reboots.
  1050. *WARNING* If your board configuration uses automatic
  1051. detection of the RAM size, you must make sure that
  1052. this memory test is non-destructive. So far, the
  1053. following board configurations are known to be
  1054. "pRAM-clean":
  1055. ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
  1056. HERMES, IP860, RPXlite, LWMON, LANTEC,
  1057. PCU_E, FLAGADM, TQM8260
  1058. - Error Recovery:
  1059. CONFIG_PANIC_HANG
  1060. Define this variable to stop the system in case of a
  1061. fatal error, so that you have to reset it manually.
  1062. This is probably NOT a good idea for an embedded
  1063. system where you want to system to reboot
  1064. automatically as fast as possible, but it may be
  1065. useful during development since you can try to debug
  1066. the conditions that lead to the situation.
  1067. CONFIG_NET_RETRY_COUNT
  1068. This variable defines the number of retries for
  1069. network operations like ARP, RARP, TFTP, or BOOTP
  1070. before giving up the operation. If not defined, a
  1071. default value of 5 is used.
  1072. - Command Interpreter:
  1073. CFG_AUTO_COMPLETE
  1074. Enable auto completion of commands using TAB.
  1075. CFG_HUSH_PARSER
  1076. Define this variable to enable the "hush" shell (from
  1077. Busybox) as command line interpreter, thus enabling
  1078. powerful command line syntax like
  1079. if...then...else...fi conditionals or `&&' and '||'
  1080. constructs ("shell scripts").
  1081. If undefined, you get the old, much simpler behaviour
  1082. with a somewhat smaller memory footprint.
  1083. CFG_PROMPT_HUSH_PS2
  1084. This defines the secondary prompt string, which is
  1085. printed when the command interpreter needs more input
  1086. to complete a command. Usually "> ".
  1087. Note:
  1088. In the current implementation, the local variables
  1089. space and global environment variables space are
  1090. separated. Local variables are those you define by
  1091. simply typing `name=value'. To access a local
  1092. variable later on, you have write `$name' or
  1093. `${name}'; to execute the contents of a variable
  1094. directly type `$name' at the command prompt.
  1095. Global environment variables are those you use
  1096. setenv/printenv to work with. To run a command stored
  1097. in such a variable, you need to use the run command,
  1098. and you must not use the '$' sign to access them.
  1099. To store commands and special characters in a
  1100. variable, please use double quotation marks
  1101. surrounding the whole text of the variable, instead
  1102. of the backslashes before semicolons and special
  1103. symbols.
  1104. - Default Environment:
  1105. CONFIG_EXTRA_ENV_SETTINGS
  1106. Define this to contain any number of null terminated
  1107. strings (variable = value pairs) that will be part of
  1108. the default environment compiled into the boot image.
  1109. For example, place something like this in your
  1110. board's config file:
  1111. #define CONFIG_EXTRA_ENV_SETTINGS \
  1112. "myvar1=value1\0" \
  1113. "myvar2=value2\0"
  1114. Warning: This method is based on knowledge about the
  1115. internal format how the environment is stored by the
  1116. U-Boot code. This is NOT an official, exported
  1117. interface! Although it is unlikely that this format
  1118. will change soon, there is no guarantee either.
  1119. You better know what you are doing here.
  1120. Note: overly (ab)use of the default environment is
  1121. discouraged. Make sure to check other ways to preset
  1122. the environment like the autoscript function or the
  1123. boot command first.
  1124. - DataFlash Support:
  1125. CONFIG_HAS_DATAFLASH
  1126. Defining this option enables DataFlash features and
  1127. allows to read/write in Dataflash via the standard
  1128. commands cp, md...
  1129. - SystemACE Support:
  1130. CONFIG_SYSTEMACE
  1131. Adding this option adds support for Xilinx SystemACE
  1132. chips attached via some sort of local bus. The address
  1133. of the chip must alsh be defined in the
  1134. CFG_SYSTEMACE_BASE macro. For example:
  1135. #define CONFIG_SYSTEMACE
  1136. #define CFG_SYSTEMACE_BASE 0xf0000000
  1137. When SystemACE support is added, the "ace" device type
  1138. becomes available to the fat commands, i.e. fatls.
  1139. - Show boot progress:
  1140. CONFIG_SHOW_BOOT_PROGRESS
  1141. Defining this option allows to add some board-
  1142. specific code (calling a user-provided function
  1143. "show_boot_progress(int)") that enables you to show
  1144. the system's boot progress on some display (for
  1145. example, some LED's) on your board. At the moment,
  1146. the following checkpoints are implemented:
  1147. Arg Where When
  1148. 1 common/cmd_bootm.c before attempting to boot an image
  1149. -1 common/cmd_bootm.c Image header has bad magic number
  1150. 2 common/cmd_bootm.c Image header has correct magic number
  1151. -2 common/cmd_bootm.c Image header has bad checksum
  1152. 3 common/cmd_bootm.c Image header has correct checksum
  1153. -3 common/cmd_bootm.c Image data has bad checksum
  1154. 4 common/cmd_bootm.c Image data has correct checksum
  1155. -4 common/cmd_bootm.c Image is for unsupported architecture
  1156. 5 common/cmd_bootm.c Architecture check OK
  1157. -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
  1158. 6 common/cmd_bootm.c Image Type check OK
  1159. -6 common/cmd_bootm.c gunzip uncompression error
  1160. -7 common/cmd_bootm.c Unimplemented compression type
  1161. 7 common/cmd_bootm.c Uncompression OK
  1162. -8 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
  1163. 8 common/cmd_bootm.c Image Type check OK
  1164. -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
  1165. 9 common/cmd_bootm.c Start initial ramdisk verification
  1166. -10 common/cmd_bootm.c Ramdisk header has bad magic number
  1167. -11 common/cmd_bootm.c Ramdisk header has bad checksum
  1168. 10 common/cmd_bootm.c Ramdisk header is OK
  1169. -12 common/cmd_bootm.c Ramdisk data has bad checksum
  1170. 11 common/cmd_bootm.c Ramdisk data has correct checksum
  1171. 12 common/cmd_bootm.c Ramdisk verification complete, start loading
  1172. -13 common/cmd_bootm.c Wrong Image Type (not PPC Linux Ramdisk)
  1173. 13 common/cmd_bootm.c Start multifile image verification
  1174. 14 common/cmd_bootm.c No initial ramdisk, no multifile, continue.
  1175. 15 common/cmd_bootm.c All preparation done, transferring control to OS
  1176. -30 lib_ppc/board.c Fatal error, hang the system
  1177. -31 post/post.c POST test failed, detected by post_output_backlog()
  1178. -32 post/post.c POST test failed, detected by post_run_single()
  1179. -1 common/cmd_doc.c Bad usage of "doc" command
  1180. -1 common/cmd_doc.c No boot device
  1181. -1 common/cmd_doc.c Unknown Chip ID on boot device
  1182. -1 common/cmd_doc.c Read Error on boot device
  1183. -1 common/cmd_doc.c Image header has bad magic number
  1184. -1 common/cmd_ide.c Bad usage of "ide" command
  1185. -1 common/cmd_ide.c No boot device
  1186. -1 common/cmd_ide.c Unknown boot device
  1187. -1 common/cmd_ide.c Unknown partition table
  1188. -1 common/cmd_ide.c Invalid partition type
  1189. -1 common/cmd_ide.c Read Error on boot device
  1190. -1 common/cmd_ide.c Image header has bad magic number
  1191. -1 common/cmd_nand.c Bad usage of "nand" command
  1192. -1 common/cmd_nand.c No boot device
  1193. -1 common/cmd_nand.c Unknown Chip ID on boot device
  1194. -1 common/cmd_nand.c Read Error on boot device
  1195. -1 common/cmd_nand.c Image header has bad magic number
  1196. -1 common/env_common.c Environment has a bad CRC, using default
  1197. Modem Support:
  1198. --------------
  1199. [so far only for SMDK2400 and TRAB boards]
  1200. - Modem support endable:
  1201. CONFIG_MODEM_SUPPORT
  1202. - RTS/CTS Flow control enable:
  1203. CONFIG_HWFLOW
  1204. - Modem debug support:
  1205. CONFIG_MODEM_SUPPORT_DEBUG
  1206. Enables debugging stuff (char screen[1024], dbg())
  1207. for modem support. Useful only with BDI2000.
  1208. - Interrupt support (PPC):
  1209. There are common interrupt_init() and timer_interrupt()
  1210. for all PPC archs. interrupt_init() calls interrupt_init_cpu()
  1211. for cpu specific initialization. interrupt_init_cpu()
  1212. should set decrementer_count to appropriate value. If
  1213. cpu resets decrementer automatically after interrupt
  1214. (ppc4xx) it should set decrementer_count to zero.
  1215. timer_interrupt() calls timer_interrupt_cpu() for cpu
  1216. specific handling. If board has watchdog / status_led
  1217. / other_activity_monitor it works automatically from
  1218. general timer_interrupt().
  1219. - General:
  1220. In the target system modem support is enabled when a
  1221. specific key (key combination) is pressed during
  1222. power-on. Otherwise U-Boot will boot normally
  1223. (autoboot). The key_pressed() fuction is called from
  1224. board_init(). Currently key_pressed() is a dummy
  1225. function, returning 1 and thus enabling modem
  1226. initialization.
  1227. If there are no modem init strings in the
  1228. environment, U-Boot proceed to autoboot; the
  1229. previous output (banner, info printfs) will be
  1230. supressed, though.
  1231. See also: doc/README.Modem
  1232. Configuration Settings:
  1233. -----------------------
  1234. - CFG_LONGHELP: Defined when you want long help messages included;
  1235. undefine this when you're short of memory.
  1236. - CFG_PROMPT: This is what U-Boot prints on the console to
  1237. prompt for user input.
  1238. - CFG_CBSIZE: Buffer size for input from the Console
  1239. - CFG_PBSIZE: Buffer size for Console output
  1240. - CFG_MAXARGS: max. Number of arguments accepted for monitor commands
  1241. - CFG_BARGSIZE: Buffer size for Boot Arguments which are passed to
  1242. the application (usually a Linux kernel) when it is
  1243. booted
  1244. - CFG_BAUDRATE_TABLE:
  1245. List of legal baudrate settings for this board.
  1246. - CFG_CONSOLE_INFO_QUIET
  1247. Suppress display of console information at boot.
  1248. - CFG_CONSOLE_IS_IN_ENV
  1249. If the board specific function
  1250. extern int overwrite_console (void);
  1251. returns 1, the stdin, stderr and stdout are switched to the
  1252. serial port, else the settings in the environment are used.
  1253. - CFG_CONSOLE_OVERWRITE_ROUTINE
  1254. Enable the call to overwrite_console().
  1255. - CFG_CONSOLE_ENV_OVERWRITE
  1256. Enable overwrite of previous console environment settings.
  1257. - CFG_MEMTEST_START, CFG_MEMTEST_END:
  1258. Begin and End addresses of the area used by the
  1259. simple memory test.
  1260. - CFG_ALT_MEMTEST:
  1261. Enable an alternate, more extensive memory test.
  1262. - CFG_MEMTEST_SCRATCH:
  1263. Scratch address used by the alternate memory test
  1264. You only need to set this if address zero isn't writeable
  1265. - CFG_TFTP_LOADADDR:
  1266. Default load address for network file downloads
  1267. - CFG_LOADS_BAUD_CHANGE:
  1268. Enable temporary baudrate change while serial download
  1269. - CFG_SDRAM_BASE:
  1270. Physical start address of SDRAM. _Must_ be 0 here.
  1271. - CFG_MBIO_BASE:
  1272. Physical start address of Motherboard I/O (if using a
  1273. Cogent motherboard)
  1274. - CFG_FLASH_BASE:
  1275. Physical start address of Flash memory.
  1276. - CFG_MONITOR_BASE:
  1277. Physical start address of boot monitor code (set by
  1278. make config files to be same as the text base address
  1279. (TEXT_BASE) used when linking) - same as
  1280. CFG_FLASH_BASE when booting from flash.
  1281. - CFG_MONITOR_LEN:
  1282. Size of memory reserved for monitor code, used to
  1283. determine _at_compile_time_ (!) if the environment is
  1284. embedded within the U-Boot image, or in a separate
  1285. flash sector.
  1286. - CFG_MALLOC_LEN:
  1287. Size of DRAM reserved for malloc() use.
  1288. - CFG_BOOTMAPSZ:
  1289. Maximum size of memory mapped by the startup code of
  1290. the Linux kernel; all data that must be processed by
  1291. the Linux kernel (bd_info, boot arguments, eventually
  1292. initrd image) must be put below this limit.
  1293. - CFG_MAX_FLASH_BANKS:
  1294. Max number of Flash memory banks
  1295. - CFG_MAX_FLASH_SECT:
  1296. Max number of sectors on a Flash chip
  1297. - CFG_FLASH_ERASE_TOUT:
  1298. Timeout for Flash erase operations (in ms)
  1299. - CFG_FLASH_WRITE_TOUT:
  1300. Timeout for Flash write operations (in ms)
  1301. - CFG_FLASH_LOCK_TOUT
  1302. Timeout for Flash set sector lock bit operation (in ms)
  1303. - CFG_FLASH_UNLOCK_TOUT
  1304. Timeout for Flash clear lock bits operation (in ms)
  1305. - CFG_FLASH_PROTECTION
  1306. If defined, hardware flash sectors protection is used
  1307. instead of U-Boot software protection.
  1308. - CFG_DIRECT_FLASH_TFTP:
  1309. Enable TFTP transfers directly to flash memory;
  1310. without this option such a download has to be
  1311. performed in two steps: (1) download to RAM, and (2)
  1312. copy from RAM to flash.
  1313. The two-step approach is usually more reliable, since
  1314. you can check if the download worked before you erase
  1315. the flash, but in some situations (when sytem RAM is
  1316. too limited to allow for a tempory copy of the
  1317. downloaded image) this option may be very useful.
  1318. - CFG_FLASH_CFI:
  1319. Define if the flash driver uses extra elements in the
  1320. common flash structure for storing flash geometry.
  1321. - CFG_FLASH_CFI_DRIVER
  1322. This option also enables the building of the cfi_flash driver
  1323. in the drivers directory
  1324. - CFG_RX_ETH_BUFFER:
  1325. Defines the number of ethernet receive buffers. On some
  1326. ethernet controllers it is recommended to set this value
  1327. to 8 or even higher (EEPRO100 or 405 EMAC), since all
  1328. buffers can be full shortly after enabling the interface
  1329. on high ethernet traffic.
  1330. Defaults to 4 if not defined.
  1331. The following definitions that deal with the placement and management
  1332. of environment data (variable area); in general, we support the
  1333. following configurations:
  1334. - CFG_ENV_IS_IN_FLASH:
  1335. Define this if the environment is in flash memory.
  1336. a) The environment occupies one whole flash sector, which is
  1337. "embedded" in the text segment with the U-Boot code. This
  1338. happens usually with "bottom boot sector" or "top boot
  1339. sector" type flash chips, which have several smaller
  1340. sectors at the start or the end. For instance, such a
  1341. layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
  1342. such a case you would place the environment in one of the
  1343. 4 kB sectors - with U-Boot code before and after it. With
  1344. "top boot sector" type flash chips, you would put the
  1345. environment in one of the last sectors, leaving a gap
  1346. between U-Boot and the environment.
  1347. - CFG_ENV_OFFSET:
  1348. Offset of environment data (variable area) to the
  1349. beginning of flash memory; for instance, with bottom boot
  1350. type flash chips the second sector can be used: the offset
  1351. for this sector is given here.
  1352. CFG_ENV_OFFSET is used relative to CFG_FLASH_BASE.
  1353. - CFG_ENV_ADDR:
  1354. This is just another way to specify the start address of
  1355. the flash sector containing the environment (instead of
  1356. CFG_ENV_OFFSET).
  1357. - CFG_ENV_SECT_SIZE:
  1358. Size of the sector containing the environment.
  1359. b) Sometimes flash chips have few, equal sized, BIG sectors.
  1360. In such a case you don't want to spend a whole sector for
  1361. the environment.
  1362. - CFG_ENV_SIZE:
  1363. If you use this in combination with CFG_ENV_IS_IN_FLASH
  1364. and CFG_ENV_SECT_SIZE, you can specify to use only a part
  1365. of this flash sector for the environment. This saves
  1366. memory for the RAM copy of the environment.
  1367. It may also save flash memory if you decide to use this
  1368. when your environment is "embedded" within U-Boot code,
  1369. since then the remainder of the flash sector could be used
  1370. for U-Boot code. It should be pointed out that this is
  1371. STRONGLY DISCOURAGED from a robustness point of view:
  1372. updating the environment in flash makes it always
  1373. necessary to erase the WHOLE sector. If something goes
  1374. wrong before the contents has been restored from a copy in
  1375. RAM, your target system will be dead.
  1376. - CFG_ENV_ADDR_REDUND
  1377. CFG_ENV_SIZE_REDUND
  1378. These settings describe a second storage area used to hold
  1379. a redundand copy of the environment data, so that there is
  1380. a valid backup copy in case there is a power failure during
  1381. a "saveenv" operation.
  1382. BE CAREFUL! Any changes to the flash layout, and some changes to the
  1383. source code will make it necessary to adapt <board>/u-boot.lds*
  1384. accordingly!
  1385. - CFG_ENV_IS_IN_NVRAM:
  1386. Define this if you have some non-volatile memory device
  1387. (NVRAM, battery buffered SRAM) which you want to use for the
  1388. environment.
  1389. - CFG_ENV_ADDR:
  1390. - CFG_ENV_SIZE:
  1391. These two #defines are used to determin the memory area you
  1392. want to use for environment. It is assumed that this memory
  1393. can just be read and written to, without any special
  1394. provision.
  1395. BE CAREFUL! The first access to the environment happens quite early
  1396. in U-Boot initalization (when we try to get the setting of for the
  1397. console baudrate). You *MUST* have mappend your NVRAM area then, or
  1398. U-Boot will hang.
  1399. Please note that even with NVRAM we still use a copy of the
  1400. environment in RAM: we could work on NVRAM directly, but we want to
  1401. keep settings there always unmodified except somebody uses "saveenv"
  1402. to save the current settings.
  1403. - CFG_ENV_IS_IN_EEPROM:
  1404. Use this if you have an EEPROM or similar serial access
  1405. device and a driver for it.
  1406. - CFG_ENV_OFFSET:
  1407. - CFG_ENV_SIZE:
  1408. These two #defines specify the offset and size of the
  1409. environment area within the total memory of your EEPROM.
  1410. - CFG_I2C_EEPROM_ADDR:
  1411. If defined, specified the chip address of the EEPROM device.
  1412. The default address is zero.
  1413. - CFG_EEPROM_PAGE_WRITE_BITS:
  1414. If defined, the number of bits used to address bytes in a
  1415. single page in the EEPROM device. A 64 byte page, for example
  1416. would require six bits.
  1417. - CFG_EEPROM_PAGE_WRITE_DELAY_MS:
  1418. If defined, the number of milliseconds to delay between
  1419. page writes. The default is zero milliseconds.
  1420. - CFG_I2C_EEPROM_ADDR_LEN:
  1421. The length in bytes of the EEPROM memory array address. Note
  1422. that this is NOT the chip address length!
  1423. - CFG_I2C_EEPROM_ADDR_OVERFLOW:
  1424. EEPROM chips that implement "address overflow" are ones
  1425. like Catalyst 24WC04/08/16 which has 9/10/11 bits of
  1426. address and the extra bits end up in the "chip address" bit
  1427. slots. This makes a 24WC08 (1Kbyte) chip look like four 256
  1428. byte chips.
  1429. Note that we consider the length of the address field to
  1430. still be one byte because the extra address bits are hidden
  1431. in the chip address.
  1432. - CFG_EEPROM_SIZE:
  1433. The size in bytes of the EEPROM device.
  1434. - CFG_ENV_IS_IN_DATAFLASH:
  1435. Define this if you have a DataFlash memory device which you
  1436. want to use for the environment.
  1437. - CFG_ENV_OFFSET:
  1438. - CFG_ENV_ADDR:
  1439. - CFG_ENV_SIZE:
  1440. These three #defines specify the offset and size of the
  1441. environment area within the total memory of your DataFlash placed
  1442. at the specified address.
  1443. - CFG_ENV_IS_IN_NAND:
  1444. Define this if you have a NAND device which you want to use
  1445. for the environment.
  1446. - CFG_ENV_OFFSET:
  1447. - CFG_ENV_SIZE:
  1448. These two #defines specify the offset and size of the environment
  1449. area within the first NAND device.
  1450. - CFG_SPI_INIT_OFFSET
  1451. Defines offset to the initial SPI buffer area in DPRAM. The
  1452. area is used at an early stage (ROM part) if the environment
  1453. is configured to reside in the SPI EEPROM: We need a 520 byte
  1454. scratch DPRAM area. It is used between the two initialization
  1455. calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems
  1456. to be a good choice since it makes it far enough from the
  1457. start of the data area as well as from the stack pointer.
  1458. Please note that the environment is read-only as long as the monitor
  1459. has been relocated to RAM and a RAM copy of the environment has been
  1460. created; also, when using EEPROM you will have to use getenv_r()
  1461. until then to read environment variables.
  1462. The environment is protected by a CRC32 checksum. Before the monitor
  1463. is relocated into RAM, as a result of a bad CRC you will be working
  1464. with the compiled-in default environment - *silently*!!! [This is
  1465. necessary, because the first environment variable we need is the
  1466. "baudrate" setting for the console - if we have a bad CRC, we don't
  1467. have any device yet where we could complain.]
  1468. Note: once the monitor has been relocated, then it will complain if
  1469. the default environment is used; a new CRC is computed as soon as you
  1470. use the "saveenv" command to store a valid environment.
  1471. - CFG_FAULT_ECHO_LINK_DOWN:
  1472. Echo the inverted Ethernet link state to the fault LED.
  1473. Note: If this option is active, then CFG_FAULT_MII_ADDR
  1474. also needs to be defined.
  1475. - CFG_FAULT_MII_ADDR:
  1476. MII address of the PHY to check for the Ethernet link state.
  1477. - CFG_64BIT_VSPRINTF:
  1478. Makes vsprintf (and all *printf functions) support printing
  1479. of 64bit values by using the L quantifier
  1480. - CFG_64BIT_STRTOUL:
  1481. Adds simple_strtoull that returns a 64bit value
  1482. Low Level (hardware related) configuration options:
  1483. ---------------------------------------------------
  1484. - CFG_CACHELINE_SIZE:
  1485. Cache Line Size of the CPU.
  1486. - CFG_DEFAULT_IMMR:
  1487. Default address of the IMMR after system reset.
  1488. Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,
  1489. and RPXsuper) to be able to adjust the position of
  1490. the IMMR register after a reset.
  1491. - Floppy Disk Support:
  1492. CFG_FDC_DRIVE_NUMBER
  1493. the default drive number (default value 0)
  1494. CFG_ISA_IO_STRIDE
  1495. defines the spacing between fdc chipset registers
  1496. (default value 1)
  1497. CFG_ISA_IO_OFFSET
  1498. defines the offset of register from address. It
  1499. depends on which part of the data bus is connected to
  1500. the fdc chipset. (default value 0)
  1501. If CFG_ISA_IO_STRIDE CFG_ISA_IO_OFFSET and
  1502. CFG_FDC_DRIVE_NUMBER are undefined, they take their
  1503. default value.
  1504. if CFG_FDC_HW_INIT is defined, then the function
  1505. fdc_hw_init() is called at the beginning of the FDC
  1506. setup. fdc_hw_init() must be provided by the board
  1507. source code. It is used to make hardware dependant
  1508. initializations.
  1509. - CFG_IMMR: Physical address of the Internal Memory.
  1510. DO NOT CHANGE unless you know exactly what you're
  1511. doing! (11-4) [MPC8xx/82xx systems only]
  1512. - CFG_INIT_RAM_ADDR:
  1513. Start address of memory area that can be used for
  1514. initial data and stack; please note that this must be
  1515. writable memory that is working WITHOUT special
  1516. initialization, i. e. you CANNOT use normal RAM which
  1517. will become available only after programming the
  1518. memory controller and running certain initialization
  1519. sequences.
  1520. U-Boot uses the following memory types:
  1521. - MPC8xx and MPC8260: IMMR (internal memory of the CPU)
  1522. - MPC824X: data cache
  1523. - PPC4xx: data cache
  1524. - CFG_GBL_DATA_OFFSET:
  1525. Offset of the initial data structure in the memory
  1526. area defined by CFG_INIT_RAM_ADDR. Usually
  1527. CFG_GBL_DATA_OFFSET is chosen such that the initial
  1528. data is located at the end of the available space
  1529. (sometimes written as (CFG_INIT_RAM_END -
  1530. CFG_INIT_DATA_SIZE), and the initial stack is just
  1531. below that area (growing from (CFG_INIT_RAM_ADDR +
  1532. CFG_GBL_DATA_OFFSET) downward.
  1533. Note:
  1534. On the MPC824X (or other systems that use the data
  1535. cache for initial memory) the address chosen for
  1536. CFG_INIT_RAM_ADDR is basically arbitrary - it must
  1537. point to an otherwise UNUSED address space between
  1538. the top of RAM and the start of the PCI space.
  1539. - CFG_SIUMCR: SIU Module Configuration (11-6)
  1540. - CFG_SYPCR: System Protection Control (11-9)
  1541. - CFG_TBSCR: Time Base Status and Control (11-26)
  1542. - CFG_PISCR: Periodic Interrupt Status and Control (11-31)
  1543. - CFG_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30)
  1544. - CFG_SCCR: System Clock and reset Control Register (15-27)
  1545. - CFG_OR_TIMING_SDRAM:
  1546. SDRAM timing
  1547. - CFG_MAMR_PTA:
  1548. periodic timer for refresh
  1549. - CFG_DER: Debug Event Register (37-47)
  1550. - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CFG_REMAP_OR_AM,
  1551. CFG_PRELIM_OR_AM, CFG_OR_TIMING_FLASH, CFG_OR0_REMAP,
  1552. CFG_OR0_PRELIM, CFG_BR0_PRELIM, CFG_OR1_REMAP, CFG_OR1_PRELIM,
  1553. CFG_BR1_PRELIM:
  1554. Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
  1555. - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
  1556. CFG_OR_TIMING_SDRAM, CFG_OR2_PRELIM, CFG_BR2_PRELIM,
  1557. CFG_OR3_PRELIM, CFG_BR3_PRELIM:
  1558. Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
  1559. - CFG_MAMR_PTA, CFG_MPTPR_2BK_4K, CFG_MPTPR_1BK_4K, CFG_MPTPR_2BK_8K,
  1560. CFG_MPTPR_1BK_8K, CFG_MAMR_8COL, CFG_MAMR_9COL:
  1561. Machine Mode Register and Memory Periodic Timer
  1562. Prescaler definitions (SDRAM timing)
  1563. - CFG_I2C_UCODE_PATCH, CFG_I2C_DPMEM_OFFSET [0x1FC0]:
  1564. enable I2C microcode relocation patch (MPC8xx);
  1565. define relocation offset in DPRAM [DSP2]
  1566. - CFG_SPI_UCODE_PATCH, CFG_SPI_DPMEM_OFFSET [0x1FC0]:
  1567. enable SPI microcode relocation patch (MPC8xx);
  1568. define relocation offset in DPRAM [SCC4]
  1569. - CFG_USE_OSCCLK:
  1570. Use OSCM clock mode on MBX8xx board. Be careful,
  1571. wrong setting might damage your board. Read
  1572. doc/README.MBX before setting this variable!
  1573. - CFG_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)
  1574. Offset of the bootmode word in DPRAM used by post
  1575. (Power On Self Tests). This definition overrides
  1576. #define'd default value in commproc.h resp.
  1577. cpm_8260.h.
  1578. - CFG_PCI_SLV_MEM_LOCAL, CFG_PCI_SLV_MEM_BUS, CFG_PICMR0_MASK_ATTRIB,
  1579. CFG_PCI_MSTR0_LOCAL, CFG_PCIMSK0_MASK, CFG_PCI_MSTR1_LOCAL,
  1580. CFG_PCIMSK1_MASK, CFG_PCI_MSTR_MEM_LOCAL, CFG_PCI_MSTR_MEM_BUS,
  1581. CFG_CPU_PCI_MEM_START, CFG_PCI_MSTR_MEM_SIZE, CFG_POCMR0_MASK_ATTRIB,
  1582. CFG_PCI_MSTR_MEMIO_LOCAL, CFG_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,
  1583. CFG_PCI_MSTR_MEMIO_SIZE, CFG_POCMR1_MASK_ATTRIB, CFG_PCI_MSTR_IO_LOCAL,
  1584. CFG_PCI_MSTR_IO_BUS, CFG_CPU_PCI_IO_START, CFG_PCI_MSTR_IO_SIZE,
  1585. CFG_POCMR2_MASK_ATTRIB: (MPC826x only)
  1586. Overrides the default PCI memory map in cpu/mpc8260/pci.c if set.
  1587. - CONFIG_ETHER_ON_FEC[12]
  1588. Define to enable FEC[12] on a 8xx series processor.
  1589. - CONFIG_FEC[12]_PHY
  1590. Define to the hardcoded PHY address which corresponds
  1591. to the given FEC; i. e.
  1592. #define CONFIG_FEC1_PHY 4
  1593. means that the PHY with address 4 is connected to FEC1
  1594. When set to -1, means to probe for first available.
  1595. - CONFIG_FEC[12]_PHY_NORXERR
  1596. The PHY does not have a RXERR line (RMII only).
  1597. (so program the FEC to ignore it).
  1598. - CONFIG_RMII
  1599. Enable RMII mode for all FECs.
  1600. Note that this is a global option, we can't
  1601. have one FEC in standard MII mode and another in RMII mode.
  1602. - CONFIG_CRC32_VERIFY
  1603. Add a verify option to the crc32 command.
  1604. The syntax is:
  1605. => crc32 -v <address> <count> <crc32>
  1606. Where address/count indicate a memory area
  1607. and crc32 is the correct crc32 which the
  1608. area should have.
  1609. - CONFIG_LOOPW
  1610. Add the "loopw" memory command. This only takes effect if
  1611. the memory commands are activated globally (CFG_CMD_MEM).
  1612. - CONFIG_MX_CYCLIC
  1613. Add the "mdc" and "mwc" memory commands. These are cyclic
  1614. "md/mw" commands.
  1615. Examples:
  1616. => mdc.b 10 4 500
  1617. This command will print 4 bytes (10,11,12,13) each 500 ms.
  1618. => mwc.l 100 12345678 10
  1619. This command will write 12345678 to address 100 all 10 ms.
  1620. This only takes effect if the memory commands are activated
  1621. globally (CFG_CMD_MEM).
  1622. - CONFIG_SKIP_LOWLEVEL_INIT
  1623. - CONFIG_SKIP_RELOCATE_UBOOT
  1624. [ARM only] If these variables are defined, then
  1625. certain low level initializations (like setting up
  1626. the memory controller) are omitted and/or U-Boot does
  1627. not relocate itself into RAM.
  1628. Normally these variables MUST NOT be defined. The
  1629. only exception is when U-Boot is loaded (to RAM) by
  1630. some other boot loader or by a debugger which
  1631. performs these intializations itself.
  1632. Building the Software:
  1633. ======================
  1634. Building U-Boot has been tested in native PPC environments (on a
  1635. PowerBook G3 running LinuxPPC 2000) and in cross environments
  1636. (running RedHat 6.x and 7.x Linux on x86, Solaris 2.6 on a SPARC, and
  1637. NetBSD 1.5 on x86).
  1638. If you are not using a native PPC environment, it is assumed that you
  1639. have the GNU cross compiling tools available in your path and named
  1640. with a prefix of "powerpc-linux-". If this is not the case, (e.g. if
  1641. you are using Monta Vista's Hard Hat Linux CDK 1.2) you must change
  1642. the definition of CROSS_COMPILE in Makefile. For HHL on a 4xx CPU,
  1643. change it to:
  1644. CROSS_COMPILE = ppc_4xx-
  1645. U-Boot is intended to be simple to build. After installing the
  1646. sources you must configure U-Boot for one specific board type. This
  1647. is done by typing:
  1648. make NAME_config
  1649. where "NAME_config" is the name of one of the existing
  1650. configurations; the following names are supported:
  1651. ADCIOP_config FPS860L_config omap730p2_config
  1652. ADS860_config GEN860T_config pcu_e_config
  1653. Alaska8220_config
  1654. AR405_config GENIETV_config PIP405_config
  1655. at91rm9200dk_config GTH_config QS823_config
  1656. CANBT_config hermes_config QS850_config
  1657. cmi_mpc5xx_config hymod_config QS860T_config
  1658. cogent_common_config IP860_config RPXlite_config
  1659. cogent_mpc8260_config IVML24_config RPXlite_DW_config
  1660. cogent_mpc8xx_config IVMS8_config RPXsuper_config
  1661. CPCI405_config JSE_config rsdproto_config
  1662. CPCIISER4_config LANTEC_config Sandpoint8240_config
  1663. csb272_config lwmon_config sbc8260_config
  1664. CU824_config MBX860T_config sbc8560_33_config
  1665. DUET_ADS_config MBX_config sbc8560_66_config
  1666. EBONY_config MPC8260ADS_config SM850_config
  1667. ELPT860_config MPC8540ADS_config SPD823TS_config
  1668. ESTEEM192E_config MPC8560ADS_config stxgp3_config
  1669. ETX094_config NETVIA_config SXNI855T_config
  1670. FADS823_config omap1510inn_config TQM823L_config
  1671. FADS850SAR_config omap1610h2_config TQM850L_config
  1672. FADS860T_config omap1610inn_config TQM855L_config
  1673. FPS850L_config omap5912osk_config TQM860L_config
  1674. omap2420h4_config walnut_config
  1675. Yukon8220_config
  1676. ZPC1900_config
  1677. Note: for some board special configuration names may exist; check if
  1678. additional information is available from the board vendor; for
  1679. instance, the TQM823L systems are available without (standard)
  1680. or with LCD support. You can select such additional "features"
  1681. when chosing the configuration, i. e.
  1682. make TQM823L_config
  1683. - will configure for a plain TQM823L, i. e. no LCD support
  1684. make TQM823L_LCD_config
  1685. - will configure for a TQM823L with U-Boot console on LCD
  1686. etc.
  1687. Finally, type "make all", and you should get some working U-Boot
  1688. images ready for download to / installation on your system:
  1689. - "u-boot.bin" is a raw binary image
  1690. - "u-boot" is an image in ELF binary format
  1691. - "u-boot.srec" is in Motorola S-Record format
  1692. Please be aware that the Makefiles assume you are using GNU make, so
  1693. for instance on NetBSD you might need to use "gmake" instead of
  1694. native "make".
  1695. If the system board that you have is not listed, then you will need
  1696. to port U-Boot to your hardware platform. To do this, follow these
  1697. steps:
  1698. 1. Add a new configuration option for your board to the toplevel
  1699. "Makefile" and to the "MAKEALL" script, using the existing
  1700. entries as examples. Note that here and at many other places
  1701. boards and other names are listed in alphabetical sort order. Please
  1702. keep this order.
  1703. 2. Create a new directory to hold your board specific code. Add any
  1704. files you need. In your board directory, you will need at least
  1705. the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
  1706. 3. Create a new configuration file "include/configs/<board>.h" for
  1707. your board
  1708. 3. If you're porting U-Boot to a new CPU, then also create a new
  1709. directory to hold your CPU specific code. Add any files you need.
  1710. 4. Run "make <board>_config" with your new name.
  1711. 5. Type "make", and you should get a working "u-boot.srec" file
  1712. to be installed on your target system.
  1713. 6. Debug and solve any problems that might arise.
  1714. [Of course, this last step is much harder than it sounds.]
  1715. Testing of U-Boot Modifications, Ports to New Hardware, etc.:
  1716. ==============================================================
  1717. If you have modified U-Boot sources (for instance added a new board
  1718. or support for new devices, a new CPU, etc.) you are expected to
  1719. provide feedback to the other developers. The feedback normally takes
  1720. the form of a "patch", i. e. a context diff against a certain (latest
  1721. official or latest in CVS) version of U-Boot sources.
  1722. But before you submit such a patch, please verify that your modifi-
  1723. cation did not break existing code. At least make sure that *ALL* of
  1724. the supported boards compile WITHOUT ANY compiler warnings. To do so,
  1725. just run the "MAKEALL" script, which will configure and build U-Boot
  1726. for ALL supported system. Be warned, this will take a while. You can
  1727. select which (cross) compiler to use by passing a `CROSS_COMPILE'
  1728. environment variable to the script, i. e. to use the cross tools from
  1729. MontaVista's Hard Hat Linux you can type
  1730. CROSS_COMPILE=ppc_8xx- MAKEALL
  1731. or to build on a native PowerPC system you can type
  1732. CROSS_COMPILE=' ' MAKEALL
  1733. See also "U-Boot Porting Guide" below.
  1734. Monitor Commands - Overview:
  1735. ============================
  1736. go - start application at address 'addr'
  1737. run - run commands in an environment variable
  1738. bootm - boot application image from memory
  1739. bootp - boot image via network using BootP/TFTP protocol
  1740. tftpboot- boot image via network using TFTP protocol
  1741. and env variables "ipaddr" and "serverip"
  1742. (and eventually "gatewayip")
  1743. rarpboot- boot image via network using RARP/TFTP protocol
  1744. diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
  1745. loads - load S-Record file over serial line
  1746. loadb - load binary file over serial line (kermit mode)
  1747. md - memory display
  1748. mm - memory modify (auto-incrementing)
  1749. nm - memory modify (constant address)
  1750. mw - memory write (fill)
  1751. cp - memory copy
  1752. cmp - memory compare
  1753. crc32 - checksum calculation
  1754. imd - i2c memory display
  1755. imm - i2c memory modify (auto-incrementing)
  1756. inm - i2c memory modify (constant address)
  1757. imw - i2c memory write (fill)
  1758. icrc32 - i2c checksum calculation
  1759. iprobe - probe to discover valid I2C chip addresses
  1760. iloop - infinite loop on address range
  1761. isdram - print SDRAM configuration information
  1762. sspi - SPI utility commands
  1763. base - print or set address offset
  1764. printenv- print environment variables
  1765. setenv - set environment variables
  1766. saveenv - save environment variables to persistent storage
  1767. protect - enable or disable FLASH write protection
  1768. erase - erase FLASH memory
  1769. flinfo - print FLASH memory information
  1770. bdinfo - print Board Info structure
  1771. iminfo - print header information for application image
  1772. coninfo - print console devices and informations
  1773. ide - IDE sub-system
  1774. loop - infinite loop on address range
  1775. loopw - infinite write loop on address range
  1776. mtest - simple RAM test
  1777. icache - enable or disable instruction cache
  1778. dcache - enable or disable data cache
  1779. reset - Perform RESET of the CPU
  1780. echo - echo args to console
  1781. version - print monitor version
  1782. help - print online help
  1783. ? - alias for 'help'
  1784. Monitor Commands - Detailed Description:
  1785. ========================================
  1786. TODO.
  1787. For now: just type "help <command>".
  1788. Environment Variables:
  1789. ======================
  1790. U-Boot supports user configuration using Environment Variables which
  1791. can be made persistent by saving to Flash memory.
  1792. Environment Variables are set using "setenv", printed using
  1793. "printenv", and saved to Flash using "saveenv". Using "setenv"
  1794. without a value can be used to delete a variable from the
  1795. environment. As long as you don't save the environment you are
  1796. working with an in-memory copy. In case the Flash area containing the
  1797. environment is erased by accident, a default environment is provided.
  1798. Some configuration options can be set using Environment Variables:
  1799. baudrate - see CONFIG_BAUDRATE
  1800. bootdelay - see CONFIG_BOOTDELAY
  1801. bootcmd - see CONFIG_BOOTCOMMAND
  1802. bootargs - Boot arguments when booting an RTOS image
  1803. bootfile - Name of the image to load with TFTP
  1804. autoload - if set to "no" (any string beginning with 'n'),
  1805. "bootp" will just load perform a lookup of the
  1806. configuration from the BOOTP server, but not try to
  1807. load any image using TFTP
  1808. autostart - if set to "yes", an image loaded using the "bootp",
  1809. "rarpboot", "tftpboot" or "diskboot" commands will
  1810. be automatically started (by internally calling
  1811. "bootm")
  1812. If set to "no", a standalone image passed to the
  1813. "bootm" command will be copied to the load address
  1814. (and eventually uncompressed), but NOT be started.
  1815. This can be used to load and uncompress arbitrary
  1816. data.
  1817. i2cfast - (PPC405GP|PPC405EP only)
  1818. if set to 'y' configures Linux I2C driver for fast
  1819. mode (400kHZ). This environment variable is used in
  1820. initialization code. So, for changes to be effective
  1821. it must be saved and board must be reset.
  1822. initrd_high - restrict positioning of initrd images:
  1823. If this variable is not set, initrd images will be
  1824. copied to the highest possible address in RAM; this
  1825. is usually what you want since it allows for
  1826. maximum initrd size. If for some reason you want to
  1827. make sure that the initrd image is loaded below the
  1828. CFG_BOOTMAPSZ limit, you can set this environment
  1829. variable to a value of "no" or "off" or "0".
  1830. Alternatively, you can set it to a maximum upper
  1831. address to use (U-Boot will still check that it
  1832. does not overwrite the U-Boot stack and data).
  1833. For instance, when you have a system with 16 MB
  1834. RAM, and want to reserve 4 MB from use by Linux,
  1835. you can do this by adding "mem=12M" to the value of
  1836. the "bootargs" variable. However, now you must make
  1837. sure that the initrd image is placed in the first
  1838. 12 MB as well - this can be done with
  1839. setenv initrd_high 00c00000
  1840. If you set initrd_high to 0xFFFFFFFF, this is an
  1841. indication to U-Boot that all addresses are legal
  1842. for the Linux kernel, including addresses in flash
  1843. memory. In this case U-Boot will NOT COPY the
  1844. ramdisk at all. This may be useful to reduce the
  1845. boot time on your system, but requires that this
  1846. feature is supported by your Linux kernel.
  1847. ipaddr - IP address; needed for tftpboot command
  1848. loadaddr - Default load address for commands like "bootp",
  1849. "rarpboot", "tftpboot", "loadb" or "diskboot"
  1850. loads_echo - see CONFIG_LOADS_ECHO
  1851. serverip - TFTP server IP address; needed for tftpboot command
  1852. bootretry - see CONFIG_BOOT_RETRY_TIME
  1853. bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
  1854. bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
  1855. ethprime - When CONFIG_NET_MULTI is enabled controls which
  1856. interface is used first.
  1857. ethact - When CONFIG_NET_MULTI is enabled controls which
  1858. interface is currently active. For example you
  1859. can do the following
  1860. => setenv ethact FEC ETHERNET
  1861. => ping 192.168.0.1 # traffic sent on FEC ETHERNET
  1862. => setenv ethact SCC ETHERNET
  1863. => ping 10.0.0.1 # traffic sent on SCC ETHERNET
  1864. netretry - When set to "no" each network operation will
  1865. either succeed or fail without retrying.
  1866. When set to "once" the network operation will
  1867. fail when all the available network interfaces
  1868. are tried once without success.
  1869. Useful on scripts which control the retry operation
  1870. themselves.
  1871. vlan - When set to a value < 4095 the traffic over
  1872. ethernet is encapsulated/received over 802.1q
  1873. VLAN tagged frames.
  1874. The following environment variables may be used and automatically
  1875. updated by the network boot commands ("bootp" and "rarpboot"),
  1876. depending the information provided by your boot server:
  1877. bootfile - see above
  1878. dnsip - IP address of your Domain Name Server
  1879. dnsip2 - IP address of your secondary Domain Name Server
  1880. gatewayip - IP address of the Gateway (Router) to use
  1881. hostname - Target hostname
  1882. ipaddr - see above
  1883. netmask - Subnet Mask
  1884. rootpath - Pathname of the root filesystem on the NFS server
  1885. serverip - see above
  1886. There are two special Environment Variables:
  1887. serial# - contains hardware identification information such
  1888. as type string and/or serial number
  1889. ethaddr - Ethernet address
  1890. These variables can be set only once (usually during manufacturing of
  1891. the board). U-Boot refuses to delete or overwrite these variables
  1892. once they have been set once.
  1893. Further special Environment Variables:
  1894. ver - Contains the U-Boot version string as printed
  1895. with the "version" command. This variable is
  1896. readonly (see CONFIG_VERSION_VARIABLE).
  1897. Please note that changes to some configuration parameters may take
  1898. only effect after the next boot (yes, that's just like Windoze :-).
  1899. Command Line Parsing:
  1900. =====================
  1901. There are two different command line parsers available with U-Boot:
  1902. the old "simple" one, and the much more powerful "hush" shell:
  1903. Old, simple command line parser:
  1904. --------------------------------
  1905. - supports environment variables (through setenv / saveenv commands)
  1906. - several commands on one line, separated by ';'
  1907. - variable substitution using "... $(name) ..." syntax
  1908. - special characters ('$', ';') can be escaped by prefixing with '\',
  1909. for example:
  1910. setenv bootcmd bootm \$(address)
  1911. - You can also escape text by enclosing in single apostrophes, for example:
  1912. setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
  1913. Hush shell:
  1914. -----------
  1915. - similar to Bourne shell, with control structures like
  1916. if...then...else...fi, for...do...done; while...do...done,
  1917. until...do...done, ...
  1918. - supports environment ("global") variables (through setenv / saveenv
  1919. commands) and local shell variables (through standard shell syntax
  1920. "name=value"); only environment variables can be used with "run"
  1921. command
  1922. General rules:
  1923. --------------
  1924. (1) If a command line (or an environment variable executed by a "run"
  1925. command) contains several commands separated by semicolon, and
  1926. one of these commands fails, then the remaining commands will be
  1927. executed anyway.
  1928. (2) If you execute several variables with one call to run (i. e.
  1929. calling run with a list af variables as arguments), any failing
  1930. command will cause "run" to terminate, i. e. the remaining
  1931. variables are not executed.
  1932. Note for Redundant Ethernet Interfaces:
  1933. =======================================
  1934. Some boards come with redundant ethernet interfaces; U-Boot supports
  1935. such configurations and is capable of automatic selection of a
  1936. "working" interface when needed. MAC assignment works as follows:
  1937. Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
  1938. MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
  1939. "eth1addr" (=>eth1), "eth2addr", ...
  1940. If the network interface stores some valid MAC address (for instance
  1941. in SROM), this is used as default address if there is NO correspon-
  1942. ding setting in the environment; if the corresponding environment
  1943. variable is set, this overrides the settings in the card; that means:
  1944. o If the SROM has a valid MAC address, and there is no address in the
  1945. environment, the SROM's address is used.
  1946. o If there is no valid address in the SROM, and a definition in the
  1947. environment exists, then the value from the environment variable is
  1948. used.
  1949. o If both the SROM and the environment contain a MAC address, and
  1950. both addresses are the same, this MAC address is used.
  1951. o If both the SROM and the environment contain a MAC address, and the
  1952. addresses differ, the value from the environment is used and a
  1953. warning is printed.
  1954. o If neither SROM nor the environment contain a MAC address, an error
  1955. is raised.
  1956. Image Formats:
  1957. ==============
  1958. The "boot" commands of this monitor operate on "image" files which
  1959. can be basicly anything, preceeded by a special header; see the
  1960. definitions in include/image.h for details; basicly, the header
  1961. defines the following image properties:
  1962. * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
  1963. 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
  1964. LynxOS, pSOS, QNX, RTEMS, ARTOS;
  1965. Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, ARTOS, LynxOS).
  1966. * Target CPU Architecture (Provisions for Alpha, ARM, Intel x86,
  1967. IA64, MIPS, NIOS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
  1968. Currently supported: ARM, Intel x86, MIPS, NIOS, PowerPC).
  1969. * Compression Type (uncompressed, gzip, bzip2)
  1970. * Load Address
  1971. * Entry Point
  1972. * Image Name
  1973. * Image Timestamp
  1974. The header is marked by a special Magic Number, and both the header
  1975. and the data portions of the image are secured against corruption by
  1976. CRC32 checksums.
  1977. Linux Support:
  1978. ==============
  1979. Although U-Boot should support any OS or standalone application
  1980. easily, the main focus has always been on Linux during the design of
  1981. U-Boot.
  1982. U-Boot includes many features that so far have been part of some
  1983. special "boot loader" code within the Linux kernel. Also, any
  1984. "initrd" images to be used are no longer part of one big Linux image;
  1985. instead, kernel and "initrd" are separate images. This implementation
  1986. serves several purposes:
  1987. - the same features can be used for other OS or standalone
  1988. applications (for instance: using compressed images to reduce the
  1989. Flash memory footprint)
  1990. - it becomes much easier to port new Linux kernel versions because
  1991. lots of low-level, hardware dependent stuff are done by U-Boot
  1992. - the same Linux kernel image can now be used with different "initrd"
  1993. images; of course this also means that different kernel images can
  1994. be run with the same "initrd". This makes testing easier (you don't
  1995. have to build a new "zImage.initrd" Linux image when you just
  1996. change a file in your "initrd"). Also, a field-upgrade of the
  1997. software is easier now.
  1998. Linux HOWTO:
  1999. ============
  2000. Porting Linux to U-Boot based systems:
  2001. ---------------------------------------
  2002. U-Boot cannot save you from doing all the necessary modifications to
  2003. configure the Linux device drivers for use with your target hardware
  2004. (no, we don't intend to provide a full virtual machine interface to
  2005. Linux :-).
  2006. But now you can ignore ALL boot loader code (in arch/ppc/mbxboot).
  2007. Just make sure your machine specific header file (for instance
  2008. include/asm-ppc/tqm8xx.h) includes the same definition of the Board
  2009. Information structure as we define in include/u-boot.h, and make
  2010. sure that your definition of IMAP_ADDR uses the same value as your
  2011. U-Boot configuration in CFG_IMMR.
  2012. Configuring the Linux kernel:
  2013. -----------------------------
  2014. No specific requirements for U-Boot. Make sure you have some root
  2015. device (initial ramdisk, NFS) for your target system.
  2016. Building a Linux Image:
  2017. -----------------------
  2018. With U-Boot, "normal" build targets like "zImage" or "bzImage" are
  2019. not used. If you use recent kernel source, a new build target
  2020. "uImage" will exist which automatically builds an image usable by
  2021. U-Boot. Most older kernels also have support for a "pImage" target,
  2022. which was introduced for our predecessor project PPCBoot and uses a
  2023. 100% compatible format.
  2024. Example:
  2025. make TQM850L_config
  2026. make oldconfig
  2027. make dep
  2028. make uImage
  2029. The "uImage" build target uses a special tool (in 'tools/mkimage') to
  2030. encapsulate a compressed Linux kernel image with header information,
  2031. CRC32 checksum etc. for use with U-Boot. This is what we are doing:
  2032. * build a standard "vmlinux" kernel image (in ELF binary format):
  2033. * convert the kernel into a raw binary image:
  2034. ${CROSS_COMPILE}-objcopy -O binary \
  2035. -R .note -R .comment \
  2036. -S vmlinux linux.bin
  2037. * compress the binary image:
  2038. gzip -9 linux.bin
  2039. * package compressed binary image for U-Boot:
  2040. mkimage -A ppc -O linux -T kernel -C gzip \
  2041. -a 0 -e 0 -n "Linux Kernel Image" \
  2042. -d linux.bin.gz uImage
  2043. The "mkimage" tool can also be used to create ramdisk images for use
  2044. with U-Boot, either separated from the Linux kernel image, or
  2045. combined into one file. "mkimage" encapsulates the images with a 64
  2046. byte header containing information about target architecture,
  2047. operating system, image type, compression method, entry points, time
  2048. stamp, CRC32 checksums, etc.
  2049. "mkimage" can be called in two ways: to verify existing images and
  2050. print the header information, or to build new images.
  2051. In the first form (with "-l" option) mkimage lists the information
  2052. contained in the header of an existing U-Boot image; this includes
  2053. checksum verification:
  2054. tools/mkimage -l image
  2055. -l ==> list image header information
  2056. The second form (with "-d" option) is used to build a U-Boot image
  2057. from a "data file" which is used as image payload:
  2058. tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
  2059. -n name -d data_file image
  2060. -A ==> set architecture to 'arch'
  2061. -O ==> set operating system to 'os'
  2062. -T ==> set image type to 'type'
  2063. -C ==> set compression type 'comp'
  2064. -a ==> set load address to 'addr' (hex)
  2065. -e ==> set entry point to 'ep' (hex)
  2066. -n ==> set image name to 'name'
  2067. -d ==> use image data from 'datafile'
  2068. Right now, all Linux kernels for PowerPC systems use the same load
  2069. address (0x00000000), but the entry point address depends on the
  2070. kernel version:
  2071. - 2.2.x kernels have the entry point at 0x0000000C,
  2072. - 2.3.x and later kernels have the entry point at 0x00000000.
  2073. So a typical call to build a U-Boot image would read:
  2074. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  2075. > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
  2076. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz \
  2077. > examples/uImage.TQM850L
  2078. Image Name: 2.4.4 kernel for TQM850L
  2079. Created: Wed Jul 19 02:34:59 2000
  2080. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2081. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  2082. Load Address: 0x00000000
  2083. Entry Point: 0x00000000
  2084. To verify the contents of the image (or check for corruption):
  2085. -> tools/mkimage -l examples/uImage.TQM850L
  2086. Image Name: 2.4.4 kernel for TQM850L
  2087. Created: Wed Jul 19 02:34:59 2000
  2088. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2089. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  2090. Load Address: 0x00000000
  2091. Entry Point: 0x00000000
  2092. NOTE: for embedded systems where boot time is critical you can trade
  2093. speed for memory and install an UNCOMPRESSED image instead: this
  2094. needs more space in Flash, but boots much faster since it does not
  2095. need to be uncompressed:
  2096. -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz
  2097. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  2098. > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
  2099. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux \
  2100. > examples/uImage.TQM850L-uncompressed
  2101. Image Name: 2.4.4 kernel for TQM850L
  2102. Created: Wed Jul 19 02:34:59 2000
  2103. Image Type: PowerPC Linux Kernel Image (uncompressed)
  2104. Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
  2105. Load Address: 0x00000000
  2106. Entry Point: 0x00000000
  2107. Similar you can build U-Boot images from a 'ramdisk.image.gz' file
  2108. when your kernel is intended to use an initial ramdisk:
  2109. -> tools/mkimage -n 'Simple Ramdisk Image' \
  2110. > -A ppc -O linux -T ramdisk -C gzip \
  2111. > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
  2112. Image Name: Simple Ramdisk Image
  2113. Created: Wed Jan 12 14:01:50 2000
  2114. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2115. Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
  2116. Load Address: 0x00000000
  2117. Entry Point: 0x00000000
  2118. Installing a Linux Image:
  2119. -------------------------
  2120. To downloading a U-Boot image over the serial (console) interface,
  2121. you must convert the image to S-Record format:
  2122. objcopy -I binary -O srec examples/image examples/image.srec
  2123. The 'objcopy' does not understand the information in the U-Boot
  2124. image header, so the resulting S-Record file will be relative to
  2125. address 0x00000000. To load it to a given address, you need to
  2126. specify the target address as 'offset' parameter with the 'loads'
  2127. command.
  2128. Example: install the image to address 0x40100000 (which on the
  2129. TQM8xxL is in the first Flash bank):
  2130. => erase 40100000 401FFFFF
  2131. .......... done
  2132. Erased 8 sectors
  2133. => loads 40100000
  2134. ## Ready for S-Record download ...
  2135. ~>examples/image.srec
  2136. 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
  2137. ...
  2138. 15989 15990 15991 15992
  2139. [file transfer complete]
  2140. [connected]
  2141. ## Start Addr = 0x00000000
  2142. You can check the success of the download using the 'iminfo' command;
  2143. this includes a checksum verification so you can be sure no data
  2144. corruption happened:
  2145. => imi 40100000
  2146. ## Checking Image at 40100000 ...
  2147. Image Name: 2.2.13 for initrd on TQM850L
  2148. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2149. Data Size: 335725 Bytes = 327 kB = 0 MB
  2150. Load Address: 00000000
  2151. Entry Point: 0000000c
  2152. Verifying Checksum ... OK
  2153. Boot Linux:
  2154. -----------
  2155. The "bootm" command is used to boot an application that is stored in
  2156. memory (RAM or Flash). In case of a Linux kernel image, the contents
  2157. of the "bootargs" environment variable is passed to the kernel as
  2158. parameters. You can check and modify this variable using the
  2159. "printenv" and "setenv" commands:
  2160. => printenv bootargs
  2161. bootargs=root=/dev/ram
  2162. => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2163. => printenv bootargs
  2164. bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2165. => bootm 40020000
  2166. ## Booting Linux kernel at 40020000 ...
  2167. Image Name: 2.2.13 for NFS on TQM850L
  2168. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2169. Data Size: 381681 Bytes = 372 kB = 0 MB
  2170. Load Address: 00000000
  2171. Entry Point: 0000000c
  2172. Verifying Checksum ... OK
  2173. Uncompressing Kernel Image ... OK
  2174. Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:35:17 MEST 2000
  2175. Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2176. time_init: decrementer frequency = 187500000/60
  2177. Calibrating delay loop... 49.77 BogoMIPS
  2178. Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
  2179. ...
  2180. If you want to boot a Linux kernel with initial ram disk, you pass
  2181. the memory addresses of both the kernel and the initrd image (PPBCOOT
  2182. format!) to the "bootm" command:
  2183. => imi 40100000 40200000
  2184. ## Checking Image at 40100000 ...
  2185. Image Name: 2.2.13 for initrd on TQM850L
  2186. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2187. Data Size: 335725 Bytes = 327 kB = 0 MB
  2188. Load Address: 00000000
  2189. Entry Point: 0000000c
  2190. Verifying Checksum ... OK
  2191. ## Checking Image at 40200000 ...
  2192. Image Name: Simple Ramdisk Image
  2193. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2194. Data Size: 566530 Bytes = 553 kB = 0 MB
  2195. Load Address: 00000000
  2196. Entry Point: 00000000
  2197. Verifying Checksum ... OK
  2198. => bootm 40100000 40200000
  2199. ## Booting Linux kernel at 40100000 ...
  2200. Image Name: 2.2.13 for initrd on TQM850L
  2201. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2202. Data Size: 335725 Bytes = 327 kB = 0 MB
  2203. Load Address: 00000000
  2204. Entry Point: 0000000c
  2205. Verifying Checksum ... OK
  2206. Uncompressing Kernel Image ... OK
  2207. ## Loading RAMDisk Image at 40200000 ...
  2208. Image Name: Simple Ramdisk Image
  2209. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2210. Data Size: 566530 Bytes = 553 kB = 0 MB
  2211. Load Address: 00000000
  2212. Entry Point: 00000000
  2213. Verifying Checksum ... OK
  2214. Loading Ramdisk ... OK
  2215. Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:32:08 MEST 2000
  2216. Boot arguments: root=/dev/ram
  2217. time_init: decrementer frequency = 187500000/60
  2218. Calibrating delay loop... 49.77 BogoMIPS
  2219. ...
  2220. RAMDISK: Compressed image found at block 0
  2221. VFS: Mounted root (ext2 filesystem).
  2222. bash#
  2223. More About U-Boot Image Types:
  2224. ------------------------------
  2225. U-Boot supports the following image types:
  2226. "Standalone Programs" are directly runnable in the environment
  2227. provided by U-Boot; it is expected that (if they behave
  2228. well) you can continue to work in U-Boot after return from
  2229. the Standalone Program.
  2230. "OS Kernel Images" are usually images of some Embedded OS which
  2231. will take over control completely. Usually these programs
  2232. will install their own set of exception handlers, device
  2233. drivers, set up the MMU, etc. - this means, that you cannot
  2234. expect to re-enter U-Boot except by resetting the CPU.
  2235. "RAMDisk Images" are more or less just data blocks, and their
  2236. parameters (address, size) are passed to an OS kernel that is
  2237. being started.
  2238. "Multi-File Images" contain several images, typically an OS
  2239. (Linux) kernel image and one or more data images like
  2240. RAMDisks. This construct is useful for instance when you want
  2241. to boot over the network using BOOTP etc., where the boot
  2242. server provides just a single image file, but you want to get
  2243. for instance an OS kernel and a RAMDisk image.
  2244. "Multi-File Images" start with a list of image sizes, each
  2245. image size (in bytes) specified by an "uint32_t" in network
  2246. byte order. This list is terminated by an "(uint32_t)0".
  2247. Immediately after the terminating 0 follow the images, one by
  2248. one, all aligned on "uint32_t" boundaries (size rounded up to
  2249. a multiple of 4 bytes).
  2250. "Firmware Images" are binary images containing firmware (like
  2251. U-Boot or FPGA images) which usually will be programmed to
  2252. flash memory.
  2253. "Script files" are command sequences that will be executed by
  2254. U-Boot's command interpreter; this feature is especially
  2255. useful when you configure U-Boot to use a real shell (hush)
  2256. as command interpreter.
  2257. Standalone HOWTO:
  2258. =================
  2259. One of the features of U-Boot is that you can dynamically load and
  2260. run "standalone" applications, which can use some resources of
  2261. U-Boot like console I/O functions or interrupt services.
  2262. Two simple examples are included with the sources:
  2263. "Hello World" Demo:
  2264. -------------------
  2265. 'examples/hello_world.c' contains a small "Hello World" Demo
  2266. application; it is automatically compiled when you build U-Boot.
  2267. It's configured to run at address 0x00040004, so you can play with it
  2268. like that:
  2269. => loads
  2270. ## Ready for S-Record download ...
  2271. ~>examples/hello_world.srec
  2272. 1 2 3 4 5 6 7 8 9 10 11 ...
  2273. [file transfer complete]
  2274. [connected]
  2275. ## Start Addr = 0x00040004
  2276. => go 40004 Hello World! This is a test.
  2277. ## Starting application at 0x00040004 ...
  2278. Hello World
  2279. argc = 7
  2280. argv[0] = "40004"
  2281. argv[1] = "Hello"
  2282. argv[2] = "World!"
  2283. argv[3] = "This"
  2284. argv[4] = "is"
  2285. argv[5] = "a"
  2286. argv[6] = "test."
  2287. argv[7] = "<NULL>"
  2288. Hit any key to exit ...
  2289. ## Application terminated, rc = 0x0
  2290. Another example, which demonstrates how to register a CPM interrupt
  2291. handler with the U-Boot code, can be found in 'examples/timer.c'.
  2292. Here, a CPM timer is set up to generate an interrupt every second.
  2293. The interrupt service routine is trivial, just printing a '.'
  2294. character, but this is just a demo program. The application can be
  2295. controlled by the following keys:
  2296. ? - print current values og the CPM Timer registers
  2297. b - enable interrupts and start timer
  2298. e - stop timer and disable interrupts
  2299. q - quit application
  2300. => loads
  2301. ## Ready for S-Record download ...
  2302. ~>examples/timer.srec
  2303. 1 2 3 4 5 6 7 8 9 10 11 ...
  2304. [file transfer complete]
  2305. [connected]
  2306. ## Start Addr = 0x00040004
  2307. => go 40004
  2308. ## Starting application at 0x00040004 ...
  2309. TIMERS=0xfff00980
  2310. Using timer 1
  2311. tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
  2312. Hit 'b':
  2313. [q, b, e, ?] Set interval 1000000 us
  2314. Enabling timer
  2315. Hit '?':
  2316. [q, b, e, ?] ........
  2317. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
  2318. Hit '?':
  2319. [q, b, e, ?] .
  2320. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
  2321. Hit '?':
  2322. [q, b, e, ?] .
  2323. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
  2324. Hit '?':
  2325. [q, b, e, ?] .
  2326. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
  2327. Hit 'e':
  2328. [q, b, e, ?] ...Stopping timer
  2329. Hit 'q':
  2330. [q, b, e, ?] ## Application terminated, rc = 0x0
  2331. Minicom warning:
  2332. ================
  2333. Over time, many people have reported problems when trying to use the
  2334. "minicom" terminal emulation program for serial download. I (wd)
  2335. consider minicom to be broken, and recommend not to use it. Under
  2336. Unix, I recommend to use C-Kermit for general purpose use (and
  2337. especially for kermit binary protocol download ("loadb" command), and
  2338. use "cu" for S-Record download ("loads" command).
  2339. Nevertheless, if you absolutely want to use it try adding this
  2340. configuration to your "File transfer protocols" section:
  2341. Name Program Name U/D FullScr IO-Red. Multi
  2342. X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
  2343. Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
  2344. NetBSD Notes:
  2345. =============
  2346. Starting at version 0.9.2, U-Boot supports NetBSD both as host
  2347. (build U-Boot) and target system (boots NetBSD/mpc8xx).
  2348. Building requires a cross environment; it is known to work on
  2349. NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
  2350. need gmake since the Makefiles are not compatible with BSD make).
  2351. Note that the cross-powerpc package does not install include files;
  2352. attempting to build U-Boot will fail because <machine/ansi.h> is
  2353. missing. This file has to be installed and patched manually:
  2354. # cd /usr/pkg/cross/powerpc-netbsd/include
  2355. # mkdir powerpc
  2356. # ln -s powerpc machine
  2357. # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
  2358. # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
  2359. Native builds *don't* work due to incompatibilities between native
  2360. and U-Boot include files.
  2361. Booting assumes that (the first part of) the image booted is a
  2362. stage-2 loader which in turn loads and then invokes the kernel
  2363. proper. Loader sources will eventually appear in the NetBSD source
  2364. tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
  2365. meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
  2366. Implementation Internals:
  2367. =========================
  2368. The following is not intended to be a complete description of every
  2369. implementation detail. However, it should help to understand the
  2370. inner workings of U-Boot and make it easier to port it to custom
  2371. hardware.
  2372. Initial Stack, Global Data:
  2373. ---------------------------
  2374. The implementation of U-Boot is complicated by the fact that U-Boot
  2375. starts running out of ROM (flash memory), usually without access to
  2376. system RAM (because the memory controller is not initialized yet).
  2377. This means that we don't have writable Data or BSS segments, and BSS
  2378. is not initialized as zero. To be able to get a C environment working
  2379. at all, we have to allocate at least a minimal stack. Implementation
  2380. options for this are defined and restricted by the CPU used: Some CPU
  2381. models provide on-chip memory (like the IMMR area on MPC8xx and
  2382. MPC826x processors), on others (parts of) the data cache can be
  2383. locked as (mis-) used as memory, etc.
  2384. Chris Hallinan posted a good summary of these issues to the
  2385. u-boot-users mailing list:
  2386. Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
  2387. From: "Chris Hallinan" <clh@net1plus.com>
  2388. Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
  2389. ...
  2390. Correct me if I'm wrong, folks, but the way I understand it
  2391. is this: Using DCACHE as initial RAM for Stack, etc, does not
  2392. require any physical RAM backing up the cache. The cleverness
  2393. is that the cache is being used as a temporary supply of
  2394. necessary storage before the SDRAM controller is setup. It's
  2395. beyond the scope of this list to expain the details, but you
  2396. can see how this works by studying the cache architecture and
  2397. operation in the architecture and processor-specific manuals.
  2398. OCM is On Chip Memory, which I believe the 405GP has 4K. It
  2399. is another option for the system designer to use as an
  2400. initial stack/ram area prior to SDRAM being available. Either
  2401. option should work for you. Using CS 4 should be fine if your
  2402. board designers haven't used it for something that would
  2403. cause you grief during the initial boot! It is frequently not
  2404. used.
  2405. CFG_INIT_RAM_ADDR should be somewhere that won't interfere
  2406. with your processor/board/system design. The default value
  2407. you will find in any recent u-boot distribution in
  2408. walnut.h should work for you. I'd set it to a value larger
  2409. than your SDRAM module. If you have a 64MB SDRAM module, set
  2410. it above 400_0000. Just make sure your board has no resources
  2411. that are supposed to respond to that address! That code in
  2412. start.S has been around a while and should work as is when
  2413. you get the config right.
  2414. -Chris Hallinan
  2415. DS4.COM, Inc.
  2416. It is essential to remember this, since it has some impact on the C
  2417. code for the initialization procedures:
  2418. * Initialized global data (data segment) is read-only. Do not attempt
  2419. to write it.
  2420. * Do not use any unitialized global data (or implicitely initialized
  2421. as zero data - BSS segment) at all - this is undefined, initiali-
  2422. zation is performed later (when relocating to RAM).
  2423. * Stack space is very limited. Avoid big data buffers or things like
  2424. that.
  2425. Having only the stack as writable memory limits means we cannot use
  2426. normal global data to share information beween the code. But it
  2427. turned out that the implementation of U-Boot can be greatly
  2428. simplified by making a global data structure (gd_t) available to all
  2429. functions. We could pass a pointer to this data as argument to _all_
  2430. functions, but this would bloat the code. Instead we use a feature of
  2431. the GCC compiler (Global Register Variables) to share the data: we
  2432. place a pointer (gd) to the global data into a register which we
  2433. reserve for this purpose.
  2434. When choosing a register for such a purpose we are restricted by the
  2435. relevant (E)ABI specifications for the current architecture, and by
  2436. GCC's implementation.
  2437. For PowerPC, the following registers have specific use:
  2438. R1: stack pointer
  2439. R2: TOC pointer
  2440. R3-R4: parameter passing and return values
  2441. R5-R10: parameter passing
  2442. R13: small data area pointer
  2443. R30: GOT pointer
  2444. R31: frame pointer
  2445. (U-Boot also uses R14 as internal GOT pointer.)
  2446. ==> U-Boot will use R29 to hold a pointer to the global data
  2447. Note: on PPC, we could use a static initializer (since the
  2448. address of the global data structure is known at compile time),
  2449. but it turned out that reserving a register results in somewhat
  2450. smaller code - although the code savings are not that big (on
  2451. average for all boards 752 bytes for the whole U-Boot image,
  2452. 624 text + 127 data).
  2453. On ARM, the following registers are used:
  2454. R0: function argument word/integer result
  2455. R1-R3: function argument word
  2456. R9: GOT pointer
  2457. R10: stack limit (used only if stack checking if enabled)
  2458. R11: argument (frame) pointer
  2459. R12: temporary workspace
  2460. R13: stack pointer
  2461. R14: link register
  2462. R15: program counter
  2463. ==> U-Boot will use R8 to hold a pointer to the global data
  2464. Memory Management:
  2465. ------------------
  2466. U-Boot runs in system state and uses physical addresses, i.e. the
  2467. MMU is not used either for address mapping nor for memory protection.
  2468. The available memory is mapped to fixed addresses using the memory
  2469. controller. In this process, a contiguous block is formed for each
  2470. memory type (Flash, SDRAM, SRAM), even when it consists of several
  2471. physical memory banks.
  2472. U-Boot is installed in the first 128 kB of the first Flash bank (on
  2473. TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
  2474. booting and sizing and initializing DRAM, the code relocates itself
  2475. to the upper end of DRAM. Immediately below the U-Boot code some
  2476. memory is reserved for use by malloc() [see CFG_MALLOC_LEN
  2477. configuration setting]. Below that, a structure with global Board
  2478. Info data is placed, followed by the stack (growing downward).
  2479. Additionally, some exception handler code is copied to the low 8 kB
  2480. of DRAM (0x00000000 ... 0x00001FFF).
  2481. So a typical memory configuration with 16 MB of DRAM could look like
  2482. this:
  2483. 0x0000 0000 Exception Vector code
  2484. :
  2485. 0x0000 1FFF
  2486. 0x0000 2000 Free for Application Use
  2487. :
  2488. :
  2489. :
  2490. :
  2491. 0x00FB FF20 Monitor Stack (Growing downward)
  2492. 0x00FB FFAC Board Info Data and permanent copy of global data
  2493. 0x00FC 0000 Malloc Arena
  2494. :
  2495. 0x00FD FFFF
  2496. 0x00FE 0000 RAM Copy of Monitor Code
  2497. ... eventually: LCD or video framebuffer
  2498. ... eventually: pRAM (Protected RAM - unchanged by reset)
  2499. 0x00FF FFFF [End of RAM]
  2500. System Initialization:
  2501. ----------------------
  2502. In the reset configuration, U-Boot starts at the reset entry point
  2503. (on most PowerPC systens at address 0x00000100). Because of the reset
  2504. configuration for CS0# this is a mirror of the onboard Flash memory.
  2505. To be able to re-map memory U-Boot then jumps to its link address.
  2506. To be able to implement the initialization code in C, a (small!)
  2507. initial stack is set up in the internal Dual Ported RAM (in case CPUs
  2508. which provide such a feature like MPC8xx or MPC8260), or in a locked
  2509. part of the data cache. After that, U-Boot initializes the CPU core,
  2510. the caches and the SIU.
  2511. Next, all (potentially) available memory banks are mapped using a
  2512. preliminary mapping. For example, we put them on 512 MB boundaries
  2513. (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
  2514. on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
  2515. programmed for SDRAM access. Using the temporary configuration, a
  2516. simple memory test is run that determines the size of the SDRAM
  2517. banks.
  2518. When there is more than one SDRAM bank, and the banks are of
  2519. different size, the largest is mapped first. For equal size, the first
  2520. bank (CS2#) is mapped first. The first mapping is always for address
  2521. 0x00000000, with any additional banks following immediately to create
  2522. contiguous memory starting from 0.
  2523. Then, the monitor installs itself at the upper end of the SDRAM area
  2524. and allocates memory for use by malloc() and for the global Board
  2525. Info data; also, the exception vector code is copied to the low RAM
  2526. pages, and the final stack is set up.
  2527. Only after this relocation will you have a "normal" C environment;
  2528. until that you are restricted in several ways, mostly because you are
  2529. running from ROM, and because the code will have to be relocated to a
  2530. new address in RAM.
  2531. U-Boot Porting Guide:
  2532. ----------------------
  2533. [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
  2534. list, October 2002]
  2535. int main (int argc, char *argv[])
  2536. {
  2537. sighandler_t no_more_time;
  2538. signal (SIGALRM, no_more_time);
  2539. alarm (PROJECT_DEADLINE - toSec (3 * WEEK));
  2540. if (available_money > available_manpower) {
  2541. pay consultant to port U-Boot;
  2542. return 0;
  2543. }
  2544. Download latest U-Boot source;
  2545. Subscribe to u-boot-users mailing list;
  2546. if (clueless) {
  2547. email ("Hi, I am new to U-Boot, how do I get started?");
  2548. }
  2549. while (learning) {
  2550. Read the README file in the top level directory;
  2551. Read http://www.denx.de/twiki/bin/view/DULG/Manual ;
  2552. Read the source, Luke;
  2553. }
  2554. if (available_money > toLocalCurrency ($2500)) {
  2555. Buy a BDI2000;
  2556. } else {
  2557. Add a lot of aggravation and time;
  2558. }
  2559. Create your own board support subdirectory;
  2560. Create your own board config file;
  2561. while (!running) {
  2562. do {
  2563. Add / modify source code;
  2564. } until (compiles);
  2565. Debug;
  2566. if (clueless)
  2567. email ("Hi, I am having problems...");
  2568. }
  2569. Send patch file to Wolfgang;
  2570. return 0;
  2571. }
  2572. void no_more_time (int sig)
  2573. {
  2574. hire_a_guru();
  2575. }
  2576. Coding Standards:
  2577. -----------------
  2578. All contributions to U-Boot should conform to the Linux kernel
  2579. coding style; see the file "Documentation/CodingStyle" in your Linux
  2580. kernel source directory.
  2581. Please note that U-Boot is implemented in C (and to some small parts
  2582. in Assembler); no C++ is used, so please do not use C++ style
  2583. comments (//) in your code.
  2584. Please also stick to the following formatting rules:
  2585. - remove any trailing white space
  2586. - use TAB characters for indentation, not spaces
  2587. - make sure NOT to use DOS '\r\n' line feeds
  2588. - do not add more than 2 empty lines to source files
  2589. - do not add trailing empty lines to source files
  2590. Submissions which do not conform to the standards may be returned
  2591. with a request to reformat the changes.
  2592. Submitting Patches:
  2593. -------------------
  2594. Since the number of patches for U-Boot is growing, we need to
  2595. establish some rules. Submissions which do not conform to these rules
  2596. may be rejected, even when they contain important and valuable stuff.
  2597. Patches shall be sent to the u-boot-users mailing list.
  2598. When you send a patch, please include the following information with
  2599. it:
  2600. * For bug fixes: a description of the bug and how your patch fixes
  2601. this bug. Please try to include a way of demonstrating that the
  2602. patch actually fixes something.
  2603. * For new features: a description of the feature and your
  2604. implementation.
  2605. * A CHANGELOG entry as plaintext (separate from the patch)
  2606. * For major contributions, your entry to the CREDITS file
  2607. * When you add support for a new board, don't forget to add this
  2608. board to the MAKEALL script, too.
  2609. * If your patch adds new configuration options, don't forget to
  2610. document these in the README file.
  2611. * The patch itself. If you are accessing the CVS repository use "cvs
  2612. update; cvs diff -puRN"; else, use "diff -purN OLD NEW". If your
  2613. version of diff does not support these options, then get the latest
  2614. version of GNU diff.
  2615. The current directory when running this command shall be the top
  2616. level directory of the U-Boot source tree, or it's parent directory
  2617. (i. e. please make sure that your patch includes sufficient
  2618. directory information for the affected files).
  2619. We accept patches as plain text, MIME attachments or as uuencoded
  2620. gzipped text.
  2621. * If one logical set of modifications affects or creates several
  2622. files, all these changes shall be submitted in a SINGLE patch file.
  2623. * Changesets that contain different, unrelated modifications shall be
  2624. submitted as SEPARATE patches, one patch per changeset.
  2625. Notes:
  2626. * Before sending the patch, run the MAKEALL script on your patched
  2627. source tree and make sure that no errors or warnings are reported
  2628. for any of the boards.
  2629. * Keep your modifications to the necessary minimum: A patch
  2630. containing several unrelated changes or arbitrary reformats will be
  2631. returned with a request to re-formatting / split it.
  2632. * If you modify existing code, make sure that your new code does not
  2633. add to the memory footprint of the code ;-) Small is beautiful!
  2634. When adding new features, these should compile conditionally only
  2635. (using #ifdef), and the resulting code with the new feature
  2636. disabled must not need more memory than the old code without your
  2637. modification.
  2638. * Remember that there is a size limit of 40 kB per message on the
  2639. u-boot-users mailing list. Compression may help.