Eric Lee / smarc-uboot

1

#

1

#

2

3

# Wolfgang Denk, DENX Software Engineering, wd@denx.de.

3

# Wolfgang Denk, DENX Software Engineering, wd@denx.de.

4

#

4

#

5

# See file CREDITS for list of people who contributed to this

5

# See file CREDITS for list of people who contributed to this

6

# project.

6

# project.

7

#

7

#

8

# This program is free software; you can redistribute it and/or

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

9

# modify it under the terms of the GNU General Public License as

10

# published by the Free Software Foundation; either version 2 of

10

# published by the Free Software Foundation; either version 2 of

11

# the License, or (at your option) any later version.

11

# the License, or (at your option) any later version.

12

#

12

#

13

# This program is distributed in the hope that it will be useful,

13

# This program is distributed in the hope that it will be useful,

14

# but WITHOUT ANY WARRANTY; without even the implied warranty of

14

# but WITHOUT ANY WARRANTY; without even the implied warranty of

15

# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

15

# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

16

# GNU General Public License for more details.

16

# GNU General Public License for more details.

17

#

17

#

18

# You should have received a copy of the GNU General Public License

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

19

# along with this program; if not, write to the Free Software

20

# Foundation, Inc., 59 Temple Place, Suite 330, Boston,

20

# Foundation, Inc., 59 Temple Place, Suite 330, Boston,

21

# MA 02111-1307 USA

21

# MA 02111-1307 USA

22

#

22

#

23

24

Summary:

24

Summary:

25

========

25

========

26

27

This directory contains the source code for U-Boot, a boot loader for

27

This directory contains the source code for U-Boot, a boot loader for

28

Embedded boards based on PowerPC, ARM, MIPS and several other

28

Embedded boards based on PowerPC, ARM, MIPS and several other

29

processors, which can be installed in a boot ROM and used to

29

processors, which can be installed in a boot ROM and used to

30

initialize and test the hardware or to download and run application

30

initialize and test the hardware or to download and run application

31

code.

31

code.

32

33

The development of U-Boot is closely related to Linux: some parts of

33

The development of U-Boot is closely related to Linux: some parts of

34

the source code originate in the Linux source tree, we have some

34

the source code originate in the Linux source tree, we have some

35

header files in common, and special provision has been made to

35

header files in common, and special provision has been made to

36

support booting of Linux images.

36

support booting of Linux images.

37

38

Some attention has been paid to make this software easily

38

Some attention has been paid to make this software easily

39

configurable and extendable. For instance, all monitor commands are

39

configurable and extendable. For instance, all monitor commands are

40

implemented with the same call interface, so that it's very easy to

40

implemented with the same call interface, so that it's very easy to

41

add new commands. Also, instead of permanently adding rarely used

41

add new commands. Also, instead of permanently adding rarely used

42

code (for instance hardware test utilities) to the monitor, you can

42

code (for instance hardware test utilities) to the monitor, you can

43

load and run it dynamically.

43

load and run it dynamically.

44

45

46

Status:

46

Status:

47

=======

47

=======

48

49

In general, all boards for which a configuration option exists in the

49

In general, all boards for which a configuration option exists in the

50

Makefile have been tested to some extent and can be considered

50

Makefile have been tested to some extent and can be considered

51

"working". In fact, many of them are used in production systems.

51

"working". In fact, many of them are used in production systems.

52

53

In case of problems see the CHANGELOG and CREDITS files to find out

53

In case of problems see the CHANGELOG and CREDITS files to find out

54

who contributed the specific port. The MAINTAINERS file lists board

54

who contributed the specific port. The MAINTAINERS file lists board

55

maintainers.

55

maintainers.

56

57

58

Where to get help:

58

Where to get help:

59

==================

59

==================

60

61

In case you have questions about, problems with or contributions for

61

In case you have questions about, problems with or contributions for

62

U-Boot you should send a message to the U-Boot mailing list at

62

U-Boot you should send a message to the U-Boot mailing list at

63

<u-boot@lists.denx.de>. There is also an archive of previous traffic

63

<u-boot@lists.denx.de>. There is also an archive of previous traffic

64

on the mailing list - please search the archive before asking FAQ's.

64

on the mailing list - please search the archive before asking FAQ's.

65

Please see http://lists.denx.de/pipermail/u-boot and

65

Please see http://lists.denx.de/pipermail/u-boot and

66

http://dir.gmane.org/gmane.comp.boot-loaders.u-boot

66

http://dir.gmane.org/gmane.comp.boot-loaders.u-boot

67

68

69

Where to get source code:

69

Where to get source code:

70

=========================

70

=========================

71

72

The U-Boot source code is maintained in the git repository at

72

The U-Boot source code is maintained in the git repository at

73

git://www.denx.de/git/u-boot.git ; you can browse it online at

73

git://www.denx.de/git/u-boot.git ; you can browse it online at

74

http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary

74

http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary

75

76

The "snapshot" links on this page allow you to download tarballs of

76

The "snapshot" links on this page allow you to download tarballs of

77

any version you might be interested in. Official releases are also

77

any version you might be interested in. Official releases are also

78

available for FTP download from the ftp://ftp.denx.de/pub/u-boot/

78

available for FTP download from the ftp://ftp.denx.de/pub/u-boot/

79

directory.

79

directory.

80

81

Pre-built (and tested) images are available from

81

Pre-built (and tested) images are available from

82

ftp://ftp.denx.de/pub/u-boot/images/

82

ftp://ftp.denx.de/pub/u-boot/images/

83

84

85

Where we come from:

85

Where we come from:

86

===================

86

===================

87

88

- start from 8xxrom sources

88

- start from 8xxrom sources

89

- create PPCBoot project (http://sourceforge.net/projects/ppcboot)

89

- create PPCBoot project (http://sourceforge.net/projects/ppcboot)

90

- clean up code

90

- clean up code

91

- make it easier to add custom boards

91

- make it easier to add custom boards

92

- make it possible to add other [PowerPC] CPUs

92

- make it possible to add other [PowerPC] CPUs

93

- extend functions, especially:

93

- extend functions, especially:

94

* Provide extended interface to Linux boot loader

94

* Provide extended interface to Linux boot loader

95

* S-Record download

95

* S-Record download

96

* network boot

96

* network boot

97

* PCMCIA / CompactFlash / ATA disk / SCSI ... boot

97

* PCMCIA / CompactFlash / ATA disk / SCSI ... boot

98

- create ARMBoot project (http://sourceforge.net/projects/armboot)

98

- create ARMBoot project (http://sourceforge.net/projects/armboot)

99

- add other CPU families (starting with ARM)

99

- add other CPU families (starting with ARM)

100

- create U-Boot project (http://sourceforge.net/projects/u-boot)

100

- create U-Boot project (http://sourceforge.net/projects/u-boot)

101

- current project page: see http://www.denx.de/wiki/U-Boot

101

- current project page: see http://www.denx.de/wiki/U-Boot

102

103

104

Names and Spelling:

104

Names and Spelling:

105

===================

105

===================

106

107

The "official" name of this project is "Das U-Boot". The spelling

107

The "official" name of this project is "Das U-Boot". The spelling

108

"U-Boot" shall be used in all written text (documentation, comments

108

"U-Boot" shall be used in all written text (documentation, comments

109

in source files etc.). Example:

109

in source files etc.). Example:

110

111

This is the README file for the U-Boot project.

111

This is the README file for the U-Boot project.

112

113

File names etc. shall be based on the string "u-boot". Examples:

113

File names etc. shall be based on the string "u-boot". Examples:

114

115

include/asm-ppc/u-boot.h

115

include/asm-ppc/u-boot.h

116

117

#include <asm/u-boot.h>

117

#include <asm/u-boot.h>

118

119

Variable names, preprocessor constants etc. shall be either based on

119

Variable names, preprocessor constants etc. shall be either based on

120

the string "u_boot" or on "U_BOOT". Example:

120

the string "u_boot" or on "U_BOOT". Example:

121

122

U_BOOT_VERSION u_boot_logo

122

U_BOOT_VERSION u_boot_logo

123

IH_OS_U_BOOT u_boot_hush_start

123

IH_OS_U_BOOT u_boot_hush_start

124

125

126

Versioning:

126

Versioning:

127

===========

127

===========

128

129

U-Boot uses a 3 level version number containing a version, a

129

U-Boot uses a 3 level version number containing a version, a

130

sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2",

130

sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2",

131

sub-version "34", and patchlevel "4".

131

sub-version "34", and patchlevel "4".

132

133

The patchlevel is used to indicate certain stages of development

133

The patchlevel is used to indicate certain stages of development

134

between released versions, i. e. officially released versions of

134

between released versions, i. e. officially released versions of

135

U-Boot will always have a patchlevel of "0".

135

U-Boot will always have a patchlevel of "0".

136

137

138

Directory Hierarchy:

138

Directory Hierarchy:

139

====================

139

====================

140

141

- board Board dependent files

141

- board Board dependent files

142

- common Misc architecture independent functions

142

- common Misc architecture independent functions

143

- cpu CPU specific files

143

- cpu CPU specific files

144

- 74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs

144

- 74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs

145

- arm720t Files specific to ARM 720 CPUs

145

- arm720t Files specific to ARM 720 CPUs

146

- arm920t Files specific to ARM 920 CPUs

146

- arm920t Files specific to ARM 920 CPUs

147

- at91rm9200 Files specific to Atmel AT91RM9200 CPU

147

- at91rm9200 Files specific to Atmel AT91RM9200 CPU

148

- imx Files specific to Freescale MC9328 i.MX CPUs

148

- imx Files specific to Freescale MC9328 i.MX CPUs

149

- s3c24x0 Files specific to Samsung S3C24X0 CPUs

149

- s3c24x0 Files specific to Samsung S3C24X0 CPUs

150

- arm925t Files specific to ARM 925 CPUs

150

- arm925t Files specific to ARM 925 CPUs

151

- arm926ejs Files specific to ARM 926 CPUs

151

- arm926ejs Files specific to ARM 926 CPUs

152

- arm1136 Files specific to ARM 1136 CPUs

152

- arm1136 Files specific to ARM 1136 CPUs

153

- at32ap Files specific to Atmel AVR32 AP CPUs

153

- at32ap Files specific to Atmel AVR32 AP CPUs

154

- blackfin Files specific to Analog Devices Blackfin CPUs

154

- blackfin Files specific to Analog Devices Blackfin CPUs

155

- i386 Files specific to i386 CPUs

155

- i386 Files specific to i386 CPUs

156

- ixp Files specific to Intel XScale IXP CPUs

156

- ixp Files specific to Intel XScale IXP CPUs

157

- leon2 Files specific to Gaisler LEON2 SPARC CPU

157

- leon2 Files specific to Gaisler LEON2 SPARC CPU

158

- leon3 Files specific to Gaisler LEON3 SPARC CPU

158

- leon3 Files specific to Gaisler LEON3 SPARC CPU

159

- mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs

159

- mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs

160

- mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs

160

- mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs

161

- mcf532x Files specific to Freescale ColdFire MCF5329 CPUs

161

- mcf532x Files specific to Freescale ColdFire MCF5329 CPUs

162

- mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs

162

- mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs

163

- mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs

163

- mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs

164

- mips Files specific to MIPS CPUs

164

- mips Files specific to MIPS CPUs

165

- mpc5xx Files specific to Freescale MPC5xx CPUs

165

- mpc5xx Files specific to Freescale MPC5xx CPUs

166

- mpc5xxx Files specific to Freescale MPC5xxx CPUs

166

- mpc5xxx Files specific to Freescale MPC5xxx CPUs

167

- mpc8xx Files specific to Freescale MPC8xx CPUs

167

- mpc8xx Files specific to Freescale MPC8xx CPUs

168

- mpc8220 Files specific to Freescale MPC8220 CPUs

168

- mpc8220 Files specific to Freescale MPC8220 CPUs

169

- mpc824x Files specific to Freescale MPC824x CPUs

169

- mpc824x Files specific to Freescale MPC824x CPUs

170

- mpc8260 Files specific to Freescale MPC8260 CPUs

170

- mpc8260 Files specific to Freescale MPC8260 CPUs

171

- mpc85xx Files specific to Freescale MPC85xx CPUs

171

- mpc85xx Files specific to Freescale MPC85xx CPUs

172

- nios Files specific to Altera NIOS CPUs

172

- nios Files specific to Altera NIOS CPUs

173

- nios2 Files specific to Altera Nios-II CPUs

173

- nios2 Files specific to Altera Nios-II CPUs

174

- ppc4xx Files specific to AMCC PowerPC 4xx CPUs

174

- ppc4xx Files specific to AMCC PowerPC 4xx CPUs

175

- pxa Files specific to Intel XScale PXA CPUs

175

- pxa Files specific to Intel XScale PXA CPUs

176

- s3c44b0 Files specific to Samsung S3C44B0 CPUs

176

- s3c44b0 Files specific to Samsung S3C44B0 CPUs

177

- sa1100 Files specific to Intel StrongARM SA1100 CPUs

177

- sa1100 Files specific to Intel StrongARM SA1100 CPUs

178

- disk Code for disk drive partition handling

178

- disk Code for disk drive partition handling

179

- doc Documentation (don't expect too much)

179

- doc Documentation (don't expect too much)

180

- drivers Commonly used device drivers

180

- drivers Commonly used device drivers

181

- dtt Digital Thermometer and Thermostat drivers

181

- dtt Digital Thermometer and Thermostat drivers

182

- examples Example code for standalone applications, etc.

182

- examples Example code for standalone applications, etc.

183

- include Header Files

183

- include Header Files

184

- lib_arm Files generic to ARM architecture

184

- lib_arm Files generic to ARM architecture

185

- lib_avr32 Files generic to AVR32 architecture

185

- lib_avr32 Files generic to AVR32 architecture

186

- lib_blackfin Files generic to Blackfin architecture

186

- lib_blackfin Files generic to Blackfin architecture

187

- lib_generic Files generic to all architectures

187

- lib_generic Files generic to all architectures

188

- lib_i386 Files generic to i386 architecture

188

- lib_i386 Files generic to i386 architecture

189

- lib_m68k Files generic to m68k architecture

189

- lib_m68k Files generic to m68k architecture

190

- lib_mips Files generic to MIPS architecture

190

- lib_mips Files generic to MIPS architecture

191

- lib_nios Files generic to NIOS architecture

191

- lib_nios Files generic to NIOS architecture

192

- lib_ppc Files generic to PowerPC architecture

192

- lib_ppc Files generic to PowerPC architecture

193

- lib_sparc Files generic to SPARC architecture

193

- lib_sparc Files generic to SPARC architecture

194

- libfdt Library files to support flattened device trees

194

- libfdt Library files to support flattened device trees

195

- net Networking code

195

- net Networking code

196

- post Power On Self Test

196

- post Power On Self Test

197

- rtc Real Time Clock drivers

197

- rtc Real Time Clock drivers

198

- tools Tools to build S-Record or U-Boot images, etc.

198

- tools Tools to build S-Record or U-Boot images, etc.

199

200

Software Configuration:

200

Software Configuration:

201

=======================

201

=======================

202

203

Configuration is usually done using C preprocessor defines; the

203

Configuration is usually done using C preprocessor defines; the

204

rationale behind that is to avoid dead code whenever possible.

204

rationale behind that is to avoid dead code whenever possible.

205

206

There are two classes of configuration variables:

206

There are two classes of configuration variables:

207

208

* Configuration _OPTIONS_:

208

* Configuration _OPTIONS_:

209

These are selectable by the user and have names beginning with

209

These are selectable by the user and have names beginning with

210

"CONFIG_".

210

"CONFIG_".

211

212

* Configuration _SETTINGS_:

212

* Configuration _SETTINGS_:

213

These depend on the hardware etc. and should not be meddled with if

213

These depend on the hardware etc. and should not be meddled with if

214

you don't know what you're doing; they have names beginning with

214

you don't know what you're doing; they have names beginning with

215

"CONFIG_SYS_".

215

"CONFIG_SYS_".

216

217

Later we will add a configuration tool - probably similar to or even

217

Later we will add a configuration tool - probably similar to or even

218

identical to what's used for the Linux kernel. Right now, we have to

218

identical to what's used for the Linux kernel. Right now, we have to

219

do the configuration by hand, which means creating some symbolic

219

do the configuration by hand, which means creating some symbolic

220

links and editing some configuration files. We use the TQM8xxL boards

220

links and editing some configuration files. We use the TQM8xxL boards

221

as an example here.

221

as an example here.

222

223

224

Selection of Processor Architecture and Board Type:

224

Selection of Processor Architecture and Board Type:

225

---------------------------------------------------

225

---------------------------------------------------

226

227

For all supported boards there are ready-to-use default

227

For all supported boards there are ready-to-use default

228

configurations available; just type "make <board_name>_config".

228

configurations available; just type "make <board_name>_config".

229

230

Example: For a TQM823L module type:

230

Example: For a TQM823L module type:

231

232

cd u-boot

232

cd u-boot

233

make TQM823L_config

233

make TQM823L_config

234

235

For the Cogent platform, you need to specify the CPU type as well;

235

For the Cogent platform, you need to specify the CPU type as well;

236

e.g. "make cogent_mpc8xx_config". And also configure the cogent

236

e.g. "make cogent_mpc8xx_config". And also configure the cogent

237

directory according to the instructions in cogent/README.

237

directory according to the instructions in cogent/README.

238

239

240

Configuration Options:

240

Configuration Options:

241

----------------------

241

----------------------

242

243

Configuration depends on the combination of board and CPU type; all

243

Configuration depends on the combination of board and CPU type; all

244

such information is kept in a configuration file

244

such information is kept in a configuration file

245

"include/configs/<board_name>.h".

245

"include/configs/<board_name>.h".

246

247

Example: For a TQM823L module, all configuration settings are in

247

Example: For a TQM823L module, all configuration settings are in

248

"include/configs/TQM823L.h".

248

"include/configs/TQM823L.h".

249

250

251

Many of the options are named exactly as the corresponding Linux

251

Many of the options are named exactly as the corresponding Linux

252

kernel configuration options. The intention is to make it easier to

252

kernel configuration options. The intention is to make it easier to

253

build a config tool - later.

253

build a config tool - later.

254

255

256

The following options need to be configured:

256

The following options need to be configured:

257

258

- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.

258

- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.

259

260

- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.

260

- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.

261

262

- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)

262

- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)

263

Define exactly one, e.g. CONFIG_ATSTK1002

263

Define exactly one, e.g. CONFIG_ATSTK1002

264

265

- CPU Module Type: (if CONFIG_COGENT is defined)

265

- CPU Module Type: (if CONFIG_COGENT is defined)

266

Define exactly one of

266

Define exactly one of

267

CONFIG_CMA286_60_OLD

267

CONFIG_CMA286_60_OLD

268

--- FIXME --- not tested yet:

268

--- FIXME --- not tested yet:

269

CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,

269

CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,

270

CONFIG_CMA287_23, CONFIG_CMA287_50

270

CONFIG_CMA287_23, CONFIG_CMA287_50

271

272

- Motherboard Type: (if CONFIG_COGENT is defined)

272

- Motherboard Type: (if CONFIG_COGENT is defined)

273

Define exactly one of

273

Define exactly one of

274

CONFIG_CMA101, CONFIG_CMA102

274

CONFIG_CMA101, CONFIG_CMA102

275

276

- Motherboard I/O Modules: (if CONFIG_COGENT is defined)

276

- Motherboard I/O Modules: (if CONFIG_COGENT is defined)

277

Define one or more of

277

Define one or more of

278

CONFIG_CMA302

278

CONFIG_CMA302

279

280

- Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)

280

- Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)

281

Define one or more of

281

Define one or more of

282

CONFIG_LCD_HEARTBEAT - update a character position on

282

CONFIG_LCD_HEARTBEAT - update a character position on

283

the LCD display every second with

283

the LCD display every second with

284

a "rotator" |\-/|\-/

284

a "rotator" |\-/|\-/

285

286

- Board flavour: (if CONFIG_MPC8260ADS is defined)

286

- Board flavour: (if CONFIG_MPC8260ADS is defined)

287

CONFIG_ADSTYPE

287

CONFIG_ADSTYPE

288

Possible values are:

288

Possible values are:

289

CONFIG_SYS_8260ADS - original MPC8260ADS

289

CONFIG_SYS_8260ADS - original MPC8260ADS

290

CONFIG_SYS_8266ADS - MPC8266ADS

290

CONFIG_SYS_8266ADS - MPC8266ADS

291

CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR

291

CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR

292

CONFIG_SYS_8272ADS - MPC8272ADS

292

CONFIG_SYS_8272ADS - MPC8272ADS

293

294

- MPC824X Family Member (if CONFIG_MPC824X is defined)

294

- MPC824X Family Member (if CONFIG_MPC824X is defined)

295

Define exactly one of

295

Define exactly one of

296

CONFIG_MPC8240, CONFIG_MPC8245

296

CONFIG_MPC8240, CONFIG_MPC8245

297

298

- 8xx CPU Options: (if using an MPC8xx CPU)

298

- 8xx CPU Options: (if using an MPC8xx CPU)

299

CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if

299

CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if

300

get_gclk_freq() cannot work

300

get_gclk_freq() cannot work

301

e.g. if there is no 32KHz

301

e.g. if there is no 32KHz

302

reference PIT/RTC clock

302

reference PIT/RTC clock

303

CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK

303

CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK

304

or XTAL/EXTAL)

304

or XTAL/EXTAL)

305

306

- 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):

306

- 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):

307

CONFIG_SYS_8xx_CPUCLK_MIN

307

CONFIG_SYS_8xx_CPUCLK_MIN

308

CONFIG_SYS_8xx_CPUCLK_MAX

308

CONFIG_SYS_8xx_CPUCLK_MAX

309

CONFIG_8xx_CPUCLK_DEFAULT

309

CONFIG_8xx_CPUCLK_DEFAULT

310

See doc/README.MPC866

310

See doc/README.MPC866

311

312

CONFIG_SYS_MEASURE_CPUCLK

312

CONFIG_SYS_MEASURE_CPUCLK

313

314

Define this to measure the actual CPU clock instead

314

Define this to measure the actual CPU clock instead

315

of relying on the correctness of the configured

315

of relying on the correctness of the configured

316

values. Mostly useful for board bringup to make sure

316

values. Mostly useful for board bringup to make sure

317

the PLL is locked at the intended frequency. Note

317

the PLL is locked at the intended frequency. Note

318

that this requires a (stable) reference clock (32 kHz

318

that this requires a (stable) reference clock (32 kHz

319

RTC clock or CONFIG_SYS_8XX_XIN)

319

RTC clock or CONFIG_SYS_8XX_XIN)

320

321

CONFIG_SYS_DELAYED_ICACHE

321

CONFIG_SYS_DELAYED_ICACHE

322

323

Define this option if you want to enable the

323

Define this option if you want to enable the

324

ICache only when Code runs from RAM.

324

ICache only when Code runs from RAM.

325

326

- Intel Monahans options:

326

- Intel Monahans options:

327

CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO

327

CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO

328

329

Defines the Monahans run mode to oscillator

329

Defines the Monahans run mode to oscillator

330

ratio. Valid values are 8, 16, 24, 31. The core

330

ratio. Valid values are 8, 16, 24, 31. The core

331

frequency is this value multiplied by 13 MHz.

331

frequency is this value multiplied by 13 MHz.

332

333

CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO

333

CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO

334

335

Defines the Monahans turbo mode to oscillator

335

Defines the Monahans turbo mode to oscillator

336

ratio. Valid values are 1 (default if undefined) and

336

ratio. Valid values are 1 (default if undefined) and

337

2. The core frequency as calculated above is multiplied

337

2. The core frequency as calculated above is multiplied

338

by this value.

338

by this value.

339

340

- Linux Kernel Interface:

340

- Linux Kernel Interface:

341

CONFIG_CLOCKS_IN_MHZ

341

CONFIG_CLOCKS_IN_MHZ

342

343

U-Boot stores all clock information in Hz

343

U-Boot stores all clock information in Hz

344

internally. For binary compatibility with older Linux

344

internally. For binary compatibility with older Linux

345

kernels (which expect the clocks passed in the

345

kernels (which expect the clocks passed in the

346

bd_info data to be in MHz) the environment variable

346

bd_info data to be in MHz) the environment variable

347

"clocks_in_mhz" can be defined so that U-Boot

347

"clocks_in_mhz" can be defined so that U-Boot

348

converts clock data to MHZ before passing it to the

348

converts clock data to MHZ before passing it to the

349

Linux kernel.

349

Linux kernel.

350

When CONFIG_CLOCKS_IN_MHZ is defined, a definition of

350

When CONFIG_CLOCKS_IN_MHZ is defined, a definition of

351

"clocks_in_mhz=1" is automatically included in the

351

"clocks_in_mhz=1" is automatically included in the

352

default environment.

352

default environment.

353

354

CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]

354

CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]

355

356

When transferring memsize parameter to linux, some versions

356

When transferring memsize parameter to linux, some versions

357

expect it to be in bytes, others in MB.

357

expect it to be in bytes, others in MB.

358

Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.

358

Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.

359

360

CONFIG_OF_LIBFDT

360

CONFIG_OF_LIBFDT

361

362

New kernel versions are expecting firmware settings to be

362

New kernel versions are expecting firmware settings to be

363

passed using flattened device trees (based on open firmware

363

passed using flattened device trees (based on open firmware

364

concepts).

364

concepts).

365

366

CONFIG_OF_LIBFDT

366

CONFIG_OF_LIBFDT

367

* New libfdt-based support

367

* New libfdt-based support

368

* Adds the "fdt" command

368

* Adds the "fdt" command

369

* The bootm command automatically updates the fdt

369

* The bootm command automatically updates the fdt

370

371

OF_CPU - The proper name of the cpus node.

371

OF_CPU - The proper name of the cpus node.

372

OF_SOC - The proper name of the soc node.

372

OF_SOC - The proper name of the soc node.

373

OF_TBCLK - The timebase frequency.

373

OF_TBCLK - The timebase frequency.

374

OF_STDOUT_PATH - The path to the console device

374

OF_STDOUT_PATH - The path to the console device

375

376

boards with QUICC Engines require OF_QE to set UCC MAC

376

boards with QUICC Engines require OF_QE to set UCC MAC

377

addresses

377

addresses

378

379

CONFIG_OF_BOARD_SETUP

379

CONFIG_OF_BOARD_SETUP

380

381

Board code has addition modification that it wants to make

381

Board code has addition modification that it wants to make

382

to the flat device tree before handing it off to the kernel

382

to the flat device tree before handing it off to the kernel

383

384

CONFIG_OF_BOOT_CPU

384

CONFIG_OF_BOOT_CPU

385

386

This define fills in the correct boot CPU in the boot

386

This define fills in the correct boot CPU in the boot

387

param header, the default value is zero if undefined.

387

param header, the default value is zero if undefined.

388

389

- vxWorks boot parameters:

389

- vxWorks boot parameters:

390

391

bootvx constructs a valid bootline using the following

391

bootvx constructs a valid bootline using the following

392

environments variables: bootfile, ipaddr, serverip, hostname.

392

environments variables: bootfile, ipaddr, serverip, hostname.

393

It loads the vxWorks image pointed bootfile.

393

It loads the vxWorks image pointed bootfile.

394

395

CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name

395

CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name

396

CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address

396

CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address

397

CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server

397

CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server

398

CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters

398

CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters

399

400

CONFIG_SYS_VXWORKS_ADD_PARAMS

400

CONFIG_SYS_VXWORKS_ADD_PARAMS

401

402

Add it at the end of the bootline. E.g "u=username pw=secret"

402

Add it at the end of the bootline. E.g "u=username pw=secret"

403

404

Note: If a "bootargs" environment is defined, it will overwride

404

Note: If a "bootargs" environment is defined, it will overwride

405

the defaults discussed just above.

405

the defaults discussed just above.

406

407

- Serial Ports:

407

- Serial Ports:

408

CONFIG_PL010_SERIAL

408

CONFIG_PL010_SERIAL

409

410

Define this if you want support for Amba PrimeCell PL010 UARTs.

410

Define this if you want support for Amba PrimeCell PL010 UARTs.

411

412

CONFIG_PL011_SERIAL

412

CONFIG_PL011_SERIAL

413

414

Define this if you want support for Amba PrimeCell PL011 UARTs.

414

Define this if you want support for Amba PrimeCell PL011 UARTs.

415

416

CONFIG_PL011_CLOCK

416

CONFIG_PL011_CLOCK

417

418

If you have Amba PrimeCell PL011 UARTs, set this variable to

418

If you have Amba PrimeCell PL011 UARTs, set this variable to

419

the clock speed of the UARTs.

419

the clock speed of the UARTs.

420

421

CONFIG_PL01x_PORTS

421

CONFIG_PL01x_PORTS

422

423

If you have Amba PrimeCell PL010 or PL011 UARTs on your board,

423

If you have Amba PrimeCell PL010 or PL011 UARTs on your board,

424

define this to a list of base addresses for each (supported)

424

define this to a list of base addresses for each (supported)

425

port. See e.g. include/configs/versatile.h

425

port. See e.g. include/configs/versatile.h

426

427

428

- Console Interface:

428

- Console Interface:

429

Depending on board, define exactly one serial port

429

Depending on board, define exactly one serial port

430

(like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,

430

(like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,

431

CONFIG_8xx_CONS_SCC1, ...), or switch off the serial

431

CONFIG_8xx_CONS_SCC1, ...), or switch off the serial

432

console by defining CONFIG_8xx_CONS_NONE

432

console by defining CONFIG_8xx_CONS_NONE

433

434

Note: if CONFIG_8xx_CONS_NONE is defined, the serial

434

Note: if CONFIG_8xx_CONS_NONE is defined, the serial

435

port routines must be defined elsewhere

435

port routines must be defined elsewhere

436

(i.e. serial_init(), serial_getc(), ...)

436

(i.e. serial_init(), serial_getc(), ...)

437

438

CONFIG_CFB_CONSOLE

438

CONFIG_CFB_CONSOLE

439

Enables console device for a color framebuffer. Needs following

439

Enables console device for a color framebuffer. Needs following

440

defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)

440

defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)

441

VIDEO_FB_LITTLE_ENDIAN graphic memory organisation

441

VIDEO_FB_LITTLE_ENDIAN graphic memory organisation

442

(default big endian)

442

(default big endian)

443

VIDEO_HW_RECTFILL graphic chip supports

443

VIDEO_HW_RECTFILL graphic chip supports

444

rectangle fill

444

rectangle fill

445

(cf. smiLynxEM)

445

(cf. smiLynxEM)

446

VIDEO_HW_BITBLT graphic chip supports

446

VIDEO_HW_BITBLT graphic chip supports

447

bit-blit (cf. smiLynxEM)

447

bit-blit (cf. smiLynxEM)

448

VIDEO_VISIBLE_COLS visible pixel columns

448

VIDEO_VISIBLE_COLS visible pixel columns

449

(cols=pitch)

449

(cols=pitch)

450

VIDEO_VISIBLE_ROWS visible pixel rows

450

VIDEO_VISIBLE_ROWS visible pixel rows

451

VIDEO_PIXEL_SIZE bytes per pixel

451

VIDEO_PIXEL_SIZE bytes per pixel

452

VIDEO_DATA_FORMAT graphic data format

452

VIDEO_DATA_FORMAT graphic data format

453

(0-5, cf. cfb_console.c)

453

(0-5, cf. cfb_console.c)

454

VIDEO_FB_ADRS framebuffer address

454

VIDEO_FB_ADRS framebuffer address

455

VIDEO_KBD_INIT_FCT keyboard int fct

455

VIDEO_KBD_INIT_FCT keyboard int fct

456

(i.e. i8042_kbd_init())

456

(i.e. i8042_kbd_init())

457

VIDEO_TSTC_FCT test char fct

457

VIDEO_TSTC_FCT test char fct

458

(i.e. i8042_tstc)

458

(i.e. i8042_tstc)

459

VIDEO_GETC_FCT get char fct

459

VIDEO_GETC_FCT get char fct

460

(i.e. i8042_getc)

460

(i.e. i8042_getc)

461

CONFIG_CONSOLE_CURSOR cursor drawing on/off

461

CONFIG_CONSOLE_CURSOR cursor drawing on/off

462

(requires blink timer

462

(requires blink timer

463

cf. i8042.c)

463

cf. i8042.c)

464

CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)

464

CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)

465

CONFIG_CONSOLE_TIME display time/date info in

465

CONFIG_CONSOLE_TIME display time/date info in

466

upper right corner

466

upper right corner

467

(requires CONFIG_CMD_DATE)

467

(requires CONFIG_CMD_DATE)

468

CONFIG_VIDEO_LOGO display Linux logo in

468

CONFIG_VIDEO_LOGO display Linux logo in

469

upper left corner

469

upper left corner

470

CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of

470

CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of

471

linux_logo.h for logo.

471

linux_logo.h for logo.

472

Requires CONFIG_VIDEO_LOGO

472

Requires CONFIG_VIDEO_LOGO

473

CONFIG_CONSOLE_EXTRA_INFO

473

CONFIG_CONSOLE_EXTRA_INFO

474

additional board info beside

474

additional board info beside

475

the logo

475

the logo

476

477

When CONFIG_CFB_CONSOLE is defined, video console is

477

When CONFIG_CFB_CONSOLE is defined, video console is

478

default i/o. Serial console can be forced with

478

default i/o. Serial console can be forced with

479

environment 'console=serial'.

479

environment 'console=serial'.

480

481

When CONFIG_SILENT_CONSOLE is defined, all console

481

When CONFIG_SILENT_CONSOLE is defined, all console

482

messages (by U-Boot and Linux!) can be silenced with

482

messages (by U-Boot and Linux!) can be silenced with

483

the "silent" environment variable. See

483

the "silent" environment variable. See

484

doc/README.silent for more information.

484

doc/README.silent for more information.

485

486

- Console Baudrate:

486

- Console Baudrate:

487

CONFIG_BAUDRATE - in bps

487

CONFIG_BAUDRATE - in bps

488

Select one of the baudrates listed in

488

Select one of the baudrates listed in

489

CONFIG_SYS_BAUDRATE_TABLE, see below.

489

CONFIG_SYS_BAUDRATE_TABLE, see below.

490

CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale

490

CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale

491

492

- Console Rx buffer length

492

- Console Rx buffer length

493

With CONFIG_SYS_SMC_RXBUFLEN it is possible to define

493

With CONFIG_SYS_SMC_RXBUFLEN it is possible to define

494

the maximum receive buffer length for the SMC.

494

the maximum receive buffer length for the SMC.

495

This option is actual only for 82xx and 8xx possible.

495

This option is actual only for 82xx and 8xx possible.

496

If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE

496

If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE

497

must be defined, to setup the maximum idle timeout for

497

must be defined, to setup the maximum idle timeout for

498

the SMC.

498

the SMC.

499

500

- Interrupt driven serial port input:

500

- Interrupt driven serial port input:

501

CONFIG_SERIAL_SOFTWARE_FIFO

501

CONFIG_SERIAL_SOFTWARE_FIFO

502

503

PPC405GP only.

503

PPC405GP only.

504

Use an interrupt handler for receiving data on the

504

Use an interrupt handler for receiving data on the

505

serial port. It also enables using hardware handshake

505

serial port. It also enables using hardware handshake

506

(RTS/CTS) and UART's built-in FIFO. Set the number of

506

(RTS/CTS) and UART's built-in FIFO. Set the number of

507

bytes the interrupt driven input buffer should have.

507

bytes the interrupt driven input buffer should have.

508

509

Leave undefined to disable this feature, including

509

Leave undefined to disable this feature, including

510

disable the buffer and hardware handshake.

510

disable the buffer and hardware handshake.

511

512

- Console UART Number:

512

- Console UART Number:

513

CONFIG_UART1_CONSOLE

513

CONFIG_UART1_CONSOLE

514

515

AMCC PPC4xx only.

515

AMCC PPC4xx only.

516

If defined internal UART1 (and not UART0) is used

516

If defined internal UART1 (and not UART0) is used

517

as default U-Boot console.

517

as default U-Boot console.

518

519

- Boot Delay: CONFIG_BOOTDELAY - in seconds

519

- Boot Delay: CONFIG_BOOTDELAY - in seconds

520

Delay before automatically booting the default image;

520

Delay before automatically booting the default image;

521

set to -1 to disable autoboot.

521

set to -1 to disable autoboot.

522

523

See doc/README.autoboot for these options that

523

See doc/README.autoboot for these options that

524

work with CONFIG_BOOTDELAY. None are required.

524

work with CONFIG_BOOTDELAY. None are required.

525

CONFIG_BOOT_RETRY_TIME

525

CONFIG_BOOT_RETRY_TIME

526

CONFIG_BOOT_RETRY_MIN

526

CONFIG_BOOT_RETRY_MIN

527

CONFIG_AUTOBOOT_KEYED

527

CONFIG_AUTOBOOT_KEYED

528

CONFIG_AUTOBOOT_PROMPT

528

CONFIG_AUTOBOOT_PROMPT

529

CONFIG_AUTOBOOT_DELAY_STR

529

CONFIG_AUTOBOOT_DELAY_STR

530

CONFIG_AUTOBOOT_STOP_STR

530

CONFIG_AUTOBOOT_STOP_STR

531

CONFIG_AUTOBOOT_DELAY_STR2

531

CONFIG_AUTOBOOT_DELAY_STR2

532

CONFIG_AUTOBOOT_STOP_STR2

532

CONFIG_AUTOBOOT_STOP_STR2

533

CONFIG_ZERO_BOOTDELAY_CHECK

533

CONFIG_ZERO_BOOTDELAY_CHECK

534

CONFIG_RESET_TO_RETRY

534

CONFIG_RESET_TO_RETRY

535

536

- Autoboot Command:

536

- Autoboot Command:

537

CONFIG_BOOTCOMMAND

537

CONFIG_BOOTCOMMAND

538

Only needed when CONFIG_BOOTDELAY is enabled;

538

Only needed when CONFIG_BOOTDELAY is enabled;

539

define a command string that is automatically executed

539

define a command string that is automatically executed

540

when no character is read on the console interface

540

when no character is read on the console interface

541

within "Boot Delay" after reset.

541

within "Boot Delay" after reset.

542

543

CONFIG_BOOTARGS

543

CONFIG_BOOTARGS

544

This can be used to pass arguments to the bootm

544

This can be used to pass arguments to the bootm

545

command. The value of CONFIG_BOOTARGS goes into the

545

command. The value of CONFIG_BOOTARGS goes into the

546

environment value "bootargs".

546

environment value "bootargs".

547

548

CONFIG_RAMBOOT and CONFIG_NFSBOOT

548

CONFIG_RAMBOOT and CONFIG_NFSBOOT

549

The value of these goes into the environment as

549

The value of these goes into the environment as

550

"ramboot" and "nfsboot" respectively, and can be used

550

"ramboot" and "nfsboot" respectively, and can be used

551

as a convenience, when switching between booting from

551

as a convenience, when switching between booting from

552

RAM and NFS.

552

RAM and NFS.

553

554

- Pre-Boot Commands:

554

- Pre-Boot Commands:

555

CONFIG_PREBOOT

555

CONFIG_PREBOOT

556

557

When this option is #defined, the existence of the

557

When this option is #defined, the existence of the

558

environment variable "preboot" will be checked

558

environment variable "preboot" will be checked

559

immediately before starting the CONFIG_BOOTDELAY

559

immediately before starting the CONFIG_BOOTDELAY

560

countdown and/or running the auto-boot command resp.

560

countdown and/or running the auto-boot command resp.

561

entering interactive mode.

561

entering interactive mode.

562

563

This feature is especially useful when "preboot" is

563

This feature is especially useful when "preboot" is

564

automatically generated or modified. For an example

564

automatically generated or modified. For an example

565

see the LWMON board specific code: here "preboot" is

565

see the LWMON board specific code: here "preboot" is

566

modified when the user holds down a certain

566

modified when the user holds down a certain

567

combination of keys on the (special) keyboard when

567

combination of keys on the (special) keyboard when

568

booting the systems

568

booting the systems

569

570

- Serial Download Echo Mode:

570

- Serial Download Echo Mode:

571

CONFIG_LOADS_ECHO

571

CONFIG_LOADS_ECHO

572

If defined to 1, all characters received during a

572

If defined to 1, all characters received during a

573

serial download (using the "loads" command) are

573

serial download (using the "loads" command) are

574

echoed back. This might be needed by some terminal

574

echoed back. This might be needed by some terminal

575

emulations (like "cu"), but may as well just take

575

emulations (like "cu"), but may as well just take

576

time on others. This setting #define's the initial

576

time on others. This setting #define's the initial

577

value of the "loads_echo" environment variable.

577

value of the "loads_echo" environment variable.

578

579

- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)

579

- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)

580

CONFIG_KGDB_BAUDRATE

580

CONFIG_KGDB_BAUDRATE

581

Select one of the baudrates listed in

581

Select one of the baudrates listed in

582

CONFIG_SYS_BAUDRATE_TABLE, see below.

582

CONFIG_SYS_BAUDRATE_TABLE, see below.

583

584

- Monitor Functions:

584

- Monitor Functions:

585

Monitor commands can be included or excluded

585

Monitor commands can be included or excluded

586

from the build by using the #include files

586

from the build by using the #include files

587

"config_cmd_all.h" and #undef'ing unwanted

587

"config_cmd_all.h" and #undef'ing unwanted

588

commands, or using "config_cmd_default.h"

588

commands, or using "config_cmd_default.h"

589

and augmenting with additional #define's

589

and augmenting with additional #define's

590

for wanted commands.

590

for wanted commands.

591

592

The default command configuration includes all commands

592

The default command configuration includes all commands

593

except those marked below with a "*".

593

except those marked below with a "*".

594

595

CONFIG_CMD_ASKENV * ask for env variable

595

CONFIG_CMD_ASKENV * ask for env variable

596

CONFIG_CMD_BDI bdinfo

596

CONFIG_CMD_BDI bdinfo

597

CONFIG_CMD_BEDBUG * Include BedBug Debugger

597

CONFIG_CMD_BEDBUG * Include BedBug Debugger

598

CONFIG_CMD_BMP * BMP support

598

CONFIG_CMD_BMP * BMP support

599

CONFIG_CMD_BSP * Board specific commands

599

CONFIG_CMD_BSP * Board specific commands

600

CONFIG_CMD_BOOTD bootd

600

CONFIG_CMD_BOOTD bootd

601

CONFIG_CMD_CACHE * icache, dcache

601

CONFIG_CMD_CACHE * icache, dcache

602

CONFIG_CMD_CONSOLE coninfo

602

CONFIG_CMD_CONSOLE coninfo

603

CONFIG_CMD_DATE * support for RTC, date/time...

603

CONFIG_CMD_DATE * support for RTC, date/time...

604

CONFIG_CMD_DHCP * DHCP support

604

CONFIG_CMD_DHCP * DHCP support

605

CONFIG_CMD_DIAG * Diagnostics

605

CONFIG_CMD_DIAG * Diagnostics

606

CONFIG_CMD_DS4510 * ds4510 I2C gpio commands

606

CONFIG_CMD_DS4510 * ds4510 I2C gpio commands

607

CONFIG_CMD_DS4510_INFO * ds4510 I2C info command

607

CONFIG_CMD_DS4510_INFO * ds4510 I2C info command

608

CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd

608

CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd

609

CONFIG_CMD_DS4510_RST * ds4510 I2C rst command

609

CONFIG_CMD_DS4510_RST * ds4510 I2C rst command

610

CONFIG_CMD_DTT * Digital Therm and Thermostat

610

CONFIG_CMD_DTT * Digital Therm and Thermostat

611

CONFIG_CMD_ECHO echo arguments

611

CONFIG_CMD_ECHO echo arguments

612

CONFIG_CMD_EEPROM * EEPROM read/write support

612

CONFIG_CMD_EEPROM * EEPROM read/write support

613

CONFIG_CMD_ELF * bootelf, bootvx

613

CONFIG_CMD_ELF * bootelf, bootvx

614

CONFIG_CMD_SAVEENV saveenv

614

CONFIG_CMD_SAVEENV saveenv

615

CONFIG_CMD_FDC * Floppy Disk Support

615

CONFIG_CMD_FDC * Floppy Disk Support

616

CONFIG_CMD_FAT * FAT partition support

616

CONFIG_CMD_FAT * FAT partition support

617

CONFIG_CMD_FDOS * Dos diskette Support

617

CONFIG_CMD_FDOS * Dos diskette Support

618

CONFIG_CMD_FLASH flinfo, erase, protect

618

CONFIG_CMD_FLASH flinfo, erase, protect

619

CONFIG_CMD_FPGA FPGA device initialization support

619

CONFIG_CMD_FPGA FPGA device initialization support

620

CONFIG_CMD_HWFLOW * RTS/CTS hw flow control

620

CONFIG_CMD_HWFLOW * RTS/CTS hw flow control

621

CONFIG_CMD_I2C * I2C serial bus support

621

CONFIG_CMD_I2C * I2C serial bus support

622

CONFIG_CMD_IDE * IDE harddisk support

622

CONFIG_CMD_IDE * IDE harddisk support

623

CONFIG_CMD_IMI iminfo

623

CONFIG_CMD_IMI iminfo

624

CONFIG_CMD_IMLS List all found images

624

CONFIG_CMD_IMLS List all found images

625

CONFIG_CMD_IMMAP * IMMR dump support

625

CONFIG_CMD_IMMAP * IMMR dump support

626

CONFIG_CMD_IRQ * irqinfo

626

CONFIG_CMD_IRQ * irqinfo

627

CONFIG_CMD_ITEST Integer/string test of 2 values

627

CONFIG_CMD_ITEST Integer/string test of 2 values

628

CONFIG_CMD_JFFS2 * JFFS2 Support

628

CONFIG_CMD_JFFS2 * JFFS2 Support

629

CONFIG_CMD_KGDB * kgdb

629

CONFIG_CMD_KGDB * kgdb

630

CONFIG_CMD_LOADB loadb

630

CONFIG_CMD_LOADB loadb

631

CONFIG_CMD_LOADS loads

631

CONFIG_CMD_LOADS loads

632

CONFIG_CMD_MD5SUM print md5 message digest

632

CONFIG_CMD_MD5SUM print md5 message digest

633

(requires CONFIG_CMD_MEMORY and CONFIG_MD5)

633

(requires CONFIG_CMD_MEMORY and CONFIG_MD5)

634

CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,

634

CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,

635

loop, loopw, mtest

635

loop, loopw, mtest

636

CONFIG_CMD_MISC Misc functions like sleep etc

636

CONFIG_CMD_MISC Misc functions like sleep etc

637

CONFIG_CMD_MMC * MMC memory mapped support

637

CONFIG_CMD_MMC * MMC memory mapped support

638

CONFIG_CMD_MII * MII utility commands

638

CONFIG_CMD_MII * MII utility commands

639

CONFIG_CMD_MTDPARTS * MTD partition support

639

CONFIG_CMD_MTDPARTS * MTD partition support

640

CONFIG_CMD_NAND * NAND support

640

CONFIG_CMD_NAND * NAND support

641

CONFIG_CMD_NET bootp, tftpboot, rarpboot

641

CONFIG_CMD_NET bootp, tftpboot, rarpboot

642

CONFIG_CMD_PCA953X * PCA953x I2C gpio commands

642

CONFIG_CMD_PCA953X * PCA953x I2C gpio commands

643

CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command

643

CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command

644

CONFIG_CMD_PCI * pciinfo

644

CONFIG_CMD_PCI * pciinfo

645

CONFIG_CMD_PCMCIA * PCMCIA support

645

CONFIG_CMD_PCMCIA * PCMCIA support

646

CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network

646

CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network

647

host

647

host

648

CONFIG_CMD_PORTIO * Port I/O

648

CONFIG_CMD_PORTIO * Port I/O

649

CONFIG_CMD_REGINFO * Register dump

649

CONFIG_CMD_REGINFO * Register dump

650

CONFIG_CMD_RUN run command in env variable

650

CONFIG_CMD_RUN run command in env variable

651

CONFIG_CMD_SAVES * save S record dump

651

CONFIG_CMD_SAVES * save S record dump

652

CONFIG_CMD_SCSI * SCSI Support

652

CONFIG_CMD_SCSI * SCSI Support

653

CONFIG_CMD_SDRAM * print SDRAM configuration information

653

CONFIG_CMD_SDRAM * print SDRAM configuration information

654

(requires CONFIG_CMD_I2C)

654

(requires CONFIG_CMD_I2C)

655

CONFIG_CMD_SETGETDCR Support for DCR Register access

655

CONFIG_CMD_SETGETDCR Support for DCR Register access

656

(4xx only)

656

(4xx only)

657

CONFIG_CMD_SHA1 print sha1 memory digest

657

CONFIG_CMD_SHA1 print sha1 memory digest

658

(requires CONFIG_CMD_MEMORY)

658

(requires CONFIG_CMD_MEMORY)

659

CONFIG_CMD_SOURCE "source" command Support

659

CONFIG_CMD_SOURCE "source" command Support

660

CONFIG_CMD_SPI * SPI serial bus support

660

CONFIG_CMD_SPI * SPI serial bus support

661

CONFIG_CMD_USB * USB support

661

CONFIG_CMD_USB * USB support

662

CONFIG_CMD_VFD * VFD support (TRAB)

662

CONFIG_CMD_VFD * VFD support (TRAB)

663

CONFIG_CMD_CDP * Cisco Discover Protocol support

663

CONFIG_CMD_CDP * Cisco Discover Protocol support

664

CONFIG_CMD_FSL * Microblaze FSL support

664

CONFIG_CMD_FSL * Microblaze FSL support

665

666

667

EXAMPLE: If you want all functions except of network

667

EXAMPLE: If you want all functions except of network

668

support you can write:

668

support you can write:

669

670

#include "config_cmd_all.h"

670

#include "config_cmd_all.h"

671

#undef CONFIG_CMD_NET

671

#undef CONFIG_CMD_NET

672

673

Other Commands:

673

Other Commands:

674

fdt (flattened device tree) command: CONFIG_OF_LIBFDT

674

fdt (flattened device tree) command: CONFIG_OF_LIBFDT

675

676

Note: Don't enable the "icache" and "dcache" commands

676

Note: Don't enable the "icache" and "dcache" commands

677

(configuration option CONFIG_CMD_CACHE) unless you know

677

(configuration option CONFIG_CMD_CACHE) unless you know

678

what you (and your U-Boot users) are doing. Data

678

what you (and your U-Boot users) are doing. Data

679

cache cannot be enabled on systems like the 8xx or

679

cache cannot be enabled on systems like the 8xx or

680

8260 (where accesses to the IMMR region must be

680

8260 (where accesses to the IMMR region must be

681

uncached), and it cannot be disabled on all other

681

uncached), and it cannot be disabled on all other

682

systems where we (mis-) use the data cache to hold an

682

systems where we (mis-) use the data cache to hold an

683

initial stack and some data.

683

initial stack and some data.

684

685

686

XXX - this list needs to get updated!

686

XXX - this list needs to get updated!

687

688

- Watchdog:

688

- Watchdog:

689

CONFIG_WATCHDOG

689

CONFIG_WATCHDOG

690

If this variable is defined, it enables watchdog

690

If this variable is defined, it enables watchdog

691

support. There must be support in the platform specific

691

support. There must be support in the platform specific

692

code for a watchdog. For the 8xx and 8260 CPUs, the

692

code for a watchdog. For the 8xx and 8260 CPUs, the

693

SIU Watchdog feature is enabled in the SYPCR

693

SIU Watchdog feature is enabled in the SYPCR

694

register.

694

register.

695

696

- U-Boot Version:

696

- U-Boot Version:

697

CONFIG_VERSION_VARIABLE

697

CONFIG_VERSION_VARIABLE

698

If this variable is defined, an environment variable

698

If this variable is defined, an environment variable

699

named "ver" is created by U-Boot showing the U-Boot

699

named "ver" is created by U-Boot showing the U-Boot

700

version as printed by the "version" command.

700

version as printed by the "version" command.

701

This variable is readonly.

701

This variable is readonly.

702

703

- Real-Time Clock:

703

- Real-Time Clock:

704

705

When CONFIG_CMD_DATE is selected, the type of the RTC

705

When CONFIG_CMD_DATE is selected, the type of the RTC

706

has to be selected, too. Define exactly one of the

706

has to be selected, too. Define exactly one of the

707

following options:

707

following options:

708

709

CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx

709

CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx

710

CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC

710

CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC

711

CONFIG_RTC_MC13783 - use MC13783 RTC

711

CONFIG_RTC_MC13783 - use MC13783 RTC

712

CONFIG_RTC_MC146818 - use MC146818 RTC

712

CONFIG_RTC_MC146818 - use MC146818 RTC

713

CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC

713

CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC

714

CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC

714

CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC

715

CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC

715

CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC

716

CONFIG_RTC_DS164x - use Dallas DS164x RTC

716

CONFIG_RTC_DS164x - use Dallas DS164x RTC

717

CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC

717

CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC

718

CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC

718

CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC

719

CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337

719

CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337

720

721

Note that if the RTC uses I2C, then the I2C interface

721

Note that if the RTC uses I2C, then the I2C interface

722

must also be configured. See I2C Support, below.

722

must also be configured. See I2C Support, below.

723

724

- GPIO Support:

724

- GPIO Support:

725

CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO

725

CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO

726

CONFIG_PCA953X_INFO - enable pca953x info command

726

CONFIG_PCA953X_INFO - enable pca953x info command

727

728

Note that if the GPIO device uses I2C, then the I2C interface

728

Note that if the GPIO device uses I2C, then the I2C interface

729

must also be configured. See I2C Support, below.

729

must also be configured. See I2C Support, below.

730

731

- Timestamp Support:

731

- Timestamp Support:

732

733

When CONFIG_TIMESTAMP is selected, the timestamp

733

When CONFIG_TIMESTAMP is selected, the timestamp

734

(date and time) of an image is printed by image

734

(date and time) of an image is printed by image

735

commands like bootm or iminfo. This option is

735

commands like bootm or iminfo. This option is

736

automatically enabled when you select CONFIG_CMD_DATE .

736

automatically enabled when you select CONFIG_CMD_DATE .

737

738

- Partition Support:

738

- Partition Support:

739

CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION

739

CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION

740

and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_PARTITION

740

and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_PARTITION

741

742

If IDE or SCSI support is enabled (CONFIG_CMD_IDE or

742

If IDE or SCSI support is enabled (CONFIG_CMD_IDE or

743

CONFIG_CMD_SCSI) you must configure support for at

743

CONFIG_CMD_SCSI) you must configure support for at

744

least one partition type as well.

744

least one partition type as well.

745

746

- IDE Reset method:

746

- IDE Reset method:

747

CONFIG_IDE_RESET_ROUTINE - this is defined in several

747

CONFIG_IDE_RESET_ROUTINE - this is defined in several

748

board configurations files but used nowhere!

748

board configurations files but used nowhere!

749

750

CONFIG_IDE_RESET - is this is defined, IDE Reset will

750

CONFIG_IDE_RESET - is this is defined, IDE Reset will

751

be performed by calling the function

751

be performed by calling the function

752

ide_set_reset(int reset)

752

ide_set_reset(int reset)

753

which has to be defined in a board specific file

753

which has to be defined in a board specific file

754

755

- ATAPI Support:

755

- ATAPI Support:

756

CONFIG_ATAPI

756

CONFIG_ATAPI

757

758

Set this to enable ATAPI support.

758

Set this to enable ATAPI support.

759

760

- LBA48 Support

760

- LBA48 Support

761

CONFIG_LBA48

761

CONFIG_LBA48

762

763

Set this to enable support for disks larger than 137GB

763

Set this to enable support for disks larger than 137GB

764

Also look at CONFIG_SYS_64BIT_LBA ,CONFIG_SYS_64BIT_VSPRINTF and CONFIG_SYS_64BIT_STRTOUL

764

Also look at CONFIG_SYS_64BIT_LBA ,CONFIG_SYS_64BIT_VSPRINTF and CONFIG_SYS_64BIT_STRTOUL

765

Whithout these , LBA48 support uses 32bit variables and will 'only'

765

Whithout these , LBA48 support uses 32bit variables and will 'only'

766

support disks up to 2.1TB.

766

support disks up to 2.1TB.

767

768

CONFIG_SYS_64BIT_LBA:

768

CONFIG_SYS_64BIT_LBA:

769

When enabled, makes the IDE subsystem use 64bit sector addresses.

769

When enabled, makes the IDE subsystem use 64bit sector addresses.

770

Default is 32bit.

770

Default is 32bit.

771

772

- SCSI Support:

772

- SCSI Support:

773

At the moment only there is only support for the

773

At the moment only there is only support for the

774

SYM53C8XX SCSI controller; define

774

SYM53C8XX SCSI controller; define

775

CONFIG_SCSI_SYM53C8XX to enable it.

775

CONFIG_SCSI_SYM53C8XX to enable it.

776

777

CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and

777

CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and

778

CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *

778

CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *

779

CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the

779

CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the

780

maximum numbers of LUNs, SCSI ID's and target

780

maximum numbers of LUNs, SCSI ID's and target

781

devices.

781

devices.

782

CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)

782

CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)

783

784

- NETWORK Support (PCI):

784

- NETWORK Support (PCI):

785

CONFIG_E1000

785

CONFIG_E1000

786

Support for Intel 8254x gigabit chips.

786

Support for Intel 8254x gigabit chips.

787

788

CONFIG_E1000_FALLBACK_MAC

788

CONFIG_E1000_FALLBACK_MAC

789

default MAC for empty EEPROM after production.

789

default MAC for empty EEPROM after production.

790

791

CONFIG_EEPRO100

791

CONFIG_EEPRO100

792

Support for Intel 82557/82559/82559ER chips.

792

Support for Intel 82557/82559/82559ER chips.

793

Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM

793

Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM

794

write routine for first time initialisation.

794

write routine for first time initialisation.

795

796

CONFIG_TULIP

796

CONFIG_TULIP

797

Support for Digital 2114x chips.

797

Support for Digital 2114x chips.

798

Optional CONFIG_TULIP_SELECT_MEDIA for board specific

798

Optional CONFIG_TULIP_SELECT_MEDIA for board specific

799

modem chip initialisation (KS8761/QS6611).

799

modem chip initialisation (KS8761/QS6611).

800

801

CONFIG_NATSEMI

801

CONFIG_NATSEMI

802

Support for National dp83815 chips.

802

Support for National dp83815 chips.

803

804

CONFIG_NS8382X

804

CONFIG_NS8382X

805

Support for National dp8382[01] gigabit chips.

805

Support for National dp8382[01] gigabit chips.

806

807

- NETWORK Support (other):

807

- NETWORK Support (other):

808

809

CONFIG_DRIVER_LAN91C96

809

CONFIG_DRIVER_LAN91C96

810

Support for SMSC's LAN91C96 chips.

810

Support for SMSC's LAN91C96 chips.

811

812

CONFIG_LAN91C96_BASE

812

CONFIG_LAN91C96_BASE

813

Define this to hold the physical address

813

Define this to hold the physical address

814

of the LAN91C96's I/O space

814

of the LAN91C96's I/O space

815

816

CONFIG_LAN91C96_USE_32_BIT

816

CONFIG_LAN91C96_USE_32_BIT

817

Define this to enable 32 bit addressing

817

Define this to enable 32 bit addressing

818

819

CONFIG_DRIVER_SMC91111

819

CONFIG_DRIVER_SMC91111

820

Support for SMSC's LAN91C111 chip

820

Support for SMSC's LAN91C111 chip

821

822

CONFIG_SMC91111_BASE

822

CONFIG_SMC91111_BASE

823

Define this to hold the physical address

823

Define this to hold the physical address

824

of the device (I/O space)

824

of the device (I/O space)

825

826

CONFIG_SMC_USE_32_BIT

826

CONFIG_SMC_USE_32_BIT

827

Define this if data bus is 32 bits

827

Define this if data bus is 32 bits

828

829

CONFIG_SMC_USE_IOFUNCS

829

CONFIG_SMC_USE_IOFUNCS

830

Define this to use i/o functions instead of macros

830

Define this to use i/o functions instead of macros

831

(some hardware wont work with macros)

831

(some hardware wont work with macros)

832

833

CONFIG_DRIVER_SMC911X

833

CONFIG_DRIVER_SMC911X

834

Support for SMSC's LAN911x and LAN921x chips

834

Support for SMSC's LAN911x and LAN921x chips

835

836

CONFIG_DRIVER_SMC911X_BASE

836

CONFIG_DRIVER_SMC911X_BASE

837

Define this to hold the physical address

837

Define this to hold the physical address

838

of the device (I/O space)

838

of the device (I/O space)

839

840

CONFIG_DRIVER_SMC911X_32_BIT

840

CONFIG_DRIVER_SMC911X_32_BIT

841

Define this if data bus is 32 bits

841

Define this if data bus is 32 bits

842

843

CONFIG_DRIVER_SMC911X_16_BIT

843

CONFIG_DRIVER_SMC911X_16_BIT

844

Define this if data bus is 16 bits. If your processor

844

Define this if data bus is 16 bits. If your processor

845

automatically converts one 32 bit word to two 16 bit

845

automatically converts one 32 bit word to two 16 bit

846

words you may also try CONFIG_DRIVER_SMC911X_32_BIT.

846

words you may also try CONFIG_DRIVER_SMC911X_32_BIT.

847

848

- USB Support:

848

- USB Support:

849

At the moment only the UHCI host controller is

849

At the moment only the UHCI host controller is

850

supported (PIP405, MIP405, MPC5200); define

850

supported (PIP405, MIP405, MPC5200); define

851

CONFIG_USB_UHCI to enable it.

851

CONFIG_USB_UHCI to enable it.

852

define CONFIG_USB_KEYBOARD to enable the USB Keyboard

852

define CONFIG_USB_KEYBOARD to enable the USB Keyboard

853

and define CONFIG_USB_STORAGE to enable the USB

853

and define CONFIG_USB_STORAGE to enable the USB

854

storage devices.

854

storage devices.

855

Note:

855

Note:

856

Supported are USB Keyboards and USB Floppy drives

856

Supported are USB Keyboards and USB Floppy drives

857

(TEAC FD-05PUB).

857

(TEAC FD-05PUB).

858

MPC5200 USB requires additional defines:

858

MPC5200 USB requires additional defines:

859

CONFIG_USB_CLOCK

859

CONFIG_USB_CLOCK

860

for 528 MHz Clock: 0x0001bbbb

860

for 528 MHz Clock: 0x0001bbbb

861

CONFIG_PSC3_USB

861

CONFIG_PSC3_USB

862

for USB on PSC3

862

for USB on PSC3

863

CONFIG_USB_CONFIG

863

CONFIG_USB_CONFIG

864

for differential drivers: 0x00001000

864

for differential drivers: 0x00001000

865

for single ended drivers: 0x00005000

865

for single ended drivers: 0x00005000

866

for differential drivers on PSC3: 0x00000100

866

for differential drivers on PSC3: 0x00000100

867

for single ended drivers on PSC3: 0x00004100

867

for single ended drivers on PSC3: 0x00004100

868

CONFIG_SYS_USB_EVENT_POLL

868

CONFIG_SYS_USB_EVENT_POLL

869

May be defined to allow interrupt polling

869

May be defined to allow interrupt polling

870

instead of using asynchronous interrupts

870

instead of using asynchronous interrupts

871

872

- USB Device:

872

- USB Device:

873

Define the below if you wish to use the USB console.

873

Define the below if you wish to use the USB console.

874

Once firmware is rebuilt from a serial console issue the

874

Once firmware is rebuilt from a serial console issue the

875

command "setenv stdin usbtty; setenv stdout usbtty" and

875

command "setenv stdin usbtty; setenv stdout usbtty" and

876

attach your USB cable. The Unix command "dmesg" should print

876

attach your USB cable. The Unix command "dmesg" should print

877

it has found a new device. The environment variable usbtty

877

it has found a new device. The environment variable usbtty

878

can be set to gserial or cdc_acm to enable your device to

878

can be set to gserial or cdc_acm to enable your device to

879

appear to a USB host as a Linux gserial device or a

879

appear to a USB host as a Linux gserial device or a

880

Common Device Class Abstract Control Model serial device.

880

Common Device Class Abstract Control Model serial device.

881

If you select usbtty = gserial you should be able to enumerate

881

If you select usbtty = gserial you should be able to enumerate

882

a Linux host by

882

a Linux host by

883

# modprobe usbserial vendor=0xVendorID product=0xProductID

883

# modprobe usbserial vendor=0xVendorID product=0xProductID

884

else if using cdc_acm, simply setting the environment

884

else if using cdc_acm, simply setting the environment

885

variable usbtty to be cdc_acm should suffice. The following

885

variable usbtty to be cdc_acm should suffice. The following

886

might be defined in YourBoardName.h

886

might be defined in YourBoardName.h

887

888

CONFIG_USB_DEVICE

888

CONFIG_USB_DEVICE

889

Define this to build a UDC device

889

Define this to build a UDC device

890

891

CONFIG_USB_TTY

891

CONFIG_USB_TTY

892

Define this to have a tty type of device available to

892

Define this to have a tty type of device available to

893

talk to the UDC device

893

talk to the UDC device

894

895

CONFIG_SYS_CONSOLE_IS_IN_ENV

895

CONFIG_SYS_CONSOLE_IS_IN_ENV

896

Define this if you want stdin, stdout &/or stderr to

896

Define this if you want stdin, stdout &/or stderr to

897

be set to usbtty.

897

be set to usbtty.

898

899

mpc8xx:

899

mpc8xx:

900

CONFIG_SYS_USB_EXTC_CLK 0xBLAH

900

CONFIG_SYS_USB_EXTC_CLK 0xBLAH

901

Derive USB clock from external clock "blah"

901

Derive USB clock from external clock "blah"

902

- CONFIG_SYS_USB_EXTC_CLK 0x02

902

- CONFIG_SYS_USB_EXTC_CLK 0x02

903

904

CONFIG_SYS_USB_BRG_CLK 0xBLAH

904

CONFIG_SYS_USB_BRG_CLK 0xBLAH

905

Derive USB clock from brgclk

905

Derive USB clock from brgclk

906

- CONFIG_SYS_USB_BRG_CLK 0x04

906

- CONFIG_SYS_USB_BRG_CLK 0x04

907

908

If you have a USB-IF assigned VendorID then you may wish to

908

If you have a USB-IF assigned VendorID then you may wish to

909

define your own vendor specific values either in BoardName.h

909

define your own vendor specific values either in BoardName.h

910

or directly in usbd_vendor_info.h. If you don't define

910

or directly in usbd_vendor_info.h. If you don't define

911

CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,

911

CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,

912

CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot

912

CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot

913

should pretend to be a Linux device to it's target host.

913

should pretend to be a Linux device to it's target host.

914

915

CONFIG_USBD_MANUFACTURER

915

CONFIG_USBD_MANUFACTURER

916

Define this string as the name of your company for

916

Define this string as the name of your company for

917

- CONFIG_USBD_MANUFACTURER "my company"

917

- CONFIG_USBD_MANUFACTURER "my company"

918

919

CONFIG_USBD_PRODUCT_NAME

919

CONFIG_USBD_PRODUCT_NAME

920

Define this string as the name of your product

920

Define this string as the name of your product

921

- CONFIG_USBD_PRODUCT_NAME "acme usb device"

921

- CONFIG_USBD_PRODUCT_NAME "acme usb device"

922

923

CONFIG_USBD_VENDORID

923

CONFIG_USBD_VENDORID

924

Define this as your assigned Vendor ID from the USB

924

Define this as your assigned Vendor ID from the USB

925

Implementors Forum. This *must* be a genuine Vendor ID

925

Implementors Forum. This *must* be a genuine Vendor ID

926

to avoid polluting the USB namespace.

926

to avoid polluting the USB namespace.

927

- CONFIG_USBD_VENDORID 0xFFFF

927

- CONFIG_USBD_VENDORID 0xFFFF

928

929

CONFIG_USBD_PRODUCTID

929

CONFIG_USBD_PRODUCTID

930

Define this as the unique Product ID

930

Define this as the unique Product ID

931

for your device

931

for your device

932

- CONFIG_USBD_PRODUCTID 0xFFFF

932

- CONFIG_USBD_PRODUCTID 0xFFFF

933

934

935

- MMC Support:

935

- MMC Support:

936

The MMC controller on the Intel PXA is supported. To

936

The MMC controller on the Intel PXA is supported. To

937

enable this define CONFIG_MMC. The MMC can be

937

enable this define CONFIG_MMC. The MMC can be

938

accessed from the boot prompt by mapping the device

938

accessed from the boot prompt by mapping the device

939

to physical memory similar to flash. Command line is

939

to physical memory similar to flash. Command line is

940

enabled with CONFIG_CMD_MMC. The MMC driver also works with

940

enabled with CONFIG_CMD_MMC. The MMC driver also works with

941

the FAT fs. This is enabled with CONFIG_CMD_FAT.

941

the FAT fs. This is enabled with CONFIG_CMD_FAT.

942

943

- Journaling Flash filesystem support:

943

- Journaling Flash filesystem support:

944

CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,

944

CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,

945

CONFIG_JFFS2_NAND_DEV

945

CONFIG_JFFS2_NAND_DEV

946

Define these for a default partition on a NAND device

946

Define these for a default partition on a NAND device

947

948

CONFIG_SYS_JFFS2_FIRST_SECTOR,

948

CONFIG_SYS_JFFS2_FIRST_SECTOR,

949

CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS

949

CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS

950

Define these for a default partition on a NOR device

950

Define these for a default partition on a NOR device

951

952

CONFIG_SYS_JFFS_CUSTOM_PART

952

CONFIG_SYS_JFFS_CUSTOM_PART

953

Define this to create an own partition. You have to provide a

953

Define this to create an own partition. You have to provide a

954

function struct part_info* jffs2_part_info(int part_num)

954

function struct part_info* jffs2_part_info(int part_num)

955

956

If you define only one JFFS2 partition you may also want to

956

If you define only one JFFS2 partition you may also want to

957

#define CONFIG_SYS_JFFS_SINGLE_PART 1

957

#define CONFIG_SYS_JFFS_SINGLE_PART 1

958

to disable the command chpart. This is the default when you

958

to disable the command chpart. This is the default when you

959

have not defined a custom partition

959

have not defined a custom partition

960

961

- Keyboard Support:

961

- Keyboard Support:

962

CONFIG_ISA_KEYBOARD

962

CONFIG_ISA_KEYBOARD

963

964

Define this to enable standard (PC-Style) keyboard

964

Define this to enable standard (PC-Style) keyboard

965

support

965

support

966

967

CONFIG_I8042_KBD

967

CONFIG_I8042_KBD

968

Standard PC keyboard driver with US (is default) and

968

Standard PC keyboard driver with US (is default) and

969

GERMAN key layout (switch via environment 'keymap=de') support.

969

GERMAN key layout (switch via environment 'keymap=de') support.

970

Export function i8042_kbd_init, i8042_tstc and i8042_getc

970

Export function i8042_kbd_init, i8042_tstc and i8042_getc

971

for cfb_console. Supports cursor blinking.

971

for cfb_console. Supports cursor blinking.

972

973

- Video support:

973

- Video support:

974

CONFIG_VIDEO

974

CONFIG_VIDEO

975

976

Define this to enable video support (for output to

976

Define this to enable video support (for output to

977

video).

977

video).

978

979

CONFIG_VIDEO_CT69000

979

CONFIG_VIDEO_CT69000

980

981

Enable Chips & Technologies 69000 Video chip

981

Enable Chips & Technologies 69000 Video chip

982

983

CONFIG_VIDEO_SMI_LYNXEM

983

CONFIG_VIDEO_SMI_LYNXEM

984

Enable Silicon Motion SMI 712/710/810 Video chip. The

984

Enable Silicon Motion SMI 712/710/810 Video chip. The

985

video output is selected via environment 'videoout'

985

video output is selected via environment 'videoout'

986

(1 = LCD and 2 = CRT). If videoout is undefined, CRT is

986

(1 = LCD and 2 = CRT). If videoout is undefined, CRT is

987

assumed.

987

assumed.

988

989

For the CT69000 and SMI_LYNXEM drivers, videomode is

989

For the CT69000 and SMI_LYNXEM drivers, videomode is

990

selected via environment 'videomode'. Two different ways

990

selected via environment 'videomode'. Two different ways

991

are possible:

991

are possible:

992

- "videomode=num" 'num' is a standard LiLo mode numbers.

992

- "videomode=num" 'num' is a standard LiLo mode numbers.

993

Following standard modes are supported (* is default):

993

Following standard modes are supported (* is default):

994

995

Colors 640x480 800x600 1024x768 1152x864 1280x1024

995

Colors 640x480 800x600 1024x768 1152x864 1280x1024

996

-------------+---------------------------------------------

996

-------------+---------------------------------------------

997

8 bits | 0x301* 0x303 0x305 0x161 0x307

997

8 bits | 0x301* 0x303 0x305 0x161 0x307

998

15 bits | 0x310 0x313 0x316 0x162 0x319

998

15 bits | 0x310 0x313 0x316 0x162 0x319

999

16 bits | 0x311 0x314 0x317 0x163 0x31A

999

16 bits | 0x311 0x314 0x317 0x163 0x31A

1000

24 bits | 0x312 0x315 0x318 ? 0x31B

1000

24 bits | 0x312 0x315 0x318 ? 0x31B

1001

-------------+---------------------------------------------

1001

-------------+---------------------------------------------

1002

(i.e. setenv videomode 317; saveenv; reset;)

1002

(i.e. setenv videomode 317; saveenv; reset;)

1003

1004

- "videomode=bootargs" all the video parameters are parsed

1004

- "videomode=bootargs" all the video parameters are parsed

1005

from the bootargs. (See drivers/video/videomodes.c)

1005

from the bootargs. (See drivers/video/videomodes.c)

1006

1007

1008

CONFIG_VIDEO_SED13806

1008

CONFIG_VIDEO_SED13806

1009

Enable Epson SED13806 driver. This driver supports 8bpp

1009

Enable Epson SED13806 driver. This driver supports 8bpp

1010

and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP

1010

and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP

1011

or CONFIG_VIDEO_SED13806_16BPP

1011

or CONFIG_VIDEO_SED13806_16BPP

1012

1013

- Keyboard Support:

1013

- Keyboard Support:

1014

CONFIG_KEYBOARD

1014

CONFIG_KEYBOARD

1015

1016

Define this to enable a custom keyboard support.

1016

Define this to enable a custom keyboard support.

1017

This simply calls drv_keyboard_init() which must be

1017

This simply calls drv_keyboard_init() which must be

1018

defined in your board-specific files.

1018

defined in your board-specific files.

1019

The only board using this so far is RBC823.

1019

The only board using this so far is RBC823.

1020

1021

- LCD Support: CONFIG_LCD

1021

- LCD Support: CONFIG_LCD

1022

1023

Define this to enable LCD support (for output to LCD

1023

Define this to enable LCD support (for output to LCD

1024

display); also select one of the supported displays

1024

display); also select one of the supported displays

1025

by defining one of these:

1025

by defining one of these:

1026

1027

CONFIG_ATMEL_LCD:

1027

CONFIG_ATMEL_LCD:

1028

1029

HITACHI TX09D70VM1CCA, 3.5", 240x320.

1029

HITACHI TX09D70VM1CCA, 3.5", 240x320.

1030

1031

CONFIG_NEC_NL6448AC33:

1031

CONFIG_NEC_NL6448AC33:

1032

1033

NEC NL6448AC33-18. Active, color, single scan.

1033

NEC NL6448AC33-18. Active, color, single scan.

1034

1035

CONFIG_NEC_NL6448BC20

1035

CONFIG_NEC_NL6448BC20

1036

1037

NEC NL6448BC20-08. 6.5", 640x480.

1037

NEC NL6448BC20-08. 6.5", 640x480.

1038

Active, color, single scan.

1038

Active, color, single scan.

1039

1040

CONFIG_NEC_NL6448BC33_54

1040

CONFIG_NEC_NL6448BC33_54

1041

1042

NEC NL6448BC33-54. 10.4", 640x480.

1042

NEC NL6448BC33-54. 10.4", 640x480.

1043

Active, color, single scan.

1043

Active, color, single scan.

1044

1045

CONFIG_SHARP_16x9

1045

CONFIG_SHARP_16x9

1046

1047

Sharp 320x240. Active, color, single scan.

1047

Sharp 320x240. Active, color, single scan.

1048

It isn't 16x9, and I am not sure what it is.

1048

It isn't 16x9, and I am not sure what it is.

1049

1050

CONFIG_SHARP_LQ64D341

1050

CONFIG_SHARP_LQ64D341

1051

1052

Sharp LQ64D341 display, 640x480.

1052

Sharp LQ64D341 display, 640x480.

1053

Active, color, single scan.

1053

Active, color, single scan.

1054

1055

CONFIG_HLD1045

1055

CONFIG_HLD1045

1056

1057

HLD1045 display, 640x480.

1057

HLD1045 display, 640x480.

1058

Active, color, single scan.

1058

Active, color, single scan.

1059

1060

CONFIG_OPTREX_BW

1060

CONFIG_OPTREX_BW

1061

1062

Optrex CBL50840-2 NF-FW 99 22 M5

1062

Optrex CBL50840-2 NF-FW 99 22 M5

1063

or

1063

or

1064

Hitachi LMG6912RPFC-00T

1064

Hitachi LMG6912RPFC-00T

1065

or

1065

or

1066

Hitachi SP14Q002

1066

Hitachi SP14Q002

1067

1068

320x240. Black & white.

1068

320x240. Black & white.

1069

1070

Normally display is black on white background; define

1070

Normally display is black on white background; define

1071

CONFIG_SYS_WHITE_ON_BLACK to get it inverted.

1071

CONFIG_SYS_WHITE_ON_BLACK to get it inverted.

1072

1073

- Splash Screen Support: CONFIG_SPLASH_SCREEN

1073

- Splash Screen Support: CONFIG_SPLASH_SCREEN

1074

1075

If this option is set, the environment is checked for

1075

If this option is set, the environment is checked for

1076

a variable "splashimage". If found, the usual display

1076

a variable "splashimage". If found, the usual display

1077

of logo, copyright and system information on the LCD

1077

of logo, copyright and system information on the LCD

1078

is suppressed and the BMP image at the address

1078

is suppressed and the BMP image at the address

1079

specified in "splashimage" is loaded instead. The

1079

specified in "splashimage" is loaded instead. The

1080

console is redirected to the "nulldev", too. This

1080

console is redirected to the "nulldev", too. This

1081

allows for a "silent" boot where a splash screen is

1081

allows for a "silent" boot where a splash screen is

1082

loaded very quickly after power-on.

1082

loaded very quickly after power-on.

1083

1084

CONFIG_SPLASH_SCREEN_ALIGN

1084

CONFIG_SPLASH_SCREEN_ALIGN

1085

1086

If this option is set the splash image can be freely positioned

1086

If this option is set the splash image can be freely positioned

1087

on the screen. Environment variable "splashpos" specifies the

1087

on the screen. Environment variable "splashpos" specifies the

1088

position as "x,y". If a positive number is given it is used as

1088

position as "x,y". If a positive number is given it is used as

1089

number of pixel from left/top. If a negative number is given it

1089

number of pixel from left/top. If a negative number is given it

1090

is used as number of pixel from right/bottom. You can also

1090

is used as number of pixel from right/bottom. You can also

1091

specify 'm' for centering the image.

1091

specify 'm' for centering the image.

1092

1093

Example:

1093

Example:

1094

setenv splashpos m,m

1094

setenv splashpos m,m

1095

=> image at center of screen

1095

=> image at center of screen

1096

1097

setenv splashpos 30,20

1097

setenv splashpos 30,20

1098

=> image at x = 30 and y = 20

1098

=> image at x = 30 and y = 20

1099

1100

setenv splashpos -10,m

1100

setenv splashpos -10,m

1101

=> vertically centered image

1101

=> vertically centered image

1102

at x = dspWidth - bmpWidth - 9

1102

at x = dspWidth - bmpWidth - 9

1103

1104

- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP

1104

- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP

1105

1106

If this option is set, additionally to standard BMP

1106

If this option is set, additionally to standard BMP

1107

images, gzipped BMP images can be displayed via the

1107

images, gzipped BMP images can be displayed via the

1108

splashscreen support or the bmp command.

1108

splashscreen support or the bmp command.

1109

1110

- Compression support:

1110

- Compression support:

1111

CONFIG_BZIP2

1111

CONFIG_BZIP2

1112

1113

If this option is set, support for bzip2 compressed

1113

If this option is set, support for bzip2 compressed

1114

images is included. If not, only uncompressed and gzip

1114

images is included. If not, only uncompressed and gzip

1115

compressed images are supported.

1115

compressed images are supported.

1116

1117

NOTE: the bzip2 algorithm requires a lot of RAM, so

1117

NOTE: the bzip2 algorithm requires a lot of RAM, so

1118

the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should

1118

the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should

1119

be at least 4MB.

1119

be at least 4MB.

1120

1121

CONFIG_LZMA

1121

CONFIG_LZMA

1122

1123

If this option is set, support for lzma compressed

1123

If this option is set, support for lzma compressed

1124

images is included.

1124

images is included.

1125

1126

Note: The LZMA algorithm adds between 2 and 4KB of code and it

1126

Note: The LZMA algorithm adds between 2 and 4KB of code and it

1127

requires an amount of dynamic memory that is given by the

1127

requires an amount of dynamic memory that is given by the

1128

formula:

1128

formula:

1129

1130

(1846 + 768 << (lc + lp)) * sizeof(uint16)

1130

(1846 + 768 << (lc + lp)) * sizeof(uint16)

1131

1132

Where lc and lp stand for, respectively, Literal context bits

1132

Where lc and lp stand for, respectively, Literal context bits

1133

and Literal pos bits.

1133

and Literal pos bits.

1134

1135

This value is upper-bounded by 14MB in the worst case. Anyway,

1135

This value is upper-bounded by 14MB in the worst case. Anyway,

1136

for a ~4MB large kernel image, we have lc=3 and lp=0 for a

1136

for a ~4MB large kernel image, we have lc=3 and lp=0 for a

1137

total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is

1137

total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is

1138

a very small buffer.

1138

a very small buffer.

1139

1140

Use the lzmainfo tool to determinate the lc and lp values and

1140

Use the lzmainfo tool to determinate the lc and lp values and

1141

then calculate the amount of needed dynamic memory (ensuring

1141

then calculate the amount of needed dynamic memory (ensuring

1142

the appropriate CONFIG_SYS_MALLOC_LEN value).

1142

the appropriate CONFIG_SYS_MALLOC_LEN value).

1143

1144

- MII/PHY support:

1144

- MII/PHY support:

1145

CONFIG_PHY_ADDR

1145

CONFIG_PHY_ADDR

1146

1147

The address of PHY on MII bus.

1147

The address of PHY on MII bus.

1148

1149

CONFIG_PHY_CLOCK_FREQ (ppc4xx)

1149

CONFIG_PHY_CLOCK_FREQ (ppc4xx)

1150

1151

The clock frequency of the MII bus

1151

The clock frequency of the MII bus

1152

1153

CONFIG_PHY_GIGE

1153

CONFIG_PHY_GIGE

1154

1155

If this option is set, support for speed/duplex

1155

If this option is set, support for speed/duplex

1156

detection of gigabit PHY is included.

1156

detection of gigabit PHY is included.

1157

1158

CONFIG_PHY_RESET_DELAY

1158

CONFIG_PHY_RESET_DELAY

1159

1160

Some PHY like Intel LXT971A need extra delay after

1160

Some PHY like Intel LXT971A need extra delay after

1161

reset before any MII register access is possible.

1161

reset before any MII register access is possible.

1162

For such PHY, set this option to the usec delay

1162

For such PHY, set this option to the usec delay

1163

required. (minimum 300usec for LXT971A)

1163

required. (minimum 300usec for LXT971A)

1164

1165

CONFIG_PHY_CMD_DELAY (ppc4xx)

1165

CONFIG_PHY_CMD_DELAY (ppc4xx)

1166

1167

Some PHY like Intel LXT971A need extra delay after

1167

Some PHY like Intel LXT971A need extra delay after

1168

command issued before MII status register can be read

1168

command issued before MII status register can be read

1169

1170

- Ethernet address:

1170

- Ethernet address:

1171

CONFIG_ETHADDR

1171

CONFIG_ETHADDR

1172

CONFIG_ETH1ADDR

1172

CONFIG_ETH1ADDR

1173

CONFIG_ETH2ADDR

1173

CONFIG_ETH2ADDR

1174

CONFIG_ETH3ADDR

1174

CONFIG_ETH3ADDR

1175

CONFIG_ETH4ADDR

1175

CONFIG_ETH4ADDR

1176

CONFIG_ETH5ADDR

1176

CONFIG_ETH5ADDR

1177

1178

Define a default value for Ethernet address to use

1178

Define a default value for Ethernet address to use

1179

for the respective Ethernet interface, in case this

1179

for the respective Ethernet interface, in case this

1180

is not determined automatically.

1180

is not determined automatically.

1181

1182

- IP address:

1182

- IP address:

1183

CONFIG_IPADDR

1183

CONFIG_IPADDR

1184

1185

Define a default value for the IP address to use for

1185

Define a default value for the IP address to use for

1186

the default Ethernet interface, in case this is not

1186

the default Ethernet interface, in case this is not

1187

determined through e.g. bootp.

1187

determined through e.g. bootp.

1188

1189

- Server IP address:

1189

- Server IP address:

1190

CONFIG_SERVERIP

1190

CONFIG_SERVERIP

1191

1192

Defines a default value for the IP address of a TFTP

1192

Defines a default value for the IP address of a TFTP

1193

server to contact when using the "tftboot" command.

1193

server to contact when using the "tftboot" command.

1194

1195

CONFIG_KEEP_SERVERADDR

1195

CONFIG_KEEP_SERVERADDR

1196

1197

Keeps the server's MAC address, in the env 'serveraddr'

1197

Keeps the server's MAC address, in the env 'serveraddr'

1198

for passing to bootargs (like Linux's netconsole option)

1198

for passing to bootargs (like Linux's netconsole option)

1199

1200

- Multicast TFTP Mode:

1200

- Multicast TFTP Mode:

1201

CONFIG_MCAST_TFTP

1201

CONFIG_MCAST_TFTP

1202

1203

Defines whether you want to support multicast TFTP as per

1203

Defines whether you want to support multicast TFTP as per

1204

rfc-2090; for example to work with atftp. Lets lots of targets

1204

rfc-2090; for example to work with atftp. Lets lots of targets

1205

tftp down the same boot image concurrently. Note: the Ethernet

1205

tftp down the same boot image concurrently. Note: the Ethernet

1206

driver in use must provide a function: mcast() to join/leave a

1206

driver in use must provide a function: mcast() to join/leave a

1207

multicast group.

1207

multicast group.

1208

1209

CONFIG_BOOTP_RANDOM_DELAY

1209

CONFIG_BOOTP_RANDOM_DELAY

1210

- BOOTP Recovery Mode:

1210

- BOOTP Recovery Mode:

1211

CONFIG_BOOTP_RANDOM_DELAY

1211

CONFIG_BOOTP_RANDOM_DELAY

1212

1213

If you have many targets in a network that try to

1213

If you have many targets in a network that try to

1214

boot using BOOTP, you may want to avoid that all

1214

boot using BOOTP, you may want to avoid that all

1215

systems send out BOOTP requests at precisely the same

1215

systems send out BOOTP requests at precisely the same

1216

moment (which would happen for instance at recovery

1216

moment (which would happen for instance at recovery

1217

from a power failure, when all systems will try to

1217

from a power failure, when all systems will try to

1218

boot, thus flooding the BOOTP server. Defining

1218

boot, thus flooding the BOOTP server. Defining

1219

CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be

1219

CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be

1220

inserted before sending out BOOTP requests. The

1220

inserted before sending out BOOTP requests. The

1221

following delays are inserted then:

1221

following delays are inserted then:

1222

1223

1st BOOTP request: delay 0 ... 1 sec

1223

1st BOOTP request: delay 0 ... 1 sec

1224

2nd BOOTP request: delay 0 ... 2 sec

1224

2nd BOOTP request: delay 0 ... 2 sec

1225

3rd BOOTP request: delay 0 ... 4 sec

1225

3rd BOOTP request: delay 0 ... 4 sec

1226

4th and following

1226

4th and following

1227

BOOTP requests: delay 0 ... 8 sec

1227

BOOTP requests: delay 0 ... 8 sec

1228

1229

- DHCP Advanced Options:

1229

- DHCP Advanced Options:

1230

You can fine tune the DHCP functionality by defining

1230

You can fine tune the DHCP functionality by defining

1231

CONFIG_BOOTP_* symbols:

1231

CONFIG_BOOTP_* symbols:

1232

1233

CONFIG_BOOTP_SUBNETMASK

1233

CONFIG_BOOTP_SUBNETMASK

1234

CONFIG_BOOTP_GATEWAY

1234

CONFIG_BOOTP_GATEWAY

1235

CONFIG_BOOTP_HOSTNAME

1235

CONFIG_BOOTP_HOSTNAME

1236

CONFIG_BOOTP_NISDOMAIN

1236

CONFIG_BOOTP_NISDOMAIN

1237

CONFIG_BOOTP_BOOTPATH

1237

CONFIG_BOOTP_BOOTPATH

1238

CONFIG_BOOTP_BOOTFILESIZE

1238

CONFIG_BOOTP_BOOTFILESIZE

1239

CONFIG_BOOTP_DNS

1239

CONFIG_BOOTP_DNS

1240

CONFIG_BOOTP_DNS2

1240

CONFIG_BOOTP_DNS2

1241

CONFIG_BOOTP_SEND_HOSTNAME

1241

CONFIG_BOOTP_SEND_HOSTNAME

1242

CONFIG_BOOTP_NTPSERVER

1242

CONFIG_BOOTP_NTPSERVER

1243

CONFIG_BOOTP_TIMEOFFSET

1243

CONFIG_BOOTP_TIMEOFFSET

1244

CONFIG_BOOTP_VENDOREX

1244

CONFIG_BOOTP_VENDOREX

1245

1246

CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip

1246

CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip

1247

environment variable, not the BOOTP server.

1247

environment variable, not the BOOTP server.

1248

1249

CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS

1249

CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS

1250

serverip from a DHCP server, it is possible that more

1250

serverip from a DHCP server, it is possible that more

1251

than one DNS serverip is offered to the client.

1251

than one DNS serverip is offered to the client.

1252

If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS

1252

If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS

1253

serverip will be stored in the additional environment

1253

serverip will be stored in the additional environment

1254

variable "dnsip2". The first DNS serverip is always

1254

variable "dnsip2". The first DNS serverip is always

1255

stored in the variable "dnsip", when CONFIG_BOOTP_DNS

1255

stored in the variable "dnsip", when CONFIG_BOOTP_DNS

1256

is defined.

1256

is defined.

1257

1258

CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable

1258

CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable

1259

to do a dynamic update of a DNS server. To do this, they

1259

to do a dynamic update of a DNS server. To do this, they

1260

need the hostname of the DHCP requester.

1260

need the hostname of the DHCP requester.

1261

If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content

1261

If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content

1262

of the "hostname" environment variable is passed as

1262

of the "hostname" environment variable is passed as

1263

option 12 to the DHCP server.

1263

option 12 to the DHCP server.

1264

1265

CONFIG_BOOTP_DHCP_REQUEST_DELAY

1265

CONFIG_BOOTP_DHCP_REQUEST_DELAY

1266

1267

A 32bit value in microseconds for a delay between

1267

A 32bit value in microseconds for a delay between

1268

receiving a "DHCP Offer" and sending the "DHCP Request".

1268

receiving a "DHCP Offer" and sending the "DHCP Request".

1269

This fixes a problem with certain DHCP servers that don't

1269

This fixes a problem with certain DHCP servers that don't

1270

respond 100% of the time to a "DHCP request". E.g. On an

1270

respond 100% of the time to a "DHCP request". E.g. On an

1271

AT91RM9200 processor running at 180MHz, this delay needed

1271

AT91RM9200 processor running at 180MHz, this delay needed

1272

to be *at least* 15,000 usec before a Windows Server 2003

1272

to be *at least* 15,000 usec before a Windows Server 2003

1273

DHCP server would reply 100% of the time. I recommend at

1273

DHCP server would reply 100% of the time. I recommend at

1274

least 50,000 usec to be safe. The alternative is to hope

1274

least 50,000 usec to be safe. The alternative is to hope

1275

that one of the retries will be successful but note that

1275

that one of the retries will be successful but note that

1276

the DHCP timeout and retry process takes a longer than

1276

the DHCP timeout and retry process takes a longer than

1277

this delay.

1277

this delay.

1278

1279

- CDP Options:

1279

- CDP Options:

1280

CONFIG_CDP_DEVICE_ID

1280

CONFIG_CDP_DEVICE_ID

1281

1282

The device id used in CDP trigger frames.

1282

The device id used in CDP trigger frames.

1283

1284

CONFIG_CDP_DEVICE_ID_PREFIX

1284

CONFIG_CDP_DEVICE_ID_PREFIX

1285

1286

A two character string which is prefixed to the MAC address

1286

A two character string which is prefixed to the MAC address

1287

of the device.

1287

of the device.

1288

1289

CONFIG_CDP_PORT_ID

1289

CONFIG_CDP_PORT_ID

1290

1291

A printf format string which contains the ascii name of

1291

A printf format string which contains the ascii name of

1292

the port. Normally is set to "eth%d" which sets

1292

the port. Normally is set to "eth%d" which sets

1293

eth0 for the first Ethernet, eth1 for the second etc.

1293

eth0 for the first Ethernet, eth1 for the second etc.

1294

1295

CONFIG_CDP_CAPABILITIES

1295

CONFIG_CDP_CAPABILITIES

1296

1297

A 32bit integer which indicates the device capabilities;

1297

A 32bit integer which indicates the device capabilities;

1298

0x00000010 for a normal host which does not forwards.

1298

0x00000010 for a normal host which does not forwards.

1299

1300

CONFIG_CDP_VERSION

1300

CONFIG_CDP_VERSION

1301

1302

An ascii string containing the version of the software.

1302

An ascii string containing the version of the software.

1303

1304

CONFIG_CDP_PLATFORM

1304

CONFIG_CDP_PLATFORM

1305

1306

An ascii string containing the name of the platform.

1306

An ascii string containing the name of the platform.

1307

1308

CONFIG_CDP_TRIGGER

1308

CONFIG_CDP_TRIGGER

1309

1310

A 32bit integer sent on the trigger.

1310

A 32bit integer sent on the trigger.

1311

1312

CONFIG_CDP_POWER_CONSUMPTION

1312

CONFIG_CDP_POWER_CONSUMPTION

1313

1314

A 16bit integer containing the power consumption of the

1314

A 16bit integer containing the power consumption of the

1315

device in .1 of milliwatts.

1315

device in .1 of milliwatts.

1316

1317

CONFIG_CDP_APPLIANCE_VLAN_TYPE

1317

CONFIG_CDP_APPLIANCE_VLAN_TYPE

1318

1319

A byte containing the id of the VLAN.

1319

A byte containing the id of the VLAN.

1320

1321

- Status LED: CONFIG_STATUS_LED

1321

- Status LED: CONFIG_STATUS_LED

1322

1323

Several configurations allow to display the current

1323

Several configurations allow to display the current

1324

status using a LED. For instance, the LED will blink

1324

status using a LED. For instance, the LED will blink

1325

fast while running U-Boot code, stop blinking as

1325

fast while running U-Boot code, stop blinking as

1326

soon as a reply to a BOOTP request was received, and

1326

soon as a reply to a BOOTP request was received, and

1327

start blinking slow once the Linux kernel is running

1327

start blinking slow once the Linux kernel is running

1328

(supported by a status LED driver in the Linux

1328

(supported by a status LED driver in the Linux

1329

kernel). Defining CONFIG_STATUS_LED enables this

1329

kernel). Defining CONFIG_STATUS_LED enables this

1330

feature in U-Boot.

1330

feature in U-Boot.

1331

1332

- CAN Support: CONFIG_CAN_DRIVER

1332

- CAN Support: CONFIG_CAN_DRIVER

1333

1334

Defining CONFIG_CAN_DRIVER enables CAN driver support

1334

Defining CONFIG_CAN_DRIVER enables CAN driver support

1335

on those systems that support this (optional)

1335

on those systems that support this (optional)

1336

feature, like the TQM8xxL modules.

1336

feature, like the TQM8xxL modules.

1337

1338

- I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C

1338

- I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C

1339

1340

These enable I2C serial bus commands. Defining either of

1340

These enable I2C serial bus commands. Defining either of

1341

(but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will

1341

(but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will

1342

include the appropriate I2C driver for the selected CPU.

1342

include the appropriate I2C driver for the selected CPU.

1343

1344

This will allow you to use i2c commands at the u-boot

1344

This will allow you to use i2c commands at the u-boot

1345

command line (as long as you set CONFIG_CMD_I2C in

1345

command line (as long as you set CONFIG_CMD_I2C in

1346

CONFIG_COMMANDS) and communicate with i2c based realtime

1346

CONFIG_COMMANDS) and communicate with i2c based realtime

1347

clock chips. See common/cmd_i2c.c for a description of the

1347

clock chips. See common/cmd_i2c.c for a description of the

1348

command line interface.

1348

command line interface.

1349

1350

CONFIG_HARD_I2C selects a hardware I2C controller.

1350

CONFIG_HARD_I2C selects a hardware I2C controller.

1351

1352

CONFIG_SOFT_I2C configures u-boot to use a software (aka

1352

CONFIG_SOFT_I2C configures u-boot to use a software (aka

1353

bit-banging) driver instead of CPM or similar hardware

1353

bit-banging) driver instead of CPM or similar hardware

1354

support for I2C.

1354

support for I2C.

1355

1356

There are several other quantities that must also be

1356

There are several other quantities that must also be

1357

defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.

1357

defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.

1358

1359

In both cases you will need to define CONFIG_SYS_I2C_SPEED

1359

In both cases you will need to define CONFIG_SYS_I2C_SPEED

1360

to be the frequency (in Hz) at which you wish your i2c bus

1360

to be the frequency (in Hz) at which you wish your i2c bus

1361

to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie

1361

to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie

1362

the CPU's i2c node address).

1362

the CPU's i2c node address).

1363

1364

Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)

1364

Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)

1365

sets the CPU up as a master node and so its address should

1365

sets the CPU up as a master node and so its address should

1366

therefore be cleared to 0 (See, eg, MPC823e User's Manual

1366

therefore be cleared to 0 (See, eg, MPC823e User's Manual

1367

p.16-473). So, set CONFIG_SYS_I2C_SLAVE to 0.

1367

p.16-473). So, set CONFIG_SYS_I2C_SLAVE to 0.

1368

1369

CONFIG_SYS_I2C_INIT_MPC5XXX

1370

1371

When a board is reset during an i2c bus transfer

1372

chips might think that the current transfer is still

1373

in progress. Reset the slave devices by sending start

1374

commands until the slave device responds.

1375

1369

That's all that's required for CONFIG_HARD_I2C.

1376

That's all that's required for CONFIG_HARD_I2C.

1370

1377

1371

If you use the software i2c interface (CONFIG_SOFT_I2C)

1378

If you use the software i2c interface (CONFIG_SOFT_I2C)

1372

then the following macros need to be defined (examples are

1379

then the following macros need to be defined (examples are

1373

from include/configs/lwmon.h):

1380

from include/configs/lwmon.h):

1374

1381

1375

I2C_INIT

1382

I2C_INIT

1376

1383

1377

(Optional). Any commands necessary to enable the I2C

1384

(Optional). Any commands necessary to enable the I2C

1378

controller or configure ports.

1385

controller or configure ports.

1379

1386

1380

eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)

1387

eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)

1381

1388

1382

I2C_PORT

1389

I2C_PORT

1383

1390

1384

(Only for MPC8260 CPU). The I/O port to use (the code

1391

(Only for MPC8260 CPU). The I/O port to use (the code

1385

assumes both bits are on the same port). Valid values

1392

assumes both bits are on the same port). Valid values

1386

are 0..3 for ports A..D.

1393

are 0..3 for ports A..D.

1387

1394

1388

I2C_ACTIVE

1395

I2C_ACTIVE

1389

1396

1390

The code necessary to make the I2C data line active

1397

The code necessary to make the I2C data line active

1391

(driven). If the data line is open collector, this

1398

(driven). If the data line is open collector, this

1392

define can be null.

1399

define can be null.

1393

1400

1394

eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)

1401

eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)

1395

1402

1396

I2C_TRISTATE

1403

I2C_TRISTATE

1397

1404

1398

The code necessary to make the I2C data line tri-stated

1405

The code necessary to make the I2C data line tri-stated

1399

(inactive). If the data line is open collector, this

1406

(inactive). If the data line is open collector, this

1400

define can be null.

1407

define can be null.

1401

1408

1402

eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)

1409

eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)

1403

1410

1404

I2C_READ

1411

I2C_READ

1405

1412

1406

Code that returns TRUE if the I2C data line is high,

1413

Code that returns TRUE if the I2C data line is high,

1407

FALSE if it is low.

1414

FALSE if it is low.

1408

1415

1409

eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)

1416

eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)

1410

1417

1411

I2C_SDA(bit)

1418

I2C_SDA(bit)

1412

1419

1413

If <bit> is TRUE, sets the I2C data line high. If it

1420

If <bit> is TRUE, sets the I2C data line high. If it

1414

is FALSE, it clears it (low).

1421

is FALSE, it clears it (low).

1415

1422

1416

eg: #define I2C_SDA(bit) \

1423

eg: #define I2C_SDA(bit) \

1417

if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \

1424

if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \

1418

else immr->im_cpm.cp_pbdat &= ~PB_SDA

1425

else immr->im_cpm.cp_pbdat &= ~PB_SDA

1419

1426

1420

I2C_SCL(bit)

1427

I2C_SCL(bit)

1421

1428

1422

If <bit> is TRUE, sets the I2C clock line high. If it

1429

If <bit> is TRUE, sets the I2C clock line high. If it

1423

is FALSE, it clears it (low).

1430

is FALSE, it clears it (low).

1424

1431

1425

eg: #define I2C_SCL(bit) \

1432

eg: #define I2C_SCL(bit) \

1426

if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \

1433

if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \

1427

else immr->im_cpm.cp_pbdat &= ~PB_SCL

1434

else immr->im_cpm.cp_pbdat &= ~PB_SCL

1428

1435

1429

I2C_DELAY

1436

I2C_DELAY

1430

1437

1431

This delay is invoked four times per clock cycle so this

1438

This delay is invoked four times per clock cycle so this

1432

controls the rate of data transfer. The data rate thus

1439

controls the rate of data transfer. The data rate thus

1433

is 1 / (I2C_DELAY * 4). Often defined to be something

1440

is 1 / (I2C_DELAY * 4). Often defined to be something

1434

like:

1441

like:

1435

1442

1436

#define I2C_DELAY udelay(2)

1443

#define I2C_DELAY udelay(2)

1437

1444

1438

CONFIG_SYS_I2C_INIT_BOARD

1445

CONFIG_SYS_I2C_INIT_BOARD

1439

1446

1440

When a board is reset during an i2c bus transfer

1447

When a board is reset during an i2c bus transfer

1441

chips might think that the current transfer is still

1448

chips might think that the current transfer is still

1442

in progress. On some boards it is possible to access

1449

in progress. On some boards it is possible to access

1443

the i2c SCLK line directly, either by using the

1450

the i2c SCLK line directly, either by using the

1444

processor pin as a GPIO or by having a second pin

1451

processor pin as a GPIO or by having a second pin

1445

connected to the bus. If this option is defined a

1452

connected to the bus. If this option is defined a

1446

custom i2c_init_board() routine in boards/xxx/board.c

1453

custom i2c_init_board() routine in boards/xxx/board.c

1447

is run early in the boot sequence.

1454

is run early in the boot sequence.

1448

1455

1449

CONFIG_I2CFAST (PPC405GP|PPC405EP only)

1456

CONFIG_I2CFAST (PPC405GP|PPC405EP only)

1450

1457

1451

This option enables configuration of bi_iic_fast[] flags

1458

This option enables configuration of bi_iic_fast[] flags

1452

in u-boot bd_info structure based on u-boot environment

1459

in u-boot bd_info structure based on u-boot environment

1453

variable "i2cfast". (see also i2cfast)

1460

variable "i2cfast". (see also i2cfast)

1454

1461

1455

CONFIG_I2C_MULTI_BUS

1462

CONFIG_I2C_MULTI_BUS

1456

1463

1457

This option allows the use of multiple I2C buses, each of which

1464

This option allows the use of multiple I2C buses, each of which

1458

must have a controller. At any point in time, only one bus is

1465

must have a controller. At any point in time, only one bus is

1459

active. To switch to a different bus, use the 'i2c dev' command.

1466

active. To switch to a different bus, use the 'i2c dev' command.

1460

Note that bus numbering is zero-based.

1467

Note that bus numbering is zero-based.

1461

1468

1462

CONFIG_SYS_I2C_NOPROBES

1469

CONFIG_SYS_I2C_NOPROBES

1463

1470

1464

This option specifies a list of I2C devices that will be skipped

1471

This option specifies a list of I2C devices that will be skipped

1465

when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS

1472

when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS

1466

is set, specify a list of bus-device pairs. Otherwise, specify

1473

is set, specify a list of bus-device pairs. Otherwise, specify

1467

a 1D array of device addresses

1474

a 1D array of device addresses

1468

1475

1469

e.g.

1476

e.g.

1470

#undef CONFIG_I2C_MULTI_BUS

1477

#undef CONFIG_I2C_MULTI_BUS

1471

#define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}

1478

#define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}

1472

1479

1473

will skip addresses 0x50 and 0x68 on a board with one I2C bus

1480

will skip addresses 0x50 and 0x68 on a board with one I2C bus

1474

1481

1475

#define CONFIG_I2C_MULTI_BUS

1482

#define CONFIG_I2C_MULTI_BUS

1476

#define CONFIG_SYS_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}

1483

#define CONFIG_SYS_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}

1477

1484

1478

will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1

1485

will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1

1479

1486

1480

CONFIG_SYS_SPD_BUS_NUM

1487

CONFIG_SYS_SPD_BUS_NUM

1481

1488

1482

If defined, then this indicates the I2C bus number for DDR SPD.

1489

If defined, then this indicates the I2C bus number for DDR SPD.

1483

If not defined, then U-Boot assumes that SPD is on I2C bus 0.

1490

If not defined, then U-Boot assumes that SPD is on I2C bus 0.

1484

1491

1485

CONFIG_SYS_RTC_BUS_NUM

1492

CONFIG_SYS_RTC_BUS_NUM

1486

1493

1487

If defined, then this indicates the I2C bus number for the RTC.

1494

If defined, then this indicates the I2C bus number for the RTC.

1488

If not defined, then U-Boot assumes that RTC is on I2C bus 0.

1495

If not defined, then U-Boot assumes that RTC is on I2C bus 0.

1489

1496

1490

CONFIG_SYS_DTT_BUS_NUM

1497

CONFIG_SYS_DTT_BUS_NUM

1491

1498

1492

If defined, then this indicates the I2C bus number for the DTT.

1499

If defined, then this indicates the I2C bus number for the DTT.

1493

If not defined, then U-Boot assumes that DTT is on I2C bus 0.

1500

If not defined, then U-Boot assumes that DTT is on I2C bus 0.

1494

1501

1495

CONFIG_SYS_I2C_DTT_ADDR:

1502

CONFIG_SYS_I2C_DTT_ADDR:

1496

1503

1497

If defined, specifies the I2C address of the DTT device.

1504

If defined, specifies the I2C address of the DTT device.

1498

If not defined, then U-Boot uses predefined value for

1505

If not defined, then U-Boot uses predefined value for

1499

specified DTT device.

1506

specified DTT device.

1500

1507

1501

CONFIG_FSL_I2C

1508

CONFIG_FSL_I2C

1502

1509

1503

Define this option if you want to use Freescale's I2C driver in

1510

Define this option if you want to use Freescale's I2C driver in

1504

drivers/i2c/fsl_i2c.c.

1511

drivers/i2c/fsl_i2c.c.

1505

1512

1506

CONFIG_I2C_MUX

1513

CONFIG_I2C_MUX

1507

1514

1508

Define this option if you have I2C devices reached over 1 .. n

1515

Define this option if you have I2C devices reached over 1 .. n

1509

I2C Muxes like the pca9544a. This option addes a new I2C

1516

I2C Muxes like the pca9544a. This option addes a new I2C

1510

Command "i2c bus [muxtype:muxaddr:muxchannel]" which adds a

1517

Command "i2c bus [muxtype:muxaddr:muxchannel]" which adds a

1511

new I2C Bus to the existing I2C Busses. If you select the

1518

new I2C Bus to the existing I2C Busses. If you select the

1512

new Bus with "i2c dev", u-bbot sends first the commandos for

1519

new Bus with "i2c dev", u-bbot sends first the commandos for

1513

the muxes to activate this new "bus".

1520

the muxes to activate this new "bus".

1514

1521

1515

CONFIG_I2C_MULTI_BUS must be also defined, to use this

1522

CONFIG_I2C_MULTI_BUS must be also defined, to use this

1516

feature!

1523

feature!

1517

1524

1518

Example:

1525

Example:

1519

Adding a new I2C Bus reached over 2 pca9544a muxes

1526

Adding a new I2C Bus reached over 2 pca9544a muxes

1520

The First mux with address 70 and channel 6

1527

The First mux with address 70 and channel 6

1521

The Second mux with address 71 and channel 4

1528

The Second mux with address 71 and channel 4

1522

1529

1523

=> i2c bus pca9544a:70:6:pca9544a:71:4

1530

=> i2c bus pca9544a:70:6:pca9544a:71:4

1524

1531

1525

Use the "i2c bus" command without parameter, to get a list

1532

Use the "i2c bus" command without parameter, to get a list

1526

of I2C Busses with muxes:

1533

of I2C Busses with muxes:

1527

1534

1528

=> i2c bus

1535

=> i2c bus

1529

Busses reached over muxes:

1536

Busses reached over muxes:

1530

Bus ID: 2

1537

Bus ID: 2

1531

reached over Mux(es):

1538

reached over Mux(es):

1532

pca9544a@70 ch: 4

1539

pca9544a@70 ch: 4

1533

Bus ID: 3

1540

Bus ID: 3

1534

reached over Mux(es):

1541

reached over Mux(es):

1535

pca9544a@70 ch: 6

1542

pca9544a@70 ch: 6

1536

pca9544a@71 ch: 4

1543

pca9544a@71 ch: 4

1537

=>

1544

=>

1538

1545

1539

If you now switch to the new I2C Bus 3 with "i2c dev 3"

1546

If you now switch to the new I2C Bus 3 with "i2c dev 3"

1540

u-boot sends First the Commando to the mux@70 to enable

1547

u-boot sends First the Commando to the mux@70 to enable

1541

channel 6, and then the Commando to the mux@71 to enable

1548

channel 6, and then the Commando to the mux@71 to enable

1542

the channel 4.

1549

the channel 4.

1543

1550

1544

After that, you can use the "normal" i2c commands as

1551

After that, you can use the "normal" i2c commands as

1545

usual, to communicate with your I2C devices behind

1552

usual, to communicate with your I2C devices behind

1546

the 2 muxes.

1553

the 2 muxes.

1547

1554

1548

This option is actually implemented for the bitbanging

1555

This option is actually implemented for the bitbanging

1549

algorithm in common/soft_i2c.c and for the Hardware I2C

1556

algorithm in common/soft_i2c.c and for the Hardware I2C

1550

Bus on the MPC8260. But it should be not so difficult

1557

Bus on the MPC8260. But it should be not so difficult

1551

to add this option to other architectures.

1558

to add this option to other architectures.

1552

1559

1553

CONFIG_SOFT_I2C_READ_REPEATED_START

1560

CONFIG_SOFT_I2C_READ_REPEATED_START

1554

1561

1555

defining this will force the i2c_read() function in

1562

defining this will force the i2c_read() function in

1556

the soft_i2c driver to perform an I2C repeated start

1563

the soft_i2c driver to perform an I2C repeated start

1557

between writing the address pointer and reading the

1564

between writing the address pointer and reading the

1558

data. If this define is omitted the default behaviour

1565

data. If this define is omitted the default behaviour

1559

of doing a stop-start sequence will be used. Most I2C

1566

of doing a stop-start sequence will be used. Most I2C

1560

devices can use either method, but some require one or

1567

devices can use either method, but some require one or

1561

the other.

1568

the other.

1562

1569

1563

- SPI Support: CONFIG_SPI

1570

- SPI Support: CONFIG_SPI

1564

1571

1565

Enables SPI driver (so far only tested with

1572

Enables SPI driver (so far only tested with

1566

SPI EEPROM, also an instance works with Crystal A/D and

1573

SPI EEPROM, also an instance works with Crystal A/D and

1567

D/As on the SACSng board)

1574

D/As on the SACSng board)

1568

1575

1569

CONFIG_SPI_X

1576

CONFIG_SPI_X

1570

1577

1571

Enables extended (16-bit) SPI EEPROM addressing.

1578

Enables extended (16-bit) SPI EEPROM addressing.

1572

(symmetrical to CONFIG_I2C_X)

1579

(symmetrical to CONFIG_I2C_X)

1573

1580

1574

CONFIG_SOFT_SPI

1581

CONFIG_SOFT_SPI

1575

1582

1576

Enables a software (bit-bang) SPI driver rather than

1583

Enables a software (bit-bang) SPI driver rather than

1577

using hardware support. This is a general purpose

1584

using hardware support. This is a general purpose

1578

driver that only requires three general I/O port pins

1585

driver that only requires three general I/O port pins

1579

(two outputs, one input) to function. If this is

1586

(two outputs, one input) to function. If this is

1580

defined, the board configuration must define several

1587

defined, the board configuration must define several

1581

SPI configuration items (port pins to use, etc). For

1588

SPI configuration items (port pins to use, etc). For

1582

an example, see include/configs/sacsng.h.

1589

an example, see include/configs/sacsng.h.

1583

1590

1584

CONFIG_HARD_SPI

1591

CONFIG_HARD_SPI

1585

1592

1586

Enables a hardware SPI driver for general-purpose reads

1593

Enables a hardware SPI driver for general-purpose reads

1587

and writes. As with CONFIG_SOFT_SPI, the board configuration

1594

and writes. As with CONFIG_SOFT_SPI, the board configuration

1588

must define a list of chip-select function pointers.

1595

must define a list of chip-select function pointers.

1589

Currently supported on some MPC8xxx processors. For an

1596

Currently supported on some MPC8xxx processors. For an

1590

example, see include/configs/mpc8349emds.h.

1597

example, see include/configs/mpc8349emds.h.

1591

1598

1592

CONFIG_MXC_SPI

1599

CONFIG_MXC_SPI

1593

1600

1594

Enables the driver for the SPI controllers on i.MX and MXC

1601

Enables the driver for the SPI controllers on i.MX and MXC

1595

SoCs. Currently only i.MX31 is supported.

1602

SoCs. Currently only i.MX31 is supported.

1596

1603

1597

- FPGA Support: CONFIG_FPGA

1604

- FPGA Support: CONFIG_FPGA

1598

1605

1599

Enables FPGA subsystem.

1606

Enables FPGA subsystem.

1600

1607

1601

CONFIG_FPGA_<vendor>

1608

CONFIG_FPGA_<vendor>

1602

1609

1603

Enables support for specific chip vendors.

1610

Enables support for specific chip vendors.

1604

(ALTERA, XILINX)

1611

(ALTERA, XILINX)

1605

1612

1606

CONFIG_FPGA_<family>

1613

CONFIG_FPGA_<family>

1607

1614

1608

Enables support for FPGA family.

1615

Enables support for FPGA family.

1609

(SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)

1616

(SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)

1610

1617

1611

CONFIG_FPGA_COUNT

1618

CONFIG_FPGA_COUNT

1612

1619

1613

Specify the number of FPGA devices to support.

1620

Specify the number of FPGA devices to support.

1614

1621

1615

CONFIG_SYS_FPGA_PROG_FEEDBACK

1622

CONFIG_SYS_FPGA_PROG_FEEDBACK

1616

1623

1617

Enable printing of hash marks during FPGA configuration.

1624

Enable printing of hash marks during FPGA configuration.

1618

1625

1619

CONFIG_SYS_FPGA_CHECK_BUSY

1626

CONFIG_SYS_FPGA_CHECK_BUSY

1620

1627

1621

Enable checks on FPGA configuration interface busy

1628

Enable checks on FPGA configuration interface busy

1622

status by the configuration function. This option

1629

status by the configuration function. This option

1623

will require a board or device specific function to

1630

will require a board or device specific function to

1624

be written.

1631

be written.

1625

1632

1626

CONFIG_FPGA_DELAY

1633

CONFIG_FPGA_DELAY

1627

1634

1628

If defined, a function that provides delays in the FPGA

1635

If defined, a function that provides delays in the FPGA

1629

configuration driver.

1636

configuration driver.

1630

1637

1631

CONFIG_SYS_FPGA_CHECK_CTRLC

1638

CONFIG_SYS_FPGA_CHECK_CTRLC

1632

Allow Control-C to interrupt FPGA configuration

1639

Allow Control-C to interrupt FPGA configuration

1633

1640

1634

CONFIG_SYS_FPGA_CHECK_ERROR

1641

CONFIG_SYS_FPGA_CHECK_ERROR

1635

1642

1636

Check for configuration errors during FPGA bitfile

1643

Check for configuration errors during FPGA bitfile

1637

loading. For example, abort during Virtex II

1644

loading. For example, abort during Virtex II

1638

configuration if the INIT_B line goes low (which

1645

configuration if the INIT_B line goes low (which

1639

indicated a CRC error).

1646

indicated a CRC error).

1640

1647

1641

CONFIG_SYS_FPGA_WAIT_INIT

1648

CONFIG_SYS_FPGA_WAIT_INIT

1642

1649

1643

Maximum time to wait for the INIT_B line to deassert

1650

Maximum time to wait for the INIT_B line to deassert

1644

after PROB_B has been deasserted during a Virtex II

1651

after PROB_B has been deasserted during a Virtex II

1645

FPGA configuration sequence. The default time is 500

1652

FPGA configuration sequence. The default time is 500

1646

ms.

1653

ms.

1647

1654

1648

CONFIG_SYS_FPGA_WAIT_BUSY

1655

CONFIG_SYS_FPGA_WAIT_BUSY

1649

1656

1650

Maximum time to wait for BUSY to deassert during

1657

Maximum time to wait for BUSY to deassert during

1651

Virtex II FPGA configuration. The default is 5 ms.

1658

Virtex II FPGA configuration. The default is 5 ms.

1652

1659

1653

CONFIG_SYS_FPGA_WAIT_CONFIG

1660

CONFIG_SYS_FPGA_WAIT_CONFIG

1654

1661

1655

Time to wait after FPGA configuration. The default is

1662

Time to wait after FPGA configuration. The default is

1656

200 ms.

1663

200 ms.

1657

1664

1658

- Configuration Management:

1665

- Configuration Management:

1659

CONFIG_IDENT_STRING

1666

CONFIG_IDENT_STRING

1660

1667

1661

If defined, this string will be added to the U-Boot

1668

If defined, this string will be added to the U-Boot

1662

version information (U_BOOT_VERSION)

1669

version information (U_BOOT_VERSION)

1663

1670

1664

- Vendor Parameter Protection:

1671

- Vendor Parameter Protection:

1665

1672

1666

U-Boot considers the values of the environment

1673

U-Boot considers the values of the environment

1667

variables "serial#" (Board Serial Number) and

1674

variables "serial#" (Board Serial Number) and

1668

"ethaddr" (Ethernet Address) to be parameters that

1675

"ethaddr" (Ethernet Address) to be parameters that

1669

are set once by the board vendor / manufacturer, and

1676

are set once by the board vendor / manufacturer, and

1670

protects these variables from casual modification by

1677

protects these variables from casual modification by

1671

the user. Once set, these variables are read-only,

1678

the user. Once set, these variables are read-only,

1672

and write or delete attempts are rejected. You can

1679

and write or delete attempts are rejected. You can

1673

change this behaviour:

1680

change this behaviour:

1674

1681

1675

If CONFIG_ENV_OVERWRITE is #defined in your config

1682

If CONFIG_ENV_OVERWRITE is #defined in your config

1676

file, the write protection for vendor parameters is

1683

file, the write protection for vendor parameters is

1677

completely disabled. Anybody can change or delete

1684

completely disabled. Anybody can change or delete

1678

these parameters.

1685

these parameters.

1679

1686

1680

Alternatively, if you #define _both_ CONFIG_ETHADDR

1687

Alternatively, if you #define _both_ CONFIG_ETHADDR

1681

_and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default

1688

_and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default

1682

Ethernet address is installed in the environment,

1689

Ethernet address is installed in the environment,

1683

which can be changed exactly ONCE by the user. [The

1690

which can be changed exactly ONCE by the user. [The

1684

serial# is unaffected by this, i. e. it remains

1691

serial# is unaffected by this, i. e. it remains

1685

read-only.]

1692

read-only.]

1686

1693

1687

- Protected RAM:

1694

- Protected RAM:

1688

CONFIG_PRAM

1695

CONFIG_PRAM

1689

1696

1690

Define this variable to enable the reservation of

1697

Define this variable to enable the reservation of

1691

"protected RAM", i. e. RAM which is not overwritten

1698

"protected RAM", i. e. RAM which is not overwritten

1692

by U-Boot. Define CONFIG_PRAM to hold the number of

1699

by U-Boot. Define CONFIG_PRAM to hold the number of

1693

kB you want to reserve for pRAM. You can overwrite

1700

kB you want to reserve for pRAM. You can overwrite

1694

this default value by defining an environment

1701

this default value by defining an environment

1695

variable "pram" to the number of kB you want to

1702

variable "pram" to the number of kB you want to

1696

reserve. Note that the board info structure will

1703

reserve. Note that the board info structure will

1697

still show the full amount of RAM. If pRAM is

1704

still show the full amount of RAM. If pRAM is

1698

reserved, a new environment variable "mem" will

1705

reserved, a new environment variable "mem" will

1699

automatically be defined to hold the amount of

1706

automatically be defined to hold the amount of

1700

remaining RAM in a form that can be passed as boot

1707

remaining RAM in a form that can be passed as boot

1701

argument to Linux, for instance like that:

1708

argument to Linux, for instance like that:

1702

1709

1703

setenv bootargs ... mem=\${mem}

1710

setenv bootargs ... mem=\${mem}

1704

saveenv

1711

saveenv

1705

1712

1706

This way you can tell Linux not to use this memory,

1713

This way you can tell Linux not to use this memory,

1707

either, which results in a memory region that will

1714

either, which results in a memory region that will

1708

not be affected by reboots.

1715

not be affected by reboots.

1709

1716

1710

*WARNING* If your board configuration uses automatic

1717

*WARNING* If your board configuration uses automatic

1711

detection of the RAM size, you must make sure that

1718

detection of the RAM size, you must make sure that

1712

this memory test is non-destructive. So far, the

1719

this memory test is non-destructive. So far, the

1713

following board configurations are known to be

1720

following board configurations are known to be

1714

"pRAM-clean":

1721

"pRAM-clean":

1715

1722

1716

ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,

1723

ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,

1717

HERMES, IP860, RPXlite, LWMON, LANTEC,

1724

HERMES, IP860, RPXlite, LWMON, LANTEC,

1718

PCU_E, FLAGADM, TQM8260

1725

PCU_E, FLAGADM, TQM8260

1719

1726

1720

- Error Recovery:

1727

- Error Recovery:

1721

CONFIG_PANIC_HANG

1728

CONFIG_PANIC_HANG

1722

1729

1723

Define this variable to stop the system in case of a

1730

Define this variable to stop the system in case of a

1724

fatal error, so that you have to reset it manually.

1731

fatal error, so that you have to reset it manually.

1725

This is probably NOT a good idea for an embedded

1732

This is probably NOT a good idea for an embedded

1726

system where you want the system to reboot

1733

system where you want the system to reboot

1727

automatically as fast as possible, but it may be

1734

automatically as fast as possible, but it may be

1728

useful during development since you can try to debug

1735

useful during development since you can try to debug

1729

the conditions that lead to the situation.

1736

the conditions that lead to the situation.

1730

1737

1731

CONFIG_NET_RETRY_COUNT

1738

CONFIG_NET_RETRY_COUNT

1732

1739

1733

This variable defines the number of retries for

1740

This variable defines the number of retries for

1734

network operations like ARP, RARP, TFTP, or BOOTP

1741

network operations like ARP, RARP, TFTP, or BOOTP

1735

before giving up the operation. If not defined, a

1742

before giving up the operation. If not defined, a

1736

default value of 5 is used.

1743

default value of 5 is used.

1737

1744

1738

CONFIG_ARP_TIMEOUT

1745

CONFIG_ARP_TIMEOUT

1739

1746

1740

Timeout waiting for an ARP reply in milliseconds.

1747

Timeout waiting for an ARP reply in milliseconds.

1741

1748

1742

- Command Interpreter:

1749

- Command Interpreter:

1743

CONFIG_AUTO_COMPLETE

1750

CONFIG_AUTO_COMPLETE

1744

1751

1745

Enable auto completion of commands using TAB.

1752

Enable auto completion of commands using TAB.

1746

1753

1747

Note that this feature has NOT been implemented yet

1754

Note that this feature has NOT been implemented yet

1748

for the "hush" shell.

1755

for the "hush" shell.

1749

1756

1750

1757

1751

CONFIG_SYS_HUSH_PARSER

1758

CONFIG_SYS_HUSH_PARSER

1752

1759

1753

Define this variable to enable the "hush" shell (from

1760

Define this variable to enable the "hush" shell (from

1754

Busybox) as command line interpreter, thus enabling

1761

Busybox) as command line interpreter, thus enabling

1755

powerful command line syntax like

1762

powerful command line syntax like

1756

if...then...else...fi conditionals or `&&' and '||'

1763

if...then...else...fi conditionals or `&&' and '||'

1757

constructs ("shell scripts").

1764

constructs ("shell scripts").

1758

1765

1759

If undefined, you get the old, much simpler behaviour

1766

If undefined, you get the old, much simpler behaviour

1760

with a somewhat smaller memory footprint.

1767

with a somewhat smaller memory footprint.

1761

1768

1762

1769

1763

CONFIG_SYS_PROMPT_HUSH_PS2

1770

CONFIG_SYS_PROMPT_HUSH_PS2

1764

1771

1765

This defines the secondary prompt string, which is

1772

This defines the secondary prompt string, which is

1766

printed when the command interpreter needs more input

1773

printed when the command interpreter needs more input

1767

to complete a command. Usually "> ".

1774

to complete a command. Usually "> ".

1768

1775

1769

Note:

1776

Note:

1770

1777

1771

In the current implementation, the local variables

1778

In the current implementation, the local variables

1772

space and global environment variables space are

1779

space and global environment variables space are

1773

separated. Local variables are those you define by

1780

separated. Local variables are those you define by

1774

simply typing `name=value'. To access a local

1781

simply typing `name=value'. To access a local

1775

variable later on, you have write `$name' or

1782

variable later on, you have write `$name' or

1776

`${name}'; to execute the contents of a variable

1783

`${name}'; to execute the contents of a variable

1777

directly type `$name' at the command prompt.

1784

directly type `$name' at the command prompt.

1778

1785

1779

Global environment variables are those you use

1786

Global environment variables are those you use

1780

setenv/printenv to work with. To run a command stored

1787

setenv/printenv to work with. To run a command stored

1781

in such a variable, you need to use the run command,

1788

in such a variable, you need to use the run command,

1782

and you must not use the '$' sign to access them.

1789

and you must not use the '$' sign to access them.

1783

1790

1784

To store commands and special characters in a

1791

To store commands and special characters in a

1785

variable, please use double quotation marks

1792

variable, please use double quotation marks

1786

surrounding the whole text of the variable, instead

1793

surrounding the whole text of the variable, instead

1787

of the backslashes before semicolons and special

1794

of the backslashes before semicolons and special

1788

symbols.

1795

symbols.

1789

1796

1790

- Commandline Editing and History:

1797

- Commandline Editing and History:

1791

CONFIG_CMDLINE_EDITING

1798

CONFIG_CMDLINE_EDITING

1792

1799

1793

Enable editing and History functions for interactive

1800

Enable editing and History functions for interactive

1794

commandline input operations

1801

commandline input operations

1795

1802

1796

- Default Environment:

1803

- Default Environment:

1797

CONFIG_EXTRA_ENV_SETTINGS

1804

CONFIG_EXTRA_ENV_SETTINGS

1798

1805

1799

Define this to contain any number of null terminated

1806

Define this to contain any number of null terminated

1800

strings (variable = value pairs) that will be part of

1807

strings (variable = value pairs) that will be part of

1801

the default environment compiled into the boot image.

1808

the default environment compiled into the boot image.

1802

1809

1803

For example, place something like this in your

1810

For example, place something like this in your

1804

board's config file:

1811

board's config file:

1805

1812

1806

#define CONFIG_EXTRA_ENV_SETTINGS \

1813

#define CONFIG_EXTRA_ENV_SETTINGS \

1807

"myvar1=value1\0" \

1814

"myvar1=value1\0" \

1808

"myvar2=value2\0"

1815

"myvar2=value2\0"

1809

1816

1810

Warning: This method is based on knowledge about the

1817

Warning: This method is based on knowledge about the

1811

internal format how the environment is stored by the

1818

internal format how the environment is stored by the

1812

U-Boot code. This is NOT an official, exported

1819

U-Boot code. This is NOT an official, exported

1813

interface! Although it is unlikely that this format

1820

interface! Although it is unlikely that this format

1814

will change soon, there is no guarantee either.

1821

will change soon, there is no guarantee either.

1815

You better know what you are doing here.

1822

You better know what you are doing here.

1816

1823

1817

Note: overly (ab)use of the default environment is

1824

Note: overly (ab)use of the default environment is

1818

discouraged. Make sure to check other ways to preset

1825

discouraged. Make sure to check other ways to preset

1819

the environment like the "source" command or the

1826

the environment like the "source" command or the

1820

boot command first.

1827

boot command first.

1821

1828

1822

- DataFlash Support:

1829

- DataFlash Support:

1823

CONFIG_HAS_DATAFLASH

1830

CONFIG_HAS_DATAFLASH

1824

1831

1825

Defining this option enables DataFlash features and

1832

Defining this option enables DataFlash features and

1826

allows to read/write in Dataflash via the standard

1833

allows to read/write in Dataflash via the standard

1827

commands cp, md...

1834

commands cp, md...

1828

1835

1829

- SystemACE Support:

1836

- SystemACE Support:

1830

CONFIG_SYSTEMACE

1837

CONFIG_SYSTEMACE

1831

1838

1832

Adding this option adds support for Xilinx SystemACE

1839

Adding this option adds support for Xilinx SystemACE

1833

chips attached via some sort of local bus. The address

1840

chips attached via some sort of local bus. The address

1834

of the chip must also be defined in the

1841

of the chip must also be defined in the

1835

CONFIG_SYS_SYSTEMACE_BASE macro. For example:

1842

CONFIG_SYS_SYSTEMACE_BASE macro. For example:

1836

1843

1837

#define CONFIG_SYSTEMACE

1844

#define CONFIG_SYSTEMACE

1838

#define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000

1845

#define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000

1839

1846

1840

When SystemACE support is added, the "ace" device type

1847

When SystemACE support is added, the "ace" device type

1841

becomes available to the fat commands, i.e. fatls.

1848

becomes available to the fat commands, i.e. fatls.

1842

1849

1843

- TFTP Fixed UDP Port:

1850

- TFTP Fixed UDP Port:

1844

CONFIG_TFTP_PORT

1851

CONFIG_TFTP_PORT

1845

1852

1846

If this is defined, the environment variable tftpsrcp

1853

If this is defined, the environment variable tftpsrcp

1847

is used to supply the TFTP UDP source port value.

1854

is used to supply the TFTP UDP source port value.

1848

If tftpsrcp isn't defined, the normal pseudo-random port

1855

If tftpsrcp isn't defined, the normal pseudo-random port

1849

number generator is used.

1856

number generator is used.

1850

1857

1851

Also, the environment variable tftpdstp is used to supply

1858

Also, the environment variable tftpdstp is used to supply

1852

the TFTP UDP destination port value. If tftpdstp isn't

1859

the TFTP UDP destination port value. If tftpdstp isn't

1853

defined, the normal port 69 is used.

1860

defined, the normal port 69 is used.

1854

1861

1855

The purpose for tftpsrcp is to allow a TFTP server to

1862

The purpose for tftpsrcp is to allow a TFTP server to

1856

blindly start the TFTP transfer using the pre-configured

1863

blindly start the TFTP transfer using the pre-configured

1857

target IP address and UDP port. This has the effect of

1864

target IP address and UDP port. This has the effect of

1858

"punching through" the (Windows XP) firewall, allowing

1865

"punching through" the (Windows XP) firewall, allowing

1859

the remainder of the TFTP transfer to proceed normally.

1866

the remainder of the TFTP transfer to proceed normally.

1860

A better solution is to properly configure the firewall,

1867

A better solution is to properly configure the firewall,

1861

but sometimes that is not allowed.

1868

but sometimes that is not allowed.

1862

1869

1863

- Show boot progress:

1870

- Show boot progress:

1864

CONFIG_SHOW_BOOT_PROGRESS

1871

CONFIG_SHOW_BOOT_PROGRESS

1865

1872

1866

Defining this option allows to add some board-

1873

Defining this option allows to add some board-

1867

specific code (calling a user-provided function

1874

specific code (calling a user-provided function

1868

"show_boot_progress(int)") that enables you to show

1875

"show_boot_progress(int)") that enables you to show

1869

the system's boot progress on some display (for

1876

the system's boot progress on some display (for

1870

example, some LED's) on your board. At the moment,

1877

example, some LED's) on your board. At the moment,

1871

the following checkpoints are implemented:

1878

the following checkpoints are implemented:

1872

1879

1873

- Automatic software updates via TFTP server

1880

- Automatic software updates via TFTP server

1874

CONFIG_UPDATE_TFTP

1881

CONFIG_UPDATE_TFTP

1875

CONFIG_UPDATE_TFTP_CNT_MAX

1882

CONFIG_UPDATE_TFTP_CNT_MAX

1876

CONFIG_UPDATE_TFTP_MSEC_MAX

1883

CONFIG_UPDATE_TFTP_MSEC_MAX

1877

1884

1878

These options enable and control the auto-update feature;

1885

These options enable and control the auto-update feature;

1879

for a more detailed description refer to doc/README.update.

1886

for a more detailed description refer to doc/README.update.

1880

1887

1881

- MTD Support (mtdparts command, UBI support)

1888

- MTD Support (mtdparts command, UBI support)

1882

CONFIG_MTD_DEVICE

1889

CONFIG_MTD_DEVICE

1883

1890

1884

Adds the MTD device infrastructure from the Linux kernel.

1891

Adds the MTD device infrastructure from the Linux kernel.

1885

Needed for mtdparts command support.

1892

Needed for mtdparts command support.

1886

1893

1887

CONFIG_MTD_PARTITIONS

1894

CONFIG_MTD_PARTITIONS

1888

1895

1889

Adds the MTD partitioning infrastructure from the Linux

1896

Adds the MTD partitioning infrastructure from the Linux

1890

kernel. Needed for UBI support.

1897

kernel. Needed for UBI support.

1891

1898

1892

Legacy uImage format:

1899

Legacy uImage format:

1893

1900

1894

Arg Where When

1901

Arg Where When

1895

1 common/cmd_bootm.c before attempting to boot an image

1902

1 common/cmd_bootm.c before attempting to boot an image

1896

-1 common/cmd_bootm.c Image header has bad magic number

1903

-1 common/cmd_bootm.c Image header has bad magic number

1897

2 common/cmd_bootm.c Image header has correct magic number

1904

2 common/cmd_bootm.c Image header has correct magic number

1898

-2 common/cmd_bootm.c Image header has bad checksum

1905

-2 common/cmd_bootm.c Image header has bad checksum

1899

3 common/cmd_bootm.c Image header has correct checksum

1906

3 common/cmd_bootm.c Image header has correct checksum

1900

-3 common/cmd_bootm.c Image data has bad checksum

1907

-3 common/cmd_bootm.c Image data has bad checksum

1901

4 common/cmd_bootm.c Image data has correct checksum

1908

4 common/cmd_bootm.c Image data has correct checksum

1902

-4 common/cmd_bootm.c Image is for unsupported architecture

1909

-4 common/cmd_bootm.c Image is for unsupported architecture

1903

5 common/cmd_bootm.c Architecture check OK

1910

5 common/cmd_bootm.c Architecture check OK

1904

-5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)

1911

-5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)

1905

6 common/cmd_bootm.c Image Type check OK

1912

6 common/cmd_bootm.c Image Type check OK

1906

-6 common/cmd_bootm.c gunzip uncompression error

1913

-6 common/cmd_bootm.c gunzip uncompression error

1907

-7 common/cmd_bootm.c Unimplemented compression type

1914

-7 common/cmd_bootm.c Unimplemented compression type

1908

7 common/cmd_bootm.c Uncompression OK

1915

7 common/cmd_bootm.c Uncompression OK

1909

8 common/cmd_bootm.c No uncompress/copy overwrite error

1916

8 common/cmd_bootm.c No uncompress/copy overwrite error

1910

-9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)

1917

-9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)

1911

1918

1912

9 common/image.c Start initial ramdisk verification

1919

9 common/image.c Start initial ramdisk verification

1913

-10 common/image.c Ramdisk header has bad magic number

1920

-10 common/image.c Ramdisk header has bad magic number

1914

-11 common/image.c Ramdisk header has bad checksum

1921

-11 common/image.c Ramdisk header has bad checksum

1915

10 common/image.c Ramdisk header is OK

1922

10 common/image.c Ramdisk header is OK

1916

-12 common/image.c Ramdisk data has bad checksum

1923

-12 common/image.c Ramdisk data has bad checksum

1917

11 common/image.c Ramdisk data has correct checksum

1924

11 common/image.c Ramdisk data has correct checksum

1918

12 common/image.c Ramdisk verification complete, start loading

1925

12 common/image.c Ramdisk verification complete, start loading

1919

-13 common/image.c Wrong Image Type (not PPC Linux ramdisk)

1926

-13 common/image.c Wrong Image Type (not PPC Linux ramdisk)

1920

13 common/image.c Start multifile image verification

1927

13 common/image.c Start multifile image verification

1921

14 common/image.c No initial ramdisk, no multifile, continue.

1928

14 common/image.c No initial ramdisk, no multifile, continue.

1922

1929

1923

15 lib_<arch>/bootm.c All preparation done, transferring control to OS

1930

15 lib_<arch>/bootm.c All preparation done, transferring control to OS

1924

1931

1925

-30 lib_ppc/board.c Fatal error, hang the system

1932

-30 lib_ppc/board.c Fatal error, hang the system

1926

-31 post/post.c POST test failed, detected by post_output_backlog()

1933

-31 post/post.c POST test failed, detected by post_output_backlog()

1927

-32 post/post.c POST test failed, detected by post_run_single()

1934

-32 post/post.c POST test failed, detected by post_run_single()

1928

1935

1929

34 common/cmd_doc.c before loading a Image from a DOC device

1936

34 common/cmd_doc.c before loading a Image from a DOC device

1930

-35 common/cmd_doc.c Bad usage of "doc" command

1937

-35 common/cmd_doc.c Bad usage of "doc" command

1931

35 common/cmd_doc.c correct usage of "doc" command

1938

35 common/cmd_doc.c correct usage of "doc" command

1932

-36 common/cmd_doc.c No boot device

1939

-36 common/cmd_doc.c No boot device

1933

36 common/cmd_doc.c correct boot device

1940

36 common/cmd_doc.c correct boot device

1934

-37 common/cmd_doc.c Unknown Chip ID on boot device

1941

-37 common/cmd_doc.c Unknown Chip ID on boot device

1935

37 common/cmd_doc.c correct chip ID found, device available

1942

37 common/cmd_doc.c correct chip ID found, device available

1936

-38 common/cmd_doc.c Read Error on boot device

1943

-38 common/cmd_doc.c Read Error on boot device

1937

38 common/cmd_doc.c reading Image header from DOC device OK

1944

38 common/cmd_doc.c reading Image header from DOC device OK

1938

-39 common/cmd_doc.c Image header has bad magic number

1945

-39 common/cmd_doc.c Image header has bad magic number

1939

39 common/cmd_doc.c Image header has correct magic number

1946

39 common/cmd_doc.c Image header has correct magic number

1940

-40 common/cmd_doc.c Error reading Image from DOC device

1947

-40 common/cmd_doc.c Error reading Image from DOC device

1941

40 common/cmd_doc.c Image header has correct magic number

1948

40 common/cmd_doc.c Image header has correct magic number

1942

41 common/cmd_ide.c before loading a Image from a IDE device

1949

41 common/cmd_ide.c before loading a Image from a IDE device

1943

-42 common/cmd_ide.c Bad usage of "ide" command

1950

-42 common/cmd_ide.c Bad usage of "ide" command

1944

42 common/cmd_ide.c correct usage of "ide" command

1951

42 common/cmd_ide.c correct usage of "ide" command

1945

-43 common/cmd_ide.c No boot device

1952

-43 common/cmd_ide.c No boot device

1946

43 common/cmd_ide.c boot device found

1953

43 common/cmd_ide.c boot device found

1947

-44 common/cmd_ide.c Device not available

1954

-44 common/cmd_ide.c Device not available

1948

44 common/cmd_ide.c Device available

1955

44 common/cmd_ide.c Device available

1949

-45 common/cmd_ide.c wrong partition selected

1956

-45 common/cmd_ide.c wrong partition selected

1950

45 common/cmd_ide.c partition selected

1957

45 common/cmd_ide.c partition selected

1951

-46 common/cmd_ide.c Unknown partition table

1958

-46 common/cmd_ide.c Unknown partition table

1952

46 common/cmd_ide.c valid partition table found

1959

46 common/cmd_ide.c valid partition table found

1953

-47 common/cmd_ide.c Invalid partition type

1960

-47 common/cmd_ide.c Invalid partition type

1954

47 common/cmd_ide.c correct partition type

1961

47 common/cmd_ide.c correct partition type

1955

-48 common/cmd_ide.c Error reading Image Header on boot device

1962

-48 common/cmd_ide.c Error reading Image Header on boot device

1956

48 common/cmd_ide.c reading Image Header from IDE device OK

1963

48 common/cmd_ide.c reading Image Header from IDE device OK

1957

-49 common/cmd_ide.c Image header has bad magic number

1964

-49 common/cmd_ide.c Image header has bad magic number

1958

49 common/cmd_ide.c Image header has correct magic number

1965

49 common/cmd_ide.c Image header has correct magic number

1959

-50 common/cmd_ide.c Image header has bad checksum

1966

-50 common/cmd_ide.c Image header has bad checksum

1960

50 common/cmd_ide.c Image header has correct checksum

1967

50 common/cmd_ide.c Image header has correct checksum

1961

-51 common/cmd_ide.c Error reading Image from IDE device

1968

-51 common/cmd_ide.c Error reading Image from IDE device

1962

51 common/cmd_ide.c reading Image from IDE device OK

1969

51 common/cmd_ide.c reading Image from IDE device OK

1963

52 common/cmd_nand.c before loading a Image from a NAND device

1970

52 common/cmd_nand.c before loading a Image from a NAND device

1964

-53 common/cmd_nand.c Bad usage of "nand" command

1971

-53 common/cmd_nand.c Bad usage of "nand" command

1965

53 common/cmd_nand.c correct usage of "nand" command

1972

53 common/cmd_nand.c correct usage of "nand" command

1966

-54 common/cmd_nand.c No boot device

1973

-54 common/cmd_nand.c No boot device

1967

54 common/cmd_nand.c boot device found

1974

54 common/cmd_nand.c boot device found

1968

-55 common/cmd_nand.c Unknown Chip ID on boot device

1975

-55 common/cmd_nand.c Unknown Chip ID on boot device

1969

55 common/cmd_nand.c correct chip ID found, device available

1976

55 common/cmd_nand.c correct chip ID found, device available

1970

-56 common/cmd_nand.c Error reading Image Header on boot device

1977

-56 common/cmd_nand.c Error reading Image Header on boot device

1971

56 common/cmd_nand.c reading Image Header from NAND device OK

1978

56 common/cmd_nand.c reading Image Header from NAND device OK

1972

-57 common/cmd_nand.c Image header has bad magic number

1979

-57 common/cmd_nand.c Image header has bad magic number

1973

57 common/cmd_nand.c Image header has correct magic number

1980

57 common/cmd_nand.c Image header has correct magic number

1974

-58 common/cmd_nand.c Error reading Image from NAND device

1981

-58 common/cmd_nand.c Error reading Image from NAND device

1975

58 common/cmd_nand.c reading Image from NAND device OK

1982

58 common/cmd_nand.c reading Image from NAND device OK

1976

1983

1977

-60 common/env_common.c Environment has a bad CRC, using default

1984

-60 common/env_common.c Environment has a bad CRC, using default

1978

1985

1979

64 net/eth.c starting with Ethernet configuration.

1986

64 net/eth.c starting with Ethernet configuration.

1980

-64 net/eth.c no Ethernet found.

1987

-64 net/eth.c no Ethernet found.

1981

65 net/eth.c Ethernet found.

1988

65 net/eth.c Ethernet found.

1982

1989

1983

-80 common/cmd_net.c usage wrong

1990

-80 common/cmd_net.c usage wrong

1984

80 common/cmd_net.c before calling NetLoop()

1991

80 common/cmd_net.c before calling NetLoop()

1985

-81 common/cmd_net.c some error in NetLoop() occurred

1992

-81 common/cmd_net.c some error in NetLoop() occurred

1986

81 common/cmd_net.c NetLoop() back without error

1993

81 common/cmd_net.c NetLoop() back without error

1987

-82 common/cmd_net.c size == 0 (File with size 0 loaded)

1994

-82 common/cmd_net.c size == 0 (File with size 0 loaded)

1988

82 common/cmd_net.c trying automatic boot

1995

82 common/cmd_net.c trying automatic boot

1989

83 common/cmd_net.c running "source" command

1996

83 common/cmd_net.c running "source" command

1990

-83 common/cmd_net.c some error in automatic boot or "source" command

1997

-83 common/cmd_net.c some error in automatic boot or "source" command

1991

84 common/cmd_net.c end without errors

1998

84 common/cmd_net.c end without errors

1992

1999

1993

FIT uImage format:

2000

FIT uImage format:

1994

2001

1995

Arg Where When

2002

Arg Where When

1996

100 common/cmd_bootm.c Kernel FIT Image has correct format

2003

100 common/cmd_bootm.c Kernel FIT Image has correct format

1997

-100 common/cmd_bootm.c Kernel FIT Image has incorrect format

2004

-100 common/cmd_bootm.c Kernel FIT Image has incorrect format

1998

101 common/cmd_bootm.c No Kernel subimage unit name, using configuration

2005

101 common/cmd_bootm.c No Kernel subimage unit name, using configuration

1999

-101 common/cmd_bootm.c Can't get configuration for kernel subimage

2006

-101 common/cmd_bootm.c Can't get configuration for kernel subimage

2000

102 common/cmd_bootm.c Kernel unit name specified

2007

102 common/cmd_bootm.c Kernel unit name specified

2001

-103 common/cmd_bootm.c Can't get kernel subimage node offset

2008

-103 common/cmd_bootm.c Can't get kernel subimage node offset

2002

103 common/cmd_bootm.c Found configuration node

2009

103 common/cmd_bootm.c Found configuration node

2003

104 common/cmd_bootm.c Got kernel subimage node offset

2010

104 common/cmd_bootm.c Got kernel subimage node offset

2004

-104 common/cmd_bootm.c Kernel subimage hash verification failed

2011

-104 common/cmd_bootm.c Kernel subimage hash verification failed

2005

105 common/cmd_bootm.c Kernel subimage hash verification OK

2012

105 common/cmd_bootm.c Kernel subimage hash verification OK

2006

-105 common/cmd_bootm.c Kernel subimage is for unsupported architecture

2013

-105 common/cmd_bootm.c Kernel subimage is for unsupported architecture

2007

106 common/cmd_bootm.c Architecture check OK

2014

106 common/cmd_bootm.c Architecture check OK

2008

-106 common/cmd_bootm.c Kernel subimage has wrong type

2015

-106 common/cmd_bootm.c Kernel subimage has wrong type

2009

107 common/cmd_bootm.c Kernel subimage type OK

2016

107 common/cmd_bootm.c Kernel subimage type OK

2010

-107 common/cmd_bootm.c Can't get kernel subimage data/size

2017

-107 common/cmd_bootm.c Can't get kernel subimage data/size

2011

108 common/cmd_bootm.c Got kernel subimage data/size

2018

108 common/cmd_bootm.c Got kernel subimage data/size

2012

-108 common/cmd_bootm.c Wrong image type (not legacy, FIT)

2019

-108 common/cmd_bootm.c Wrong image type (not legacy, FIT)

2013

-109 common/cmd_bootm.c Can't get kernel subimage type

2020

-109 common/cmd_bootm.c Can't get kernel subimage type

2014

-110 common/cmd_bootm.c Can't get kernel subimage comp

2021

-110 common/cmd_bootm.c Can't get kernel subimage comp

2015

-111 common/cmd_bootm.c Can't get kernel subimage os

2022

-111 common/cmd_bootm.c Can't get kernel subimage os

2016

-112 common/cmd_bootm.c Can't get kernel subimage load address

2023

-112 common/cmd_bootm.c Can't get kernel subimage load address

2017

-113 common/cmd_bootm.c Image uncompress/copy overwrite error

2024

-113 common/cmd_bootm.c Image uncompress/copy overwrite error

2018

2025

2019

120 common/image.c Start initial ramdisk verification

2026

120 common/image.c Start initial ramdisk verification

2020

-120 common/image.c Ramdisk FIT image has incorrect format

2027

-120 common/image.c Ramdisk FIT image has incorrect format

2021

121 common/image.c Ramdisk FIT image has correct format

2028

121 common/image.c Ramdisk FIT image has correct format

2022

122 common/image.c No ramdisk subimage unit name, using configuration

2029

122 common/image.c No ramdisk subimage unit name, using configuration

2023

-122 common/image.c Can't get configuration for ramdisk subimage

2030

-122 common/image.c Can't get configuration for ramdisk subimage

2024

123 common/image.c Ramdisk unit name specified

2031

123 common/image.c Ramdisk unit name specified

2025

-124 common/image.c Can't get ramdisk subimage node offset

2032

-124 common/image.c Can't get ramdisk subimage node offset

2026

125 common/image.c Got ramdisk subimage node offset

2033

125 common/image.c Got ramdisk subimage node offset

2027

-125 common/image.c Ramdisk subimage hash verification failed

2034

-125 common/image.c Ramdisk subimage hash verification failed

2028

126 common/image.c Ramdisk subimage hash verification OK

2035

126 common/image.c Ramdisk subimage hash verification OK

2029

-126 common/image.c Ramdisk subimage for unsupported architecture

2036

-126 common/image.c Ramdisk subimage for unsupported architecture

2030

127 common/image.c Architecture check OK

2037

127 common/image.c Architecture check OK

2031

-127 common/image.c Can't get ramdisk subimage data/size

2038

-127 common/image.c Can't get ramdisk subimage data/size

2032

128 common/image.c Got ramdisk subimage data/size

2039

128 common/image.c Got ramdisk subimage data/size

2033

129 common/image.c Can't get ramdisk load address

2040

129 common/image.c Can't get ramdisk load address

2034

-129 common/image.c Got ramdisk load address

2041

-129 common/image.c Got ramdisk load address

2035

2042

2036

-130 common/cmd_doc.c Incorrect FIT image format

2043

-130 common/cmd_doc.c Incorrect FIT image format

2037

131 common/cmd_doc.c FIT image format OK

2044

131 common/cmd_doc.c FIT image format OK

2038

2045

2039

-140 common/cmd_ide.c Incorrect FIT image format

2046

-140 common/cmd_ide.c Incorrect FIT image format

2040

141 common/cmd_ide.c FIT image format OK

2047

141 common/cmd_ide.c FIT image format OK

2041

2048

2042

-150 common/cmd_nand.c Incorrect FIT image format

2049

-150 common/cmd_nand.c Incorrect FIT image format

2043

151 common/cmd_nand.c FIT image format OK

2050

151 common/cmd_nand.c FIT image format OK

2044

2051

2045

2052

2046

Modem Support:

2053

Modem Support:

2047

--------------

2054

--------------

2048

2055

2049

[so far only for SMDK2400 and TRAB boards]

2056

[so far only for SMDK2400 and TRAB boards]

2050

2057

2051

- Modem support enable:

2058

- Modem support enable:

2052

CONFIG_MODEM_SUPPORT

2059

CONFIG_MODEM_SUPPORT

2053

2060

2054

- RTS/CTS Flow control enable:

2061

- RTS/CTS Flow control enable:

2055

CONFIG_HWFLOW

2062

CONFIG_HWFLOW

2056

2063

2057

- Modem debug support:

2064

- Modem debug support:

2058

CONFIG_MODEM_SUPPORT_DEBUG

2065

CONFIG_MODEM_SUPPORT_DEBUG

2059

2066

2060

Enables debugging stuff (char screen[1024], dbg())

2067

Enables debugging stuff (char screen[1024], dbg())

2061

for modem support. Useful only with BDI2000.

2068

for modem support. Useful only with BDI2000.

2062

2069

2063

- Interrupt support (PPC):

2070

- Interrupt support (PPC):

2064

2071

2065

There are common interrupt_init() and timer_interrupt()

2072

There are common interrupt_init() and timer_interrupt()

2066

for all PPC archs. interrupt_init() calls interrupt_init_cpu()

2073

for all PPC archs. interrupt_init() calls interrupt_init_cpu()

2067

for CPU specific initialization. interrupt_init_cpu()

2074

for CPU specific initialization. interrupt_init_cpu()

2068

should set decrementer_count to appropriate value. If

2075

should set decrementer_count to appropriate value. If

2069

CPU resets decrementer automatically after interrupt

2076

CPU resets decrementer automatically after interrupt

2070

(ppc4xx) it should set decrementer_count to zero.

2077

(ppc4xx) it should set decrementer_count to zero.

2071

timer_interrupt() calls timer_interrupt_cpu() for CPU

2078

timer_interrupt() calls timer_interrupt_cpu() for CPU

2072

specific handling. If board has watchdog / status_led

2079

specific handling. If board has watchdog / status_led

2073

/ other_activity_monitor it works automatically from

2080

/ other_activity_monitor it works automatically from

2074

general timer_interrupt().

2081

general timer_interrupt().

2075

2082

2076

- General:

2083

- General:

2077

2084

2078

In the target system modem support is enabled when a

2085

In the target system modem support is enabled when a

2079

specific key (key combination) is pressed during

2086

specific key (key combination) is pressed during

2080

power-on. Otherwise U-Boot will boot normally

2087

power-on. Otherwise U-Boot will boot normally

2081

(autoboot). The key_pressed() function is called from

2088

(autoboot). The key_pressed() function is called from

2082

board_init(). Currently key_pressed() is a dummy

2089

board_init(). Currently key_pressed() is a dummy

2083

function, returning 1 and thus enabling modem

2090

function, returning 1 and thus enabling modem

2084

initialization.

2091

initialization.

2085

2092

2086

If there are no modem init strings in the

2093

If there are no modem init strings in the

2087

environment, U-Boot proceed to autoboot; the

2094

environment, U-Boot proceed to autoboot; the

2088

previous output (banner, info printfs) will be

2095

previous output (banner, info printfs) will be

2089

suppressed, though.

2096

suppressed, though.

2090

2097

2091

GITLAB

Reset i2c slave devices during init on mpc5xxx cpus

 #
 # (C) Copyright 2000 - 2008
 # Wolfgang Denk, DENX Software Engineering, wd@denx.de.
 #
 # See file CREDITS for list of people who contributed to this
 # project.
 #
 # This program is free software; you can redistribute it and/or
 # modify it under the terms of the GNU General Public License as
 # published by the Free Software Foundation; either version 2 of
 # the License, or (at your option) any later version.
 #
 # This program is distributed in the hope that it will be useful,
 # but WITHOUT ANY WARRANTY; without even the implied warranty of
 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.	See the
 # GNU General Public License for more details.
 #
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
 # Foundation, Inc., 59 Temple Place, Suite 330, Boston,
 # MA 02111-1307 USA
 #
 Summary:
 ========
 This directory contains the source code for U-Boot, a boot loader for
 Embedded boards based on PowerPC, ARM, MIPS and several other
 processors, which can be installed in a boot ROM and used to
 initialize and test the hardware or to download and run application
 code.
 The development of U-Boot is closely related to Linux: some parts of
 the source code originate in the Linux source tree, we have some
 header files in common, and special provision has been made to
 support booting of Linux images.
 Some attention has been paid to make this software easily
 configurable and extendable. For instance, all monitor commands are
 implemented with the same call interface, so that it's very easy to
 add new commands. Also, instead of permanently adding rarely used
 code (for instance hardware test utilities) to the monitor, you can
 load and run it dynamically.
 Status:
 =======
 In general, all boards for which a configuration option exists in the
 Makefile have been tested to some extent and can be considered
 "working". In fact, many of them are used in production systems.
 In case of problems see the CHANGELOG and CREDITS files to find out
 who contributed the specific port. The MAINTAINERS file lists board
 maintainers.
 Where to get help:
 ==================
 In case you have questions about, problems with or contributions for
 U-Boot you should send a message to the U-Boot mailing list at
 <u-boot@lists.denx.de>. There is also an archive of previous traffic
 on the mailing list - please search the archive before asking FAQ's.
 Please see http://lists.denx.de/pipermail/u-boot and
 http://dir.gmane.org/gmane.comp.boot-loaders.u-boot
 Where to get source code:
 =========================
 The U-Boot source code is maintained in the git repository at
 git://www.denx.de/git/u-boot.git ; you can browse it online at
 http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary
 The "snapshot" links on this page allow you to download tarballs of
 any version you might be interested in. Official releases are also
 available for FTP download from the ftp://ftp.denx.de/pub/u-boot/
 directory.
 Pre-built (and tested) images are available from
 ftp://ftp.denx.de/pub/u-boot/images/
 Where we come from:
 ===================
 - start from 8xxrom sources
 - create PPCBoot project (http://sourceforge.net/projects/ppcboot)
 - clean up code
 - make it easier to add custom boards
 - make it possible to add other [PowerPC] CPUs
 - extend functions, especially:
   * Provide extended interface to Linux boot loader
   * S-Record download
   * network boot
   * PCMCIA / CompactFlash / ATA disk / SCSI ... boot
 - create ARMBoot project (http://sourceforge.net/projects/armboot)
 - add other CPU families (starting with ARM)
 - create U-Boot project (http://sourceforge.net/projects/u-boot)
 - current project page: see http://www.denx.de/wiki/U-Boot
 Names and Spelling:
 ===================
 The "official" name of this project is "Das U-Boot". The spelling
 "U-Boot" shall be used in all written text (documentation, comments
 in source files etc.). Example:
 	This is the README file for the U-Boot project.
 File names etc. shall be based on the string "u-boot". Examples:
 	include/asm-ppc/u-boot.h
 	#include <asm/u-boot.h>
 Variable names, preprocessor constants etc. shall be either based on
 the string "u_boot" or on "U_BOOT". Example:
 	U_BOOT_VERSION		u_boot_logo
 	IH_OS_U_BOOT		u_boot_hush_start
 Versioning:
 ===========
 U-Boot uses a 3 level version number containing a version, a
 sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2",
 sub-version "34", and patchlevel "4".
 The patchlevel is used to indicate certain stages of development
 between released versions, i. e. officially released versions of
 U-Boot will always have a patchlevel of "0".
 Directory Hierarchy:
 ====================
 - board		Board dependent files
 - common	Misc architecture independent functions
 - cpu		CPU specific files
   - 74xx_7xx	Files specific to Freescale MPC74xx and 7xx CPUs
   - arm720t	Files specific to ARM 720 CPUs
   - arm920t	Files specific to ARM 920 CPUs
     - at91rm9200 Files specific to Atmel AT91RM9200 CPU
     - imx	Files specific to Freescale MC9328 i.MX CPUs
     - s3c24x0	Files specific to Samsung S3C24X0 CPUs
   - arm925t	Files specific to ARM 925 CPUs
   - arm926ejs	Files specific to ARM 926 CPUs
   - arm1136	Files specific to ARM 1136 CPUs
   - at32ap	Files specific to Atmel AVR32 AP CPUs
   - blackfin	Files specific to Analog Devices Blackfin CPUs
   - i386	Files specific to i386 CPUs
   - ixp		Files specific to Intel XScale IXP CPUs
   - leon2	Files specific to Gaisler LEON2 SPARC CPU
   - leon3	Files specific to Gaisler LEON3 SPARC CPU
   - mcf52x2	Files specific to Freescale ColdFire MCF52x2 CPUs
   - mcf5227x	Files specific to Freescale ColdFire MCF5227x CPUs
   - mcf532x	Files specific to Freescale ColdFire MCF5329 CPUs
   - mcf5445x	Files specific to Freescale ColdFire MCF5445x CPUs
   - mcf547x_8x	Files specific to Freescale ColdFire MCF547x_8x CPUs
   - mips	Files specific to MIPS CPUs
   - mpc5xx	Files specific to Freescale MPC5xx  CPUs
   - mpc5xxx	Files specific to Freescale MPC5xxx CPUs
   - mpc8xx	Files specific to Freescale MPC8xx  CPUs
   - mpc8220	Files specific to Freescale MPC8220 CPUs
   - mpc824x	Files specific to Freescale MPC824x CPUs
   - mpc8260	Files specific to Freescale MPC8260 CPUs
   - mpc85xx	Files specific to Freescale MPC85xx CPUs
   - nios	Files specific to Altera NIOS CPUs
   - nios2	Files specific to Altera Nios-II CPUs
   - ppc4xx	Files specific to AMCC PowerPC 4xx CPUs
   - pxa		Files specific to Intel XScale PXA CPUs
   - s3c44b0	Files specific to Samsung S3C44B0 CPUs
   - sa1100	Files specific to Intel StrongARM SA1100 CPUs
 - disk		Code for disk drive partition handling
 - doc		Documentation (don't expect too much)
 - drivers	Commonly used device drivers
 - dtt		Digital Thermometer and Thermostat drivers
 - examples	Example code for standalone applications, etc.
 - include	Header Files
 - lib_arm	Files generic to ARM	 architecture
 - lib_avr32	Files generic to AVR32	 architecture
 - lib_blackfin	Files generic to Blackfin architecture
 - lib_generic	Files generic to all	 architectures
 - lib_i386	Files generic to i386	 architecture
 - lib_m68k	Files generic to m68k	 architecture
 - lib_mips	Files generic to MIPS	 architecture
 - lib_nios	Files generic to NIOS	 architecture
 - lib_ppc	Files generic to PowerPC architecture
 - lib_sparc	Files generic to SPARC	 architecture
 - libfdt	Library files to support flattened device trees
 - net		Networking code
 - post		Power On Self Test
 - rtc		Real Time Clock drivers
 - tools		Tools to build S-Record or U-Boot images, etc.
 Software Configuration:
 =======================
 Configuration is usually done using C preprocessor defines; the
 rationale behind that is to avoid dead code whenever possible.
 There are two classes of configuration variables:
 * Configuration _OPTIONS_:
   These are selectable by the user and have names beginning with
   "CONFIG_".
 * Configuration _SETTINGS_:
   These depend on the hardware etc. and should not be meddled with if
   you don't know what you're doing; they have names beginning with
   "CONFIG_SYS_".
 Later we will add a configuration tool - probably similar to or even
 identical to what's used for the Linux kernel. Right now, we have to
 do the configuration by hand, which means creating some symbolic
 links and editing some configuration files. We use the TQM8xxL boards
 as an example here.
 Selection of Processor Architecture and Board Type:
 ---------------------------------------------------
 For all supported boards there are ready-to-use default
 configurations available; just type "make <board_name>_config".
 Example: For a TQM823L module type:
 	cd u-boot
 	make TQM823L_config
 For the Cogent platform, you need to specify the CPU type as well;
 e.g. "make cogent_mpc8xx_config". And also configure the cogent
 directory according to the instructions in cogent/README.
 Configuration Options:
 ----------------------
 Configuration depends on the combination of board and CPU type; all
 such information is kept in a configuration file
 "include/configs/<board_name>.h".
 Example: For a TQM823L module, all configuration settings are in
 "include/configs/TQM823L.h".
 Many of the options are named exactly as the corresponding Linux
 kernel configuration options. The intention is to make it easier to
 build a config tool - later.
 The following options need to be configured:
 - CPU Type:	Define exactly one, e.g. CONFIG_MPC85XX.
 - Board Type:	Define exactly one, e.g. CONFIG_MPC8540ADS.
 - CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)
 		Define exactly one, e.g. CONFIG_ATSTK1002
 - CPU Module Type: (if CONFIG_COGENT is defined)
 		Define exactly one of
 		CONFIG_CMA286_60_OLD
 --- FIXME --- not tested yet:
 		CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
 		CONFIG_CMA287_23, CONFIG_CMA287_50
 - Motherboard Type: (if CONFIG_COGENT is defined)
 		Define exactly one of
 		CONFIG_CMA101, CONFIG_CMA102
 - Motherboard I/O Modules: (if CONFIG_COGENT is defined)
 		Define one or more of
 		CONFIG_CMA302
 - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
 		Define one or more of
 		CONFIG_LCD_HEARTBEAT	- update a character position on
 					  the LCD display every second with
 					  a "rotator" |\-/|\-/
 - Board flavour: (if CONFIG_MPC8260ADS is defined)
 		CONFIG_ADSTYPE
 		Possible values are:
 			CONFIG_SYS_8260ADS	- original MPC8260ADS
 			CONFIG_SYS_8266ADS	- MPC8266ADS
 			CONFIG_SYS_PQ2FADS	- PQ2FADS-ZU or PQ2FADS-VR
 			CONFIG_SYS_8272ADS	- MPC8272ADS
 - MPC824X Family Member (if CONFIG_MPC824X is defined)
 		Define exactly one of
 		CONFIG_MPC8240, CONFIG_MPC8245
 - 8xx CPU Options: (if using an MPC8xx CPU)
 		CONFIG_8xx_GCLK_FREQ	- deprecated: CPU clock if
 					  get_gclk_freq() cannot work
 					  e.g. if there is no 32KHz
 					  reference PIT/RTC clock
 		CONFIG_8xx_OSCLK	- PLL input clock (either EXTCLK
 					  or XTAL/EXTAL)
 - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
 		CONFIG_SYS_8xx_CPUCLK_MIN
 		CONFIG_SYS_8xx_CPUCLK_MAX
 		CONFIG_8xx_CPUCLK_DEFAULT
 			See doc/README.MPC866
 		CONFIG_SYS_MEASURE_CPUCLK
 		Define this to measure the actual CPU clock instead
 		of relying on the correctness of the configured
 		values. Mostly useful for board bringup to make sure
 		the PLL is locked at the intended frequency. Note
 		that this requires a (stable) reference clock (32 kHz
 		RTC clock or CONFIG_SYS_8XX_XIN)
 		CONFIG_SYS_DELAYED_ICACHE
 		Define this option if you want to enable the
 		ICache only when Code runs from RAM.
 - Intel Monahans options:
 		CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO
 		Defines the Monahans run mode to oscillator
 		ratio. Valid values are 8, 16, 24, 31. The core
 		frequency is this value multiplied by 13 MHz.
 		CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO
 		Defines the Monahans turbo mode to oscillator
 		ratio. Valid values are 1 (default if undefined) and
 		2. The core frequency as calculated above is multiplied
 		by this value.
 - Linux Kernel Interface:
 		CONFIG_CLOCKS_IN_MHZ
 		U-Boot stores all clock information in Hz
 		internally. For binary compatibility with older Linux
 		kernels (which expect the clocks passed in the
 		bd_info data to be in MHz) the environment variable
 		"clocks_in_mhz" can be defined so that U-Boot
 		converts clock data to MHZ before passing it to the
 		Linux kernel.
 		When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
 		"clocks_in_mhz=1" is automatically included in the
 		default environment.
 		CONFIG_MEMSIZE_IN_BYTES		[relevant for MIPS only]
 		When transferring memsize parameter to linux, some versions
 		expect it to be in bytes, others in MB.
 		Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
 		CONFIG_OF_LIBFDT
 		New kernel versions are expecting firmware settings to be
 		passed using flattened device trees (based on open firmware
 		concepts).
 		CONFIG_OF_LIBFDT
 		 * New libfdt-based support
 		 * Adds the "fdt" command
 		 * The bootm command automatically updates the fdt
 		OF_CPU - The proper name of the cpus node.
 		OF_SOC - The proper name of the soc node.
 		OF_TBCLK - The timebase frequency.
 		OF_STDOUT_PATH - The path to the console device
 		boards with QUICC Engines require OF_QE to set UCC MAC
 		addresses
 		CONFIG_OF_BOARD_SETUP
 		Board code has addition modification that it wants to make
 		to the flat device tree before handing it off to the kernel
 		CONFIG_OF_BOOT_CPU
 		This define fills in the correct boot CPU in the boot
 		param header, the default value is zero if undefined.
 - vxWorks boot parameters:
 		bootvx constructs a valid bootline using the following
 		environments variables: bootfile, ipaddr, serverip, hostname.
 		It loads the vxWorks image pointed bootfile.
 		CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name
 		CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address
 		CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server
 		CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters
 		CONFIG_SYS_VXWORKS_ADD_PARAMS
 		Add it at the end of the bootline. E.g "u=username pw=secret"
 		Note: If a "bootargs" environment is defined, it will overwride
 		the defaults discussed just above.
 - Serial Ports:
 		CONFIG_PL010_SERIAL
 		Define this if you want support for Amba PrimeCell PL010 UARTs.
 		CONFIG_PL011_SERIAL
 		Define this if you want support for Amba PrimeCell PL011 UARTs.
 		CONFIG_PL011_CLOCK
 		If you have Amba PrimeCell PL011 UARTs, set this variable to
 		the clock speed of the UARTs.
 		CONFIG_PL01x_PORTS
 		If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
 		define this to a list of base addresses for each (supported)
 		port. See e.g. include/configs/versatile.h
 - Console Interface:
 		Depending on board, define exactly one serial port
 		(like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
 		CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
 		console by defining CONFIG_8xx_CONS_NONE
 		Note: if CONFIG_8xx_CONS_NONE is defined, the serial
 		port routines must be defined elsewhere
 		(i.e. serial_init(), serial_getc(), ...)
 		CONFIG_CFB_CONSOLE
 		Enables console device for a color framebuffer. Needs following
 		defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)
 			VIDEO_FB_LITTLE_ENDIAN	graphic memory organisation
 						(default big endian)
 			VIDEO_HW_RECTFILL	graphic chip supports
 						rectangle fill
 						(cf. smiLynxEM)
 			VIDEO_HW_BITBLT		graphic chip supports
 						bit-blit (cf. smiLynxEM)
 			VIDEO_VISIBLE_COLS	visible pixel columns
 						(cols=pitch)
 			VIDEO_VISIBLE_ROWS	visible pixel rows
 			VIDEO_PIXEL_SIZE	bytes per pixel
 			VIDEO_DATA_FORMAT	graphic data format
 						(0-5, cf. cfb_console.c)
 			VIDEO_FB_ADRS		framebuffer address
 			VIDEO_KBD_INIT_FCT	keyboard int fct
 						(i.e. i8042_kbd_init())
 			VIDEO_TSTC_FCT		test char fct
 						(i.e. i8042_tstc)
 			VIDEO_GETC_FCT		get char fct
 						(i.e. i8042_getc)
 			CONFIG_CONSOLE_CURSOR	cursor drawing on/off
 						(requires blink timer
 						cf. i8042.c)
 			CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
 			CONFIG_CONSOLE_TIME	display time/date info in
 						upper right corner
 						(requires CONFIG_CMD_DATE)
 			CONFIG_VIDEO_LOGO	display Linux logo in
 						upper left corner
 			CONFIG_VIDEO_BMP_LOGO	use bmp_logo.h instead of
 						linux_logo.h for logo.
 						Requires CONFIG_VIDEO_LOGO
 			CONFIG_CONSOLE_EXTRA_INFO
 						additional board info beside
 						the logo
 		When CONFIG_CFB_CONSOLE is defined, video console is
 		default i/o. Serial console can be forced with
 		environment 'console=serial'.
 		When CONFIG_SILENT_CONSOLE is defined, all console
 		messages (by U-Boot and Linux!) can be silenced with
 		the "silent" environment variable. See
 		doc/README.silent for more information.
 - Console Baudrate:
 		CONFIG_BAUDRATE - in bps
 		Select one of the baudrates listed in
 		CONFIG_SYS_BAUDRATE_TABLE, see below.
 		CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale
 - Console Rx buffer length
 		With CONFIG_SYS_SMC_RXBUFLEN it is possible to define
 		the maximum receive buffer length for the SMC.
 		This option is actual only for 82xx and 8xx possible.
 		If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE
 		must be defined, to setup the maximum idle timeout for
 		the SMC.
 - Interrupt driven serial port input:
 		CONFIG_SERIAL_SOFTWARE_FIFO
 		PPC405GP only.
 		Use an interrupt handler for receiving data on the
 		serial port. It also enables using hardware handshake
 		(RTS/CTS) and UART's built-in FIFO. Set the number of
 		bytes the interrupt driven input buffer should have.
 		Leave undefined to disable this feature, including
 		disable the buffer and hardware handshake.
 - Console UART Number:
 		CONFIG_UART1_CONSOLE
 		AMCC PPC4xx only.
 		If defined internal UART1 (and not UART0) is used
 		as default U-Boot console.
 - Boot Delay:	CONFIG_BOOTDELAY - in seconds
 		Delay before automatically booting the default image;
 		set to -1 to disable autoboot.
 		See doc/README.autoboot for these options that
 		work with CONFIG_BOOTDELAY. None are required.
 		CONFIG_BOOT_RETRY_TIME
 		CONFIG_BOOT_RETRY_MIN
 		CONFIG_AUTOBOOT_KEYED
 		CONFIG_AUTOBOOT_PROMPT
 		CONFIG_AUTOBOOT_DELAY_STR
 		CONFIG_AUTOBOOT_STOP_STR
 		CONFIG_AUTOBOOT_DELAY_STR2
 		CONFIG_AUTOBOOT_STOP_STR2
 		CONFIG_ZERO_BOOTDELAY_CHECK
 		CONFIG_RESET_TO_RETRY
 - Autoboot Command:
 		CONFIG_BOOTCOMMAND
 		Only needed when CONFIG_BOOTDELAY is enabled;
 		define a command string that is automatically executed
 		when no character is read on the console interface
 		within "Boot Delay" after reset.
 		CONFIG_BOOTARGS
 		This can be used to pass arguments to the bootm
 		command. The value of CONFIG_BOOTARGS goes into the
 		environment value "bootargs".
 		CONFIG_RAMBOOT and CONFIG_NFSBOOT
 		The value of these goes into the environment as
 		"ramboot" and "nfsboot" respectively, and can be used
 		as a convenience, when switching between booting from
 		RAM and NFS.
 - Pre-Boot Commands:
 		CONFIG_PREBOOT
 		When this option is #defined, the existence of the
 		environment variable "preboot" will be checked
 		immediately before starting the CONFIG_BOOTDELAY
 		countdown and/or running the auto-boot command resp.
 		entering interactive mode.
 		This feature is especially useful when "preboot" is
 		automatically generated or modified. For an example
 		see the LWMON board specific code: here "preboot" is
 		modified when the user holds down a certain
 		combination of keys on the (special) keyboard when
 		booting the systems
 - Serial Download Echo Mode:
 		CONFIG_LOADS_ECHO
 		If defined to 1, all characters received during a
 		serial download (using the "loads" command) are
 		echoed back. This might be needed by some terminal
 		emulations (like "cu"), but may as well just take
 		time on others. This setting #define's the initial
 		value of the "loads_echo" environment variable.
 - Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
 		CONFIG_KGDB_BAUDRATE
 		Select one of the baudrates listed in
 		CONFIG_SYS_BAUDRATE_TABLE, see below.
 - Monitor Functions:
 		Monitor commands can be included or excluded
 		from the build by using the #include files
 		"config_cmd_all.h" and #undef'ing unwanted
 		commands, or using "config_cmd_default.h"
 		and augmenting with additional #define's
 		for wanted commands.
 		The default command configuration includes all commands
 		except those marked below with a "*".
 		CONFIG_CMD_ASKENV	* ask for env variable
 		CONFIG_CMD_BDI		  bdinfo
 		CONFIG_CMD_BEDBUG	* Include BedBug Debugger
 		CONFIG_CMD_BMP		* BMP support
 		CONFIG_CMD_BSP		* Board specific commands
 		CONFIG_CMD_BOOTD	  bootd
 		CONFIG_CMD_CACHE	* icache, dcache
 		CONFIG_CMD_CONSOLE	  coninfo
 		CONFIG_CMD_DATE		* support for RTC, date/time...
 		CONFIG_CMD_DHCP		* DHCP support
 		CONFIG_CMD_DIAG		* Diagnostics
 		CONFIG_CMD_DS4510	* ds4510 I2C gpio commands
 		CONFIG_CMD_DS4510_INFO	* ds4510 I2C info command
 		CONFIG_CMD_DS4510_MEM	* ds4510 I2C eeprom/sram commansd
 		CONFIG_CMD_DS4510_RST	* ds4510 I2C rst command
 		CONFIG_CMD_DTT		* Digital Therm and Thermostat
 		CONFIG_CMD_ECHO		  echo arguments
 		CONFIG_CMD_EEPROM	* EEPROM read/write support
 		CONFIG_CMD_ELF		* bootelf, bootvx
 		CONFIG_CMD_SAVEENV	  saveenv
 		CONFIG_CMD_FDC		* Floppy Disk Support
 		CONFIG_CMD_FAT		* FAT partition support
 		CONFIG_CMD_FDOS		* Dos diskette Support
 		CONFIG_CMD_FLASH	  flinfo, erase, protect
 		CONFIG_CMD_FPGA		  FPGA device initialization support
 		CONFIG_CMD_HWFLOW	* RTS/CTS hw flow control
 		CONFIG_CMD_I2C		* I2C serial bus support
 		CONFIG_CMD_IDE		* IDE harddisk support
 		CONFIG_CMD_IMI		  iminfo
 		CONFIG_CMD_IMLS		  List all found images
 		CONFIG_CMD_IMMAP	* IMMR dump support
 		CONFIG_CMD_IRQ		* irqinfo
 		CONFIG_CMD_ITEST	  Integer/string test of 2 values
 		CONFIG_CMD_JFFS2	* JFFS2 Support
 		CONFIG_CMD_KGDB		* kgdb
 		CONFIG_CMD_LOADB	  loadb
 		CONFIG_CMD_LOADS	  loads
 		CONFIG_CMD_MD5SUM	  print md5 message digest
 					  (requires CONFIG_CMD_MEMORY and CONFIG_MD5)
 		CONFIG_CMD_MEMORY	  md, mm, nm, mw, cp, cmp, crc, base,
 					  loop, loopw, mtest
 		CONFIG_CMD_MISC		  Misc functions like sleep etc
 		CONFIG_CMD_MMC		* MMC memory mapped support
 		CONFIG_CMD_MII		* MII utility commands
 		CONFIG_CMD_MTDPARTS	* MTD partition support
 		CONFIG_CMD_NAND		* NAND support
 		CONFIG_CMD_NET		  bootp, tftpboot, rarpboot
 		CONFIG_CMD_PCA953X	* PCA953x I2C gpio commands
 		CONFIG_CMD_PCA953X_INFO	* PCA953x I2C gpio info command
 		CONFIG_CMD_PCI		* pciinfo
 		CONFIG_CMD_PCMCIA		* PCMCIA support
 		CONFIG_CMD_PING		* send ICMP ECHO_REQUEST to network
 					  host
 		CONFIG_CMD_PORTIO	* Port I/O
 		CONFIG_CMD_REGINFO	* Register dump
 		CONFIG_CMD_RUN		  run command in env variable
 		CONFIG_CMD_SAVES	* save S record dump
 		CONFIG_CMD_SCSI		* SCSI Support
 		CONFIG_CMD_SDRAM	* print SDRAM configuration information
 					  (requires CONFIG_CMD_I2C)
 		CONFIG_CMD_SETGETDCR	  Support for DCR Register access
 					  (4xx only)
 		CONFIG_CMD_SHA1		  print sha1 memory digest
 					  (requires CONFIG_CMD_MEMORY)
 		CONFIG_CMD_SOURCE	  "source" command Support
 		CONFIG_CMD_SPI		* SPI serial bus support
 		CONFIG_CMD_USB		* USB support
 		CONFIG_CMD_VFD		* VFD support (TRAB)
 		CONFIG_CMD_CDP		* Cisco Discover Protocol support
 		CONFIG_CMD_FSL		* Microblaze FSL support
 		EXAMPLE: If you want all functions except of network
 		support you can write:
 		#include "config_cmd_all.h"
 		#undef CONFIG_CMD_NET
 	Other Commands:
 		fdt (flattened device tree) command: CONFIG_OF_LIBFDT
 	Note:	Don't enable the "icache" and "dcache" commands
 		(configuration option CONFIG_CMD_CACHE) unless you know
 		what you (and your U-Boot users) are doing. Data
 		cache cannot be enabled on systems like the 8xx or
 		8260 (where accesses to the IMMR region must be
 		uncached), and it cannot be disabled on all other
 		systems where we (mis-) use the data cache to hold an
 		initial stack and some data.
 		XXX - this list needs to get updated!
 - Watchdog:
 		CONFIG_WATCHDOG
 		If this variable is defined, it enables watchdog
 		support. There must be support in the platform specific
 		code for a watchdog. For the 8xx and 8260 CPUs, the
 		SIU Watchdog feature is enabled in the SYPCR
 		register.
 - U-Boot Version:
 		CONFIG_VERSION_VARIABLE
 		If this variable is defined, an environment variable
 		named "ver" is created by U-Boot showing the U-Boot
 		version as printed by the "version" command.
 		This variable is readonly.
 - Real-Time Clock:
 		When CONFIG_CMD_DATE is selected, the type of the RTC
 		has to be selected, too. Define exactly one of the
 		following options:
 		CONFIG_RTC_MPC8xx	- use internal RTC of MPC8xx
 		CONFIG_RTC_PCF8563	- use Philips PCF8563 RTC
 		CONFIG_RTC_MC13783	- use MC13783 RTC
 		CONFIG_RTC_MC146818	- use MC146818 RTC
 		CONFIG_RTC_DS1307	- use Maxim, Inc. DS1307 RTC
 		CONFIG_RTC_DS1337	- use Maxim, Inc. DS1337 RTC
 		CONFIG_RTC_DS1338	- use Maxim, Inc. DS1338 RTC
 		CONFIG_RTC_DS164x	- use Dallas DS164x RTC
 		CONFIG_RTC_ISL1208	- use Intersil ISL1208 RTC
 		CONFIG_RTC_MAX6900	- use Maxim, Inc. MAX6900 RTC
 		CONFIG_SYS_RTC_DS1337_NOOSC	- Turn off the OSC output for DS1337
 		Note that if the RTC uses I2C, then the I2C interface
 		must also be configured. See I2C Support, below.
 - GPIO Support:
 		CONFIG_PCA953X		- use NXP's PCA953X series I2C GPIO
 		CONFIG_PCA953X_INFO	- enable pca953x info command
 		Note that if the GPIO device uses I2C, then the I2C interface
 		must also be configured. See I2C Support, below.
 - Timestamp Support:
 		When CONFIG_TIMESTAMP is selected, the timestamp
 		(date and time) of an image is printed by image
 		commands like bootm or iminfo. This option is
 		automatically enabled when you select CONFIG_CMD_DATE .
 - Partition Support:
 		CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
 		and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_PARTITION
 		If IDE or SCSI support is enabled (CONFIG_CMD_IDE or
 		CONFIG_CMD_SCSI) you must configure support for at
 		least one partition type as well.
 - IDE Reset method:
 		CONFIG_IDE_RESET_ROUTINE - this is defined in several
 		board configurations files but used nowhere!
 		CONFIG_IDE_RESET - is this is defined, IDE Reset will
 		be performed by calling the function
 			ide_set_reset(int reset)
 		which has to be defined in a board specific file
 - ATAPI Support:
 		CONFIG_ATAPI
 		Set this to enable ATAPI support.
 - LBA48 Support
 		CONFIG_LBA48
 		Set this to enable support for disks larger than 137GB
 		Also look at CONFIG_SYS_64BIT_LBA ,CONFIG_SYS_64BIT_VSPRINTF and CONFIG_SYS_64BIT_STRTOUL
 		Whithout these , LBA48 support uses 32bit variables and will 'only'
 		support disks up to 2.1TB.
 		CONFIG_SYS_64BIT_LBA:
 			When enabled, makes the IDE subsystem use 64bit sector addresses.
 			Default is 32bit.
 - SCSI Support:
 		At the moment only there is only support for the
 		SYM53C8XX SCSI controller; define
 		CONFIG_SCSI_SYM53C8XX to enable it.
 		CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
 		CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
 		CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
 		maximum numbers of LUNs, SCSI ID's and target
 		devices.
 		CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
 - NETWORK Support (PCI):
 		CONFIG_E1000
 		Support for Intel 8254x gigabit chips.
 		CONFIG_E1000_FALLBACK_MAC
 		default MAC for empty EEPROM after production.
 		CONFIG_EEPRO100
 		Support for Intel 82557/82559/82559ER chips.
 		Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM
 		write routine for first time initialisation.
 		CONFIG_TULIP
 		Support for Digital 2114x chips.
 		Optional CONFIG_TULIP_SELECT_MEDIA for board specific
 		modem chip initialisation (KS8761/QS6611).
 		CONFIG_NATSEMI
 		Support for National dp83815 chips.
 		CONFIG_NS8382X
 		Support for National dp8382[01] gigabit chips.
 - NETWORK Support (other):
 		CONFIG_DRIVER_LAN91C96
 		Support for SMSC's LAN91C96 chips.
 			CONFIG_LAN91C96_BASE
 			Define this to hold the physical address
 			of the LAN91C96's I/O space
 			CONFIG_LAN91C96_USE_32_BIT
 			Define this to enable 32 bit addressing
 		CONFIG_DRIVER_SMC91111
 		Support for SMSC's LAN91C111 chip
 			CONFIG_SMC91111_BASE
 			Define this to hold the physical address
 			of the device (I/O space)
 			CONFIG_SMC_USE_32_BIT
 			Define this if data bus is 32 bits
 			CONFIG_SMC_USE_IOFUNCS
 			Define this to use i/o functions instead of macros
 			(some hardware wont work with macros)
 		CONFIG_DRIVER_SMC911X
 		Support for SMSC's LAN911x and LAN921x chips
 			CONFIG_DRIVER_SMC911X_BASE
 			Define this to hold the physical address
 			of the device (I/O space)
 			CONFIG_DRIVER_SMC911X_32_BIT
 			Define this if data bus is 32 bits
 			CONFIG_DRIVER_SMC911X_16_BIT
 			Define this if data bus is 16 bits. If your processor
 			automatically converts one 32 bit word to two 16 bit
 			words you may also try CONFIG_DRIVER_SMC911X_32_BIT.
 - USB Support:
 		At the moment only the UHCI host controller is
 		supported (PIP405, MIP405, MPC5200); define
 		CONFIG_USB_UHCI to enable it.
 		define CONFIG_USB_KEYBOARD to enable the USB Keyboard
 		and define CONFIG_USB_STORAGE to enable the USB
 		storage devices.
 		Note:
 		Supported are USB Keyboards and USB Floppy drives
 		(TEAC FD-05PUB).
 		MPC5200 USB requires additional defines:
 			CONFIG_USB_CLOCK
 				for 528 MHz Clock: 0x0001bbbb
 			CONFIG_PSC3_USB
 				for USB on PSC3
 			CONFIG_USB_CONFIG
 				for differential drivers: 0x00001000
 				for single ended drivers: 0x00005000
 				for differential drivers on PSC3: 0x00000100
 				for single ended drivers on PSC3: 0x00004100
 			CONFIG_SYS_USB_EVENT_POLL
 				May be defined to allow interrupt polling
 				instead of using asynchronous interrupts
 - USB Device:
 		Define the below if you wish to use the USB console.
 		Once firmware is rebuilt from a serial console issue the
 		command "setenv stdin usbtty; setenv stdout usbtty" and
 		attach your USB cable. The Unix command "dmesg" should print
 		it has found a new device. The environment variable usbtty
 		can be set to gserial or cdc_acm to enable your device to
 		appear to a USB host as a Linux gserial device or a
 		Common Device Class Abstract Control Model serial device.
 		If you select usbtty = gserial you should be able to enumerate
 		a Linux host by
 		# modprobe usbserial vendor=0xVendorID product=0xProductID
 		else if using cdc_acm, simply setting the environment
 		variable usbtty to be cdc_acm should suffice. The following
 		might be defined in YourBoardName.h
 			CONFIG_USB_DEVICE
 			Define this to build a UDC device
 			CONFIG_USB_TTY
 			Define this to have a tty type of device available to
 			talk to the UDC device
 			CONFIG_SYS_CONSOLE_IS_IN_ENV
 			Define this if you want stdin, stdout &/or stderr to
 			be set to usbtty.
 			mpc8xx:
 				CONFIG_SYS_USB_EXTC_CLK 0xBLAH
 				Derive USB clock from external clock "blah"
 				- CONFIG_SYS_USB_EXTC_CLK 0x02
 				CONFIG_SYS_USB_BRG_CLK 0xBLAH
 				Derive USB clock from brgclk
 				- CONFIG_SYS_USB_BRG_CLK 0x04
 		If you have a USB-IF assigned VendorID then you may wish to
 		define your own vendor specific values either in BoardName.h
 		or directly in usbd_vendor_info.h. If you don't define
 		CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
 		CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
 		should pretend to be a Linux device to it's target host.
 			CONFIG_USBD_MANUFACTURER
 			Define this string as the name of your company for
 			- CONFIG_USBD_MANUFACTURER "my company"
 			CONFIG_USBD_PRODUCT_NAME
 			Define this string as the name of your product
 			- CONFIG_USBD_PRODUCT_NAME "acme usb device"
 			CONFIG_USBD_VENDORID
 			Define this as your assigned Vendor ID from the USB
 			Implementors Forum. This *must* be a genuine Vendor ID
 			to avoid polluting the USB namespace.
 			- CONFIG_USBD_VENDORID 0xFFFF
 			CONFIG_USBD_PRODUCTID
 			Define this as the unique Product ID
 			for your device
 			- CONFIG_USBD_PRODUCTID 0xFFFF
 - MMC Support:
 		The MMC controller on the Intel PXA is supported. To
 		enable this define CONFIG_MMC. The MMC can be
 		accessed from the boot prompt by mapping the device
 		to physical memory similar to flash. Command line is
 		enabled with CONFIG_CMD_MMC. The MMC driver also works with
 		the FAT fs. This is enabled with CONFIG_CMD_FAT.
 - Journaling Flash filesystem support:
 		CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
 		CONFIG_JFFS2_NAND_DEV
 		Define these for a default partition on a NAND device
 		CONFIG_SYS_JFFS2_FIRST_SECTOR,
 		CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
 		Define these for a default partition on a NOR device
 		CONFIG_SYS_JFFS_CUSTOM_PART
 		Define this to create an own partition. You have to provide a
 		function struct part_info* jffs2_part_info(int part_num)
 		If you define only one JFFS2 partition you may also want to
 		#define CONFIG_SYS_JFFS_SINGLE_PART	1
 		to disable the command chpart. This is the default when you
 		have not defined a custom partition
 - Keyboard Support:
 		CONFIG_ISA_KEYBOARD
 		Define this to enable standard (PC-Style) keyboard
 		support
 		CONFIG_I8042_KBD
 		Standard PC keyboard driver with US (is default) and
 		GERMAN key layout (switch via environment 'keymap=de') support.
 		Export function i8042_kbd_init, i8042_tstc and i8042_getc
 		for cfb_console. Supports cursor blinking.
 - Video support:
 		CONFIG_VIDEO
 		Define this to enable video support (for output to
 		video).
 		CONFIG_VIDEO_CT69000
 		Enable Chips & Technologies 69000 Video chip
 		CONFIG_VIDEO_SMI_LYNXEM
 		Enable Silicon Motion SMI 712/710/810 Video chip. The
 		video output is selected via environment 'videoout'
 		(1 = LCD and 2 = CRT). If videoout is undefined, CRT is
 		assumed.
 		For the CT69000 and SMI_LYNXEM drivers, videomode is
 		selected via environment 'videomode'. Two different ways
 		are possible:
 		- "videomode=num"   'num' is a standard LiLo mode numbers.
 		Following standard modes are supported	(* is default):
 		      Colors	640x480 800x600 1024x768 1152x864 1280x1024
 		-------------+---------------------------------------------
 		      8 bits |	0x301*	0x303	 0x305	  0x161	    0x307
 		     15 bits |	0x310	0x313	 0x316	  0x162	    0x319
 		     16 bits |	0x311	0x314	 0x317	  0x163	    0x31A
 		     24 bits |	0x312	0x315	 0x318	    ?	    0x31B
 		-------------+---------------------------------------------
 		(i.e. setenv videomode 317; saveenv; reset;)
 		- "videomode=bootargs" all the video parameters are parsed
 		from the bootargs. (See drivers/video/videomodes.c)
 		CONFIG_VIDEO_SED13806
 		Enable Epson SED13806 driver. This driver supports 8bpp
 		and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
 		or CONFIG_VIDEO_SED13806_16BPP
 - Keyboard Support:
 		CONFIG_KEYBOARD
 		Define this to enable a custom keyboard support.
 		This simply calls drv_keyboard_init() which must be
 		defined in your board-specific files.
 		The only board using this so far is RBC823.
 - LCD Support:	CONFIG_LCD
 		Define this to enable LCD support (for output to LCD
 		display); also select one of the supported displays
 		by defining one of these:
 		CONFIG_ATMEL_LCD:
 			HITACHI TX09D70VM1CCA, 3.5", 240x320.
 		CONFIG_NEC_NL6448AC33:
 			NEC NL6448AC33-18. Active, color, single scan.
 		CONFIG_NEC_NL6448BC20
 			NEC NL6448BC20-08. 6.5", 640x480.
 			Active, color, single scan.
 		CONFIG_NEC_NL6448BC33_54
 			NEC NL6448BC33-54. 10.4", 640x480.
 			Active, color, single scan.
 		CONFIG_SHARP_16x9
 			Sharp 320x240. Active, color, single scan.
 			It isn't 16x9, and I am not sure what it is.
 		CONFIG_SHARP_LQ64D341
 			Sharp LQ64D341 display, 640x480.
 			Active, color, single scan.
 		CONFIG_HLD1045
 			HLD1045 display, 640x480.
 			Active, color, single scan.
 		CONFIG_OPTREX_BW
 			Optrex	 CBL50840-2 NF-FW 99 22 M5
 			or
 			Hitachi	 LMG6912RPFC-00T
 			or
 			Hitachi	 SP14Q002
 			320x240. Black & white.
 		Normally display is black on white background; define
 		CONFIG_SYS_WHITE_ON_BLACK to get it inverted.
 - Splash Screen Support: CONFIG_SPLASH_SCREEN
 		If this option is set, the environment is checked for
 		a variable "splashimage". If found, the usual display
 		of logo, copyright and system information on the LCD
 		is suppressed and the BMP image at the address
 		specified in "splashimage" is loaded instead. The
 		console is redirected to the "nulldev", too. This
 		allows for a "silent" boot where a splash screen is
 		loaded very quickly after power-on.
 		CONFIG_SPLASH_SCREEN_ALIGN
 		If this option is set the splash image can be freely positioned
 		on the screen. Environment variable "splashpos" specifies the
 		position as "x,y". If a positive number is given it is used as
 		number of pixel from left/top. If a negative number is given it
 		is used as number of pixel from right/bottom. You can also
 		specify 'm' for centering the image.
 		Example:
 		setenv splashpos m,m
 			=> image at center of screen
 		setenv splashpos 30,20
 			=> image at x = 30 and y = 20
 		setenv splashpos -10,m
 			=> vertically centered image
 			   at x = dspWidth - bmpWidth - 9
 - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
 		If this option is set, additionally to standard BMP
 		images, gzipped BMP images can be displayed via the
 		splashscreen support or the bmp command.
 - Compression support:
 		CONFIG_BZIP2
 		If this option is set, support for bzip2 compressed
 		images is included. If not, only uncompressed and gzip
 		compressed images are supported.
 		NOTE: the bzip2 algorithm requires a lot of RAM, so
 		the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
 		be at least 4MB.
 		CONFIG_LZMA
 		If this option is set, support for lzma compressed
 		images is included.
 		Note: The LZMA algorithm adds between 2 and 4KB of code and it
 		requires an amount of dynamic memory that is given by the
 		formula:
 			(1846 + 768 << (lc + lp)) * sizeof(uint16)
 		Where lc and lp stand for, respectively, Literal context bits
 		and Literal pos bits.
 		This value is upper-bounded by 14MB in the worst case. Anyway,
 		for a ~4MB large kernel image, we have lc=3 and lp=0 for a
 		total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is
 		a very small buffer.
 		Use the lzmainfo tool to determinate the lc and lp values and
 		then calculate the amount of needed dynamic memory (ensuring
 		the appropriate CONFIG_SYS_MALLOC_LEN value).
 - MII/PHY support:
 		CONFIG_PHY_ADDR
 		The address of PHY on MII bus.
 		CONFIG_PHY_CLOCK_FREQ (ppc4xx)
 		The clock frequency of the MII bus
 		CONFIG_PHY_GIGE
 		If this option is set, support for speed/duplex
 		detection of gigabit PHY is included.
 		CONFIG_PHY_RESET_DELAY
 		Some PHY like Intel LXT971A need extra delay after
 		reset before any MII register access is possible.
 		For such PHY, set this option to the usec delay
 		required. (minimum 300usec for LXT971A)
 		CONFIG_PHY_CMD_DELAY (ppc4xx)
 		Some PHY like Intel LXT971A need extra delay after
 		command issued before MII status register can be read
 - Ethernet address:
 		CONFIG_ETHADDR
 		CONFIG_ETH1ADDR
 		CONFIG_ETH2ADDR
 		CONFIG_ETH3ADDR
 		CONFIG_ETH4ADDR
 		CONFIG_ETH5ADDR
 		Define a default value for Ethernet address to use
 		for the respective Ethernet interface, in case this
 		is not determined automatically.
 - IP address:
 		CONFIG_IPADDR
 		Define a default value for the IP address to use for
 		the default Ethernet interface, in case this is not
 		determined through e.g. bootp.
 - Server IP address:
 		CONFIG_SERVERIP
 		Defines a default value for the IP address of a TFTP
 		server to contact when using the "tftboot" command.
 		CONFIG_KEEP_SERVERADDR
 		Keeps the server's MAC address, in the env 'serveraddr'
 		for passing to bootargs (like Linux's netconsole option)
 - Multicast TFTP Mode:
 		CONFIG_MCAST_TFTP
 		Defines whether you want to support multicast TFTP as per
 		rfc-2090; for example to work with atftp.  Lets lots of targets
 		tftp down the same boot image concurrently.  Note: the Ethernet
 		driver in use must provide a function: mcast() to join/leave a
 		multicast group.
 		CONFIG_BOOTP_RANDOM_DELAY
 - BOOTP Recovery Mode:
 		CONFIG_BOOTP_RANDOM_DELAY
 		If you have many targets in a network that try to
 		boot using BOOTP, you may want to avoid that all
 		systems send out BOOTP requests at precisely the same
 		moment (which would happen for instance at recovery
 		from a power failure, when all systems will try to
 		boot, thus flooding the BOOTP server. Defining
 		CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
 		inserted before sending out BOOTP requests. The
 		following delays are inserted then:
 		1st BOOTP request:	delay 0 ... 1 sec
 		2nd BOOTP request:	delay 0 ... 2 sec
 		3rd BOOTP request:	delay 0 ... 4 sec
 		4th and following
 		BOOTP requests:		delay 0 ... 8 sec
 - DHCP Advanced Options:
 		You can fine tune the DHCP functionality by defining
 		CONFIG_BOOTP_* symbols:
 		CONFIG_BOOTP_SUBNETMASK
 		CONFIG_BOOTP_GATEWAY
 		CONFIG_BOOTP_HOSTNAME
 		CONFIG_BOOTP_NISDOMAIN
 		CONFIG_BOOTP_BOOTPATH
 		CONFIG_BOOTP_BOOTFILESIZE
 		CONFIG_BOOTP_DNS
 		CONFIG_BOOTP_DNS2
 		CONFIG_BOOTP_SEND_HOSTNAME
 		CONFIG_BOOTP_NTPSERVER
 		CONFIG_BOOTP_TIMEOFFSET
 		CONFIG_BOOTP_VENDOREX
 		CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
 		environment variable, not the BOOTP server.
 		CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
 		serverip from a DHCP server, it is possible that more
 		than one DNS serverip is offered to the client.
 		If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
 		serverip will be stored in the additional environment
 		variable "dnsip2". The first DNS serverip is always
 		stored in the variable "dnsip", when CONFIG_BOOTP_DNS
 		is defined.
 		CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
 		to do a dynamic update of a DNS server. To do this, they
 		need the hostname of the DHCP requester.
 		If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
 		of the "hostname" environment variable is passed as
 		option 12 to the DHCP server.
 		CONFIG_BOOTP_DHCP_REQUEST_DELAY
 		A 32bit value in microseconds for a delay between
 		receiving a "DHCP Offer" and sending the "DHCP Request".
 		This fixes a problem with certain DHCP servers that don't
 		respond 100% of the time to a "DHCP request". E.g. On an
 		AT91RM9200 processor running at 180MHz, this delay needed
 		to be *at least* 15,000 usec before a Windows Server 2003
 		DHCP server would reply 100% of the time. I recommend at
 		least 50,000 usec to be safe. The alternative is to hope
 		that one of the retries will be successful but note that
 		the DHCP timeout and retry process takes a longer than
 		this delay.
  - CDP Options:
 		CONFIG_CDP_DEVICE_ID
 		The device id used in CDP trigger frames.
 		CONFIG_CDP_DEVICE_ID_PREFIX
 		A two character string which is prefixed to the MAC address
 		of the device.
 		CONFIG_CDP_PORT_ID
 		A printf format string which contains the ascii name of
 		the port. Normally is set to "eth%d" which sets
 		eth0 for the first Ethernet, eth1 for the second etc.
 		CONFIG_CDP_CAPABILITIES
 		A 32bit integer which indicates the device capabilities;
 		0x00000010 for a normal host which does not forwards.
 		CONFIG_CDP_VERSION
 		An ascii string containing the version of the software.
 		CONFIG_CDP_PLATFORM
 		An ascii string containing the name of the platform.
 		CONFIG_CDP_TRIGGER
 		A 32bit integer sent on the trigger.
 		CONFIG_CDP_POWER_CONSUMPTION
 		A 16bit integer containing the power consumption of the
 		device in .1 of milliwatts.
 		CONFIG_CDP_APPLIANCE_VLAN_TYPE
 		A byte containing the id of the VLAN.
 - Status LED:	CONFIG_STATUS_LED
 		Several configurations allow to display the current
 		status using a LED. For instance, the LED will blink
 		fast while running U-Boot code, stop blinking as
 		soon as a reply to a BOOTP request was received, and
 		start blinking slow once the Linux kernel is running
 		(supported by a status LED driver in the Linux
 		kernel). Defining CONFIG_STATUS_LED enables this
 		feature in U-Boot.
 - CAN Support:	CONFIG_CAN_DRIVER
 		Defining CONFIG_CAN_DRIVER enables CAN driver support
 		on those systems that support this (optional)
 		feature, like the TQM8xxL modules.
 - I2C Support:	CONFIG_HARD_I2C | CONFIG_SOFT_I2C
 		These enable I2C serial bus commands. Defining either of
 		(but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will
 		include the appropriate I2C driver for the selected CPU.
 		This will allow you to use i2c commands at the u-boot
 		command line (as long as you set CONFIG_CMD_I2C in
 		CONFIG_COMMANDS) and communicate with i2c based realtime
 		clock chips. See common/cmd_i2c.c for a description of the
 		command line interface.
 		CONFIG_HARD_I2C selects a hardware I2C controller.
 		CONFIG_SOFT_I2C configures u-boot to use a software (aka
 		bit-banging) driver instead of CPM or similar hardware
 		support for I2C.
 		There are several other quantities that must also be
 		defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.
 		In both cases you will need to define CONFIG_SYS_I2C_SPEED
 		to be the frequency (in Hz) at which you wish your i2c bus
 		to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie
 		the CPU's i2c node address).
 		Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)
 		sets the CPU up as a master node and so its address should
 		therefore be cleared to 0 (See, eg, MPC823e User's Manual
 		p.16-473). So, set CONFIG_SYS_I2C_SLAVE to 0.
+		CONFIG_SYS_I2C_INIT_MPC5XXX
+		When a board is reset during an i2c bus transfer
+		chips might think that the current transfer is still
+		in progress.  Reset the slave devices by sending start
+		commands until the slave device responds.
 		That's all that's required for CONFIG_HARD_I2C.
 		If you use the software i2c interface (CONFIG_SOFT_I2C)
 		then the following macros need to be defined (examples are
 		from include/configs/lwmon.h):
 		I2C_INIT
 		(Optional). Any commands necessary to enable the I2C
 		controller or configure ports.
 		eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |=	PB_SCL)
 		I2C_PORT
 		(Only for MPC8260 CPU). The I/O port to use (the code
 		assumes both bits are on the same port). Valid values
 		are 0..3 for ports A..D.
 		I2C_ACTIVE
 		The code necessary to make the I2C data line active
 		(driven).  If the data line is open collector, this
 		define can be null.
 		eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |=  PB_SDA)
 		I2C_TRISTATE
 		The code necessary to make the I2C data line tri-stated
 		(inactive).  If the data line is open collector, this
 		define can be null.
 		eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
 		I2C_READ
 		Code that returns TRUE if the I2C data line is high,
 		FALSE if it is low.
 		eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
 		I2C_SDA(bit)
 		If <bit> is TRUE, sets the I2C data line high. If it
 		is FALSE, it clears it (low).
 		eg: #define I2C_SDA(bit) \
 			if(bit) immr->im_cpm.cp_pbdat |=  PB_SDA; \
 			else	immr->im_cpm.cp_pbdat &= ~PB_SDA
 		I2C_SCL(bit)
 		If <bit> is TRUE, sets the I2C clock line high. If it
 		is FALSE, it clears it (low).
 		eg: #define I2C_SCL(bit) \
 			if(bit) immr->im_cpm.cp_pbdat |=  PB_SCL; \
 			else	immr->im_cpm.cp_pbdat &= ~PB_SCL
 		I2C_DELAY
 		This delay is invoked four times per clock cycle so this
 		controls the rate of data transfer.  The data rate thus
 		is 1 / (I2C_DELAY * 4). Often defined to be something
 		like:
 		#define I2C_DELAY  udelay(2)
 		CONFIG_SYS_I2C_INIT_BOARD
 		When a board is reset during an i2c bus transfer
 		chips might think that the current transfer is still
 		in progress. On some boards it is possible to access
 		the i2c SCLK line directly, either by using the
 		processor pin as a GPIO or by having a second pin
 		connected to the bus. If this option is defined a
 		custom i2c_init_board() routine in boards/xxx/board.c
 		is run early in the boot sequence.
 		CONFIG_I2CFAST (PPC405GP|PPC405EP only)
 		This option enables configuration of bi_iic_fast[] flags
 		in u-boot bd_info structure based on u-boot environment
 		variable "i2cfast". (see also i2cfast)
 		CONFIG_I2C_MULTI_BUS
 		This option allows the use of multiple I2C buses, each of which
 		must have a controller.  At any point in time, only one bus is
 		active.  To switch to a different bus, use the 'i2c dev' command.
 		Note that bus numbering is zero-based.
 		CONFIG_SYS_I2C_NOPROBES
 		This option specifies a list of I2C devices that will be skipped
 		when the 'i2c probe' command is issued.  If CONFIG_I2C_MULTI_BUS
 		is set, specify a list of bus-device pairs.  Otherwise, specify
 		a 1D array of device addresses
 		e.g.
 			#undef	CONFIG_I2C_MULTI_BUS
 			#define CONFIG_SYS_I2C_NOPROBES	{0x50,0x68}
 		will skip addresses 0x50 and 0x68 on a board with one I2C bus
 			#define	CONFIG_I2C_MULTI_BUS
 			#define CONFIG_SYS_I2C_MULTI_NOPROBES	{{0,0x50},{0,0x68},{1,0x54}}
 		will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
 		CONFIG_SYS_SPD_BUS_NUM
 		If defined, then this indicates the I2C bus number for DDR SPD.
 		If not defined, then U-Boot assumes that SPD is on I2C bus 0.
 		CONFIG_SYS_RTC_BUS_NUM
 		If defined, then this indicates the I2C bus number for the RTC.
 		If not defined, then U-Boot assumes that RTC is on I2C bus 0.
 		CONFIG_SYS_DTT_BUS_NUM
 		If defined, then this indicates the I2C bus number for the DTT.
 		If not defined, then U-Boot assumes that DTT is on I2C bus 0.
 		CONFIG_SYS_I2C_DTT_ADDR:
 		If defined, specifies the I2C address of the DTT device.
 		If not defined, then U-Boot uses predefined value for
 		specified DTT device.
 		CONFIG_FSL_I2C
 		Define this option if you want to use Freescale's I2C driver in
 		drivers/i2c/fsl_i2c.c.
 		CONFIG_I2C_MUX
 		Define this option if you have I2C devices reached over 1 .. n
 		I2C Muxes like the pca9544a. This option addes a new I2C
 		Command "i2c bus [muxtype:muxaddr:muxchannel]" which adds a
 		new I2C Bus to the existing I2C Busses. If you select the
 		new Bus with "i2c dev", u-bbot sends first the commandos for
 		the muxes to activate this new "bus".
 		CONFIG_I2C_MULTI_BUS must be also defined, to use this
 		feature!
 		Example:
 		Adding a new I2C Bus reached over 2 pca9544a muxes
 			The First mux with address 70 and channel 6
 			The Second mux with address 71 and channel 4
 		=> i2c bus pca9544a:70:6:pca9544a:71:4
 		Use the "i2c bus" command without parameter, to get a list
 		of I2C Busses with muxes:
 		=> i2c bus
 		Busses reached over muxes:
 		Bus ID: 2
 		  reached over Mux(es):
 		    pca9544a@70 ch: 4
 		Bus ID: 3
 		  reached over Mux(es):
 		    pca9544a@70 ch: 6
 		    pca9544a@71 ch: 4
 		=>
 		If you now switch to the new I2C Bus 3 with "i2c dev 3"
 		u-boot sends First the Commando to the mux@70 to enable
 		channel 6, and then the Commando to the mux@71 to enable
 		the channel 4.
 		After that, you can use the "normal" i2c commands as
 		usual, to communicate with your I2C devices behind
 		the 2 muxes.
 		This option is actually implemented for the bitbanging
 		algorithm in common/soft_i2c.c and for the Hardware I2C
 		Bus on the MPC8260. But it should be not so difficult
 		to add this option to other architectures.
 		CONFIG_SOFT_I2C_READ_REPEATED_START
 		defining this will force the i2c_read() function in
 		the soft_i2c driver to perform an I2C repeated start
 		between writing the address pointer and reading the
 		data.  If this define is omitted the default behaviour
 		of doing a stop-start sequence will be used.  Most I2C
 		devices can use either method, but some require one or
 		the other.
 - SPI Support:	CONFIG_SPI
 		Enables SPI driver (so far only tested with
 		SPI EEPROM, also an instance works with Crystal A/D and
 		D/As on the SACSng board)
 		CONFIG_SPI_X
 		Enables extended (16-bit) SPI EEPROM addressing.
 		(symmetrical to CONFIG_I2C_X)
 		CONFIG_SOFT_SPI
 		Enables a software (bit-bang) SPI driver rather than
 		using hardware support. This is a general purpose
 		driver that only requires three general I/O port pins
 		(two outputs, one input) to function. If this is
 		defined, the board configuration must define several
 		SPI configuration items (port pins to use, etc). For
 		an example, see include/configs/sacsng.h.
 		CONFIG_HARD_SPI
 		Enables a hardware SPI driver for general-purpose reads
 		and writes.  As with CONFIG_SOFT_SPI, the board configuration
 		must define a list of chip-select function pointers.
 		Currently supported on some MPC8xxx processors.  For an
 		example, see include/configs/mpc8349emds.h.
 		CONFIG_MXC_SPI
 		Enables the driver for the SPI controllers on i.MX and MXC
 		SoCs. Currently only i.MX31 is supported.
 - FPGA Support: CONFIG_FPGA
 		Enables FPGA subsystem.
 		CONFIG_FPGA_<vendor>
 		Enables support for specific chip vendors.
 		(ALTERA, XILINX)
 		CONFIG_FPGA_<family>
 		Enables support for FPGA family.
 		(SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
 		CONFIG_FPGA_COUNT
 		Specify the number of FPGA devices to support.
 		CONFIG_SYS_FPGA_PROG_FEEDBACK
 		Enable printing of hash marks during FPGA configuration.
 		CONFIG_SYS_FPGA_CHECK_BUSY
 		Enable checks on FPGA configuration interface busy
 		status by the configuration function. This option
 		will require a board or device specific function to
 		be written.
 		CONFIG_FPGA_DELAY
 		If defined, a function that provides delays in the FPGA
 		configuration driver.
 		CONFIG_SYS_FPGA_CHECK_CTRLC
 		Allow Control-C to interrupt FPGA configuration
 		CONFIG_SYS_FPGA_CHECK_ERROR
 		Check for configuration errors during FPGA bitfile
 		loading. For example, abort during Virtex II
 		configuration if the INIT_B line goes low (which
 		indicated a CRC error).
 		CONFIG_SYS_FPGA_WAIT_INIT
 		Maximum time to wait for the INIT_B line to deassert
 		after PROB_B has been deasserted during a Virtex II
 		FPGA configuration sequence. The default time is 500
 		ms.
 		CONFIG_SYS_FPGA_WAIT_BUSY
 		Maximum time to wait for BUSY to deassert during
 		Virtex II FPGA configuration. The default is 5 ms.
 		CONFIG_SYS_FPGA_WAIT_CONFIG
 		Time to wait after FPGA configuration. The default is
 		200 ms.
 - Configuration Management:
 		CONFIG_IDENT_STRING
 		If defined, this string will be added to the U-Boot
 		version information (U_BOOT_VERSION)
 - Vendor Parameter Protection:
 		U-Boot considers the values of the environment
 		variables "serial#" (Board Serial Number) and
 		"ethaddr" (Ethernet Address) to be parameters that
 		are set once by the board vendor / manufacturer, and
 		protects these variables from casual modification by
 		the user. Once set, these variables are read-only,
 		and write or delete attempts are rejected. You can
 		change this behaviour:
 		If CONFIG_ENV_OVERWRITE is #defined in your config
 		file, the write protection for vendor parameters is
 		completely disabled. Anybody can change or delete
 		these parameters.
 		Alternatively, if you #define _both_ CONFIG_ETHADDR
 		_and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
 		Ethernet address is installed in the environment,
 		which can be changed exactly ONCE by the user. [The
 		serial# is unaffected by this, i. e. it remains
 		read-only.]
 - Protected RAM:
 		CONFIG_PRAM
 		Define this variable to enable the reservation of
 		"protected RAM", i. e. RAM which is not overwritten
 		by U-Boot. Define CONFIG_PRAM to hold the number of
 		kB you want to reserve for pRAM. You can overwrite
 		this default value by defining an environment
 		variable "pram" to the number of kB you want to
 		reserve. Note that the board info structure will
 		still show the full amount of RAM. If pRAM is
 		reserved, a new environment variable "mem" will
 		automatically be defined to hold the amount of
 		remaining RAM in a form that can be passed as boot
 		argument to Linux, for instance like that:
 			setenv bootargs ... mem=\${mem}
 			saveenv
 		This way you can tell Linux not to use this memory,
 		either, which results in a memory region that will
 		not be affected by reboots.
 		*WARNING* If your board configuration uses automatic
 		detection of the RAM size, you must make sure that
 		this memory test is non-destructive. So far, the
 		following board configurations are known to be
 		"pRAM-clean":
 			ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
 			HERMES, IP860, RPXlite, LWMON, LANTEC,
 			PCU_E, FLAGADM, TQM8260
 - Error Recovery:
 		CONFIG_PANIC_HANG
 		Define this variable to stop the system in case of a
 		fatal error, so that you have to reset it manually.
 		This is probably NOT a good idea for an embedded
 		system where you want the system to reboot
 		automatically as fast as possible, but it may be
 		useful during development since you can try to debug
 		the conditions that lead to the situation.
 		CONFIG_NET_RETRY_COUNT
 		This variable defines the number of retries for
 		network operations like ARP, RARP, TFTP, or BOOTP
 		before giving up the operation. If not defined, a
 		default value of 5 is used.
 		CONFIG_ARP_TIMEOUT
 		Timeout waiting for an ARP reply in milliseconds.
 - Command Interpreter:
 		CONFIG_AUTO_COMPLETE
 		Enable auto completion of commands using TAB.
 		Note that this feature has NOT been implemented yet
 		for the "hush" shell.
 		CONFIG_SYS_HUSH_PARSER
 		Define this variable to enable the "hush" shell (from
 		Busybox) as command line interpreter, thus enabling
 		powerful command line syntax like
 		if...then...else...fi conditionals or `&&' and '||'
 		constructs ("shell scripts").
 		If undefined, you get the old, much simpler behaviour
 		with a somewhat smaller memory footprint.
 		CONFIG_SYS_PROMPT_HUSH_PS2
 		This defines the secondary prompt string, which is
 		printed when the command interpreter needs more input
 		to complete a command. Usually "> ".
 	Note:
 		In the current implementation, the local variables
 		space and global environment variables space are
 		separated. Local variables are those you define by
 		simply typing `name=value'. To access a local
 		variable later on, you have write `$name' or
 		`${name}'; to execute the contents of a variable
 		directly type `$name' at the command prompt.
 		Global environment variables are those you use
 		setenv/printenv to work with. To run a command stored
 		in such a variable, you need to use the run command,
 		and you must not use the '$' sign to access them.
 		To store commands and special characters in a
 		variable, please use double quotation marks
 		surrounding the whole text of the variable, instead
 		of the backslashes before semicolons and special
 		symbols.
 - Commandline Editing and History:
 		CONFIG_CMDLINE_EDITING
 		Enable editing and History functions for interactive
 		commandline input operations
 - Default Environment:
 		CONFIG_EXTRA_ENV_SETTINGS
 		Define this to contain any number of null terminated
 		strings (variable = value pairs) that will be part of
 		the default environment compiled into the boot image.
 		For example, place something like this in your
 		board's config file:
 		#define CONFIG_EXTRA_ENV_SETTINGS \
 			"myvar1=value1\0" \
 			"myvar2=value2\0"
 		Warning: This method is based on knowledge about the
 		internal format how the environment is stored by the
 		U-Boot code. This is NOT an official, exported
 		interface! Although it is unlikely that this format
 		will change soon, there is no guarantee either.
 		You better know what you are doing here.
 		Note: overly (ab)use of the default environment is
 		discouraged. Make sure to check other ways to preset
 		the environment like the "source" command or the
 		boot command first.
 - DataFlash Support:
 		CONFIG_HAS_DATAFLASH
 		Defining this option enables DataFlash features and
 		allows to read/write in Dataflash via the standard
 		commands cp, md...
 - SystemACE Support:
 		CONFIG_SYSTEMACE
 		Adding this option adds support for Xilinx SystemACE
 		chips attached via some sort of local bus. The address
 		of the chip must also be defined in the
 		CONFIG_SYS_SYSTEMACE_BASE macro. For example:
 		#define CONFIG_SYSTEMACE
 		#define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000
 		When SystemACE support is added, the "ace" device type
 		becomes available to the fat commands, i.e. fatls.
 - TFTP Fixed UDP Port:
 		CONFIG_TFTP_PORT
 		If this is defined, the environment variable tftpsrcp
 		is used to supply the TFTP UDP source port value.
 		If tftpsrcp isn't defined, the normal pseudo-random port
 		number generator is used.
 		Also, the environment variable tftpdstp is used to supply
 		the TFTP UDP destination port value.  If tftpdstp isn't
 		defined, the normal port 69 is used.
 		The purpose for tftpsrcp is to allow a TFTP server to
 		blindly start the TFTP transfer using the pre-configured
 		target IP address and UDP port. This has the effect of
 		"punching through" the (Windows XP) firewall, allowing
 		the remainder of the TFTP transfer to proceed normally.
 		A better solution is to properly configure the firewall,
 		but sometimes that is not allowed.
 - Show boot progress:
 		CONFIG_SHOW_BOOT_PROGRESS
 		Defining this option allows to add some board-
 		specific code (calling a user-provided function
 		"show_boot_progress(int)") that enables you to show
 		the system's boot progress on some display (for
 		example, some LED's) on your board. At the moment,
 		the following checkpoints are implemented:
 - Automatic software updates via TFTP server
 		CONFIG_UPDATE_TFTP
 		CONFIG_UPDATE_TFTP_CNT_MAX
 		CONFIG_UPDATE_TFTP_MSEC_MAX
 		These options enable and control the auto-update feature;
 		for a more detailed description refer to doc/README.update.
 - MTD Support (mtdparts command, UBI support)
 		CONFIG_MTD_DEVICE
 		Adds the MTD device infrastructure from the Linux kernel.
 		Needed for mtdparts command support.
 		CONFIG_MTD_PARTITIONS
 		Adds the MTD partitioning infrastructure from the Linux
 		kernel. Needed for UBI support.
 Legacy uImage format:
   Arg	Where			When
     1	common/cmd_bootm.c	before attempting to boot an image
    -1	common/cmd_bootm.c	Image header has bad	 magic number
     2	common/cmd_bootm.c	Image header has correct magic number
    -2	common/cmd_bootm.c	Image header has bad	 checksum
     3	common/cmd_bootm.c	Image header has correct checksum
    -3	common/cmd_bootm.c	Image data   has bad	 checksum
     4	common/cmd_bootm.c	Image data   has correct checksum
    -4	common/cmd_bootm.c	Image is for unsupported architecture
     5	common/cmd_bootm.c	Architecture check OK
    -5	common/cmd_bootm.c	Wrong Image Type (not kernel, multi)
     6	common/cmd_bootm.c	Image Type check OK
    -6	common/cmd_bootm.c	gunzip uncompression error
    -7	common/cmd_bootm.c	Unimplemented compression type
     7	common/cmd_bootm.c	Uncompression OK
     8	common/cmd_bootm.c	No uncompress/copy overwrite error
    -9	common/cmd_bootm.c	Unsupported OS (not Linux, BSD, VxWorks, QNX)
     9	common/image.c		Start initial ramdisk verification
   -10	common/image.c		Ramdisk header has bad	   magic number
   -11	common/image.c		Ramdisk header has bad	   checksum
    10	common/image.c		Ramdisk header is OK
   -12	common/image.c		Ramdisk data   has bad	   checksum
    11	common/image.c		Ramdisk data   has correct checksum
    12	common/image.c		Ramdisk verification complete, start loading
   -13	common/image.c		Wrong Image Type (not PPC Linux ramdisk)
    13	common/image.c		Start multifile image verification
    14	common/image.c		No initial ramdisk, no multifile, continue.
    15	lib_<arch>/bootm.c	All preparation done, transferring control to OS
   -30	lib_ppc/board.c		Fatal error, hang the system
   -31	post/post.c		POST test failed, detected by post_output_backlog()
   -32	post/post.c		POST test failed, detected by post_run_single()
    34	common/cmd_doc.c	before loading a Image from a DOC device
   -35	common/cmd_doc.c	Bad usage of "doc" command
    35	common/cmd_doc.c	correct usage of "doc" command
   -36	common/cmd_doc.c	No boot device
    36	common/cmd_doc.c	correct boot device
   -37	common/cmd_doc.c	Unknown Chip ID on boot device
    37	common/cmd_doc.c	correct chip ID found, device available
   -38	common/cmd_doc.c	Read Error on boot device
    38	common/cmd_doc.c	reading Image header from DOC device OK
   -39	common/cmd_doc.c	Image header has bad magic number
    39	common/cmd_doc.c	Image header has correct magic number
   -40	common/cmd_doc.c	Error reading Image from DOC device
    40	common/cmd_doc.c	Image header has correct magic number
    41	common/cmd_ide.c	before loading a Image from a IDE device
   -42	common/cmd_ide.c	Bad usage of "ide" command
    42	common/cmd_ide.c	correct usage of "ide" command
   -43	common/cmd_ide.c	No boot device
    43	common/cmd_ide.c	boot device found
   -44	common/cmd_ide.c	Device not available
    44	common/cmd_ide.c	Device available
   -45	common/cmd_ide.c	wrong partition selected
    45	common/cmd_ide.c	partition selected
   -46	common/cmd_ide.c	Unknown partition table
    46	common/cmd_ide.c	valid partition table found
   -47	common/cmd_ide.c	Invalid partition type
    47	common/cmd_ide.c	correct partition type
   -48	common/cmd_ide.c	Error reading Image Header on boot device
    48	common/cmd_ide.c	reading Image Header from IDE device OK
   -49	common/cmd_ide.c	Image header has bad magic number
    49	common/cmd_ide.c	Image header has correct magic number
   -50	common/cmd_ide.c	Image header has bad	 checksum
    50	common/cmd_ide.c	Image header has correct checksum
   -51	common/cmd_ide.c	Error reading Image from IDE device
    51	common/cmd_ide.c	reading Image from IDE device OK
    52	common/cmd_nand.c	before loading a Image from a NAND device
   -53	common/cmd_nand.c	Bad usage of "nand" command
    53	common/cmd_nand.c	correct usage of "nand" command
   -54	common/cmd_nand.c	No boot device
    54	common/cmd_nand.c	boot device found
   -55	common/cmd_nand.c	Unknown Chip ID on boot device
    55	common/cmd_nand.c	correct chip ID found, device available
   -56	common/cmd_nand.c	Error reading Image Header on boot device
    56	common/cmd_nand.c	reading Image Header from NAND device OK
   -57	common/cmd_nand.c	Image header has bad magic number
    57	common/cmd_nand.c	Image header has correct magic number
   -58	common/cmd_nand.c	Error reading Image from NAND device
    58	common/cmd_nand.c	reading Image from NAND device OK
   -60	common/env_common.c	Environment has a bad CRC, using default
    64	net/eth.c		starting with Ethernet configuration.
   -64	net/eth.c		no Ethernet found.
    65	net/eth.c		Ethernet found.
   -80	common/cmd_net.c	usage wrong
    80	common/cmd_net.c	before calling NetLoop()
   -81	common/cmd_net.c	some error in NetLoop() occurred
    81	common/cmd_net.c	NetLoop() back without error
   -82	common/cmd_net.c	size == 0 (File with size 0 loaded)
    82	common/cmd_net.c	trying automatic boot
    83	common/cmd_net.c	running "source" command
   -83	common/cmd_net.c	some error in automatic boot or "source" command
    84	common/cmd_net.c	end without errors
 FIT uImage format:
   Arg	Where			When
   100	common/cmd_bootm.c	Kernel FIT Image has correct format
  -100	common/cmd_bootm.c	Kernel FIT Image has incorrect format
   101	common/cmd_bootm.c	No Kernel subimage unit name, using configuration
  -101	common/cmd_bootm.c	Can't get configuration for kernel subimage
   102	common/cmd_bootm.c	Kernel unit name specified
  -103	common/cmd_bootm.c	Can't get kernel subimage node offset
   103	common/cmd_bootm.c	Found configuration node
   104	common/cmd_bootm.c	Got kernel subimage node offset
  -104	common/cmd_bootm.c	Kernel subimage hash verification failed
   105	common/cmd_bootm.c	Kernel subimage hash verification OK
  -105	common/cmd_bootm.c	Kernel subimage is for unsupported architecture
   106	common/cmd_bootm.c	Architecture check OK
  -106	common/cmd_bootm.c	Kernel subimage has wrong type
   107	common/cmd_bootm.c	Kernel subimage type OK
  -107	common/cmd_bootm.c	Can't get kernel subimage data/size
   108	common/cmd_bootm.c	Got kernel subimage data/size
  -108	common/cmd_bootm.c	Wrong image type (not legacy, FIT)
  -109	common/cmd_bootm.c	Can't get kernel subimage type
  -110	common/cmd_bootm.c	Can't get kernel subimage comp
  -111	common/cmd_bootm.c	Can't get kernel subimage os
  -112	common/cmd_bootm.c	Can't get kernel subimage load address
  -113	common/cmd_bootm.c	Image uncompress/copy overwrite error
   120	common/image.c		Start initial ramdisk verification
  -120	common/image.c		Ramdisk FIT image has incorrect format
   121	common/image.c		Ramdisk FIT image has correct format
   122	common/image.c		No ramdisk subimage unit name, using configuration
  -122	common/image.c		Can't get configuration for ramdisk subimage
   123	common/image.c		Ramdisk unit name specified
  -124	common/image.c		Can't get ramdisk subimage node offset
   125	common/image.c		Got ramdisk subimage node offset
  -125	common/image.c		Ramdisk subimage hash verification failed
   126	common/image.c		Ramdisk subimage hash verification OK
  -126	common/image.c		Ramdisk subimage for unsupported architecture
   127	common/image.c		Architecture check OK
  -127	common/image.c		Can't get ramdisk subimage data/size
   128	common/image.c		Got ramdisk subimage data/size
   129	common/image.c		Can't get ramdisk load address
  -129	common/image.c		Got ramdisk load address
  -130	common/cmd_doc.c	Incorrect FIT image format
   131	common/cmd_doc.c	FIT image format OK
  -140	common/cmd_ide.c	Incorrect FIT image format
   141	common/cmd_ide.c	FIT image format OK
  -150	common/cmd_nand.c	Incorrect FIT image format
   151	common/cmd_nand.c	FIT image format OK
 Modem Support:
 --------------
 [so far only for SMDK2400 and TRAB boards]
 - Modem support enable:
 		CONFIG_MODEM_SUPPORT
 - RTS/CTS Flow control enable:
 		CONFIG_HWFLOW
 - Modem debug support:
 		CONFIG_MODEM_SUPPORT_DEBUG
 		Enables debugging stuff (char screen[1024], dbg())
 		for modem support. Useful only with BDI2000.
 - Interrupt support (PPC):
 		There are common interrupt_init() and timer_interrupt()
 		for all PPC archs. interrupt_init() calls interrupt_init_cpu()
 		for CPU specific initialization. interrupt_init_cpu()
 		should set decrementer_count to appropriate value. If
 		CPU resets decrementer automatically after interrupt
 		(ppc4xx) it should set decrementer_count to zero.
 		timer_interrupt() calls timer_interrupt_cpu() for CPU
 		specific handling. If board has watchdog / status_led
 		/ other_activity_monitor it works automatically from
 		general timer_interrupt().
 - General:
 		In the target system modem support is enabled when a
 		specific key (key combination) is pressed during
 		power-on. Otherwise U-Boot will boot normally
 		(autoboot). The key_pressed() function is called from
 		board_init(). Currently key_pressed() is a dummy
 		function, returning 1 and thus enabling modem
 		initialization.
 		If there are no modem init strings in the
 		environment, U-Boot proceed to autoboot; the
 		previous output (banner, info printfs) will be
 		suppressed, though.
 		See also: doc/README.Modem
 Configuration Settings:
 -----------------------
 - CONFIG_SYS_LONGHELP: Defined when you want long help messages included;
 		undefine this when you're short of memory.
 - CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default
 		width of the commands listed in the 'help' command output.
 - CONFIG_SYS_PROMPT:	This is what U-Boot prints on the console to
 		prompt for user input.
 - CONFIG_SYS_CBSIZE:	Buffer size for input from the Console
 - CONFIG_SYS_PBSIZE:	Buffer size for Console output
 - CONFIG_SYS_MAXARGS:	max. Number of arguments accepted for monitor commands
 - CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to
 		the application (usually a Linux kernel) when it is
 		booted
 - CONFIG_SYS_BAUDRATE_TABLE:
 		List of legal baudrate settings for this board.
 - CONFIG_SYS_CONSOLE_INFO_QUIET
 		Suppress display of console information at boot.
 - CONFIG_SYS_CONSOLE_IS_IN_ENV
 		If the board specific function
 			extern int overwrite_console (void);
 		returns 1, the stdin, stderr and stdout are switched to the
 		serial port, else the settings in the environment are used.
 - CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE
 		Enable the call to overwrite_console().
 - CONFIG_SYS_CONSOLE_ENV_OVERWRITE
 		Enable overwrite of previous console environment settings.
 - CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END:
 		Begin and End addresses of the area used by the
 		simple memory test.
 - CONFIG_SYS_ALT_MEMTEST:
 		Enable an alternate, more extensive memory test.
 - CONFIG_SYS_MEMTEST_SCRATCH:
 		Scratch address used by the alternate memory test
 		You only need to set this if address zero isn't writeable
 - CONFIG_SYS_MEM_TOP_HIDE (PPC only):
 		If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header,
 		this specified memory area will get subtracted from the top
 		(end) of RAM and won't get "touched" at all by U-Boot. By
 		fixing up gd->ram_size the Linux kernel should gets passed
 		the now "corrected" memory size and won't touch it either.
 		This should work for arch/ppc and arch/powerpc. Only Linux
 		board ports in arch/powerpc with bootwrapper support that
 		recalculate the memory size from the SDRAM controller setup
 		will have to get fixed in Linux additionally.
 		This option can be used as a workaround for the 440EPx/GRx
 		CHIP 11 errata where the last 256 bytes in SDRAM shouldn't
 		be touched.
 		WARNING: Please make sure that this value is a multiple of
 		the Linux page size (normally 4k). If this is not the case,
 		then the end address of the Linux memory will be located at a
 		non page size aligned address and this could cause major
 		problems.
 - CONFIG_SYS_TFTP_LOADADDR:
 		Default load address for network file downloads
 - CONFIG_SYS_LOADS_BAUD_CHANGE:
 		Enable temporary baudrate change while serial download
 - CONFIG_SYS_SDRAM_BASE:
 		Physical start address of SDRAM. _Must_ be 0 here.
 - CONFIG_SYS_MBIO_BASE:
 		Physical start address of Motherboard I/O (if using a
 		Cogent motherboard)
 - CONFIG_SYS_FLASH_BASE:
 		Physical start address of Flash memory.
 - CONFIG_SYS_MONITOR_BASE:
 		Physical start address of boot monitor code (set by
 		make config files to be same as the text base address
 		(TEXT_BASE) used when linking) - same as
 		CONFIG_SYS_FLASH_BASE when booting from flash.
 - CONFIG_SYS_MONITOR_LEN:
 		Size of memory reserved for monitor code, used to
 		determine _at_compile_time_ (!) if the environment is
 		embedded within the U-Boot image, or in a separate
 		flash sector.
 - CONFIG_SYS_MALLOC_LEN:
 		Size of DRAM reserved for malloc() use.
 - CONFIG_SYS_BOOTM_LEN:
 		Normally compressed uImages are limited to an
 		uncompressed size of 8 MBytes. If this is not enough,
 		you can define CONFIG_SYS_BOOTM_LEN in your board config file
 		to adjust this setting to your needs.
 - CONFIG_SYS_BOOTMAPSZ:
 		Maximum size of memory mapped by the startup code of
 		the Linux kernel; all data that must be processed by
 		the Linux kernel (bd_info, boot arguments, FDT blob if
 		used) must be put below this limit, unless "bootm_low"
 		enviroment variable is defined and non-zero. In such case
 		all data for the Linux kernel must be between "bootm_low"
 		and "bootm_low" + CONFIG_SYS_BOOTMAPSZ.
 - CONFIG_SYS_MAX_FLASH_BANKS:
 		Max number of Flash memory banks
 - CONFIG_SYS_MAX_FLASH_SECT:
 		Max number of sectors on a Flash chip
 - CONFIG_SYS_FLASH_ERASE_TOUT:
 		Timeout for Flash erase operations (in ms)
 - CONFIG_SYS_FLASH_WRITE_TOUT:
 		Timeout for Flash write operations (in ms)
 - CONFIG_SYS_FLASH_LOCK_TOUT
 		Timeout for Flash set sector lock bit operation (in ms)
 - CONFIG_SYS_FLASH_UNLOCK_TOUT
 		Timeout for Flash clear lock bits operation (in ms)
 - CONFIG_SYS_FLASH_PROTECTION
 		If defined, hardware flash sectors protection is used
 		instead of U-Boot software protection.
 - CONFIG_SYS_DIRECT_FLASH_TFTP:
 		Enable TFTP transfers directly to flash memory;
 		without this option such a download has to be
 		performed in two steps: (1) download to RAM, and (2)
 		copy from RAM to flash.
 		The two-step approach is usually more reliable, since
 		you can check if the download worked before you erase
 		the flash, but in some situations (when system RAM is
 		too limited to allow for a temporary copy of the
 		downloaded image) this option may be very useful.
 - CONFIG_SYS_FLASH_CFI:
 		Define if the flash driver uses extra elements in the
 		common flash structure for storing flash geometry.
 - CONFIG_FLASH_CFI_DRIVER
 		This option also enables the building of the cfi_flash driver
 		in the drivers directory
 - CONFIG_FLASH_CFI_MTD
 		This option enables the building of the cfi_mtd driver
 		in the drivers directory. The driver exports CFI flash
 		to the MTD layer.
 - CONFIG_SYS_FLASH_USE_BUFFER_WRITE
 		Use buffered writes to flash.
 - CONFIG_FLASH_SPANSION_S29WS_N
 		s29ws-n MirrorBit flash has non-standard addresses for buffered
 		write commands.
 - CONFIG_SYS_FLASH_QUIET_TEST
 		If this option is defined, the common CFI flash doesn't
 		print it's warning upon not recognized FLASH banks. This
 		is useful, if some of the configured banks are only
 		optionally available.
 - CONFIG_FLASH_SHOW_PROGRESS
 		If defined (must be an integer), print out countdown
 		digits and dots.  Recommended value: 45 (9..1) for 80
 		column displays, 15 (3..1) for 40 column displays.
 - CONFIG_SYS_RX_ETH_BUFFER:
 		Defines the number of Ethernet receive buffers. On some
 		Ethernet controllers it is recommended to set this value
 		to 8 or even higher (EEPRO100 or 405 EMAC), since all
 		buffers can be full shortly after enabling the interface
 		on high Ethernet traffic.
 		Defaults to 4 if not defined.
 The following definitions that deal with the placement and management
 of environment data (variable area); in general, we support the
 following configurations:
 - CONFIG_ENV_IS_IN_FLASH:
 	Define this if the environment is in flash memory.
 	a) The environment occupies one whole flash sector, which is
 	   "embedded" in the text segment with the U-Boot code. This
 	   happens usually with "bottom boot sector" or "top boot
 	   sector" type flash chips, which have several smaller
 	   sectors at the start or the end. For instance, such a
 	   layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
 	   such a case you would place the environment in one of the
 	   4 kB sectors - with U-Boot code before and after it. With
 	   "top boot sector" type flash chips, you would put the
 	   environment in one of the last sectors, leaving a gap
 	   between U-Boot and the environment.
 	- CONFIG_ENV_OFFSET:
 	   Offset of environment data (variable area) to the
 	   beginning of flash memory; for instance, with bottom boot
 	   type flash chips the second sector can be used: the offset
 	   for this sector is given here.
 	   CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
 	- CONFIG_ENV_ADDR:
 	   This is just another way to specify the start address of
 	   the flash sector containing the environment (instead of
 	   CONFIG_ENV_OFFSET).
 	- CONFIG_ENV_SECT_SIZE:
 	   Size of the sector containing the environment.
 	b) Sometimes flash chips have few, equal sized, BIG sectors.
 	   In such a case you don't want to spend a whole sector for
 	   the environment.
 	- CONFIG_ENV_SIZE:
 	   If you use this in combination with CONFIG_ENV_IS_IN_FLASH
 	   and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
 	   of this flash sector for the environment. This saves
 	   memory for the RAM copy of the environment.
 	   It may also save flash memory if you decide to use this
 	   when your environment is "embedded" within U-Boot code,
 	   since then the remainder of the flash sector could be used
 	   for U-Boot code. It should be pointed out that this is
 	   STRONGLY DISCOURAGED from a robustness point of view:
 	   updating the environment in flash makes it always
 	   necessary to erase the WHOLE sector. If something goes
 	   wrong before the contents has been restored from a copy in
 	   RAM, your target system will be dead.
 	- CONFIG_ENV_ADDR_REDUND
 	  CONFIG_ENV_SIZE_REDUND
 	   These settings describe a second storage area used to hold
 	   a redundant copy of the environment data, so that there is
 	   a valid backup copy in case there is a power failure during
 	   a "saveenv" operation.
 BE CAREFUL! Any changes to the flash layout, and some changes to the
 source code will make it necessary to adapt <board>/u-boot.lds*
 accordingly!
 - CONFIG_ENV_IS_IN_NVRAM:
 	Define this if you have some non-volatile memory device
 	(NVRAM, battery buffered SRAM) which you want to use for the
 	environment.
 	- CONFIG_ENV_ADDR:
 	- CONFIG_ENV_SIZE:
 	  These two #defines are used to determine the memory area you
 	  want to use for environment. It is assumed that this memory
 	  can just be read and written to, without any special
 	  provision.
 BE CAREFUL! The first access to the environment happens quite early
 in U-Boot initalization (when we try to get the setting of for the
 console baudrate). You *MUST* have mapped your NVRAM area then, or
 U-Boot will hang.
 Please note that even with NVRAM we still use a copy of the
 environment in RAM: we could work on NVRAM directly, but we want to
 keep settings there always unmodified except somebody uses "saveenv"
 to save the current settings.
 - CONFIG_ENV_IS_IN_EEPROM:
 	Use this if you have an EEPROM or similar serial access
 	device and a driver for it.
 	- CONFIG_ENV_OFFSET:
 	- CONFIG_ENV_SIZE:
 	  These two #defines specify the offset and size of the
 	  environment area within the total memory of your EEPROM.
 	- CONFIG_SYS_I2C_EEPROM_ADDR:
 	  If defined, specified the chip address of the EEPROM device.
 	  The default address is zero.
 	- CONFIG_SYS_EEPROM_PAGE_WRITE_BITS:
 	  If defined, the number of bits used to address bytes in a
 	  single page in the EEPROM device.  A 64 byte page, for example
 	  would require six bits.
 	- CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS:
 	  If defined, the number of milliseconds to delay between
 	  page writes.	The default is zero milliseconds.
 	- CONFIG_SYS_I2C_EEPROM_ADDR_LEN:
 	  The length in bytes of the EEPROM memory array address.  Note
 	  that this is NOT the chip address length!
 	- CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW:
 	  EEPROM chips that implement "address overflow" are ones
 	  like Catalyst 24WC04/08/16 which has 9/10/11 bits of
 	  address and the extra bits end up in the "chip address" bit
 	  slots. This makes a 24WC08 (1Kbyte) chip look like four 256
 	  byte chips.
 	  Note that we consider the length of the address field to
 	  still be one byte because the extra address bits are hidden
 	  in the chip address.
 	- CONFIG_SYS_EEPROM_SIZE:
 	  The size in bytes of the EEPROM device.
 - CONFIG_ENV_IS_IN_DATAFLASH:
 	Define this if you have a DataFlash memory device which you
 	want to use for the environment.
 	- CONFIG_ENV_OFFSET:
 	- CONFIG_ENV_ADDR:
 	- CONFIG_ENV_SIZE:
 	  These three #defines specify the offset and size of the
 	  environment area within the total memory of your DataFlash placed
 	  at the specified address.
 - CONFIG_ENV_IS_IN_NAND:
 	Define this if you have a NAND device which you want to use
 	for the environment.
 	- CONFIG_ENV_OFFSET:
 	- CONFIG_ENV_SIZE:
 	  These two #defines specify the offset and size of the environment
 	  area within the first NAND device.
 	- CONFIG_ENV_OFFSET_REDUND
 	  This setting describes a second storage area of CONFIG_ENV_SIZE
 	  size used to hold a redundant copy of the environment data,
 	  so that there is a valid backup copy in case there is a
 	  power failure during a "saveenv" operation.
 	Note: CONFIG_ENV_OFFSET and CONFIG_ENV_OFFSET_REDUND must be aligned
 	to a block boundary, and CONFIG_ENV_SIZE must be a multiple of
 	the NAND devices block size.
 - CONFIG_NAND_ENV_DST
 	Defines address in RAM to which the nand_spl code should copy the
 	environment. If redundant environment is used, it will be copied to
 	CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE.
 - CONFIG_SYS_SPI_INIT_OFFSET
 	Defines offset to the initial SPI buffer area in DPRAM. The
 	area is used at an early stage (ROM part) if the environment
 	is configured to reside in the SPI EEPROM: We need a 520 byte
 	scratch DPRAM area. It is used between the two initialization
 	calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems
 	to be a good choice since it makes it far enough from the
 	start of the data area as well as from the stack pointer.
 Please note that the environment is read-only until the monitor
 has been relocated to RAM and a RAM copy of the environment has been
 created; also, when using EEPROM you will have to use getenv_r()
 until then to read environment variables.
 The environment is protected by a CRC32 checksum. Before the monitor
 is relocated into RAM, as a result of a bad CRC you will be working
 with the compiled-in default environment - *silently*!!! [This is
 necessary, because the first environment variable we need is the
 "baudrate" setting for the console - if we have a bad CRC, we don't
 have any device yet where we could complain.]
 Note: once the monitor has been relocated, then it will complain if
 the default environment is used; a new CRC is computed as soon as you
 use the "saveenv" command to store a valid environment.
 - CONFIG_SYS_FAULT_ECHO_LINK_DOWN:
 		Echo the inverted Ethernet link state to the fault LED.
 		Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR
 		      also needs to be defined.
 - CONFIG_SYS_FAULT_MII_ADDR:
 		MII address of the PHY to check for the Ethernet link state.
 - CONFIG_SYS_64BIT_VSPRINTF:
 		Makes vsprintf (and all *printf functions) support printing
 		of 64bit values by using the L quantifier
 - CONFIG_SYS_64BIT_STRTOUL:
 		Adds simple_strtoull that returns a 64bit value
 - CONFIG_NS16550_MIN_FUNCTIONS:
 		Define this if you desire to only have use of the NS16550_init
 		and NS16550_putc functions for the serial driver located at
 		drivers/serial/ns16550.c.  This option is useful for saving
 		space for already greatly restricted images, including but not
 		limited to NAND_SPL configurations.
 Low Level (hardware related) configuration options:
 ---------------------------------------------------
 - CONFIG_SYS_CACHELINE_SIZE:
 		Cache Line Size of the CPU.
 - CONFIG_SYS_DEFAULT_IMMR:
 		Default address of the IMMR after system reset.
 		Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,
 		and RPXsuper) to be able to adjust the position of
 		the IMMR register after a reset.
 - Floppy Disk Support:
 		CONFIG_SYS_FDC_DRIVE_NUMBER
 		the default drive number (default value 0)
 		CONFIG_SYS_ISA_IO_STRIDE
 		defines the spacing between FDC chipset registers
 		(default value 1)
 		CONFIG_SYS_ISA_IO_OFFSET
 		defines the offset of register from address. It
 		depends on which part of the data bus is connected to
 		the FDC chipset. (default value 0)
 		If CONFIG_SYS_ISA_IO_STRIDE CONFIG_SYS_ISA_IO_OFFSET and
 		CONFIG_SYS_FDC_DRIVE_NUMBER are undefined, they take their
 		default value.
 		if CONFIG_SYS_FDC_HW_INIT is defined, then the function
 		fdc_hw_init() is called at the beginning of the FDC
 		setup. fdc_hw_init() must be provided by the board
 		source code. It is used to make hardware dependant
 		initializations.
 - CONFIG_SYS_IMMR:	Physical address of the Internal Memory.
 		DO NOT CHANGE unless you know exactly what you're
 		doing! (11-4) [MPC8xx/82xx systems only]
 - CONFIG_SYS_INIT_RAM_ADDR:
 		Start address of memory area that can be used for
 		initial data and stack; please note that this must be
 		writable memory that is working WITHOUT special
 		initialization, i. e. you CANNOT use normal RAM which
 		will become available only after programming the
 		memory controller and running certain initialization
 		sequences.
 		U-Boot uses the following memory types:
 		- MPC8xx and MPC8260: IMMR (internal memory of the CPU)
 		- MPC824X: data cache
 		- PPC4xx:  data cache
 - CONFIG_SYS_GBL_DATA_OFFSET:
 		Offset of the initial data structure in the memory
 		area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually
 		CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial
 		data is located at the end of the available space
 		(sometimes written as (CONFIG_SYS_INIT_RAM_END -
 		CONFIG_SYS_INIT_DATA_SIZE), and the initial stack is just
 		below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR +
 		CONFIG_SYS_GBL_DATA_OFFSET) downward.
 	Note:
 		On the MPC824X (or other systems that use the data
 		cache for initial memory) the address chosen for
 		CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must
 		point to an otherwise UNUSED address space between
 		the top of RAM and the start of the PCI space.
 - CONFIG_SYS_SIUMCR:	SIU Module Configuration (11-6)
 - CONFIG_SYS_SYPCR:	System Protection Control (11-9)
 - CONFIG_SYS_TBSCR:	Time Base Status and Control (11-26)
 - CONFIG_SYS_PISCR:	Periodic Interrupt Status and Control (11-31)
 - CONFIG_SYS_PLPRCR:	PLL, Low-Power, and Reset Control Register (15-30)
 - CONFIG_SYS_SCCR:	System Clock and reset Control Register (15-27)
 - CONFIG_SYS_OR_TIMING_SDRAM:
 		SDRAM timing
 - CONFIG_SYS_MAMR_PTA:
 		periodic timer for refresh
 - CONFIG_SYS_DER:	Debug Event Register (37-47)
 - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM,
   CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP,
   CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM,
   CONFIG_SYS_BR1_PRELIM:
 		Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
 - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
   CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM,
   CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM:
 		Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
 - CONFIG_SYS_MAMR_PTA, CONFIG_SYS_MPTPR_2BK_4K, CONFIG_SYS_MPTPR_1BK_4K, CONFIG_SYS_MPTPR_2BK_8K,
   CONFIG_SYS_MPTPR_1BK_8K, CONFIG_SYS_MAMR_8COL, CONFIG_SYS_MAMR_9COL:
 		Machine Mode Register and Memory Periodic Timer
 		Prescaler definitions (SDRAM timing)
 - CONFIG_SYS_I2C_UCODE_PATCH, CONFIG_SYS_I2C_DPMEM_OFFSET [0x1FC0]:
 		enable I2C microcode relocation patch (MPC8xx);
 		define relocation offset in DPRAM [DSP2]
 - CONFIG_SYS_SMC_UCODE_PATCH, CONFIG_SYS_SMC_DPMEM_OFFSET [0x1FC0]:
 		enable SMC microcode relocation patch (MPC8xx);
 		define relocation offset in DPRAM [SMC1]
 - CONFIG_SYS_SPI_UCODE_PATCH, CONFIG_SYS_SPI_DPMEM_OFFSET [0x1FC0]:
 		enable SPI microcode relocation patch (MPC8xx);
 		define relocation offset in DPRAM [SCC4]
 - CONFIG_SYS_USE_OSCCLK:
 		Use OSCM clock mode on MBX8xx board. Be careful,
 		wrong setting might damage your board. Read
 		doc/README.MBX before setting this variable!
 - CONFIG_SYS_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)
 		Offset of the bootmode word in DPRAM used by post
 		(Power On Self Tests). This definition overrides
 		#define'd default value in commproc.h resp.
 		cpm_8260.h.
 - CONFIG_SYS_PCI_SLV_MEM_LOCAL, CONFIG_SYS_PCI_SLV_MEM_BUS, CONFIG_SYS_PICMR0_MASK_ATTRIB,
   CONFIG_SYS_PCI_MSTR0_LOCAL, CONFIG_SYS_PCIMSK0_MASK, CONFIG_SYS_PCI_MSTR1_LOCAL,
   CONFIG_SYS_PCIMSK1_MASK, CONFIG_SYS_PCI_MSTR_MEM_LOCAL, CONFIG_SYS_PCI_MSTR_MEM_BUS,
   CONFIG_SYS_CPU_PCI_MEM_START, CONFIG_SYS_PCI_MSTR_MEM_SIZE, CONFIG_SYS_POCMR0_MASK_ATTRIB,
   CONFIG_SYS_PCI_MSTR_MEMIO_LOCAL, CONFIG_SYS_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,
   CONFIG_SYS_PCI_MSTR_MEMIO_SIZE, CONFIG_SYS_POCMR1_MASK_ATTRIB, CONFIG_SYS_PCI_MSTR_IO_LOCAL,
   CONFIG_SYS_PCI_MSTR_IO_BUS, CONFIG_SYS_CPU_PCI_IO_START, CONFIG_SYS_PCI_MSTR_IO_SIZE,
   CONFIG_SYS_POCMR2_MASK_ATTRIB: (MPC826x only)
 		Overrides the default PCI memory map in cpu/mpc8260/pci.c if set.
 - CONFIG_PCI_DISABLE_PCIE:
 		Disable PCI-Express on systems where it is supported but not
 		required.
 - CONFIG_SPD_EEPROM
 		Get DDR timing information from an I2C EEPROM. Common
 		with pluggable memory modules such as SODIMMs
   SPD_EEPROM_ADDRESS
 		I2C address of the SPD EEPROM
 - CONFIG_SYS_SPD_BUS_NUM
 		If SPD EEPROM is on an I2C bus other than the first
 		one, specify here. Note that the value must resolve
 		to something your driver can deal with.
 - CONFIG_SYS_83XX_DDR_USES_CS0
 		Only for 83xx systems. If specified, then DDR should
 		be configured using CS0 and CS1 instead of CS2 and CS3.
 - CONFIG_ETHER_ON_FEC[12]
 		Define to enable FEC[12] on a 8xx series processor.
 - CONFIG_FEC[12]_PHY
 		Define to the hardcoded PHY address which corresponds
 		to the given FEC; i. e.
 			#define CONFIG_FEC1_PHY 4
 		means that the PHY with address 4 is connected to FEC1
 		When set to -1, means to probe for first available.
 - CONFIG_FEC[12]_PHY_NORXERR
 		The PHY does not have a RXERR line (RMII only).
 		(so program the FEC to ignore it).
 - CONFIG_RMII
 		Enable RMII mode for all FECs.
 		Note that this is a global option, we can't
 		have one FEC in standard MII mode and another in RMII mode.
 - CONFIG_CRC32_VERIFY
 		Add a verify option to the crc32 command.
 		The syntax is:
 		=> crc32 -v <address> <count> <crc32>
 		Where address/count indicate a memory area
 		and crc32 is the correct crc32 which the
 		area should have.
 - CONFIG_LOOPW
 		Add the "loopw" memory command. This only takes effect if
 		the memory commands are activated globally (CONFIG_CMD_MEM).
 - CONFIG_MX_CYCLIC
 		Add the "mdc" and "mwc" memory commands. These are cyclic
 		"md/mw" commands.
 		Examples:
 		=> mdc.b 10 4 500
 		This command will print 4 bytes (10,11,12,13) each 500 ms.
 		=> mwc.l 100 12345678 10
 		This command will write 12345678 to address 100 all 10 ms.
 		This only takes effect if the memory commands are activated
 		globally (CONFIG_CMD_MEM).
 - CONFIG_SKIP_LOWLEVEL_INIT
 - CONFIG_SKIP_RELOCATE_UBOOT
 		[ARM only] If these variables are defined, then
 		certain low level initializations (like setting up
 		the memory controller) are omitted and/or U-Boot does
 		not relocate itself into RAM.
 		Normally these variables MUST NOT be defined. The
 		only exception is when U-Boot is loaded (to RAM) by
 		some other boot loader or by a debugger which
 		performs these initializations itself.
 - CONFIG_PRELOADER
 		Modifies the behaviour of start.S when compiling a loader
 		that is executed before the actual U-Boot. E.g. when
 		compiling a NAND SPL.
 Building the Software:
 ======================
 Building U-Boot has been tested in several native build environments
 and in many different cross environments. Of course we cannot support
 all possibly existing versions of cross development tools in all
 (potentially obsolete) versions. In case of tool chain problems we
 recommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK)
 which is extensively used to build and test U-Boot.
 If you are not using a native environment, it is assumed that you
 have GNU cross compiling tools available in your path. In this case,
 you must set the environment variable CROSS_COMPILE in your shell.
 Note that no changes to the Makefile or any other source files are
 necessary. For example using the ELDK on a 4xx CPU, please enter:
 	$ CROSS_COMPILE=ppc_4xx-
 	$ export CROSS_COMPILE
 Note: If you wish to generate Windows versions of the utilities in
       the tools directory you can use the MinGW toolchain
       (http://www.mingw.org).  Set your HOST tools to the MinGW
       toolchain and execute 'make tools'.  For example:
        $ make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools
       Binaries such as tools/mkimage.exe will be created which can
       be executed on computers running Windows.
 U-Boot is intended to be simple to build. After installing the
 sources you must configure U-Boot for one specific board type. This
 is done by typing:
 	make NAME_config
 where "NAME_config" is the name of one of the existing configu-
 rations; see the main Makefile for supported names.
 Note: for some board special configuration names may exist; check if
       additional information is available from the board vendor; for
       instance, the TQM823L systems are available without (standard)
       or with LCD support. You can select such additional "features"
       when choosing the configuration, i. e.
       make TQM823L_config
 	- will configure for a plain TQM823L, i. e. no LCD support
       make TQM823L_LCD_config
 	- will configure for a TQM823L with U-Boot console on LCD
       etc.
 Finally, type "make all", and you should get some working U-Boot
 images ready for download to / installation on your system:
 - "u-boot.bin" is a raw binary image
 - "u-boot" is an image in ELF binary format
 - "u-boot.srec" is in Motorola S-Record format
 By default the build is performed locally and the objects are saved
 in the source directory. One of the two methods can be used to change
 this behavior and build U-Boot to some external directory:
 1. Add O= to the make command line invocations:
 	make O=/tmp/build distclean
 	make O=/tmp/build NAME_config
 	make O=/tmp/build all
 2. Set environment variable BUILD_DIR to point to the desired location:
 	export BUILD_DIR=/tmp/build
 	make distclean
 	make NAME_config
 	make all
 Note that the command line "O=" setting overrides the BUILD_DIR environment
 variable.
 Please be aware that the Makefiles assume you are using GNU make, so
 for instance on NetBSD you might need to use "gmake" instead of
 native "make".
 If the system board that you have is not listed, then you will need
 to port U-Boot to your hardware platform. To do this, follow these
 steps:
 1.  Add a new configuration option for your board to the toplevel
     "Makefile" and to the "MAKEALL" script, using the existing
     entries as examples. Note that here and at many other places
     boards and other names are listed in alphabetical sort order. Please
     keep this order.
 2.  Create a new directory to hold your board specific code. Add any
     files you need. In your board directory, you will need at least
     the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
 3.  Create a new configuration file "include/configs/<board>.h" for
     your board
 3.  If you're porting U-Boot to a new CPU, then also create a new
     directory to hold your CPU specific code. Add any files you need.
 4.  Run "make <board>_config" with your new name.
 5.  Type "make", and you should get a working "u-boot.srec" file
     to be installed on your target system.
 6.  Debug and solve any problems that might arise.
     [Of course, this last step is much harder than it sounds.]
 Testing of U-Boot Modifications, Ports to New Hardware, etc.:
 ==============================================================
 If you have modified U-Boot sources (for instance added a new board
 or support for new devices, a new CPU, etc.) you are expected to
 provide feedback to the other developers. The feedback normally takes
 the form of a "patch", i. e. a context diff against a certain (latest
 official or latest in the git repository) version of U-Boot sources.
 But before you submit such a patch, please verify that your modifi-
 cation did not break existing code. At least make sure that *ALL* of
 the supported boards compile WITHOUT ANY compiler warnings. To do so,
 just run the "MAKEALL" script, which will configure and build U-Boot
 for ALL supported system. Be warned, this will take a while. You can
 select which (cross) compiler to use by passing a `CROSS_COMPILE'
 environment variable to the script, i. e. to use the ELDK cross tools
 you can type
 	CROSS_COMPILE=ppc_8xx- MAKEALL
 or to build on a native PowerPC system you can type
 	CROSS_COMPILE=' ' MAKEALL
 When using the MAKEALL script, the default behaviour is to build
 U-Boot in the source directory. This location can be changed by
 setting the BUILD_DIR environment variable. Also, for each target
 built, the MAKEALL script saves two log files (<target>.ERR and
 <target>.MAKEALL) in the <source dir>/LOG directory. This default
 location can be changed by setting the MAKEALL_LOGDIR environment
 variable. For example:
 	export BUILD_DIR=/tmp/build
 	export MAKEALL_LOGDIR=/tmp/log
 	CROSS_COMPILE=ppc_8xx- MAKEALL
 With the above settings build objects are saved in the /tmp/build,
 log files are saved in the /tmp/log and the source tree remains clean
 during the whole build process.
 See also "U-Boot Porting Guide" below.
 Monitor Commands - Overview:
 ============================
 go	- start application at address 'addr'
 run	- run commands in an environment variable
 bootm	- boot application image from memory
 bootp	- boot image via network using BootP/TFTP protocol
 tftpboot- boot image via network using TFTP protocol
 	       and env variables "ipaddr" and "serverip"
 	       (and eventually "gatewayip")
 rarpboot- boot image via network using RARP/TFTP protocol
 diskboot- boot from IDE devicebootd   - boot default, i.e., run 'bootcmd'
 loads	- load S-Record file over serial line
 loadb	- load binary file over serial line (kermit mode)
 md	- memory display
 mm	- memory modify (auto-incrementing)
 nm	- memory modify (constant address)
 mw	- memory write (fill)
 cp	- memory copy
 cmp	- memory compare
 crc32	- checksum calculation
 i2c	- I2C sub-system
 sspi	- SPI utility commands
 base	- print or set address offset
 printenv- print environment variables
 setenv	- set environment variables
 saveenv - save environment variables to persistent storage
 protect - enable or disable FLASH write protection
 erase	- erase FLASH memory
 flinfo	- print FLASH memory information
 bdinfo	- print Board Info structure
 iminfo	- print header information for application image
 coninfo - print console devices and informations
 ide	- IDE sub-system
 loop	- infinite loop on address range
 loopw	- infinite write loop on address range
 mtest	- simple RAM test
 icache	- enable or disable instruction cache
 dcache	- enable or disable data cache
 reset	- Perform RESET of the CPU
 echo	- echo args to console
 version - print monitor version
 help	- print online help
 ?	- alias for 'help'
 Monitor Commands - Detailed Description:
 ========================================
 TODO.
 For now: just type "help <command>".
 Environment Variables:
 ======================
 U-Boot supports user configuration using Environment Variables which
 can be made persistent by saving to Flash memory.
 Environment Variables are set using "setenv", printed using
 "printenv", and saved to Flash using "saveenv". Using "setenv"
 without a value can be used to delete a variable from the
 environment. As long as you don't save the environment you are
 working with an in-memory copy. In case the Flash area containing the
 environment is erased by accident, a default environment is provided.
 Some configuration options can be set using Environment Variables:
   baudrate	- see CONFIG_BAUDRATE
   bootdelay	- see CONFIG_BOOTDELAY
   bootcmd	- see CONFIG_BOOTCOMMAND
   bootargs	- Boot arguments when booting an RTOS image
   bootfile	- Name of the image to load with TFTP
   bootm_low	- Memory range available for image processing in the bootm
 		  command can be restricted. This variable is given as
 		  a hexadecimal number and defines lowest address allowed
 		  for use by the bootm command. See also "bootm_size"
 		  environment variable. Address defined by "bootm_low" is
 		  also the base of the initial memory mapping for the Linux
 		  kernel -- see the description of CONFIG_SYS_BOOTMAPSZ.
   bootm_size	- Memory range available for image processing in the bootm
 		  command can be restricted. This variable is given as
 		  a hexadecimal number and defines the size of the region
 		  allowed for use by the bootm command. See also "bootm_low"
 		  environment variable.
   updatefile	- Location of the software update file on a TFTP server, used
 		  by the automatic software update feature. Please refer to
 		  documentation in doc/README.update for more details.
   autoload	- if set to "no" (any string beginning with 'n'),
 		  "bootp" will just load perform a lookup of the
 		  configuration from the BOOTP server, but not try to
 		  load any image using TFTP
   autoscript	- if set to "yes" commands like "loadb", "loady",
 		  "bootp", "tftpb", "rarpboot" and "nfs" will attempt
 		  to automatically run script images (by internally
 		  calling "source").
   autoscript_uname - if script image is in a format (FIT) this
 		     variable is used to get script subimage unit name.
   autostart	- if set to "yes", an image loaded using the "bootp",
 		  "rarpboot", "tftpboot" or "diskboot" commands will
 		  be automatically started (by internally calling
 		  "bootm")
 		  If set to "no", a standalone image passed to the
 		  "bootm" command will be copied to the load address
 		  (and eventually uncompressed), but NOT be started.
 		  This can be used to load and uncompress arbitrary
 		  data.
   i2cfast	- (PPC405GP|PPC405EP only)
 		  if set to 'y' configures Linux I2C driver for fast
 		  mode (400kHZ). This environment variable is used in
 		  initialization code. So, for changes to be effective
 		  it must be saved and board must be reset.
   initrd_high	- restrict positioning of initrd images:
 		  If this variable is not set, initrd images will be
 		  copied to the highest possible address in RAM; this
 		  is usually what you want since it allows for
 		  maximum initrd size. If for some reason you want to
 		  make sure that the initrd image is loaded below the
 		  CONFIG_SYS_BOOTMAPSZ limit, you can set this environment
 		  variable to a value of "no" or "off" or "0".
 		  Alternatively, you can set it to a maximum upper
 		  address to use (U-Boot will still check that it
 		  does not overwrite the U-Boot stack and data).
 		  For instance, when you have a system with 16 MB
 		  RAM, and want to reserve 4 MB from use by Linux,
 		  you can do this by adding "mem=12M" to the value of
 		  the "bootargs" variable. However, now you must make
 		  sure that the initrd image is placed in the first
 		  12 MB as well - this can be done with
 		  setenv initrd_high 00c00000
 		  If you set initrd_high to 0xFFFFFFFF, this is an
 		  indication to U-Boot that all addresses are legal
 		  for the Linux kernel, including addresses in flash
 		  memory. In this case U-Boot will NOT COPY the
 		  ramdisk at all. This may be useful to reduce the
 		  boot time on your system, but requires that this
 		  feature is supported by your Linux kernel.
   ipaddr	- IP address; needed for tftpboot command
   loadaddr	- Default load address for commands like "bootp",
 		  "rarpboot", "tftpboot", "loadb" or "diskboot"
   loads_echo	- see CONFIG_LOADS_ECHO
   serverip	- TFTP server IP address; needed for tftpboot command
   bootretry	- see CONFIG_BOOT_RETRY_TIME
   bootdelaykey	- see CONFIG_AUTOBOOT_DELAY_STR
   bootstopkey	- see CONFIG_AUTOBOOT_STOP_STR
   ethprime	- When CONFIG_NET_MULTI is enabled controls which
 		  interface is used first.
   ethact	- When CONFIG_NET_MULTI is enabled controls which
 		  interface is currently active. For example you
 		  can do the following
 		  => setenv ethact FEC ETHERNET
 		  => ping 192.168.0.1 # traffic sent on FEC ETHERNET
 		  => setenv ethact SCC ETHERNET
 		  => ping 10.0.0.1 # traffic sent on SCC ETHERNET
   ethrotate	- When set to "no" U-Boot does not go through all
 		  available network interfaces.
 		  It just stays at the currently selected interface.
    netretry	- When set to "no" each network operation will
 		  either succeed or fail without retrying.
 		  When set to "once" the network operation will
 		  fail when all the available network interfaces
 		  are tried once without success.
 		  Useful on scripts which control the retry operation
 		  themselves.
   npe_ucode	- set load address for the NPE microcode
   tftpsrcport	- If this is set, the value is used for TFTP's
 		  UDP source port.
   tftpdstport	- If this is set, the value is used for TFTP's UDP
 		  destination port instead of the Well Know Port 69.
    vlan		- When set to a value < 4095 the traffic over
 		  Ethernet is encapsulated/received over 802.1q
 		  VLAN tagged frames.
 The following environment variables may be used and automatically
 updated by the network boot commands ("bootp" and "rarpboot"),
 depending the information provided by your boot server:
   bootfile	- see above
   dnsip		- IP address of your Domain Name Server
   dnsip2	- IP address of your secondary Domain Name Server
   gatewayip	- IP address of the Gateway (Router) to use
   hostname	- Target hostname
   ipaddr	- see above
   netmask	- Subnet Mask
   rootpath	- Pathname of the root filesystem on the NFS server
   serverip	- see above
 There are two special Environment Variables:
   serial#	- contains hardware identification information such
 		  as type string and/or serial number
   ethaddr	- Ethernet address
 These variables can be set only once (usually during manufacturing of
 the board). U-Boot refuses to delete or overwrite these variables
 once they have been set once.
 Further special Environment Variables:
   ver		- Contains the U-Boot version string as printed
 		  with the "version" command. This variable is
 		  readonly (see CONFIG_VERSION_VARIABLE).
 Please note that changes to some configuration parameters may take
 only effect after the next boot (yes, that's just like Windoze :-).
 Command Line Parsing:
 =====================
 There are two different command line parsers available with U-Boot:
 the old "simple" one, and the much more powerful "hush" shell:
 Old, simple command line parser:
 --------------------------------
 - supports environment variables (through setenv / saveenv commands)
 - several commands on one line, separated by ';'
 - variable substitution using "... ${name} ..." syntax
 - special characters ('$', ';') can be escaped by prefixing with '\',
   for example:
 	setenv bootcmd bootm \${address}
 - You can also escape text by enclosing in single apostrophes, for example:
 	setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
 Hush shell:
 -----------
 - similar to Bourne shell, with control structures like
   if...then...else...fi, for...do...done; while...do...done,
   until...do...done, ...
 - supports environment ("global") variables (through setenv / saveenv
   commands) and local shell variables (through standard shell syntax
   "name=value"); only environment variables can be used with "run"
   command
 General rules:
 --------------
 (1) If a command line (or an environment variable executed by a "run"
     command) contains several commands separated by semicolon, and
     one of these commands fails, then the remaining commands will be
     executed anyway.
 (2) If you execute several variables with one call to run (i. e.
     calling run with a list of variables as arguments), any failing
     command will cause "run" to terminate, i. e. the remaining
     variables are not executed.
 Note for Redundant Ethernet Interfaces:
 =======================================
 Some boards come with redundant Ethernet interfaces; U-Boot supports
 such configurations and is capable of automatic selection of a
 "working" interface when needed. MAC assignment works as follows:
 Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
 MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
 "eth1addr" (=>eth1), "eth2addr", ...
 If the network interface stores some valid MAC address (for instance
 in SROM), this is used as default address if there is NO correspon-
 ding setting in the environment; if the corresponding environment
 variable is set, this overrides the settings in the card; that means:
 o If the SROM has a valid MAC address, and there is no address in the
   environment, the SROM's address is used.
 o If there is no valid address in the SROM, and a definition in the
   environment exists, then the value from the environment variable is
   used.
 o If both the SROM and the environment contain a MAC address, and
   both addresses are the same, this MAC address is used.
 o If both the SROM and the environment contain a MAC address, and the
   addresses differ, the value from the environment is used and a
   warning is printed.
 o If neither SROM nor the environment contain a MAC address, an error
   is raised.
 Image Formats:
 ==============
 U-Boot is capable of booting (and performing other auxiliary operations on)
 images in two formats:
 New uImage format (FIT)
 -----------------------
 Flexible and powerful format based on Flattened Image Tree -- FIT (similar
 to Flattened Device Tree). It allows the use of images with multiple
 components (several kernels, ramdisks, etc.), with contents protected by
 SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory.
 Old uImage format
 -----------------
 Old image format is based on binary files which can be basically anything,
 preceded by a special header; see the definitions in include/image.h for
 details; basically, the header defines the following image properties:
 * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
   4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
   LynxOS, pSOS, QNX, RTEMS, INTEGRITY;
   Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS,
   INTEGRITY).
 * Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86,
   IA64, MIPS, NIOS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
   Currently supported: ARM, AVR32, Intel x86, MIPS, NIOS, PowerPC).
 * Compression Type (uncompressed, gzip, bzip2)
 * Load Address
 * Entry Point
 * Image Name
 * Image Timestamp
 The header is marked by a special Magic Number, and both the header
 and the data portions of the image are secured against corruption by
 CRC32 checksums.
 Linux Support:
 ==============
 Although U-Boot should support any OS or standalone application
 easily, the main focus has always been on Linux during the design of
 U-Boot.
 U-Boot includes many features that so far have been part of some
 special "boot loader" code within the Linux kernel. Also, any
 "initrd" images to be used are no longer part of one big Linux image;
 instead, kernel and "initrd" are separate images. This implementation
 serves several purposes:
 - the same features can be used for other OS or standalone
   applications (for instance: using compressed images to reduce the
   Flash memory footprint)
 - it becomes much easier to port new Linux kernel versions because
   lots of low-level, hardware dependent stuff are done by U-Boot
 - the same Linux kernel image can now be used with different "initrd"
   images; of course this also means that different kernel images can
   be run with the same "initrd". This makes testing easier (you don't
   have to build a new "zImage.initrd" Linux image when you just
   change a file in your "initrd"). Also, a field-upgrade of the
   software is easier now.
 Linux HOWTO:
 ============
 Porting Linux to U-Boot based systems:
 ---------------------------------------
 U-Boot cannot save you from doing all the necessary modifications to
 configure the Linux device drivers for use with your target hardware
 (no, we don't intend to provide a full virtual machine interface to
 Linux :-).
 But now you can ignore ALL boot loader code (in arch/ppc/mbxboot).
 Just make sure your machine specific header file (for instance
 include/asm-ppc/tqm8xx.h) includes the same definition of the Board
 Information structure as we define in include/asm-<arch>/u-boot.h,
 and make sure that your definition of IMAP_ADDR uses the same value
 as your U-Boot configuration in CONFIG_SYS_IMMR.
 Configuring the Linux kernel:
 -----------------------------
 No specific requirements for U-Boot. Make sure you have some root
 device (initial ramdisk, NFS) for your target system.
 Building a Linux Image:
 -----------------------
 With U-Boot, "normal" build targets like "zImage" or "bzImage" are
 not used. If you use recent kernel source, a new build target
 "uImage" will exist which automatically builds an image usable by
 U-Boot. Most older kernels also have support for a "pImage" target,
 which was introduced for our predecessor project PPCBoot and uses a
 100% compatible format.
 Example:
 	make TQM850L_config
 	make oldconfig
 	make dep
 	make uImage
 The "uImage" build target uses a special tool (in 'tools/mkimage') to
 encapsulate a compressed Linux kernel image with header	 information,
 CRC32 checksum etc. for use with U-Boot. This is what we are doing:
 * build a standard "vmlinux" kernel image (in ELF binary format):
 * convert the kernel into a raw binary image:
 	${CROSS_COMPILE}-objcopy -O binary \
 				 -R .note -R .comment \
 				 -S vmlinux linux.bin
 * compress the binary image:
 	gzip -9 linux.bin
 * package compressed binary image for U-Boot:
 	mkimage -A ppc -O linux -T kernel -C gzip \
 		-a 0 -e 0 -n "Linux Kernel Image" \
 		-d linux.bin.gz uImage
 The "mkimage" tool can also be used to create ramdisk images for use
 with U-Boot, either separated from the Linux kernel image, or
 combined into one file. "mkimage" encapsulates the images with a 64
 byte header containing information about target architecture,
 operating system, image type, compression method, entry points, time
 stamp, CRC32 checksums, etc.
 "mkimage" can be called in two ways: to verify existing images and
 print the header information, or to build new images.
 In the first form (with "-l" option) mkimage lists the information
 contained in the header of an existing U-Boot image; this includes
 checksum verification:
 	tools/mkimage -l image
 	  -l ==> list image header information
 The second form (with "-d" option) is used to build a U-Boot image
 from a "data file" which is used as image payload:
 	tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
 		      -n name -d data_file image
 	  -A ==> set architecture to 'arch'
 	  -O ==> set operating system to 'os'
 	  -T ==> set image type to 'type'
 	  -C ==> set compression type 'comp'
 	  -a ==> set load address to 'addr' (hex)
 	  -e ==> set entry point to 'ep' (hex)
 	  -n ==> set image name to 'name'
 	  -d ==> use image data from 'datafile'
 Right now, all Linux kernels for PowerPC systems use the same load
 address (0x00000000), but the entry point address depends on the
 kernel version:
 - 2.2.x kernels have the entry point at 0x0000000C,
 - 2.3.x and later kernels have the entry point at 0x00000000.
 So a typical call to build a U-Boot image would read:
 	-> tools/mkimage -n '2.4.4 kernel for TQM850L' \
 	> -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
 	> -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz \
 	> examples/uImage.TQM850L
 	Image Name:   2.4.4 kernel for TQM850L
 	Created:      Wed Jul 19 02:34:59 2000
 	Image Type:   PowerPC Linux Kernel Image (gzip compressed)
 	Data Size:    335725 Bytes = 327.86 kB = 0.32 MB
 	Load Address: 0x00000000
 	Entry Point:  0x00000000
 To verify the contents of the image (or check for corruption):
 	-> tools/mkimage -l examples/uImage.TQM850L
 	Image Name:   2.4.4 kernel for TQM850L
 	Created:      Wed Jul 19 02:34:59 2000
 	Image Type:   PowerPC Linux Kernel Image (gzip compressed)
 	Data Size:    335725 Bytes = 327.86 kB = 0.32 MB
 	Load Address: 0x00000000
 	Entry Point:  0x00000000
 NOTE: for embedded systems where boot time is critical you can trade
 speed for memory and install an UNCOMPRESSED image instead: this
 needs more space in Flash, but boots much faster since it does not
 need to be uncompressed:
 	-> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz
 	-> tools/mkimage -n '2.4.4 kernel for TQM850L' \
 	> -A ppc -O linux -T kernel -C none -a 0 -e 0 \
 	> -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux \
 	> examples/uImage.TQM850L-uncompressed
 	Image Name:   2.4.4 kernel for TQM850L
 	Created:      Wed Jul 19 02:34:59 2000
 	Image Type:   PowerPC Linux Kernel Image (uncompressed)
 	Data Size:    792160 Bytes = 773.59 kB = 0.76 MB
 	Load Address: 0x00000000
 	Entry Point:  0x00000000
 Similar you can build U-Boot images from a 'ramdisk.image.gz' file
 when your kernel is intended to use an initial ramdisk:
 	-> tools/mkimage -n 'Simple Ramdisk Image' \
 	> -A ppc -O linux -T ramdisk -C gzip \
 	> -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
 	Image Name:   Simple Ramdisk Image
 	Created:      Wed Jan 12 14:01:50 2000
 	Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
 	Data Size:    566530 Bytes = 553.25 kB = 0.54 MB
 	Load Address: 0x00000000
 	Entry Point:  0x00000000
 Installing a Linux Image:
 -------------------------
 To downloading a U-Boot image over the serial (console) interface,
 you must convert the image to S-Record format:
 	objcopy -I binary -O srec examples/image examples/image.srec
 The 'objcopy' does not understand the information in the U-Boot
 image header, so the resulting S-Record file will be relative to
 address 0x00000000. To load it to a given address, you need to
 specify the target address as 'offset' parameter with the 'loads'
 command.
 Example: install the image to address 0x40100000 (which on the
 TQM8xxL is in the first Flash bank):
 	=> erase 40100000 401FFFFF
 	.......... done
 	Erased 8 sectors
 	=> loads 40100000
 	## Ready for S-Record download ...
 	~>examples/image.srec
 	1 2 3 4 5 6 7 8 9 10 11 12 13 ...
 	...
 	15989 15990 15991 15992
 	[file transfer complete]
 	[connected]
 	## Start Addr = 0x00000000
 You can check the success of the download using the 'iminfo' command;
 this includes a checksum verification so you can be sure no data
 corruption happened:
 	=> imi 40100000
 	## Checking Image at 40100000 ...
 	   Image Name:	 2.2.13 for initrd on TQM850L
 	   Image Type:	 PowerPC Linux Kernel Image (gzip compressed)
 	   Data Size:	 335725 Bytes = 327 kB = 0 MB
 	   Load Address: 00000000
 	   Entry Point:	 0000000c
 	   Verifying Checksum ... OK
 Boot Linux:
 -----------
 The "bootm" command is used to boot an application that is stored in
 memory (RAM or Flash). In case of a Linux kernel image, the contents
 of the "bootargs" environment variable is passed to the kernel as
 parameters. You can check and modify this variable using the
 "printenv" and "setenv" commands:
 	=> printenv bootargs
 	bootargs=root=/dev/ram
 	=> setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
 	=> printenv bootargs
 	bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
 	=> bootm 40020000
 	## Booting Linux kernel at 40020000 ...
 	   Image Name:	 2.2.13 for NFS on TQM850L
 	   Image Type:	 PowerPC Linux Kernel Image (gzip compressed)
 	   Data Size:	 381681 Bytes = 372 kB = 0 MB
 	   Load Address: 00000000
 	   Entry Point:	 0000000c
 	   Verifying Checksum ... OK
 	   Uncompressing Kernel Image ... OK
 	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
 	Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
 	time_init: decrementer frequency = 187500000/60
 	Calibrating delay loop... 49.77 BogoMIPS
 	Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
 	...
 If you want to boot a Linux kernel with initial RAM disk, you pass
 the memory addresses of both the kernel and the initrd image (PPBCOOT
 format!) to the "bootm" command:
 	=> imi 40100000 40200000
 	## Checking Image at 40100000 ...
 	   Image Name:	 2.2.13 for initrd on TQM850L
 	   Image Type:	 PowerPC Linux Kernel Image (gzip compressed)
 	   Data Size:	 335725 Bytes = 327 kB = 0 MB
 	   Load Address: 00000000
 	   Entry Point:	 0000000c
 	   Verifying Checksum ... OK
 	## Checking Image at 40200000 ...
 	   Image Name:	 Simple Ramdisk Image
 	   Image Type:	 PowerPC Linux RAMDisk Image (gzip compressed)
 	   Data Size:	 566530 Bytes = 553 kB = 0 MB
 	   Load Address: 00000000
 	   Entry Point:	 00000000
 	   Verifying Checksum ... OK
 	=> bootm 40100000 40200000
 	## Booting Linux kernel at 40100000 ...
 	   Image Name:	 2.2.13 for initrd on TQM850L
 	   Image Type:	 PowerPC Linux Kernel Image (gzip compressed)
 	   Data Size:	 335725 Bytes = 327 kB = 0 MB
 	   Load Address: 00000000
 	   Entry Point:	 0000000c
 	   Verifying Checksum ... OK
 	   Uncompressing Kernel Image ... OK
 	## Loading RAMDisk Image at 40200000 ...
 	   Image Name:	 Simple Ramdisk Image
 	   Image Type:	 PowerPC Linux RAMDisk Image (gzip compressed)
 	   Data Size:	 566530 Bytes = 553 kB = 0 MB
 	   Load Address: 00000000
 	   Entry Point:	 00000000
 	   Verifying Checksum ... OK
 	   Loading Ramdisk ... OK
 	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
 	Boot arguments: root=/dev/ram
 	time_init: decrementer frequency = 187500000/60
 	Calibrating delay loop... 49.77 BogoMIPS
 	...
 	RAMDISK: Compressed image found at block 0
 	VFS: Mounted root (ext2 filesystem).
 	bash#
 Boot Linux and pass a flat device tree:
 -----------
 First, U-Boot must be compiled with the appropriate defines. See the section
 titled "Linux Kernel Interface" above for a more in depth explanation. The
 following is an example of how to start a kernel and pass an updated
 flat device tree:
 => print oftaddr
 oftaddr=0x300000
 => print oft
 oft=oftrees/mpc8540ads.dtb
 => tftp $oftaddr $oft
 Speed: 1000, full duplex
 Using TSEC0 device
 TFTP from server 192.168.1.1; our IP address is 192.168.1.101
 Filename 'oftrees/mpc8540ads.dtb'.
 Load address: 0x300000
 Loading: #
 done
 Bytes transferred = 4106 (100a hex)
 => tftp $loadaddr $bootfile
 Speed: 1000, full duplex
 Using TSEC0 device
 TFTP from server 192.168.1.1; our IP address is 192.168.1.2
 Filename 'uImage'.
 Load address: 0x200000
 Loading:############
 done
 Bytes transferred = 1029407 (fb51f hex)
 => print loadaddr
 loadaddr=200000
 => print oftaddr
 oftaddr=0x300000
 => bootm $loadaddr - $oftaddr
 ## Booting image at 00200000 ...
    Image Name:	 Linux-2.6.17-dirty
    Image Type:	 PowerPC Linux Kernel Image (gzip compressed)
    Data Size:	 1029343 Bytes = 1005.2 kB
    Load Address: 00000000
    Entry Point:	 00000000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK
 Booting using flat device tree at 0x300000
 Using MPC85xx ADS machine description
 Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
 [snip]
 More About U-Boot Image Types:
 ------------------------------
 U-Boot supports the following image types:
    "Standalone Programs" are directly runnable in the environment
 	provided by U-Boot; it is expected that (if they behave
 	well) you can continue to work in U-Boot after return from
 	the Standalone Program.
    "OS Kernel Images" are usually images of some Embedded OS which
 	will take over control completely. Usually these programs
 	will install their own set of exception handlers, device
 	drivers, set up the MMU, etc. - this means, that you cannot
 	expect to re-enter U-Boot except by resetting the CPU.
    "RAMDisk Images" are more or less just data blocks, and their
 	parameters (address, size) are passed to an OS kernel that is
 	being started.
    "Multi-File Images" contain several images, typically an OS
 	(Linux) kernel image and one or more data images like
 	RAMDisks. This construct is useful for instance when you want
 	to boot over the network using BOOTP etc., where the boot
 	server provides just a single image file, but you want to get
 	for instance an OS kernel and a RAMDisk image.
 	"Multi-File Images" start with a list of image sizes, each
 	image size (in bytes) specified by an "uint32_t" in network
 	byte order. This list is terminated by an "(uint32_t)0".
 	Immediately after the terminating 0 follow the images, one by
 	one, all aligned on "uint32_t" boundaries (size rounded up to
 	a multiple of 4 bytes).
    "Firmware Images" are binary images containing firmware (like
 	U-Boot or FPGA images) which usually will be programmed to
 	flash memory.
    "Script files" are command sequences that will be executed by
 	U-Boot's command interpreter; this feature is especially
 	useful when you configure U-Boot to use a real shell (hush)
 	as command interpreter.
 Standalone HOWTO:
 =================
 One of the features of U-Boot is that you can dynamically load and
 run "standalone" applications, which can use some resources of
 U-Boot like console I/O functions or interrupt services.
 Two simple examples are included with the sources:
 "Hello World" Demo:
 -------------------
 'examples/hello_world.c' contains a small "Hello World" Demo
 application; it is automatically compiled when you build U-Boot.
 It's configured to run at address 0x00040004, so you can play with it
 like that:
 	=> loads
 	## Ready for S-Record download ...
 	~>examples/hello_world.srec
 	1 2 3 4 5 6 7 8 9 10 11 ...
 	[file transfer complete]
 	[connected]
 	## Start Addr = 0x00040004
 	=> go 40004 Hello World! This is a test.
 	## Starting application at 0x00040004 ...
 	Hello World
 	argc = 7
 	argv[0] = "40004"
 	argv[1] = "Hello"
 	argv[2] = "World!"
 	argv[3] = "This"
 	argv[4] = "is"
 	argv[5] = "a"
 	argv[6] = "test."
 	argv[7] = "<NULL>"
 	Hit any key to exit ...
 	## Application terminated, rc = 0x0
 Another example, which demonstrates how to register a CPM interrupt
 handler with the U-Boot code, can be found in 'examples/timer.c'.
 Here, a CPM timer is set up to generate an interrupt every second.
 The interrupt service routine is trivial, just printing a '.'
 character, but this is just a demo program. The application can be
 controlled by the following keys:
 	? - print current values og the CPM Timer registers
 	b - enable interrupts and start timer
 	e - stop timer and disable interrupts
 	q - quit application
 	=> loads
 	## Ready for S-Record download ...
 	~>examples/timer.srec
 	1 2 3 4 5 6 7 8 9 10 11 ...
 	[file transfer complete]
 	[connected]
 	## Start Addr = 0x00040004
 	=> go 40004
 	## Starting application at 0x00040004 ...
 	TIMERS=0xfff00980
 	Using timer 1
 	  tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
 Hit 'b':
 	[q, b, e, ?] Set interval 1000000 us
 	Enabling timer
 Hit '?':
 	[q, b, e, ?] ........
 	tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
 Hit '?':
 	[q, b, e, ?] .
 	tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
 Hit '?':
 	[q, b, e, ?] .
 	tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
 Hit '?':
 	[q, b, e, ?] .
 	tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
 Hit 'e':
 	[q, b, e, ?] ...Stopping timer
 Hit 'q':
 	[q, b, e, ?] ## Application terminated, rc = 0x0
 Minicom warning:
 ================
 Over time, many people have reported problems when trying to use the
 "minicom" terminal emulation program for serial download. I (wd)
 consider minicom to be broken, and recommend not to use it. Under
 Unix, I recommend to use C-Kermit for general purpose use (and
 especially for kermit binary protocol download ("loadb" command), and
 use "cu" for S-Record download ("loads" command).
 Nevertheless, if you absolutely want to use it try adding this
 configuration to your "File transfer protocols" section:
 	   Name	   Program			Name U/D FullScr IO-Red. Multi
 	X  kermit  /usr/bin/kermit -i -l %l -s	 Y    U	   Y	   N	  N
 	Y  kermit  /usr/bin/kermit -i -l %l -r	 N    D	   Y	   N	  N
 NetBSD Notes:
 =============
 Starting at version 0.9.2, U-Boot supports NetBSD both as host
 (build U-Boot) and target system (boots NetBSD/mpc8xx).
 Building requires a cross environment; it is known to work on
 NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
 need gmake since the Makefiles are not compatible with BSD make).
 Note that the cross-powerpc package does not install include files;
 attempting to build U-Boot will fail because <machine/ansi.h> is
 missing.  This file has to be installed and patched manually:
 	# cd /usr/pkg/cross/powerpc-netbsd/include
 	# mkdir powerpc
 	# ln -s powerpc machine
 	# cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
 	# ${EDIT} powerpc/ansi.h	## must remove __va_list, _BSD_VA_LIST
 Native builds *don't* work due to incompatibilities between native
 and U-Boot include files.
 Booting assumes that (the first part of) the image booted is a
 stage-2 loader which in turn loads and then invokes the kernel
 proper. Loader sources will eventually appear in the NetBSD source
 tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
 meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
 Implementation Internals:
 =========================
 The following is not intended to be a complete description of every
 implementation detail. However, it should help to understand the
 inner workings of U-Boot and make it easier to port it to custom
 hardware.
 Initial Stack, Global Data:
 ---------------------------
 The implementation of U-Boot is complicated by the fact that U-Boot
 starts running out of ROM (flash memory), usually without access to
 system RAM (because the memory controller is not initialized yet).
 This means that we don't have writable Data or BSS segments, and BSS
 is not initialized as zero. To be able to get a C environment working
 at all, we have to allocate at least a minimal stack. Implementation
 options for this are defined and restricted by the CPU used: Some CPU
 models provide on-chip memory (like the IMMR area on MPC8xx and
 MPC826x processors), on others (parts of) the data cache can be
 locked as (mis-) used as memory, etc.
 	Chris Hallinan posted a good summary of these issues to the
 	U-Boot mailing list:
 	Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
 	From: "Chris Hallinan" <clh@net1plus.com>
 	Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
 	...
 	Correct me if I'm wrong, folks, but the way I understand it
 	is this: Using DCACHE as initial RAM for Stack, etc, does not
 	require any physical RAM backing up the cache. The cleverness
 	is that the cache is being used as a temporary supply of
 	necessary storage before the SDRAM controller is setup. It's
 	beyond the scope of this list to explain the details, but you
 	can see how this works by studying the cache architecture and
 	operation in the architecture and processor-specific manuals.
 	OCM is On Chip Memory, which I believe the 405GP has 4K. It
 	is another option for the system designer to use as an
 	initial stack/RAM area prior to SDRAM being available. Either
 	option should work for you. Using CS 4 should be fine if your
 	board designers haven't used it for something that would
 	cause you grief during the initial boot! It is frequently not
 	used.
 	CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere
 	with your processor/board/system design. The default value
 	you will find in any recent u-boot distribution in
 	walnut.h should work for you. I'd set it to a value larger
 	than your SDRAM module. If you have a 64MB SDRAM module, set
 	it above 400_0000. Just make sure your board has no resources
 	that are supposed to respond to that address! That code in
 	start.S has been around a while and should work as is when
 	you get the config right.
 	-Chris Hallinan
 	DS4.COM, Inc.
 It is essential to remember this, since it has some impact on the C
 code for the initialization procedures:
 * Initialized global data (data segment) is read-only. Do not attempt
   to write it.
 * Do not use any uninitialized global data (or implicitely initialized
   as zero data - BSS segment) at all - this is undefined, initiali-
   zation is performed later (when relocating to RAM).
 * Stack space is very limited. Avoid big data buffers or things like
   that.
 Having only the stack as writable memory limits means we cannot use
 normal global data to share information beween the code. But it
 turned out that the implementation of U-Boot can be greatly
 simplified by making a global data structure (gd_t) available to all
 functions. We could pass a pointer to this data as argument to _all_
 functions, but this would bloat the code. Instead we use a feature of
 the GCC compiler (Global Register Variables) to share the data: we
 place a pointer (gd) to the global data into a register which we
 reserve for this purpose.
 When choosing a register for such a purpose we are restricted by the
 relevant  (E)ABI  specifications for the current architecture, and by
 GCC's implementation.
 For PowerPC, the following registers have specific use:
 	R1:	stack pointer
 	R2:	reserved for system use
 	R3-R4:	parameter passing and return values
 	R5-R10: parameter passing
 	R13:	small data area pointer
 	R30:	GOT pointer
 	R31:	frame pointer
 	(U-Boot also uses R14 as internal GOT pointer.)
     ==> U-Boot will use R2 to hold a pointer to the global data
     Note: on PPC, we could use a static initializer (since the
     address of the global data structure is known at compile time),
     but it turned out that reserving a register results in somewhat
     smaller code - although the code savings are not that big (on
     average for all boards 752 bytes for the whole U-Boot image,
     624 text + 127 data).
 On Blackfin, the normal C ABI (except for P3) is followed as documented here:
 	http://docs.blackfin.uclinux.org/doku.php?id=application_binary_interface
     ==> U-Boot will use P3 to hold a pointer to the global data
 On ARM, the following registers are used:
 	R0:	function argument word/integer result
 	R1-R3:	function argument word
 	R9:	GOT pointer
 	R10:	stack limit (used only if stack checking if enabled)
 	R11:	argument (frame) pointer
 	R12:	temporary workspace
 	R13:	stack pointer
 	R14:	link register
 	R15:	program counter
     ==> U-Boot will use R8 to hold a pointer to the global data
 NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,
 or current versions of GCC may "optimize" the code too much.
 Memory Management:
 ------------------
 U-Boot runs in system state and uses physical addresses, i.e. the
 MMU is not used either for address mapping nor for memory protection.
 The available memory is mapped to fixed addresses using the memory
 controller. In this process, a contiguous block is formed for each
 memory type (Flash, SDRAM, SRAM), even when it consists of several
 physical memory banks.
 U-Boot is installed in the first 128 kB of the first Flash bank (on
 TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
 booting and sizing and initializing DRAM, the code relocates itself
 to the upper end of DRAM. Immediately below the U-Boot code some
 memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN
 configuration setting]. Below that, a structure with global Board
 Info data is placed, followed by the stack (growing downward).
 Additionally, some exception handler code is copied to the low 8 kB
 of DRAM (0x00000000 ... 0x00001FFF).
 So a typical memory configuration with 16 MB of DRAM could look like
 this:
 	0x0000 0000	Exception Vector code
 	      :
 	0x0000 1FFF
 	0x0000 2000	Free for Application Use
 	      :
 	      :
 	      :
 	      :
 	0x00FB FF20	Monitor Stack (Growing downward)
 	0x00FB FFAC	Board Info Data and permanent copy of global data
 	0x00FC 0000	Malloc Arena
 	      :
 	0x00FD FFFF
 	0x00FE 0000	RAM Copy of Monitor Code
 	...		eventually: LCD or video framebuffer
 	...		eventually: pRAM (Protected RAM - unchanged by reset)
 	0x00FF FFFF	[End of RAM]
 System Initialization:
 ----------------------
 In the reset configuration, U-Boot starts at the reset entry point
 (on most PowerPC systems at address 0x00000100). Because of the reset
 configuration for CS0# this is a mirror of the onboard Flash memory.
 To be able to re-map memory U-Boot then jumps to its link address.
 To be able to implement the initialization code in C, a (small!)
 initial stack is set up in the internal Dual Ported RAM (in case CPUs
 which provide such a feature like MPC8xx or MPC8260), or in a locked
 part of the data cache. After that, U-Boot initializes the CPU core,
 the caches and the SIU.
 Next, all (potentially) available memory banks are mapped using a
 preliminary mapping. For example, we put them on 512 MB boundaries
 (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
 on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
 programmed for SDRAM access. Using the temporary configuration, a
 simple memory test is run that determines the size of the SDRAM
 banks.
 When there is more than one SDRAM bank, and the banks are of
 different size, the largest is mapped first. For equal size, the first
 bank (CS2#) is mapped first. The first mapping is always for address
 0x00000000, with any additional banks following immediately to create
 contiguous memory starting from 0.
 Then, the monitor installs itself at the upper end of the SDRAM area
 and allocates memory for use by malloc() and for the global Board
 Info data; also, the exception vector code is copied to the low RAM
 pages, and the final stack is set up.
 Only after this relocation will you have a "normal" C environment;
 until that you are restricted in several ways, mostly because you are
 running from ROM, and because the code will have to be relocated to a
 new address in RAM.
 U-Boot Porting Guide:
 ----------------------
 [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
 list, October 2002]
 int main(int argc, char *argv[])
 {
 	sighandler_t no_more_time;
 	signal(SIGALRM, no_more_time);
 	alarm(PROJECT_DEADLINE - toSec (3 * WEEK));
 	if (available_money > available_manpower) {
 		Pay consultant to port U-Boot;
 		return 0;
 	}
 	Download latest U-Boot source;
 	Subscribe to u-boot mailing list;
 	if (clueless)
 		email("Hi, I am new to U-Boot, how do I get started?");
 	while (learning) {
 		Read the README file in the top level directory;
 		Read http://www.denx.de/twiki/bin/view/DULG/Manual;
 		Read applicable doc/*.README;
 		Read the source, Luke;
 		/* find . -name "*.[chS]" | xargs grep -i <keyword> */
 	}
 	if (available_money > toLocalCurrency ($2500))
 		Buy a BDI3000;
 	else
 		Add a lot of aggravation and time;
 	if (a similar board exists) {	/* hopefully... */
 		cp -a board/<similar> board/<myboard>
 		cp include/configs/<similar>.h include/configs/<myboard>.h
 	} else {
 		Create your own board support subdirectory;
 		Create your own board include/configs/<myboard>.h file;
 	}
 	Edit new board/<myboard> files
 	Edit new include/configs/<myboard>.h
 	while (!accepted) {
 		while (!running) {
 			do {
 				Add / modify source code;
 			} until (compiles);
 			Debug;
 			if (clueless)
 				email("Hi, I am having problems...");
 		}
 		Send patch file to the U-Boot email list;
 		if (reasonable critiques)
 			Incorporate improvements from email list code review;
 		else
 			Defend code as written;
 	}
 	return 0;
 }
 void no_more_time (int sig)
 {
       hire_a_guru();
 }
 Coding Standards:
 -----------------
 All contributions to U-Boot should conform to the Linux kernel
 coding style; see the file "Documentation/CodingStyle" and the script
 "scripts/Lindent" in your Linux kernel source directory.  In sources
 originating from U-Boot a style corresponding to "Lindent -pcs" (adding
 spaces before parameters to function calls) is actually used.
 Source files originating from a different project (for example the
 MTD subsystem) are generally exempt from these guidelines and are not
 reformated to ease subsequent migration to newer versions of those
 sources.
 Please note that U-Boot is implemented in C (and to some small parts in
 Assembler); no C++ is used, so please do not use C++ style comments (//)
 in your code.
 Please also stick to the following formatting rules:
 - remove any trailing white space
 - use TAB characters for indentation, not spaces
 - make sure NOT to use DOS '\r\n' line feeds
 - do not add more than 2 empty lines to source files
 - do not add trailing empty lines to source files
 Submissions which do not conform to the standards may be returned
 with a request to reformat the changes.
 Submitting Patches:
 -------------------
 Since the number of patches for U-Boot is growing, we need to
 establish some rules. Submissions which do not conform to these rules
 may be rejected, even when they contain important and valuable stuff.
 Please see http://www.denx.de/wiki/U-Boot/Patches for details.
 Patches shall be sent to the u-boot mailing list <u-boot@lists.denx.de>;
 see http://lists.denx.de/mailman/listinfo/u-boot
 When you send a patch, please include the following information with
 it:
 * For bug fixes: a description of the bug and how your patch fixes
   this bug. Please try to include a way of demonstrating that the
   patch actually fixes something.
 * For new features: a description of the feature and your
   implementation.
 * A CHANGELOG entry as plaintext (separate from the patch)
 * For major contributions, your entry to the CREDITS file
 * When you add support for a new board, don't forget to add this
   board to the MAKEALL script, too.
 * If your patch adds new configuration options, don't forget to
   document these in the README file.
 * The patch itself. If you are using git (which is *strongly*
   recommended) you can easily generate the patch using the
   "git-format-patch". If you then use "git-send-email" to send it to
   the U-Boot mailing list, you will avoid most of the common problems
   with some other mail clients.
   If you cannot use git, use "diff -purN OLD NEW". If your version of
   diff does not support these options, then get the latest version of
   GNU diff.
   The current directory when running this command shall be the parent
   directory of the U-Boot source tree (i. e. please make sure that
   your patch includes sufficient directory information for the
   affected files).
   We prefer patches as plain text. MIME attachments are discouraged,
   and compressed attachments must not be used.
 * If one logical set of modifications affects or creates several
   files, all these changes shall be submitted in a SINGLE patch file.
 * Changesets that contain different, unrelated modifications shall be
   submitted as SEPARATE patches, one patch per changeset.
 Notes:
 * Before sending the patch, run the MAKEALL script on your patched
   source tree and make sure that no errors or warnings are reported
   for any of the boards.
 * Keep your modifications to the necessary minimum: A patch
   containing several unrelated changes or arbitrary reformats will be
   returned with a request to re-formatting / split it.
 * If you modify existing code, make sure that your new code does not
   add to the memory footprint of the code ;-) Small is beautiful!
   When adding new features, these should compile conditionally only
   (using #ifdef), and the resulting code with the new feature
   disabled must not need more memory than the old code without your
   modification.
 * Remember that there is a size limit of 100 kB per message on the
   u-boot mailing list. Bigger patches will be moderated. If they are
   reasonable and not too big, they will be acknowledged. But patches
   bigger than the size limit should be avoided.

 /*
  * (C) Copyright 2003
  * Wolfgang Denk, DENX Software Engineering, wd@denx.de.
  *
  * See file CREDITS for list of people who contributed to this
  * project.
  *
  * This program is free software; you can redistribute it and/or
  * modify it under the terms of the GNU General Public License as
  * published by the Free Software Foundation; either version 2 of
  * the License, or (at your option) any later version.
  *
  * This program is distributed in the hope that it will be useful,
  * but WITHOUT ANY WARRANTY; without even the implied warranty of
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  * GNU General Public License for more details.
  *
  * You should have received a copy of the GNU General Public License
  * along with this program; if not, write to the Free Software
  * Foundation, Inc., 59 Temple Place, Suite 330, Boston,
  * MA 02111-1307 USA
  */
 #include <common.h>
 DECLARE_GLOBAL_DATA_PTR;
 #ifdef CONFIG_HARD_I2C
 #include <mpc5xxx.h>
 #include <i2c.h>
 #if (CONFIG_SYS_I2C_MODULE == 2)
 #define I2C_BASE	MPC5XXX_I2C2
 #elif (CONFIG_SYS_I2C_MODULE == 1)
 #define I2C_BASE	MPC5XXX_I2C1
 #else
 #error CONFIG_SYS_I2C_MODULE is not properly configured
 #endif
 #define I2C_TIMEOUT	6667
 #define I2C_RETRIES	3
 struct mpc5xxx_i2c_tap {
 	int scl2tap;
 	int tap2tap;
 };
 static int  mpc_reg_in    (volatile u32 *reg);
 static void mpc_reg_out   (volatile u32 *reg, int val, int mask);
 static int  wait_for_bb   (void);
 static int  wait_for_pin  (int *status);
 static int  do_address    (uchar chip, char rdwr_flag);
 static int  send_bytes    (uchar chip, char *buf, int len);
 static int  receive_bytes (uchar chip, char *buf, int len);
 static int  mpc_get_fdr   (int);
 static int mpc_reg_in(volatile u32 *reg)
 {
 	int ret = *reg >> 24;
 	__asm__ __volatile__ ("eieio");
 	return ret;
 }
 static void mpc_reg_out(volatile u32 *reg, int val, int mask)
 {
 	int tmp;
 	if (!mask) {
 		*reg = val << 24;
 	} else {
 		tmp = mpc_reg_in(reg);
 		*reg = ((tmp & ~mask) | (val & mask)) << 24;
 	}
 	__asm__ __volatile__ ("eieio");
 	return;
 }
 static int wait_for_bb(void)
 {
 	struct mpc5xxx_i2c *regs    = (struct mpc5xxx_i2c *)I2C_BASE;
 	int                 timeout = I2C_TIMEOUT;
 	int                 status;
 	status = mpc_reg_in(&regs->msr);
 	while (timeout-- && (status & I2C_BB)) {
 #if 1
 		volatile int temp;
 		mpc_reg_out(&regs->mcr, I2C_STA, I2C_STA);
 		temp = mpc_reg_in(&regs->mdr);
 		mpc_reg_out(&regs->mcr, 0, I2C_STA);
 		mpc_reg_out(&regs->mcr, 0, 0);
 		mpc_reg_out(&regs->mcr, I2C_EN, 0);
 #endif
 		udelay(15);
 		status = mpc_reg_in(&regs->msr);
 	}
 	return (status & I2C_BB);
 }
 static int wait_for_pin(int *status)
 {
 	struct mpc5xxx_i2c *regs    = (struct mpc5xxx_i2c *)I2C_BASE;
 	int                 timeout = I2C_TIMEOUT;
 	*status = mpc_reg_in(&regs->msr);
 	while (timeout-- && !(*status & I2C_IF)) {
 		udelay(15);
 		*status = mpc_reg_in(&regs->msr);
 	}
 	if (!(*status & I2C_IF)) {
 		return -1;
 	}
 	mpc_reg_out(&regs->msr, 0, I2C_IF);
 	return 0;
 }
 static int do_address(uchar chip, char rdwr_flag)
 {
 	struct mpc5xxx_i2c *regs = (struct mpc5xxx_i2c *)I2C_BASE;
 	int                 status;
 	chip <<= 1;
 	if (rdwr_flag) {
 		chip |= 1;
 	}
 	mpc_reg_out(&regs->mcr, I2C_TX, I2C_TX);
 	mpc_reg_out(&regs->mdr, chip, 0);
 	if (wait_for_pin(&status)) {
 		return -2;
 	}
 	if (status & I2C_RXAK) {
 		return -3;
 	}
 	return 0;
 }
 static int send_bytes(uchar chip, char *buf, int len)
 {
 	struct mpc5xxx_i2c *regs = (struct mpc5xxx_i2c *)I2C_BASE;
 	int                 wrcount;
 	int                 status;
 	for (wrcount = 0; wrcount < len; ++wrcount) {
 		mpc_reg_out(&regs->mdr, buf[wrcount], 0);
 		if (wait_for_pin(&status)) {
 			break;
 		}
 		if (status & I2C_RXAK) {
 			break;
 		}
 	}
 	return !(wrcount == len);
 }
 static int receive_bytes(uchar chip, char *buf, int len)
 {
 	struct mpc5xxx_i2c *regs    = (struct mpc5xxx_i2c *)I2C_BASE;
 	int                 dummy   = 1;
 	int                 rdcount = 0;
 	int                 status;
 	int                 i;
 	mpc_reg_out(&regs->mcr, 0, I2C_TX);
 	for (i = 0; i < len; ++i) {
 		buf[rdcount] = mpc_reg_in(&regs->mdr);
 		if (dummy) {
 			dummy = 0;
 		} else {
 			rdcount++;
 		}
 		if (wait_for_pin(&status)) {
 			return -4;
 		}
 	}
 	mpc_reg_out(&regs->mcr, I2C_TXAK, I2C_TXAK);
 	buf[rdcount++] = mpc_reg_in(&regs->mdr);
 	if (wait_for_pin(&status)) {
 		return -5;
 	}
 	mpc_reg_out(&regs->mcr, 0, I2C_TXAK);
 	return 0;
 }
+#if defined(CONFIG_SYS_I2C_INIT_MPC5XXX)
+#define FDR510(x) (u8) (((x & 0x20) >> 3) | (x & 0x3))
+#define FDR432(x) (u8) ((x & 0x1C) >> 2)
+/*
+ * Reset any i2c devices that may have been interrupted during a system reset.
+ * Normally this would be accomplished by clocking the line until SCL and SDA
+ * are released and then sending a start condtiion (From an Atmel datasheet).
+ * There is no direct access to the i2c pins so instead create start commands
+ * through the i2c interface.  Send a start command then delay for the SDA Hold
+ * time, repeat this by disabling/enabling the bus a total of 9 times.
+ */
+static void send_reset(void)
+{
+	struct mpc5xxx_i2c *regs = (struct mpc5xxx_i2c *)I2C_BASE;
+	int i;
+	u32 delay;
+	u8 fdr;
+	int SDA_Tap[] = { 3, 3, 4, 4, 1, 1, 2, 2};
+	struct mpc5xxx_i2c_tap scltap[] = {
+		{4, 1},
+		{4, 2},
+		{6, 4},
+		{6, 8},
+		{14, 16},
+		{30, 32},
+		{62, 64},
+		{126, 128}
+	};
+	fdr = (u8)mpc_reg_in(&regs->mfdr);
+	delay = scltap[FDR432(fdr)].scl2tap + ((SDA_Tap[FDR510(fdr)] - 1) * \
+		scltap[FDR432(fdr)].tap2tap) + 3;
+	for (i = 0; i < 9; i++) {
+		mpc_reg_out(&regs->mcr, I2C_EN|I2C_STA|I2C_TX, I2C_INIT_MASK);
+		udelay(delay);
+		mpc_reg_out(&regs->mcr, 0, I2C_INIT_MASK);
+		udelay(delay);
+	}
+	mpc_reg_out(&regs->mcr, I2C_EN, I2C_INIT_MASK);
+}
+#endif /* CONFIG_SYS_I2c_INIT_MPC5XXX */
 /**************** I2C API ****************/
 void i2c_init(int speed, int saddr)
 {
 	struct mpc5xxx_i2c *regs = (struct mpc5xxx_i2c *)I2C_BASE;
 	mpc_reg_out(&regs->mcr, 0, 0);
 	mpc_reg_out(&regs->madr, saddr << 1, 0);
 	/* Set clock
 	 */
 	mpc_reg_out(&regs->mfdr, mpc_get_fdr(speed), 0);
 	/* Enable module
 	 */
 	mpc_reg_out(&regs->mcr, I2C_EN, I2C_INIT_MASK);
 	mpc_reg_out(&regs->msr, 0, I2C_IF);
+#if defined(CONFIG_SYS_I2C_INIT_MPC5XXX)
+	send_reset();
+#endif
 	return;
 }
 static int mpc_get_fdr(int speed)
 {
 	static int fdr = -1;
 	if (fdr == -1) {
 		ulong best_speed = 0;
 		ulong divider;
 		ulong ipb, scl;
 		ulong bestmatch = 0xffffffffUL;
 		int best_i = 0, best_j = 0, i, j;
 		int SCL_Tap[] = { 9, 10, 12, 15, 5, 6, 7, 8};
 		struct mpc5xxx_i2c_tap scltap[] = {
 			{4, 1},
 			{4, 2},
 			{6, 4},
 			{6, 8},
 			{14, 16},
 			{30, 32},
 			{62, 64},
 			{126, 128}
 		};
 		ipb = gd->ipb_clk;
 		for (i = 7; i >= 0; i--) {
 			for (j = 7; j >= 0; j--) {
 				scl = 2 * (scltap[j].scl2tap +
 					(SCL_Tap[i] - 1) * scltap[j].tap2tap + 2);
 				if (ipb <= speed*scl) {
 					if ((speed*scl - ipb) < bestmatch) {
 						bestmatch = speed*scl - ipb;
 						best_i = i;
 						best_j = j;
 						best_speed = ipb/scl;
 					}
 				}
 			}
 		}
 		divider = (best_i & 3) | ((best_i & 4) << 3) | (best_j << 2);
 		if (gd->flags & GD_FLG_RELOC) {
 			fdr = divider;
 		} else {
 			if (gd->have_console)
 				printf("%ld kHz, ", best_speed / 1000);
 			return divider;
 		}
 	}
 	return fdr;
 }
 int i2c_probe(uchar chip)
 {
 	struct mpc5xxx_i2c *regs = (struct mpc5xxx_i2c *)I2C_BASE;
 	int                 i;
 	for (i = 0; i < I2C_RETRIES; i++) {
 		mpc_reg_out(&regs->mcr, I2C_STA, I2C_STA);
 		if (! do_address(chip, 0)) {
 			mpc_reg_out(&regs->mcr, 0, I2C_STA);
 			udelay(500);
 			break;
 		}
 		mpc_reg_out(&regs->mcr, 0, I2C_STA);
 		udelay(500);
 	}
 	return (i == I2C_RETRIES);
 }
 int i2c_read(uchar chip, uint addr, int alen, uchar *buf, int len)
 {
 	char                xaddr[4];
 	struct mpc5xxx_i2c * regs        = (struct mpc5xxx_i2c *)I2C_BASE;
 	int                  ret         = -1;
 	xaddr[0] = (addr >> 24) & 0xFF;
 	xaddr[1] = (addr >> 16) & 0xFF;
 	xaddr[2] = (addr >>  8) & 0xFF;
 	xaddr[3] =  addr	& 0xFF;
 	if (wait_for_bb()) {
 		if (gd->have_console)
 			printf("i2c_read: bus is busy\n");
 		goto Done;
 	}
 	mpc_reg_out(&regs->mcr, I2C_STA, I2C_STA);
 	if (do_address(chip, 0)) {
 		if (gd->have_console)
 			printf("i2c_read: failed to address chip\n");
 		goto Done;
 	}
 	if (send_bytes(chip, &xaddr[4-alen], alen)) {
 		if (gd->have_console)
 			printf("i2c_read: send_bytes failed\n");
 		goto Done;
 	}
 	mpc_reg_out(&regs->mcr, I2C_RSTA, I2C_RSTA);
 	if (do_address(chip, 1)) {
 		if (gd->have_console)
 			printf("i2c_read: failed to address chip\n");
 		goto Done;
 	}
 	if (receive_bytes(chip, (char *)buf, len)) {
 		if (gd->have_console)
 			printf("i2c_read: receive_bytes failed\n");
 		goto Done;
 	}
 	ret = 0;
 Done:
 	mpc_reg_out(&regs->mcr, 0, I2C_STA);
 	return ret;
 }
 int i2c_write(uchar chip, uint addr, int alen, uchar *buf, int len)
 {
 	char               xaddr[4];
 	struct mpc5xxx_i2c *regs        = (struct mpc5xxx_i2c *)I2C_BASE;
 	int                 ret         = -1;
 	xaddr[0] = (addr >> 24) & 0xFF;
 	xaddr[1] = (addr >> 16) & 0xFF;
 	xaddr[2] = (addr >>  8) & 0xFF;
 	xaddr[3] =  addr	& 0xFF;
 	if (wait_for_bb()) {
 		if (gd->have_console)
 			printf("i2c_write: bus is busy\n");
 		goto Done;
 	}
 	mpc_reg_out(&regs->mcr, I2C_STA, I2C_STA);
 	if (do_address(chip, 0)) {
 		if (gd->have_console)
 			printf("i2c_write: failed to address chip\n");
 		goto Done;
 	}
 	if (send_bytes(chip, &xaddr[4-alen], alen)) {
 		if (gd->have_console)
 			printf("i2c_write: send_bytes failed\n");
 		goto Done;
 	}
 	if (send_bytes(chip, (char *)buf, len)) {
 		if (gd->have_console)
 			printf("i2c_write: send_bytes failed\n");
 		goto Done;
 	}
 	ret = 0;
 Done:
 	mpc_reg_out(&regs->mcr, 0, I2C_STA);
 	return ret;
 }
 #endif	/* CONFIG_HARD_I2C */

 /*
  * (C) Copyright 2003-2005
  * Wolfgang Denk, DENX Software Engineering, wd@denx.de.
  *
  * (C) Copyright 2006
  * Eric Schumann, Phytec Messatechnik GmbH
  *
  * (C) Copyright 2009
  * Jon Smirl <jonsmirl@gmail.com>
  *
  * (C) Copyright 2009
  * Eric Millbrandt, DEKA Research and Development Corporation
  *
  * See file CREDITS for list of people who contributed to this
  * project.
  *
  * This program is free software; you can redistribute it and/or
  * modify it under the terms of the GNU General Public License as
  * published by the Free Software Foundation; either version 2 of
  * the License, or (at your option) any later version.
  *
  * This program is distributed in the hope that it will be useful,
  * but WITHOUT ANY WARRANTY; without even the implied warranty of
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.	 See the
  * GNU General Public License for more details.
  *
  * You should have received a copy of the GNU General Public License
  * along with this program; if not, write to the Free Software
  * Foundation, Inc., 59 Temple Place, Suite 330, Boston,
  * MA 02111-1307 USA
  */
 #ifndef __CONFIG_H
 #define __CONFIG_H
 #define CONFIG_BOARDINFO	 "galaxy5200"
 /*
  * High Level Configuration Options
  * (easy to change)
  */
 #define CONFIG_MPC5xxx		1	/* This is an MPC5xxx CPU */
 #define CONFIG_MPC5200		1	/* (more precisely an MPC5200 CPU) */
 #define CONFIG_SYS_MPC5XXX_CLKIN 33333333	/* ... running at 33.333333MHz */
 #define BOOTFLAG_COLD		0x01	/* Normal Power-On: Boot from FLASH */
 #define BOOTFLAG_WARM		0x02	/* Software reboot */
 /*
  * Serial console configuration
  */
 #define CONFIG_PSC_CONSOLE	4	/* console is on PSC4 -> */
 					/* define gps port conf. */
 					/* register later on to  */
 					/* enable UART function! */
 #define CONFIG_BAUDRATE		115200	/* ... at 115200 bps */
 #define CONFIG_SYS_BAUDRATE_TABLE { 9600, 19200, 38400, 57600, 115200, 230400 }
 /*
  * Command line configuration.
  */
 #include <config_cmd_default.h>
 #define CONFIG_CMD_DATE
 #define CONFIG_CMD_DHCP
 #define CONFIG_CMD_EEPROM
 #define CONFIG_CMD_I2C
 #define CONFIG_CMD_JFFS2
 #define CONFIG_CMD_MII
 #define CONFIG_CMD_NFS
 #define CONFIG_CMD_SNTP
 #define CONFIG_CMD_PING
 #define CONFIG_CMD_ASKENV
 #define CONFIG_CMD_USB
 #define CONFIG_CMD_CACHE
 #define CONFIG_CMD_FAT
 #define	CONFIG_TIMESTAMP	1	/* Print image info with timestamp */
 #if (TEXT_BASE == 0xFE000000)		/* Boot low */
 #define CONFIG_SYS_LOWBOOT 1
 #endif
 /* RAMBOOT will be defined automatically in memory section */
 #define MTDIDS_DEFAULT		"nor0=physmap-flash.0"
 #define MTDPARTS_DEFAULT	"mtdparts=physmap-flash.0:256k(ubootl)," \
 	"1792k(kernel),13312k(jffs2),256k(uboot)ro,256k(oftree),-(space)"
 /*
  * Autobooting
  */
 #define CONFIG_BOOTDELAY	3	/* autoboot after 3 seconds */
 #define CONFIG_ZERO_BOOTDELAY_CHECK	/* allow stopping of boot process */
 					/* even with bootdelay=0 */
 #undef	CONFIG_BOOTARGS
 #define CONFIG_PREBOOT	"echo;"	\
 	"echo Welcome to U-Boot;"\
 	"echo"
 /*
  * IPB Bus clocking configuration.
  */
 #define CONFIG_SYS_IPBCLK_EQUALS_XLBCLK	/* define for 133MHz speed */
 #define CONFIG_SYS_XLB_PIPELINING	1
 /*
  * I2C configuration
  */
 #define CONFIG_HARD_I2C 1		/* I2C with hardware support */
 #define CONFIG_SYS_I2C_MODULE 2		/* Select I2C module #1 or #2 */
 #define CONFIG_SYS_I2C_SPEED 100000	/* 100 kHz */
 #define CONFIG_SYS_I2C_SLAVE 0x7F
+#define CONFIG_SYS_I2C_INIT_MPC5XXX	/* Reset devices on i2c bus */
 /*
  * EEPROM CAT24WC32 configuration
  */
 #define CONFIG_SYS_I2C_EEPROM_ADDR	0x52	/* 1010100x */
 #define CONFIG_SYS_I2C_FACT_ADDR	0x52	/* EEPROM CAT24WC32 */
 #define CONFIG_SYS_I2C_EEPROM_ADDR_LEN	2	/* Bytes of address */
 #define CONFIG_SYS_EEPROM_SIZE		4096
 #define CONFIG_SYS_EEPROM_PAGE_WRITE_BITS 3
 #define CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS 15
 /*
  * RTC configuration
  */
 #define RTC
 #define CONFIG_RTC_DS3231		1
 #define CONFIG_SYS_I2C_RTC_ADDR		0x68
 /*
  * Flash configuration
  */
 #define CONFIG_SYS_FLASH_BASE		0xfe000000
 /*
  * The flash size is autoconfigured, but cpu/mpc5xxx/cpu_init.c needs this
  * variable defined
  */
 #define CONFIG_SYS_FLASH_SIZE		0x02000000
 #define CONFIG_SYS_FLASH_BANKS_LIST	{ CONFIG_SYS_FLASH_BASE }
 #define CONFIG_SYS_FLASH_CFI 1		/* Flash is CFI conformant */
 #define CONFIG_FLASH_CFI_DRIVER	1	/* Use the common driver */
 #define CONFIG_SYS_FLASH_EMPTY_INFO
 #define CONFIG_SYS_MAX_FLASH_SECT 259	/* max num of sects on one chip */
 #define CONFIG_SYS_MAX_FLASH_BANKS 1	/* max num of flash banks */
 					/* (= chip selects) */
 #define CONFIG_SYS_FLASH_USE_BUFFER_WRITE
 /*
  * Use hardware protection. This seems required, as the BDI uses hardware
  * protection. Without this, U-Boot can't work with this sectors as its
  * protection is software only by default.
  */
 #define CONFIG_SYS_FLASH_PROTECTION	1
 /*
  * Environment settings
  */
 #define CONFIG_ENV_IS_IN_EEPROM	1
 #define CONFIG_ENV_OFFSET	0x00	/* environment starts at the */
 					/* beginning of the EEPROM */
 #define CONFIG_ENV_SIZE		CONFIG_SYS_EEPROM_SIZE
 #define CONFIG_ENV_OVERWRITE	1
 /*
  * SDRAM configuration
  */
 #define SDRAM_DDR	1
 #define SDRAM_MODE	0x018D0000
 #define SDRAM_EMODE	0x40090000
 #define SDRAM_CONTROL	0x71500F00
 #define SDRAM_CONFIG1	0x73711930
 #define SDRAM_CONFIG2	0x47770000
 /*
  * Memory map
  */
 #define CONFIG_SYS_MBAR	0xF0000000	/* MBAR has to be switched by other */
 					/* bootloader or debugger config */
 #define CONFIG_SYS_SDRAM_BASE		0x00000000
 #define CONFIG_SYS_DEFAULT_MBAR		0x80000000
 /* Use SRAM until RAM will be available */
 #define CONFIG_SYS_INIT_RAM_ADDR	MPC5XXX_SRAM
 /* End of used area in SPRAM */
 #define CONFIG_SYS_INIT_RAM_END		MPC5XXX_SRAM_SIZE
 /* Size in bytes reserved for initial data */
 #define CONFIG_SYS_GBL_DATA_SIZE	128
 #define CONFIG_SYS_GBL_DATA_OFFSET	(CONFIG_SYS_INIT_RAM_END - \
 						CONFIG_SYS_GBL_DATA_SIZE)
 #define CONFIG_SYS_INIT_SP_OFFSET	CONFIG_SYS_GBL_DATA_OFFSET
 #define CONFIG_SYS_MONITOR_BASE	TEXT_BASE
 #if (CONFIG_SYS_MONITOR_BASE < CONFIG_SYS_FLASH_BASE)
 #	define CONFIG_SYS_RAMBOOT		1
 #endif
 #define CONFIG_SYS_MONITOR_LEN (192 << 10)	/* Reserve 192 kB for Monitor */
 #define CONFIG_SYS_MALLOC_LEN (128 << 10)	/* Reserve 128 kB for malloc() */
 #define CONFIG_SYS_BOOTMAPSZ (8 << 20)	/* Initial Memory map for Linux */
 /* Chip Select configuration for NAND flash */
 #define CONFIG_SYS_CS1_START		0x20000000
 #define CONFIG_SYS_CS1_SIZE		0x90000
 #define CONFIG_SYS_CS1_CFG		0x0002d900
 /* Chip Select configuration for Epson S1D13513 */
 #define CONFIG_SYS_CS3_START		0x10000000
 #define CONFIG_SYS_CS3_SIZE		0x400000
 #define CONFIG_SYS_CS3_CFG		0xffff3d10
 /*
  * Ethernet configuration
  */
 #define CONFIG_MPC5xxx_FEC		1
 #define CONFIG_MPC5xxx_FEC_MII100
 #define CONFIG_PHY_ADDR			0x01
 #define CONFIG_NO_AUTOLOAD		1
 /*
  * GPIO configuration
  *
  * GPS port configuration
  *
  * [29:31] = 01x
  * AC97 on PSC1
  * PSC1_0 -> AC97 SDATA out
  * PSC1_1 -> AC97 SDTA in
  * PSC1_2 -> AC97 SYNC out
  * PSC1_3 -> AC97 bitclock out
  * PSC1_4 -> AC97 reset out
  *
  * [28] = Reserved
  *
  * [25:27] = 110
  * SPI on PSC2
  * PSC2_0 -> MOSI
  * PSC2_1 -> MISO
  * PSC2_2 -> n/a
  * PSC2_3 -> CLK
  * PSC2_4 -> SS
  *
  * [24] = Reserved
  *
  * [20:23] = 0001
  * USB on PSC3
  * PSC3_0 -> USB_OE OE out
  * PSC3_1 -> USB_TXN Tx- out
  * PSC3_2 -> USB_TXP Tx+ out
  * PSC3_3 -> USB_TXD
  * PSC3_4 -> USB_RXP Rx+ in
  * PSC3_5 -> USB_RXN Rx- in
  * PSC3_6 -> USB_PWR PortPower out
  * PSC3_7 -> USB_SPEED speed out
  * PSC3_8 -> USB_SUSPEND suspend
  * PSC3_9 -> USB_OVRCURNT overcurrent in
  *
  * [18:19] = 10
  * Two UARTs
  *
  * [17] = 0
  * USB differential mode
  *
  * [16] = 1
  * PCI disabled
  *
  * [12:15] = 0101
  * Ethernet 100Mbit with MD
  * ETH_0 -> ETH Txen
  * ETH_1 -> ETH TxD0
  * ETH_2 -> ETH TxD1
  * ETH_3 -> ETH TxD2
  * ETH_4 -> ETH TxD3
  * ETH_5 -> ETH Txerr
  * ETH_6 -> ETH MDC
  * ETH_7 -> ETH MDIO
  * ETH_8 -> ETH RxDv
  * ETH_9 -> ETH RxCLK
  * ETH_10 -> ETH Collision
  * ETH_11 -> ETH TxD
  * ETH_12 -> ETH RxD0
  * ETH_13 -> ETH RxD1
  * ETH_14 -> ETH RxD2
  * ETH_15 -> ETH RxD3
  * ETH_16 -> ETH Rxerr
  * ETH_17 -> ETH CRS
  *
  * [9:11] = 111
  * SPI on PSC6
  * PSC6_0 -> MISO
  * PSC6_1 -> SS#
  * PSC6_2 -> MOSI
  * PSC6_3 -> CLK
  *
  * [8] = 0
  * IrDA/USB 48MHz clock generated internally
  *
  * [6:7] = 01
  * ATA chip selects on csb_4/5
  * CSB_4 -> ATA_CS0 out
  * CSB_5 -> ATA_CS1 out
  *
  * [5] = 1
  * PSC3_4 is used as CS6
  *
  * [4] = 1
  * PSC3_5 is used as CS7
  *
  * [2:3] = 00
  * No Alternatives
  *
  * [1] = 0
  * gpio_wkup_7 is GPIO
  *
  * [0] = 0
  * gpio_wkup_6 is GPIO
  *
  */
 #define CONFIG_SYS_GPS_PORT_CONFIG	0x0d75a162
 /*
  * Miscellaneous configurable options
  */
 #define CONFIG_SYS_LONGHELP			/* undef to save memory */
 #define CONFIG_SYS_PROMPT "uboot> "		/* Monitor Command Prompt */
 #define CONFIG_CMDLINE_EDITING 1		/* add command line history */
 #define CONFIG_SYS_CACHELINE_SIZE 32		/* For MPC5xxx CPUs */
 #if defined(CONFIG_CMD_KGDB)
 #define CONFIG_SYS_CACHELINE_SHIFT 5		/* log base 2 of the above value */
 #endif
 #if defined(CONFIG_CMD_KGDB)
 #define CONFIG_SYS_CBSIZE 1024			/* Console I/O Buffer Size */
 #else
 #define CONFIG_SYS_CBSIZE 512			/* Console I/O Buffer Size */
 #endif
 #define CONFIG_SYS_PBSIZE (CONFIG_SYS_CBSIZE + sizeof(CONFIG_SYS_PROMPT) + 16)
 						/* Print Buffer Size */
 #define CONFIG_SYS_MAXARGS 32			/* max number of command args */
 #define CONFIG_SYS_BARGSIZE CONFIG_SYS_CBSIZE	/* Boot Argument Buffer Size */
 #define CONFIG_SYS_MEMTEST_START 0x00100000	/* memtest works on */
 #define CONFIG_SYS_MEMTEST_END 0x00f00000	/* 1 ... 15 MB in DRAM */
 #define CONFIG_SYS_LOAD_ADDR 0x400000		/* default load address */
 #define CONFIG_SYS_HZ 1000			/* decrementer freq: 1 ms ticks */
 #define CONFIG_DISPLAY_BOARDINFO 1
 #define CONFIG_SYS_HUSH_PARSER 1
 #define CONFIG_SYS_PROMPT_HUSH_PS2 "> "
 #define CONFIG_CRC32_VERIFY  1
 #define CONFIG_BOOTP_MASK	(CONFIG_BOOTP_DEFAULT | \
 				 CONFIG_BOOTP_DNS | \
 				 CONFIG_BOOTP_DNS2 | \
 				 CONFIG_BOOTP_SEND_HOSTNAME )
 /*
  * Various low-level settings
  */
 #define CONFIG_SYS_HID0_INIT		HID0_ICE | HID0_ICFI
 #define CONFIG_SYS_HID0_FINAL		HID0_ICE
 /* no burst access on the LPB */
 #define CONFIG_SYS_CS_BURST		0x00000000
 /* one deadcycle for the 33MHz statemachine */
 #define CONFIG_SYS_CS_DEADCYCLE		0x33333331
 #define CONFIG_SYS_BOOTCS_CFG		0x0002d900
 #define CONFIG_SYS_BOOTCS_START		CONFIG_SYS_FLASH_BASE
 #define CONFIG_SYS_BOOTCS_SIZE		CONFIG_SYS_FLASH_SIZE
 #define CONFIG_SYS_RESET_ADDRESS	0xff000000
 /*
  * USB settings
  */
 #define CONFIG_USB_CLOCK		0x0001bbbb
 /* USB is on PSC3 */
 #define CONFIG_PSC3_USB
 #define CONFIG_USB_CONFIG		0x00000100
 #define CONFIG_USB_OHCI
 #define CONFIG_USB_STORAGE
 /*
  * IDE/ATA stuff Supports IDE harddisk
  */
 #undef  CONFIG_IDE_8xx_PCCARD	/* Use IDE with PC Card Adapter */
 #undef	CONFIG_IDE_8xx_DIRECT	/* Direct IDE not supported */
 #undef	CONFIG_IDE_LED		/* LED for ide not supported */
 #define	CONFIG_IDE_RESET 1	/* reset for ide supported */
 #define CONFIG_IDE_PREINIT
 #define CONFIG_SYS_IDE_MAXBUS 1	/* max. 1 IDE bus */
 #define CONFIG_SYS_IDE_MAXDEVICE 2	/* max. 2 drives per IDE bus */
 #define CONFIG_SYS_ATA_IDE0_OFFSET	0x0000
 #define CONFIG_SYS_ATA_BASE_ADDR	MPC5XXX_ATA
 /* Offset for data I/O			*/
 #define CONFIG_SYS_ATA_DATA_OFFSET	(0x0060)
 /* Offset for normal register accesses	*/
 #define CONFIG_SYS_ATA_REG_OFFSET	(CONFIG_SYS_ATA_DATA_OFFSET)
 /* Offset for alternate registers	*/
 #define CONFIG_SYS_ATA_ALT_OFFSET	(0x005C)
 /* Interval between registers */
 #define CONFIG_SYS_ATA_STRIDE		4
 #define CONFIG_ATAPI			1
 /* we enable IDE and FAT support, so we also need partition support */
 #define CONFIG_DOS_PARTITION 1
 /*
  * Open Firmware flat tree
  */
 #define CONFIG_OF_LIBFDT		1
 #define CONFIG_OF_BOARD_SETUP		1
 #define OF_CPU				"PowerPC,5200@0"
 #define OF_TBCLK			CONFIG_SYS_MPC5XXX_CLKIN
 #define OF_SOC				"soc5200@f0000000"
 #define OF_STDOUT_PATH			"/soc5200@f0000000/serial@2600"
 #endif /* __CONFIG_H */