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

/arch Architecture specific files

141

/arch Architecture specific files

142

/arm Files generic to ARM architecture

142

/arm Files generic to ARM architecture

143

/cpu CPU specific files

143

/cpu CPU specific files

144

/arm720t Files specific to ARM 720 CPUs

144

/arm720t Files specific to ARM 720 CPUs

145

/arm920t Files specific to ARM 920 CPUs

145

/arm920t Files specific to ARM 920 CPUs

146

/at91rm9200 Files specific to Atmel AT91RM9200 CPU

146

/at91rm9200 Files specific to Atmel AT91RM9200 CPU

147

/imx Files specific to Freescale MC9328 i.MX CPUs

147

/imx Files specific to Freescale MC9328 i.MX CPUs

148

/s3c24x0 Files specific to Samsung S3C24X0 CPUs

148

/s3c24x0 Files specific to Samsung S3C24X0 CPUs

149

/arm925t Files specific to ARM 925 CPUs

149

/arm925t Files specific to ARM 925 CPUs

150

/arm926ejs Files specific to ARM 926 CPUs

150

/arm926ejs Files specific to ARM 926 CPUs

151

/arm1136 Files specific to ARM 1136 CPUs

151

/arm1136 Files specific to ARM 1136 CPUs

152

/ixp Files specific to Intel XScale IXP CPUs

152

/ixp Files specific to Intel XScale IXP CPUs

153

/pxa Files specific to Intel XScale PXA CPUs

153

/pxa Files specific to Intel XScale PXA CPUs

154

/s3c44b0 Files specific to Samsung S3C44B0 CPUs

154

/s3c44b0 Files specific to Samsung S3C44B0 CPUs

155

/sa1100 Files specific to Intel StrongARM SA1100 CPUs

155

/sa1100 Files specific to Intel StrongARM SA1100 CPUs

156

/lib Architecture specific library files

156

/lib Architecture specific library files

157

/avr32 Files generic to AVR32 architecture

157

/avr32 Files generic to AVR32 architecture

158

/cpu CPU specific files

158

/cpu CPU specific files

159

/lib Architecture specific library files

159

/lib Architecture specific library files

160

/blackfin Files generic to Analog Devices Blackfin architecture

160

/blackfin Files generic to Analog Devices Blackfin architecture

161

/cpu CPU specific files

161

/cpu CPU specific files

162

/lib Architecture specific library files

162

/lib Architecture specific library files

163

/i386 Files generic to i386 architecture

163

/i386 Files generic to i386 architecture

164

/cpu CPU specific files

164

/cpu CPU specific files

165

/lib Architecture specific library files

165

/lib Architecture specific library files

166

/m68k Files generic to m68k architecture

166

/m68k Files generic to m68k architecture

167

/cpu CPU specific files

167

/cpu CPU specific files

168

/mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs

168

/mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs

169

/mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs

169

/mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs

170

/mcf532x Files specific to Freescale ColdFire MCF5329 CPUs

170

/mcf532x Files specific to Freescale ColdFire MCF5329 CPUs

171

/mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs

171

/mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs

172

/mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs

172

/mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs

173

/lib Architecture specific library files

173

/lib Architecture specific library files

174

/microblaze Files generic to microblaze architecture

174

/microblaze Files generic to microblaze architecture

175

/cpu CPU specific files

175

/cpu CPU specific files

176

/lib Architecture specific library files

176

/lib Architecture specific library files

177

/mips Files generic to MIPS architecture

177

/mips Files generic to MIPS architecture

178

/cpu CPU specific files

178

/cpu CPU specific files

179

/lib Architecture specific library files

179

/lib Architecture specific library files

180

/nios Files generic to Altera NIOS architecture

180

/nios Files generic to Altera NIOS architecture

181

/cpu CPU specific files

181

/cpu CPU specific files

182

/lib Architecture specific library files

182

/lib Architecture specific library files

183

/nios2 Files generic to Altera NIOS2 architecture

183

/nios2 Files generic to Altera NIOS2 architecture

184

/cpu CPU specific files

184

/cpu CPU specific files

185

/lib Architecture specific library files

185

/lib Architecture specific library files

186

/powerpc Files generic to PowerPC architecture

186

/powerpc Files generic to PowerPC architecture

187

/cpu CPU specific files

187

/cpu CPU specific files

188

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

188

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

189

/mpc5xx Files specific to Freescale MPC5xx CPUs

189

/mpc5xx Files specific to Freescale MPC5xx CPUs

190

/mpc5xxx Files specific to Freescale MPC5xxx CPUs

190

/mpc5xxx Files specific to Freescale MPC5xxx CPUs

191

/mpc8xx Files specific to Freescale MPC8xx CPUs

191

/mpc8xx Files specific to Freescale MPC8xx CPUs

192

/mpc8220 Files specific to Freescale MPC8220 CPUs

192

/mpc8220 Files specific to Freescale MPC8220 CPUs

193

/mpc824x Files specific to Freescale MPC824x CPUs

193

/mpc824x Files specific to Freescale MPC824x CPUs

194

/mpc8260 Files specific to Freescale MPC8260 CPUs

194

/mpc8260 Files specific to Freescale MPC8260 CPUs

195

/mpc85xx Files specific to Freescale MPC85xx CPUs

195

/mpc85xx Files specific to Freescale MPC85xx CPUs

196

/ppc4xx Files specific to AMCC PowerPC 4xx CPUs

196

/ppc4xx Files specific to AMCC PowerPC 4xx CPUs

197

/lib Architecture specific library files

197

/lib Architecture specific library files

198

/sh Files generic to SH architecture

198

/sh Files generic to SH architecture

199

/cpu CPU specific files

199

/cpu CPU specific files

200

/sh2 Files specific to sh2 CPUs

200

/sh2 Files specific to sh2 CPUs

201

/sh3 Files specific to sh3 CPUs

201

/sh3 Files specific to sh3 CPUs

202

/sh4 Files specific to sh4 CPUs

202

/sh4 Files specific to sh4 CPUs

203

/lib Architecture specific library files

203

/lib Architecture specific library files

204

/sparc Files generic to SPARC architecture

204

/sparc Files generic to SPARC architecture

205

/cpu CPU specific files

205

/cpu CPU specific files

206

/leon2 Files specific to Gaisler LEON2 SPARC CPU

206

/leon2 Files specific to Gaisler LEON2 SPARC CPU

207

/leon3 Files specific to Gaisler LEON3 SPARC CPU

207

/leon3 Files specific to Gaisler LEON3 SPARC CPU

208

/lib Architecture specific library files

208

/lib Architecture specific library files

209

/api Machine/arch independent API for external apps

209

/api Machine/arch independent API for external apps

210

/board Board dependent files

210

/board Board dependent files

211

/common Misc architecture independent functions

211

/common Misc architecture independent functions

212

/disk Code for disk drive partition handling

212

/disk Code for disk drive partition handling

213

/doc Documentation (don't expect too much)

213

/doc Documentation (don't expect too much)

214

/drivers Commonly used device drivers

214

/drivers Commonly used device drivers

215

/examples Example code for standalone applications, etc.

215

/examples Example code for standalone applications, etc.

216

/fs Filesystem code (cramfs, ext2, jffs2, etc.)

216

/fs Filesystem code (cramfs, ext2, jffs2, etc.)

217

/include Header Files

217

/include Header Files

218

/lib Files generic to all architectures

218

/lib Files generic to all architectures

219

/libfdt Library files to support flattened device trees

219

/libfdt Library files to support flattened device trees

220

/lzma Library files to support LZMA decompression

220

/lzma Library files to support LZMA decompression

221

/lzo Library files to support LZO decompression

221

/lzo Library files to support LZO decompression

222

/net Networking code

222

/net Networking code

223

/post Power On Self Test

223

/post Power On Self Test

224

/rtc Real Time Clock drivers

224

/rtc Real Time Clock drivers

225

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

225

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

226

227

Software Configuration:

227

Software Configuration:

228

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

228

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

229

230

Configuration is usually done using C preprocessor defines; the

230

Configuration is usually done using C preprocessor defines; the

231

rationale behind that is to avoid dead code whenever possible.

231

rationale behind that is to avoid dead code whenever possible.

232

233

There are two classes of configuration variables:

233

There are two classes of configuration variables:

234

235

* Configuration _OPTIONS_:

235

* Configuration _OPTIONS_:

236

These are selectable by the user and have names beginning with

236

These are selectable by the user and have names beginning with

237

"CONFIG_".

237

"CONFIG_".

238

239

* Configuration _SETTINGS_:

239

* Configuration _SETTINGS_:

240

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

240

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

241

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

241

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

242

"CONFIG_SYS_".

242

"CONFIG_SYS_".

243

244

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

244

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

245

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

245

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

246

do the configuration by hand, which means creating some symbolic

246

do the configuration by hand, which means creating some symbolic

247

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

247

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

248

as an example here.

248

as an example here.

249

250

251

Selection of Processor Architecture and Board Type:

251

Selection of Processor Architecture and Board Type:

252

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

252

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

253

254

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

254

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

255

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

255

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

256

257

Example: For a TQM823L module type:

257

Example: For a TQM823L module type:

258

259

cd u-boot

259

cd u-boot

260

make TQM823L_config

260

make TQM823L_config

261

262

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

262

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

263

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

263

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

264

directory according to the instructions in cogent/README.

264

directory according to the instructions in cogent/README.

265

266

267

Configuration Options:

267

Configuration Options:

268

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

268

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

269

270

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

270

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

271

such information is kept in a configuration file

271

such information is kept in a configuration file

272

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

272

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

273

274

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

274

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

275

"include/configs/TQM823L.h".

275

"include/configs/TQM823L.h".

276

277

278

Many of the options are named exactly as the corresponding Linux

278

Many of the options are named exactly as the corresponding Linux

279

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

279

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

280

build a config tool - later.

280

build a config tool - later.

281

282

283

The following options need to be configured:

283

The following options need to be configured:

284

285

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

285

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

286

287

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

287

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

288

289

- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)

289

- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)

290

Define exactly one, e.g. CONFIG_ATSTK1002

290

Define exactly one, e.g. CONFIG_ATSTK1002

291

292

- CPU Module Type: (if CONFIG_COGENT is defined)

292

- CPU Module Type: (if CONFIG_COGENT is defined)

293

Define exactly one of

293

Define exactly one of

294

CONFIG_CMA286_60_OLD

294

CONFIG_CMA286_60_OLD

295

--- FIXME --- not tested yet:

295

--- FIXME --- not tested yet:

296

CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,

296

CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,

297

CONFIG_CMA287_23, CONFIG_CMA287_50

297

CONFIG_CMA287_23, CONFIG_CMA287_50

298

299

- Motherboard Type: (if CONFIG_COGENT is defined)

299

- Motherboard Type: (if CONFIG_COGENT is defined)

300

Define exactly one of

300

Define exactly one of

301

CONFIG_CMA101, CONFIG_CMA102

301

CONFIG_CMA101, CONFIG_CMA102

302

303

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

303

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

304

Define one or more of

304

Define one or more of

305

CONFIG_CMA302

305

CONFIG_CMA302

306

307

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

307

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

308

Define one or more of

308

Define one or more of

309

CONFIG_LCD_HEARTBEAT - update a character position on

309

CONFIG_LCD_HEARTBEAT - update a character position on

310

the LCD display every second with

310

the LCD display every second with

311

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

311

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

312

313

- Board flavour: (if CONFIG_MPC8260ADS is defined)

313

- Board flavour: (if CONFIG_MPC8260ADS is defined)

314

CONFIG_ADSTYPE

314

CONFIG_ADSTYPE

315

Possible values are:

315

Possible values are:

316

CONFIG_SYS_8260ADS - original MPC8260ADS

316

CONFIG_SYS_8260ADS - original MPC8260ADS

317

CONFIG_SYS_8266ADS - MPC8266ADS

317

CONFIG_SYS_8266ADS - MPC8266ADS

318

CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR

318

CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR

319

CONFIG_SYS_8272ADS - MPC8272ADS

319

CONFIG_SYS_8272ADS - MPC8272ADS

320

321

- MPC824X Family Member (if CONFIG_MPC824X is defined)

321

- MPC824X Family Member (if CONFIG_MPC824X is defined)

322

Define exactly one of

322

Define exactly one of

323

CONFIG_MPC8240, CONFIG_MPC8245

323

CONFIG_MPC8240, CONFIG_MPC8245

324

325

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

325

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

326

CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if

326

CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if

327

get_gclk_freq() cannot work

327

get_gclk_freq() cannot work

328

e.g. if there is no 32KHz

328

e.g. if there is no 32KHz

329

reference PIT/RTC clock

329

reference PIT/RTC clock

330

CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK

330

CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK

331

or XTAL/EXTAL)

331

or XTAL/EXTAL)

332

333

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

333

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

334

CONFIG_SYS_8xx_CPUCLK_MIN

334

CONFIG_SYS_8xx_CPUCLK_MIN

335

CONFIG_SYS_8xx_CPUCLK_MAX

335

CONFIG_SYS_8xx_CPUCLK_MAX

336

CONFIG_8xx_CPUCLK_DEFAULT

336

CONFIG_8xx_CPUCLK_DEFAULT

337

See doc/README.MPC866

337

See doc/README.MPC866

338

339

CONFIG_SYS_MEASURE_CPUCLK

339

CONFIG_SYS_MEASURE_CPUCLK

340

341

Define this to measure the actual CPU clock instead

341

Define this to measure the actual CPU clock instead

342

of relying on the correctness of the configured

342

of relying on the correctness of the configured

343

values. Mostly useful for board bringup to make sure

343

values. Mostly useful for board bringup to make sure

344

the PLL is locked at the intended frequency. Note

344

the PLL is locked at the intended frequency. Note

345

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

345

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

346

RTC clock or CONFIG_SYS_8XX_XIN)

346

RTC clock or CONFIG_SYS_8XX_XIN)

347

348

CONFIG_SYS_DELAYED_ICACHE

348

CONFIG_SYS_DELAYED_ICACHE

349

350

Define this option if you want to enable the

350

Define this option if you want to enable the

351

ICache only when Code runs from RAM.

351

ICache only when Code runs from RAM.

352

353

- Intel Monahans options:

353

- Intel Monahans options:

354

CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO

354

CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO

355

356

Defines the Monahans run mode to oscillator

356

Defines the Monahans run mode to oscillator

357

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

357

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

358

frequency is this value multiplied by 13 MHz.

358

frequency is this value multiplied by 13 MHz.

359

360

CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO

360

CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO

361

362

Defines the Monahans turbo mode to oscillator

362

Defines the Monahans turbo mode to oscillator

363

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

363

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

364

2. The core frequency as calculated above is multiplied

364

2. The core frequency as calculated above is multiplied

365

by this value.

365

by this value.

366

367

- Linux Kernel Interface:

367

- Linux Kernel Interface:

368

CONFIG_CLOCKS_IN_MHZ

368

CONFIG_CLOCKS_IN_MHZ

369

370

U-Boot stores all clock information in Hz

370

U-Boot stores all clock information in Hz

371

internally. For binary compatibility with older Linux

371

internally. For binary compatibility with older Linux

372

kernels (which expect the clocks passed in the

372

kernels (which expect the clocks passed in the

373

bd_info data to be in MHz) the environment variable

373

bd_info data to be in MHz) the environment variable

374

"clocks_in_mhz" can be defined so that U-Boot

374

"clocks_in_mhz" can be defined so that U-Boot

375

converts clock data to MHZ before passing it to the

375

converts clock data to MHZ before passing it to the

376

Linux kernel.

376

Linux kernel.

377

When CONFIG_CLOCKS_IN_MHZ is defined, a definition of

377

When CONFIG_CLOCKS_IN_MHZ is defined, a definition of

378

"clocks_in_mhz=1" is automatically included in the

378

"clocks_in_mhz=1" is automatically included in the

379

default environment.

379

default environment.

380

381

CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]

381

CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]

382

383

When transferring memsize parameter to linux, some versions

383

When transferring memsize parameter to linux, some versions

384

expect it to be in bytes, others in MB.

384

expect it to be in bytes, others in MB.

385

Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.

385

Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.

386

387

CONFIG_OF_LIBFDT

387

CONFIG_OF_LIBFDT

388

389

New kernel versions are expecting firmware settings to be

389

New kernel versions are expecting firmware settings to be

390

passed using flattened device trees (based on open firmware

390

passed using flattened device trees (based on open firmware

391

concepts).

391

concepts).

392

393

CONFIG_OF_LIBFDT

393

CONFIG_OF_LIBFDT

394

* New libfdt-based support

394

* New libfdt-based support

395

* Adds the "fdt" command

395

* Adds the "fdt" command

396

* The bootm command automatically updates the fdt

396

* The bootm command automatically updates the fdt

397

398

OF_CPU - The proper name of the cpus node (only required for

398

OF_CPU - The proper name of the cpus node (only required for

399

MPC512X and MPC5xxx based boards).

399

MPC512X and MPC5xxx based boards).

400

OF_SOC - The proper name of the soc node (only required for

400

OF_SOC - The proper name of the soc node (only required for

401

MPC512X and MPC5xxx based boards).

401

MPC512X and MPC5xxx based boards).

402

OF_TBCLK - The timebase frequency.

402

OF_TBCLK - The timebase frequency.

403

OF_STDOUT_PATH - The path to the console device

403

OF_STDOUT_PATH - The path to the console device

404

405

boards with QUICC Engines require OF_QE to set UCC MAC

405

boards with QUICC Engines require OF_QE to set UCC MAC

406

addresses

406

addresses

407

408

CONFIG_OF_BOARD_SETUP

408

CONFIG_OF_BOARD_SETUP

409

410

Board code has addition modification that it wants to make

410

Board code has addition modification that it wants to make

411

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

411

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

412

413

CONFIG_OF_BOOT_CPU

413

CONFIG_OF_BOOT_CPU

414

415

This define fills in the correct boot CPU in the boot

415

This define fills in the correct boot CPU in the boot

416

param header, the default value is zero if undefined.

416

param header, the default value is zero if undefined.

417

418

CONFIG_OF_IDE_FIXUP

418

CONFIG_OF_IDE_FIXUP

419

420

U-Boot can detect if an IDE device is present or not.

420

U-Boot can detect if an IDE device is present or not.

421

If not, and this new config option is activated, U-Boot

421

If not, and this new config option is activated, U-Boot

422

removes the ATA node from the DTS before booting Linux,

422

removes the ATA node from the DTS before booting Linux,

423

so the Linux IDE driver does not probe the device and

423

so the Linux IDE driver does not probe the device and

424

crash. This is needed for buggy hardware (uc101) where

424

crash. This is needed for buggy hardware (uc101) where

425

no pull down resistor is connected to the signal IDE5V_DD7.

425

no pull down resistor is connected to the signal IDE5V_DD7.

426

427

- vxWorks boot parameters:

427

- vxWorks boot parameters:

428

429

bootvx constructs a valid bootline using the following

429

bootvx constructs a valid bootline using the following

430

environments variables: bootfile, ipaddr, serverip, hostname.

430

environments variables: bootfile, ipaddr, serverip, hostname.

431

It loads the vxWorks image pointed bootfile.

431

It loads the vxWorks image pointed bootfile.

432

433

CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name

433

CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name

434

CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address

434

CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address

435

CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server

435

CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server

436

CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters

436

CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters

437

438

CONFIG_SYS_VXWORKS_ADD_PARAMS

438

CONFIG_SYS_VXWORKS_ADD_PARAMS

439

440

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

440

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

441

442

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

442

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

443

the defaults discussed just above.

443

the defaults discussed just above.

444

445

- Serial Ports:

445

- Serial Ports:

446

CONFIG_PL010_SERIAL

446

CONFIG_PL010_SERIAL

447

448

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

448

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

449

450

CONFIG_PL011_SERIAL

450

CONFIG_PL011_SERIAL

451

452

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

452

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

453

454

CONFIG_PL011_CLOCK

454

CONFIG_PL011_CLOCK

455

456

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

456

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

457

the clock speed of the UARTs.

457

the clock speed of the UARTs.

458

459

CONFIG_PL01x_PORTS

459

CONFIG_PL01x_PORTS

460

461

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

461

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

462

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

462

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

463

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

463

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

464

465

466

- Console Interface:

466

- Console Interface:

467

Depending on board, define exactly one serial port

467

Depending on board, define exactly one serial port

468

(like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,

468

(like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,

469

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

469

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

470

console by defining CONFIG_8xx_CONS_NONE

470

console by defining CONFIG_8xx_CONS_NONE

471

472

Note: if CONFIG_8xx_CONS_NONE is defined, the serial

472

Note: if CONFIG_8xx_CONS_NONE is defined, the serial

473

port routines must be defined elsewhere

473

port routines must be defined elsewhere

474

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

474

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

475

476

CONFIG_CFB_CONSOLE

476

CONFIG_CFB_CONSOLE

477

Enables console device for a color framebuffer. Needs following

477

Enables console device for a color framebuffer. Needs following

478

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

478

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

479

VIDEO_FB_LITTLE_ENDIAN graphic memory organisation

479

VIDEO_FB_LITTLE_ENDIAN graphic memory organisation

480

(default big endian)

480

(default big endian)

481

VIDEO_HW_RECTFILL graphic chip supports

481

VIDEO_HW_RECTFILL graphic chip supports

482

rectangle fill

482

rectangle fill

483

(cf. smiLynxEM)

483

(cf. smiLynxEM)

484

VIDEO_HW_BITBLT graphic chip supports

484

VIDEO_HW_BITBLT graphic chip supports

485

bit-blit (cf. smiLynxEM)

485

bit-blit (cf. smiLynxEM)

486

VIDEO_VISIBLE_COLS visible pixel columns

486

VIDEO_VISIBLE_COLS visible pixel columns

487

(cols=pitch)

487

(cols=pitch)

488

VIDEO_VISIBLE_ROWS visible pixel rows

488

VIDEO_VISIBLE_ROWS visible pixel rows

489

VIDEO_PIXEL_SIZE bytes per pixel

489

VIDEO_PIXEL_SIZE bytes per pixel

490

VIDEO_DATA_FORMAT graphic data format

490

VIDEO_DATA_FORMAT graphic data format

491

(0-5, cf. cfb_console.c)

491

(0-5, cf. cfb_console.c)

492

VIDEO_FB_ADRS framebuffer address

492

VIDEO_FB_ADRS framebuffer address

493

VIDEO_KBD_INIT_FCT keyboard int fct

493

VIDEO_KBD_INIT_FCT keyboard int fct

494

(i.e. i8042_kbd_init())

494

(i.e. i8042_kbd_init())

495

VIDEO_TSTC_FCT test char fct

495

VIDEO_TSTC_FCT test char fct

496

(i.e. i8042_tstc)

496

(i.e. i8042_tstc)

497

VIDEO_GETC_FCT get char fct

497

VIDEO_GETC_FCT get char fct

498

(i.e. i8042_getc)

498

(i.e. i8042_getc)

499

CONFIG_CONSOLE_CURSOR cursor drawing on/off

499

CONFIG_CONSOLE_CURSOR cursor drawing on/off

500

(requires blink timer

500

(requires blink timer

501

cf. i8042.c)

501

cf. i8042.c)

502

CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)

502

CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)

503

CONFIG_CONSOLE_TIME display time/date info in

503

CONFIG_CONSOLE_TIME display time/date info in

504

upper right corner

504

upper right corner

505

(requires CONFIG_CMD_DATE)

505

(requires CONFIG_CMD_DATE)

506

CONFIG_VIDEO_LOGO display Linux logo in

506

CONFIG_VIDEO_LOGO display Linux logo in

507

upper left corner

507

upper left corner

508

CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of

508

CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of

509

linux_logo.h for logo.

509

linux_logo.h for logo.

510

Requires CONFIG_VIDEO_LOGO

510

Requires CONFIG_VIDEO_LOGO

511

CONFIG_CONSOLE_EXTRA_INFO

511

CONFIG_CONSOLE_EXTRA_INFO

512

additional board info beside

512

additional board info beside

513

the logo

513

the logo

514

515

When CONFIG_CFB_CONSOLE is defined, video console is

515

When CONFIG_CFB_CONSOLE is defined, video console is

516

default i/o. Serial console can be forced with

516

default i/o. Serial console can be forced with

517

environment 'console=serial'.

517

environment 'console=serial'.

518

519

When CONFIG_SILENT_CONSOLE is defined, all console

519

When CONFIG_SILENT_CONSOLE is defined, all console

520

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

520

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

521

the "silent" environment variable. See

521

the "silent" environment variable. See

522

doc/README.silent for more information.

522

doc/README.silent for more information.

523

524

- Console Baudrate:

524

- Console Baudrate:

525

CONFIG_BAUDRATE - in bps

525

CONFIG_BAUDRATE - in bps

526

Select one of the baudrates listed in

526

Select one of the baudrates listed in

527

CONFIG_SYS_BAUDRATE_TABLE, see below.

527

CONFIG_SYS_BAUDRATE_TABLE, see below.

528

CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale

528

CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale

529

530

- Console Rx buffer length

530

- Console Rx buffer length

531

With CONFIG_SYS_SMC_RXBUFLEN it is possible to define

531

With CONFIG_SYS_SMC_RXBUFLEN it is possible to define

532

the maximum receive buffer length for the SMC.

532

the maximum receive buffer length for the SMC.

533

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

533

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

534

If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE

534

If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE

535

must be defined, to setup the maximum idle timeout for

535

must be defined, to setup the maximum idle timeout for

536

the SMC.

536

the SMC.

537

538

- Interrupt driven serial port input:

538

- Interrupt driven serial port input:

539

CONFIG_SERIAL_SOFTWARE_FIFO

539

CONFIG_SERIAL_SOFTWARE_FIFO

540

541

PPC405GP only.

541

PPC405GP only.

542

Use an interrupt handler for receiving data on the

542

Use an interrupt handler for receiving data on the

543

serial port. It also enables using hardware handshake

543

serial port. It also enables using hardware handshake

544

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

544

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

545

bytes the interrupt driven input buffer should have.

545

bytes the interrupt driven input buffer should have.

546

547

Leave undefined to disable this feature, including

547

Leave undefined to disable this feature, including

548

disable the buffer and hardware handshake.

548

disable the buffer and hardware handshake.

549

550

- Console UART Number:

550

- Console UART Number:

551

CONFIG_UART1_CONSOLE

551

CONFIG_UART1_CONSOLE

552

553

AMCC PPC4xx only.

553

AMCC PPC4xx only.

554

If defined internal UART1 (and not UART0) is used

554

If defined internal UART1 (and not UART0) is used

555

as default U-Boot console.

555

as default U-Boot console.

556

557

- Boot Delay: CONFIG_BOOTDELAY - in seconds

557

- Boot Delay: CONFIG_BOOTDELAY - in seconds

558

Delay before automatically booting the default image;

558

Delay before automatically booting the default image;

559

set to -1 to disable autoboot.

559

set to -1 to disable autoboot.

560

561

See doc/README.autoboot for these options that

561

See doc/README.autoboot for these options that

562

work with CONFIG_BOOTDELAY. None are required.

562

work with CONFIG_BOOTDELAY. None are required.

563

CONFIG_BOOT_RETRY_TIME

563

CONFIG_BOOT_RETRY_TIME

564

CONFIG_BOOT_RETRY_MIN

564

CONFIG_BOOT_RETRY_MIN

565

CONFIG_AUTOBOOT_KEYED

565

CONFIG_AUTOBOOT_KEYED

566

CONFIG_AUTOBOOT_PROMPT

566

CONFIG_AUTOBOOT_PROMPT

567

CONFIG_AUTOBOOT_DELAY_STR

567

CONFIG_AUTOBOOT_DELAY_STR

568

CONFIG_AUTOBOOT_STOP_STR

568

CONFIG_AUTOBOOT_STOP_STR

569

CONFIG_AUTOBOOT_DELAY_STR2

569

CONFIG_AUTOBOOT_DELAY_STR2

570

CONFIG_AUTOBOOT_STOP_STR2

570

CONFIG_AUTOBOOT_STOP_STR2

571

CONFIG_ZERO_BOOTDELAY_CHECK

571

CONFIG_ZERO_BOOTDELAY_CHECK

572

CONFIG_RESET_TO_RETRY

572

CONFIG_RESET_TO_RETRY

573

574

- Autoboot Command:

574

- Autoboot Command:

575

CONFIG_BOOTCOMMAND

575

CONFIG_BOOTCOMMAND

576

Only needed when CONFIG_BOOTDELAY is enabled;

576

Only needed when CONFIG_BOOTDELAY is enabled;

577

define a command string that is automatically executed

577

define a command string that is automatically executed

578

when no character is read on the console interface

578

when no character is read on the console interface

579

within "Boot Delay" after reset.

579

within "Boot Delay" after reset.

580

581

CONFIG_BOOTARGS

581

CONFIG_BOOTARGS

582

This can be used to pass arguments to the bootm

582

This can be used to pass arguments to the bootm

583

command. The value of CONFIG_BOOTARGS goes into the

583

command. The value of CONFIG_BOOTARGS goes into the

584

environment value "bootargs".

584

environment value "bootargs".

585

586

CONFIG_RAMBOOT and CONFIG_NFSBOOT

586

CONFIG_RAMBOOT and CONFIG_NFSBOOT

587

The value of these goes into the environment as

587

The value of these goes into the environment as

588

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

588

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

589

as a convenience, when switching between booting from

589

as a convenience, when switching between booting from

590

RAM and NFS.

590

RAM and NFS.

591

592

- Pre-Boot Commands:

592

- Pre-Boot Commands:

593

CONFIG_PREBOOT

593

CONFIG_PREBOOT

594

595

When this option is #defined, the existence of the

595

When this option is #defined, the existence of the

596

environment variable "preboot" will be checked

596

environment variable "preboot" will be checked

597

immediately before starting the CONFIG_BOOTDELAY

597

immediately before starting the CONFIG_BOOTDELAY

598

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

598

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

599

entering interactive mode.

599

entering interactive mode.

600

601

This feature is especially useful when "preboot" is

601

This feature is especially useful when "preboot" is

602

automatically generated or modified. For an example

602

automatically generated or modified. For an example

603

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

603

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

604

modified when the user holds down a certain

604

modified when the user holds down a certain

605

combination of keys on the (special) keyboard when

605

combination of keys on the (special) keyboard when

606

booting the systems

606

booting the systems

607

608

- Serial Download Echo Mode:

608

- Serial Download Echo Mode:

609

CONFIG_LOADS_ECHO

609

CONFIG_LOADS_ECHO

610

If defined to 1, all characters received during a

610

If defined to 1, all characters received during a

611

serial download (using the "loads" command) are

611

serial download (using the "loads" command) are

612

echoed back. This might be needed by some terminal

612

echoed back. This might be needed by some terminal

613

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

613

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

614

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

614

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

615

value of the "loads_echo" environment variable.

615

value of the "loads_echo" environment variable.

616

617

- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)

617

- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)

618

CONFIG_KGDB_BAUDRATE

618

CONFIG_KGDB_BAUDRATE

619

Select one of the baudrates listed in

619

Select one of the baudrates listed in

620

CONFIG_SYS_BAUDRATE_TABLE, see below.

620

CONFIG_SYS_BAUDRATE_TABLE, see below.

621

622

- Monitor Functions:

622

- Monitor Functions:

623

Monitor commands can be included or excluded

623

Monitor commands can be included or excluded

624

from the build by using the #include files

624

from the build by using the #include files

625

"config_cmd_all.h" and #undef'ing unwanted

625

"config_cmd_all.h" and #undef'ing unwanted

626

commands, or using "config_cmd_default.h"

626

commands, or using "config_cmd_default.h"

627

and augmenting with additional #define's

627

and augmenting with additional #define's

628

for wanted commands.

628

for wanted commands.

629

630

The default command configuration includes all commands

630

The default command configuration includes all commands

631

except those marked below with a "*".

631

except those marked below with a "*".

632

633

CONFIG_CMD_ASKENV * ask for env variable

633

CONFIG_CMD_ASKENV * ask for env variable

634

CONFIG_CMD_BDI bdinfo

634

CONFIG_CMD_BDI bdinfo

635

CONFIG_CMD_BEDBUG * Include BedBug Debugger

635

CONFIG_CMD_BEDBUG * Include BedBug Debugger

636

CONFIG_CMD_BMP * BMP support

636

CONFIG_CMD_BMP * BMP support

637

CONFIG_CMD_BSP * Board specific commands

637

CONFIG_CMD_BSP * Board specific commands

638

CONFIG_CMD_BOOTD bootd

638

CONFIG_CMD_BOOTD bootd

639

CONFIG_CMD_CACHE * icache, dcache

639

CONFIG_CMD_CACHE * icache, dcache

640

CONFIG_CMD_CONSOLE coninfo

640

CONFIG_CMD_CONSOLE coninfo

641

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

641

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

642

CONFIG_CMD_DHCP * DHCP support

642

CONFIG_CMD_DHCP * DHCP support

643

CONFIG_CMD_DIAG * Diagnostics

643

CONFIG_CMD_DIAG * Diagnostics

644

CONFIG_CMD_DS4510 * ds4510 I2C gpio commands

644

CONFIG_CMD_DS4510 * ds4510 I2C gpio commands

645

CONFIG_CMD_DS4510_INFO * ds4510 I2C info command

645

CONFIG_CMD_DS4510_INFO * ds4510 I2C info command

646

CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd

646

CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd

647

CONFIG_CMD_DS4510_RST * ds4510 I2C rst command

647

CONFIG_CMD_DS4510_RST * ds4510 I2C rst command

648

CONFIG_CMD_DTT * Digital Therm and Thermostat

648

CONFIG_CMD_DTT * Digital Therm and Thermostat

649

CONFIG_CMD_ECHO echo arguments

649

CONFIG_CMD_ECHO echo arguments

650

CONFIG_CMD_EDITENV edit env variable

650

CONFIG_CMD_EDITENV edit env variable

651

CONFIG_CMD_EEPROM * EEPROM read/write support

651

CONFIG_CMD_EEPROM * EEPROM read/write support

652

CONFIG_CMD_ELF * bootelf, bootvx

652

CONFIG_CMD_ELF * bootelf, bootvx

653

CONFIG_CMD_SAVEENV saveenv

653

CONFIG_CMD_SAVEENV saveenv

654

CONFIG_CMD_FDC * Floppy Disk Support

654

CONFIG_CMD_FDC * Floppy Disk Support

655

CONFIG_CMD_FAT * FAT partition support

655

CONFIG_CMD_FAT * FAT partition support

656

CONFIG_CMD_FDOS * Dos diskette Support

656

CONFIG_CMD_FDOS * Dos diskette Support

657

CONFIG_CMD_FLASH flinfo, erase, protect

657

CONFIG_CMD_FLASH flinfo, erase, protect

658

CONFIG_CMD_FPGA FPGA device initialization support

658

CONFIG_CMD_FPGA FPGA device initialization support

659

CONFIG_CMD_HWFLOW * RTS/CTS hw flow control

659

CONFIG_CMD_HWFLOW * RTS/CTS hw flow control

660

CONFIG_CMD_I2C * I2C serial bus support

660

CONFIG_CMD_I2C * I2C serial bus support

661

CONFIG_CMD_IDE * IDE harddisk support

661

CONFIG_CMD_IDE * IDE harddisk support

662

CONFIG_CMD_IMI iminfo

662

CONFIG_CMD_IMI iminfo

663

CONFIG_CMD_IMLS List all found images

663

CONFIG_CMD_IMLS List all found images

664

CONFIG_CMD_IMMAP * IMMR dump support

664

CONFIG_CMD_IMMAP * IMMR dump support

665

CONFIG_CMD_IRQ * irqinfo

665

CONFIG_CMD_IRQ * irqinfo

666

CONFIG_CMD_ITEST Integer/string test of 2 values

666

CONFIG_CMD_ITEST Integer/string test of 2 values

667

CONFIG_CMD_JFFS2 * JFFS2 Support

667

CONFIG_CMD_JFFS2 * JFFS2 Support

668

CONFIG_CMD_KGDB * kgdb

668

CONFIG_CMD_KGDB * kgdb

669

CONFIG_CMD_LOADB loadb

669

CONFIG_CMD_LOADB loadb

670

CONFIG_CMD_LOADS loads

670

CONFIG_CMD_LOADS loads

671

CONFIG_CMD_MD5SUM print md5 message digest

671

CONFIG_CMD_MD5SUM print md5 message digest

672

(requires CONFIG_CMD_MEMORY and CONFIG_MD5)

672

(requires CONFIG_CMD_MEMORY and CONFIG_MD5)

673

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

673

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

674

loop, loopw, mtest

674

loop, loopw, mtest

675

CONFIG_CMD_MISC Misc functions like sleep etc

675

CONFIG_CMD_MISC Misc functions like sleep etc

676

CONFIG_CMD_MMC * MMC memory mapped support

676

CONFIG_CMD_MMC * MMC memory mapped support

677

CONFIG_CMD_MII * MII utility commands

677

CONFIG_CMD_MII * MII utility commands

678

CONFIG_CMD_MTDPARTS * MTD partition support

678

CONFIG_CMD_MTDPARTS * MTD partition support

679

CONFIG_CMD_NAND * NAND support

679

CONFIG_CMD_NAND * NAND support

680

CONFIG_CMD_NET bootp, tftpboot, rarpboot

680

CONFIG_CMD_NET bootp, tftpboot, rarpboot

681

CONFIG_CMD_PCA953X * PCA953x I2C gpio commands

681

CONFIG_CMD_PCA953X * PCA953x I2C gpio commands

682

CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command

682

CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command

683

CONFIG_CMD_PCI * pciinfo

683

CONFIG_CMD_PCI * pciinfo

684

CONFIG_CMD_PCMCIA * PCMCIA support

684

CONFIG_CMD_PCMCIA * PCMCIA support

685

CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network

685

CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network

686

host

686

host

687

CONFIG_CMD_PORTIO * Port I/O

687

CONFIG_CMD_PORTIO * Port I/O

688

CONFIG_CMD_REGINFO * Register dump

688

CONFIG_CMD_REGINFO * Register dump

689

CONFIG_CMD_RUN run command in env variable

689

CONFIG_CMD_RUN run command in env variable

690

CONFIG_CMD_SAVES * save S record dump

690

CONFIG_CMD_SAVES * save S record dump

691

CONFIG_CMD_SCSI * SCSI Support

691

CONFIG_CMD_SCSI * SCSI Support

692

CONFIG_CMD_SDRAM * print SDRAM configuration information

692

CONFIG_CMD_SDRAM * print SDRAM configuration information

693

(requires CONFIG_CMD_I2C)

693

(requires CONFIG_CMD_I2C)

694

CONFIG_CMD_SETGETDCR Support for DCR Register access

694

CONFIG_CMD_SETGETDCR Support for DCR Register access

695

(4xx only)

695

(4xx only)

696

CONFIG_CMD_SHA1 print sha1 memory digest

696

CONFIG_CMD_SHA1 print sha1 memory digest

697

(requires CONFIG_CMD_MEMORY)

697

(requires CONFIG_CMD_MEMORY)

698

CONFIG_CMD_SOURCE "source" command Support

698

CONFIG_CMD_SOURCE "source" command Support

699

CONFIG_CMD_SPI * SPI serial bus support

699

CONFIG_CMD_SPI * SPI serial bus support

700

CONFIG_CMD_USB * USB support

700

CONFIG_CMD_USB * USB support

701

CONFIG_CMD_VFD * VFD support (TRAB)

701

CONFIG_CMD_VFD * VFD support (TRAB)

702

CONFIG_CMD_CDP * Cisco Discover Protocol support

702

CONFIG_CMD_CDP * Cisco Discover Protocol support

703

CONFIG_CMD_FSL * Microblaze FSL support

703

CONFIG_CMD_FSL * Microblaze FSL support

704

705

706

EXAMPLE: If you want all functions except of network

706

EXAMPLE: If you want all functions except of network

707

support you can write:

707

support you can write:

708

709

#include "config_cmd_all.h"

709

#include "config_cmd_all.h"

710

#undef CONFIG_CMD_NET

710

#undef CONFIG_CMD_NET

711

712

Other Commands:

712

Other Commands:

713

fdt (flattened device tree) command: CONFIG_OF_LIBFDT

713

fdt (flattened device tree) command: CONFIG_OF_LIBFDT

714

715

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

715

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

716

(configuration option CONFIG_CMD_CACHE) unless you know

716

(configuration option CONFIG_CMD_CACHE) unless you know

717

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

717

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

718

cache cannot be enabled on systems like the 8xx or

718

cache cannot be enabled on systems like the 8xx or

719

8260 (where accesses to the IMMR region must be

719

8260 (where accesses to the IMMR region must be

720

uncached), and it cannot be disabled on all other

720

uncached), and it cannot be disabled on all other

721

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

721

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

722

initial stack and some data.

722

initial stack and some data.

723

724

725

XXX - this list needs to get updated!

725

XXX - this list needs to get updated!

726

727

- Watchdog:

727

- Watchdog:

728

CONFIG_WATCHDOG

728

CONFIG_WATCHDOG

729

If this variable is defined, it enables watchdog

729

If this variable is defined, it enables watchdog

730

support. There must be support in the platform specific

730

support. There must be support in the platform specific

731

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

731

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

732

SIU Watchdog feature is enabled in the SYPCR

732

SIU Watchdog feature is enabled in the SYPCR

733

register.

733

register.

734

735

- U-Boot Version:

735

- U-Boot Version:

736

CONFIG_VERSION_VARIABLE

736

CONFIG_VERSION_VARIABLE

737

If this variable is defined, an environment variable

737

If this variable is defined, an environment variable

738

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

738

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

739

version as printed by the "version" command.

739

version as printed by the "version" command.

740

This variable is readonly.

740

This variable is readonly.

741

742

- Real-Time Clock:

742

- Real-Time Clock:

743

744

When CONFIG_CMD_DATE is selected, the type of the RTC

744

When CONFIG_CMD_DATE is selected, the type of the RTC

745

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

745

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

746

following options:

746

following options:

747

748

CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx

748

CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx

749

CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC

749

CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC

750

CONFIG_RTC_MC13783 - use MC13783 RTC

750

CONFIG_RTC_MC13783 - use MC13783 RTC

751

CONFIG_RTC_MC146818 - use MC146818 RTC

751

CONFIG_RTC_MC146818 - use MC146818 RTC

752

CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC

752

CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC

753

CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC

753

CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC

754

CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC

754

CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC

755

CONFIG_RTC_DS164x - use Dallas DS164x RTC

755

CONFIG_RTC_DS164x - use Dallas DS164x RTC

756

CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC

756

CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC

757

CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC

757

CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC

758

CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337

758

CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337

759

760

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

760

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

761

must also be configured. See I2C Support, below.

761

must also be configured. See I2C Support, below.

762

763

- GPIO Support:

763

- GPIO Support:

764

CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO

764

CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO

765

CONFIG_PCA953X_INFO - enable pca953x info command

765

CONFIG_PCA953X_INFO - enable pca953x info command

766

767

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

767

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

768

must also be configured. See I2C Support, below.

768

must also be configured. See I2C Support, below.

769

770

- Timestamp Support:

770

- Timestamp Support:

771

772

When CONFIG_TIMESTAMP is selected, the timestamp

772

When CONFIG_TIMESTAMP is selected, the timestamp

773

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

773

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

774

commands like bootm or iminfo. This option is

774

commands like bootm or iminfo. This option is

775

automatically enabled when you select CONFIG_CMD_DATE .

775

automatically enabled when you select CONFIG_CMD_DATE .

776

777

- Partition Support:

777

- Partition Support:

778

CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION

778

CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION

779

and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_PARTITION

779

and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_PARTITION

780

781

If IDE or SCSI support is enabled (CONFIG_CMD_IDE or

781

If IDE or SCSI support is enabled (CONFIG_CMD_IDE or

782

CONFIG_CMD_SCSI) you must configure support for at

782

CONFIG_CMD_SCSI) you must configure support for at

783

least one partition type as well.

783

least one partition type as well.

784

785

- IDE Reset method:

785

- IDE Reset method:

786

CONFIG_IDE_RESET_ROUTINE - this is defined in several

786

CONFIG_IDE_RESET_ROUTINE - this is defined in several

787

board configurations files but used nowhere!

787

board configurations files but used nowhere!

788

789

CONFIG_IDE_RESET - is this is defined, IDE Reset will

789

CONFIG_IDE_RESET - is this is defined, IDE Reset will

790

be performed by calling the function

790

be performed by calling the function

791

ide_set_reset(int reset)

791

ide_set_reset(int reset)

792

which has to be defined in a board specific file

792

which has to be defined in a board specific file

793

794

- ATAPI Support:

794

- ATAPI Support:

795

CONFIG_ATAPI

795

CONFIG_ATAPI

796

797

Set this to enable ATAPI support.

797

Set this to enable ATAPI support.

798

799

- LBA48 Support

799

- LBA48 Support

800

CONFIG_LBA48

800

CONFIG_LBA48

801

802

Set this to enable support for disks larger than 137GB

802

Set this to enable support for disks larger than 137GB

803

Also look at CONFIG_SYS_64BIT_LBA.

803

Also look at CONFIG_SYS_64BIT_LBA.

804

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

804

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

805

support disks up to 2.1TB.

805

support disks up to 2.1TB.

806

807

CONFIG_SYS_64BIT_LBA:

807

CONFIG_SYS_64BIT_LBA:

808

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

808

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

809

Default is 32bit.

809

Default is 32bit.

810

811

- SCSI Support:

811

- SCSI Support:

812

At the moment only there is only support for the

812

At the moment only there is only support for the

813

SYM53C8XX SCSI controller; define

813

SYM53C8XX SCSI controller; define

814

CONFIG_SCSI_SYM53C8XX to enable it.

814

CONFIG_SCSI_SYM53C8XX to enable it.

815

816

CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and

816

CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and

817

CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *

817

CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *

818

CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the

818

CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the

819

maximum numbers of LUNs, SCSI ID's and target

819

maximum numbers of LUNs, SCSI ID's and target

820

devices.

820

devices.

821

CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)

821

CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)

822

823

- NETWORK Support (PCI):

823

- NETWORK Support (PCI):

824

CONFIG_E1000

824

CONFIG_E1000

825

Support for Intel 8254x gigabit chips.

825

Support for Intel 8254x gigabit chips.

826

827

CONFIG_E1000_FALLBACK_MAC

827

CONFIG_E1000_FALLBACK_MAC

828

default MAC for empty EEPROM after production.

828

default MAC for empty EEPROM after production.

829

830

CONFIG_EEPRO100

830

CONFIG_EEPRO100

831

Support for Intel 82557/82559/82559ER chips.

831

Support for Intel 82557/82559/82559ER chips.

832

Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM

832

Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM

833

write routine for first time initialisation.

833

write routine for first time initialisation.

834

835

CONFIG_TULIP

835

CONFIG_TULIP

836

Support for Digital 2114x chips.

836

Support for Digital 2114x chips.

837

Optional CONFIG_TULIP_SELECT_MEDIA for board specific

837

Optional CONFIG_TULIP_SELECT_MEDIA for board specific

838

modem chip initialisation (KS8761/QS6611).

838

modem chip initialisation (KS8761/QS6611).

839

840

CONFIG_NATSEMI

840

CONFIG_NATSEMI

841

Support for National dp83815 chips.

841

Support for National dp83815 chips.

842

843

CONFIG_NS8382X

843

CONFIG_NS8382X

844

Support for National dp8382[01] gigabit chips.

844

Support for National dp8382[01] gigabit chips.

845

846

- NETWORK Support (other):

846

- NETWORK Support (other):

847

848

CONFIG_DRIVER_AT91EMAC

848

CONFIG_DRIVER_AT91EMAC

849

Support for AT91RM9200 EMAC.

849

Support for AT91RM9200 EMAC.

850

851

CONFIG_RMII

851

CONFIG_RMII

852

Define this to use reduced MII inteface

852

Define this to use reduced MII inteface

853

854

CONFIG_DRIVER_AT91EMAC_QUIET

854

CONFIG_DRIVER_AT91EMAC_QUIET

855

If this defined, the driver is quiet.

855

If this defined, the driver is quiet.

856

The driver doen't show link status messages.

856

The driver doen't show link status messages.

857

858

CONFIG_DRIVER_LAN91C96

858

CONFIG_DRIVER_LAN91C96

859

Support for SMSC's LAN91C96 chips.

859

Support for SMSC's LAN91C96 chips.

860

861

CONFIG_LAN91C96_BASE

861

CONFIG_LAN91C96_BASE

862

Define this to hold the physical address

862

Define this to hold the physical address

863

of the LAN91C96's I/O space

863

of the LAN91C96's I/O space

864

865

CONFIG_LAN91C96_USE_32_BIT

865

CONFIG_LAN91C96_USE_32_BIT

866

Define this to enable 32 bit addressing

866

Define this to enable 32 bit addressing

867

868

CONFIG_DRIVER_SMC91111

868

CONFIG_DRIVER_SMC91111

869

Support for SMSC's LAN91C111 chip

869

Support for SMSC's LAN91C111 chip

870

871

CONFIG_SMC91111_BASE

871

CONFIG_SMC91111_BASE

872

Define this to hold the physical address

872

Define this to hold the physical address

873

of the device (I/O space)

873

of the device (I/O space)

874

875

CONFIG_SMC_USE_32_BIT

875

CONFIG_SMC_USE_32_BIT

876

Define this if data bus is 32 bits

876

Define this if data bus is 32 bits

877

878

CONFIG_SMC_USE_IOFUNCS

878

CONFIG_SMC_USE_IOFUNCS

879

Define this to use i/o functions instead of macros

879

Define this to use i/o functions instead of macros

880

(some hardware wont work with macros)

880

(some hardware wont work with macros)

881

882

CONFIG_SMC911X

882

CONFIG_SMC911X

883

Support for SMSC's LAN911x and LAN921x chips

883

Support for SMSC's LAN911x and LAN921x chips

884

885

CONFIG_SMC911X_BASE

885

CONFIG_SMC911X_BASE

886

Define this to hold the physical address

886

Define this to hold the physical address

887

of the device (I/O space)

887

of the device (I/O space)

888

889

CONFIG_SMC911X_32_BIT

889

CONFIG_SMC911X_32_BIT

890

Define this if data bus is 32 bits

890

Define this if data bus is 32 bits

891

892

CONFIG_SMC911X_16_BIT

892

CONFIG_SMC911X_16_BIT

893

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

893

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

894

automatically converts one 32 bit word to two 16 bit

894

automatically converts one 32 bit word to two 16 bit

895

words you may also try CONFIG_SMC911X_32_BIT.

895

words you may also try CONFIG_SMC911X_32_BIT.

896

897

- USB Support:

897

- USB Support:

898

At the moment only the UHCI host controller is

898

At the moment only the UHCI host controller is

899

supported (PIP405, MIP405, MPC5200); define

899

supported (PIP405, MIP405, MPC5200); define

900

CONFIG_USB_UHCI to enable it.

900

CONFIG_USB_UHCI to enable it.

901

define CONFIG_USB_KEYBOARD to enable the USB Keyboard

901

define CONFIG_USB_KEYBOARD to enable the USB Keyboard

902

and define CONFIG_USB_STORAGE to enable the USB

902

and define CONFIG_USB_STORAGE to enable the USB

903

storage devices.

903

storage devices.

904

Note:

904

Note:

905

Supported are USB Keyboards and USB Floppy drives

905

Supported are USB Keyboards and USB Floppy drives

906

(TEAC FD-05PUB).

906

(TEAC FD-05PUB).

907

MPC5200 USB requires additional defines:

907

MPC5200 USB requires additional defines:

908

CONFIG_USB_CLOCK

908

CONFIG_USB_CLOCK

909

for 528 MHz Clock: 0x0001bbbb

909

for 528 MHz Clock: 0x0001bbbb

910

CONFIG_PSC3_USB

910

CONFIG_PSC3_USB

911

for USB on PSC3

911

for USB on PSC3

912

CONFIG_USB_CONFIG

912

CONFIG_USB_CONFIG

913

for differential drivers: 0x00001000

913

for differential drivers: 0x00001000

914

for single ended drivers: 0x00005000

914

for single ended drivers: 0x00005000

915

for differential drivers on PSC3: 0x00000100

915

for differential drivers on PSC3: 0x00000100

916

for single ended drivers on PSC3: 0x00004100

916

for single ended drivers on PSC3: 0x00004100

917

CONFIG_SYS_USB_EVENT_POLL

917

CONFIG_SYS_USB_EVENT_POLL

918

May be defined to allow interrupt polling

918

May be defined to allow interrupt polling

919

instead of using asynchronous interrupts

919

instead of using asynchronous interrupts

920

921

- USB Device:

921

- USB Device:

922

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

922

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

923

Once firmware is rebuilt from a serial console issue the

923

Once firmware is rebuilt from a serial console issue the

924

command "setenv stdin usbtty; setenv stdout usbtty" and

924

command "setenv stdin usbtty; setenv stdout usbtty" and

925

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

925

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

926

it has found a new device. The environment variable usbtty

926

it has found a new device. The environment variable usbtty

927

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

927

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

928

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

928

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

929

Common Device Class Abstract Control Model serial device.

929

Common Device Class Abstract Control Model serial device.

930

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

930

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

931

a Linux host by

931

a Linux host by

932

# modprobe usbserial vendor=0xVendorID product=0xProductID

932

# modprobe usbserial vendor=0xVendorID product=0xProductID

933

else if using cdc_acm, simply setting the environment

933

else if using cdc_acm, simply setting the environment

934

variable usbtty to be cdc_acm should suffice. The following

934

variable usbtty to be cdc_acm should suffice. The following

935

might be defined in YourBoardName.h

935

might be defined in YourBoardName.h

936

937

CONFIG_USB_DEVICE

937

CONFIG_USB_DEVICE

938

Define this to build a UDC device

938

Define this to build a UDC device

939

940

CONFIG_USB_TTY

940

CONFIG_USB_TTY

941

Define this to have a tty type of device available to

941

Define this to have a tty type of device available to

942

talk to the UDC device

942

talk to the UDC device

943

944

CONFIG_SYS_CONSOLE_IS_IN_ENV

944

CONFIG_SYS_CONSOLE_IS_IN_ENV

945

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

945

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

946

be set to usbtty.

946

be set to usbtty.

947

948

mpc8xx:

948

mpc8xx:

949

CONFIG_SYS_USB_EXTC_CLK 0xBLAH

949

CONFIG_SYS_USB_EXTC_CLK 0xBLAH

950

Derive USB clock from external clock "blah"

950

Derive USB clock from external clock "blah"

951

- CONFIG_SYS_USB_EXTC_CLK 0x02

951

- CONFIG_SYS_USB_EXTC_CLK 0x02

952

953

CONFIG_SYS_USB_BRG_CLK 0xBLAH

953

CONFIG_SYS_USB_BRG_CLK 0xBLAH

954

Derive USB clock from brgclk

954

Derive USB clock from brgclk

955

- CONFIG_SYS_USB_BRG_CLK 0x04

955

- CONFIG_SYS_USB_BRG_CLK 0x04

956

957

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

957

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

958

define your own vendor specific values either in BoardName.h

958

define your own vendor specific values either in BoardName.h

959

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

959

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

960

CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,

960

CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,

961

CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot

961

CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot

962

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

962

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

963

964

CONFIG_USBD_MANUFACTURER

964

CONFIG_USBD_MANUFACTURER

965

Define this string as the name of your company for

965

Define this string as the name of your company for

966

- CONFIG_USBD_MANUFACTURER "my company"

966

- CONFIG_USBD_MANUFACTURER "my company"

967

968

CONFIG_USBD_PRODUCT_NAME

968

CONFIG_USBD_PRODUCT_NAME

969

Define this string as the name of your product

969

Define this string as the name of your product

970

- CONFIG_USBD_PRODUCT_NAME "acme usb device"

970

- CONFIG_USBD_PRODUCT_NAME "acme usb device"

971

972

CONFIG_USBD_VENDORID

972

CONFIG_USBD_VENDORID

973

Define this as your assigned Vendor ID from the USB

973

Define this as your assigned Vendor ID from the USB

974

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

974

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

975

to avoid polluting the USB namespace.

975

to avoid polluting the USB namespace.

976

- CONFIG_USBD_VENDORID 0xFFFF

976

- CONFIG_USBD_VENDORID 0xFFFF

977

978

CONFIG_USBD_PRODUCTID

978

CONFIG_USBD_PRODUCTID

979

Define this as the unique Product ID

979

Define this as the unique Product ID

980

for your device

980

for your device

981

- CONFIG_USBD_PRODUCTID 0xFFFF

981

- CONFIG_USBD_PRODUCTID 0xFFFF

982

983

984

- MMC Support:

984

- MMC Support:

985

The MMC controller on the Intel PXA is supported. To

985

The MMC controller on the Intel PXA is supported. To

986

enable this define CONFIG_MMC. The MMC can be

986

enable this define CONFIG_MMC. The MMC can be

987

accessed from the boot prompt by mapping the device

987

accessed from the boot prompt by mapping the device

988

to physical memory similar to flash. Command line is

988

to physical memory similar to flash. Command line is

989

enabled with CONFIG_CMD_MMC. The MMC driver also works with

989

enabled with CONFIG_CMD_MMC. The MMC driver also works with

990

the FAT fs. This is enabled with CONFIG_CMD_FAT.

990

the FAT fs. This is enabled with CONFIG_CMD_FAT.

991

992

- Journaling Flash filesystem support:

992

- Journaling Flash filesystem support:

993

CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,

993

CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,

994

CONFIG_JFFS2_NAND_DEV

994

CONFIG_JFFS2_NAND_DEV

995

Define these for a default partition on a NAND device

995

Define these for a default partition on a NAND device

996

997

CONFIG_SYS_JFFS2_FIRST_SECTOR,

997

CONFIG_SYS_JFFS2_FIRST_SECTOR,

998

CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS

998

CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS

999

Define these for a default partition on a NOR device

999

Define these for a default partition on a NOR device

1000

1001

CONFIG_SYS_JFFS_CUSTOM_PART

1001

CONFIG_SYS_JFFS_CUSTOM_PART

1002

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

1002

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

1003

function struct part_info* jffs2_part_info(int part_num)

1003

function struct part_info* jffs2_part_info(int part_num)

1004

1005

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

1005

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

1006

#define CONFIG_SYS_JFFS_SINGLE_PART 1

1006

#define CONFIG_SYS_JFFS_SINGLE_PART 1

1007

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

1007

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

1008

have not defined a custom partition

1008

have not defined a custom partition

1009

1010

- Keyboard Support:

1010

- Keyboard Support:

1011

CONFIG_ISA_KEYBOARD

1011

CONFIG_ISA_KEYBOARD

1012

1013

Define this to enable standard (PC-Style) keyboard

1013

Define this to enable standard (PC-Style) keyboard

1014

support

1014

support

1015

1016

CONFIG_I8042_KBD

1016

CONFIG_I8042_KBD

1017

Standard PC keyboard driver with US (is default) and

1017

Standard PC keyboard driver with US (is default) and

1018

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

1018

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

1019

Export function i8042_kbd_init, i8042_tstc and i8042_getc

1019

Export function i8042_kbd_init, i8042_tstc and i8042_getc

1020

for cfb_console. Supports cursor blinking.

1020

for cfb_console. Supports cursor blinking.

1021

1022

- Video support:

1022

- Video support:

1023

CONFIG_VIDEO

1023

CONFIG_VIDEO

1024

1025

Define this to enable video support (for output to

1025

Define this to enable video support (for output to

1026

video).

1026

video).

1027

1028

CONFIG_VIDEO_CT69000

1028

CONFIG_VIDEO_CT69000

1029

1030

Enable Chips & Technologies 69000 Video chip

1030

Enable Chips & Technologies 69000 Video chip

1031

1032

CONFIG_VIDEO_SMI_LYNXEM

1032

CONFIG_VIDEO_SMI_LYNXEM

1033

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

1033

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

1034

video output is selected via environment 'videoout'

1034

video output is selected via environment 'videoout'

1035

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

1035

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

1036

assumed.

1036

assumed.

1037

1038

For the CT69000 and SMI_LYNXEM drivers, videomode is

1038

For the CT69000 and SMI_LYNXEM drivers, videomode is

1039

selected via environment 'videomode'. Two different ways

1039

selected via environment 'videomode'. Two different ways

1040

are possible:

1040

are possible:

1041

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

1041

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

1042

Following standard modes are supported (* is default):

1042

Following standard modes are supported (* is default):

1043

1044

Colors 640x480 800x600 1024x768 1152x864 1280x1024

1044

Colors 640x480 800x600 1024x768 1152x864 1280x1024

1045

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

1045

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

1046

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

1046

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

1047

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

1047

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

1048

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

1048

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

1049

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

1049

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

1050

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

1050

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

1051

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

1051

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

1052

1053

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

1053

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

1054

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

1054

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

1055

1056

1057

CONFIG_VIDEO_SED13806

1057

CONFIG_VIDEO_SED13806

1058

Enable Epson SED13806 driver. This driver supports 8bpp

1058

Enable Epson SED13806 driver. This driver supports 8bpp

1059

and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP

1059

and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP

1060

or CONFIG_VIDEO_SED13806_16BPP

1060

or CONFIG_VIDEO_SED13806_16BPP

1061

1062

- Keyboard Support:

1062

- Keyboard Support:

1063

CONFIG_KEYBOARD

1063

CONFIG_KEYBOARD

1064

1065

Define this to enable a custom keyboard support.

1065

Define this to enable a custom keyboard support.

1066

This simply calls drv_keyboard_init() which must be

1066

This simply calls drv_keyboard_init() which must be

1067

defined in your board-specific files.

1067

defined in your board-specific files.

1068

The only board using this so far is RBC823.

1068

The only board using this so far is RBC823.

1069

1070

- LCD Support: CONFIG_LCD

1070

- LCD Support: CONFIG_LCD

1071

1072

Define this to enable LCD support (for output to LCD

1072

Define this to enable LCD support (for output to LCD

1073

display); also select one of the supported displays

1073

display); also select one of the supported displays

1074

by defining one of these:

1074

by defining one of these:

1075

1076

CONFIG_ATMEL_LCD:

1076

CONFIG_ATMEL_LCD:

1077

1078

HITACHI TX09D70VM1CCA, 3.5", 240x320.

1078

HITACHI TX09D70VM1CCA, 3.5", 240x320.

1079

1080

CONFIG_NEC_NL6448AC33:

1080

CONFIG_NEC_NL6448AC33:

1081

1082

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

1082

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

1083

1084

CONFIG_NEC_NL6448BC20

1084

CONFIG_NEC_NL6448BC20

1085

1086

NEC NL6448BC20-08. 6.5", 640x480.

1086

NEC NL6448BC20-08. 6.5", 640x480.

1087

Active, color, single scan.

1087

Active, color, single scan.

1088

1089

CONFIG_NEC_NL6448BC33_54

1089

CONFIG_NEC_NL6448BC33_54

1090

1091

NEC NL6448BC33-54. 10.4", 640x480.

1091

NEC NL6448BC33-54. 10.4", 640x480.

1092

Active, color, single scan.

1092

Active, color, single scan.

1093

1094

CONFIG_SHARP_16x9

1094

CONFIG_SHARP_16x9

1095

1096

Sharp 320x240. Active, color, single scan.

1096

Sharp 320x240. Active, color, single scan.

1097

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

1097

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

1098

1099

CONFIG_SHARP_LQ64D341

1099

CONFIG_SHARP_LQ64D341

1100

1101

Sharp LQ64D341 display, 640x480.

1101

Sharp LQ64D341 display, 640x480.

1102

Active, color, single scan.

1102

Active, color, single scan.

1103

1104

CONFIG_HLD1045

1104

CONFIG_HLD1045

1105

1106

HLD1045 display, 640x480.

1106

HLD1045 display, 640x480.

1107

Active, color, single scan.

1107

Active, color, single scan.

1108

1109

CONFIG_OPTREX_BW

1109

CONFIG_OPTREX_BW

1110

1111

Optrex CBL50840-2 NF-FW 99 22 M5

1111

Optrex CBL50840-2 NF-FW 99 22 M5

1112

or

1112

or

1113

Hitachi LMG6912RPFC-00T

1113

Hitachi LMG6912RPFC-00T

1114

or

1114

or

1115

Hitachi SP14Q002

1115

Hitachi SP14Q002

1116

1117

320x240. Black & white.

1117

320x240. Black & white.

1118

1119

Normally display is black on white background; define

1119

Normally display is black on white background; define

1120

CONFIG_SYS_WHITE_ON_BLACK to get it inverted.

1120

CONFIG_SYS_WHITE_ON_BLACK to get it inverted.

1121

1122

- Splash Screen Support: CONFIG_SPLASH_SCREEN

1122

- Splash Screen Support: CONFIG_SPLASH_SCREEN

1123

1124

If this option is set, the environment is checked for

1124

If this option is set, the environment is checked for

1125

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

1125

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

1126

of logo, copyright and system information on the LCD

1126

of logo, copyright and system information on the LCD

1127

is suppressed and the BMP image at the address

1127

is suppressed and the BMP image at the address

1128

specified in "splashimage" is loaded instead. The

1128

specified in "splashimage" is loaded instead. The

1129

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

1129

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

1130

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

1130

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

1131

loaded very quickly after power-on.

1131

loaded very quickly after power-on.

1132

1133

CONFIG_SPLASH_SCREEN_ALIGN

1133

CONFIG_SPLASH_SCREEN_ALIGN

1134

1135

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

1135

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

1136

on the screen. Environment variable "splashpos" specifies the

1136

on the screen. Environment variable "splashpos" specifies the

1137

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

1137

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

1138

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

1138

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

1139

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

1139

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

1140

specify 'm' for centering the image.

1140

specify 'm' for centering the image.

1141

1142

Example:

1142

Example:

1143

setenv splashpos m,m

1143

setenv splashpos m,m

1144

=> image at center of screen

1144

=> image at center of screen

1145

1146

setenv splashpos 30,20

1146

setenv splashpos 30,20

1147

=> image at x = 30 and y = 20

1147

=> image at x = 30 and y = 20

1148

1149

setenv splashpos -10,m

1149

setenv splashpos -10,m

1150

=> vertically centered image

1150

=> vertically centered image

1151

at x = dspWidth - bmpWidth - 9

1151

at x = dspWidth - bmpWidth - 9

1152

1153

- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP

1153

- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP

1154

1155

If this option is set, additionally to standard BMP

1155

If this option is set, additionally to standard BMP

1156

images, gzipped BMP images can be displayed via the

1156

images, gzipped BMP images can be displayed via the

1157

splashscreen support or the bmp command.

1157

splashscreen support or the bmp command.

1158

1159

- Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8

1159

- Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8

1160

1161

If this option is set, 8-bit RLE compressed BMP images

1161

If this option is set, 8-bit RLE compressed BMP images

1162

can be displayed via the splashscreen support or the

1162

can be displayed via the splashscreen support or the

1163

bmp command.

1163

bmp command.

1164

1165

- Compression support:

1165

- Compression support:

1166

CONFIG_BZIP2

1166

CONFIG_BZIP2

1167

1168

If this option is set, support for bzip2 compressed

1168

If this option is set, support for bzip2 compressed

1169

images is included. If not, only uncompressed and gzip

1169

images is included. If not, only uncompressed and gzip

1170

compressed images are supported.

1170

compressed images are supported.

1171

1172

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

1172

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

1173

the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should

1173

the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should

1174

be at least 4MB.

1174

be at least 4MB.

1175

1176

CONFIG_LZMA

1176

CONFIG_LZMA

1177

1178

If this option is set, support for lzma compressed

1178

If this option is set, support for lzma compressed

1179

images is included.

1179

images is included.

1180

1181

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

1181

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

1182

requires an amount of dynamic memory that is given by the

1182

requires an amount of dynamic memory that is given by the

1183

formula:

1183

formula:

1184

1185

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

1185

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

1186

1187

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

1187

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

1188

and Literal pos bits.

1188

and Literal pos bits.

1189

1190

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

1190

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

1191

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

1191

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

1192

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

1192

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

1193

a very small buffer.

1193

a very small buffer.

1194

1195

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

1195

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

1196

then calculate the amount of needed dynamic memory (ensuring

1196

then calculate the amount of needed dynamic memory (ensuring

1197

the appropriate CONFIG_SYS_MALLOC_LEN value).

1197

the appropriate CONFIG_SYS_MALLOC_LEN value).

1198

1199

- MII/PHY support:

1199

- MII/PHY support:

1200

CONFIG_PHY_ADDR

1200

CONFIG_PHY_ADDR

1201

1202

The address of PHY on MII bus.

1202

The address of PHY on MII bus.

1203

1204

CONFIG_PHY_CLOCK_FREQ (ppc4xx)

1204

CONFIG_PHY_CLOCK_FREQ (ppc4xx)

1205

1206

The clock frequency of the MII bus

1206

The clock frequency of the MII bus

1207

1208

CONFIG_PHY_GIGE

1208

CONFIG_PHY_GIGE

1209

1210

If this option is set, support for speed/duplex

1210

If this option is set, support for speed/duplex

1211

detection of gigabit PHY is included.

1211

detection of gigabit PHY is included.

1212

1213

CONFIG_PHY_RESET_DELAY

1213

CONFIG_PHY_RESET_DELAY

1214

1215

Some PHY like Intel LXT971A need extra delay after

1215

Some PHY like Intel LXT971A need extra delay after

1216

reset before any MII register access is possible.

1216

reset before any MII register access is possible.

1217

For such PHY, set this option to the usec delay

1217

For such PHY, set this option to the usec delay

1218

required. (minimum 300usec for LXT971A)

1218

required. (minimum 300usec for LXT971A)

1219

1220

CONFIG_PHY_CMD_DELAY (ppc4xx)

1220

CONFIG_PHY_CMD_DELAY (ppc4xx)

1221

1222

Some PHY like Intel LXT971A need extra delay after

1222

Some PHY like Intel LXT971A need extra delay after

1223

command issued before MII status register can be read

1223

command issued before MII status register can be read

1224

1225

- Ethernet address:

1225

- Ethernet address:

1226

CONFIG_ETHADDR

1226

CONFIG_ETHADDR

1227

CONFIG_ETH1ADDR

1227

CONFIG_ETH1ADDR

1228

CONFIG_ETH2ADDR

1228

CONFIG_ETH2ADDR

1229

CONFIG_ETH3ADDR

1229

CONFIG_ETH3ADDR

1230

CONFIG_ETH4ADDR

1230

CONFIG_ETH4ADDR

1231

CONFIG_ETH5ADDR

1231

CONFIG_ETH5ADDR

1232

1233

Define a default value for Ethernet address to use

1233

Define a default value for Ethernet address to use

1234

for the respective Ethernet interface, in case this

1234

for the respective Ethernet interface, in case this

1235

is not determined automatically.

1235

is not determined automatically.

1236

1237

- IP address:

1237

- IP address:

1238

CONFIG_IPADDR

1238

CONFIG_IPADDR

1239

1240

Define a default value for the IP address to use for

1240

Define a default value for the IP address to use for

1241

the default Ethernet interface, in case this is not

1241

the default Ethernet interface, in case this is not

1242

determined through e.g. bootp.

1242

determined through e.g. bootp.

1243

1244

- Server IP address:

1244

- Server IP address:

1245

CONFIG_SERVERIP

1245

CONFIG_SERVERIP

1246

1247

Defines a default value for the IP address of a TFTP

1247

Defines a default value for the IP address of a TFTP

1248

server to contact when using the "tftboot" command.

1248

server to contact when using the "tftboot" command.

1249

1250

CONFIG_KEEP_SERVERADDR

1250

CONFIG_KEEP_SERVERADDR

1251

1252

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

1252

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

1253

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

1253

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

1254

1255

- Multicast TFTP Mode:

1255

- Multicast TFTP Mode:

1256

CONFIG_MCAST_TFTP

1256

CONFIG_MCAST_TFTP

1257

1258

Defines whether you want to support multicast TFTP as per

1258

Defines whether you want to support multicast TFTP as per

1259

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

1259

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

1260

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

1260

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

1261

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

1261

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

1262

multicast group.

1262

multicast group.

1263

1264

CONFIG_BOOTP_RANDOM_DELAY

1264

CONFIG_BOOTP_RANDOM_DELAY

1265

- BOOTP Recovery Mode:

1265

- BOOTP Recovery Mode:

1266

CONFIG_BOOTP_RANDOM_DELAY

1266

CONFIG_BOOTP_RANDOM_DELAY

1267

1268

If you have many targets in a network that try to

1268

If you have many targets in a network that try to

1269

boot using BOOTP, you may want to avoid that all

1269

boot using BOOTP, you may want to avoid that all

1270

systems send out BOOTP requests at precisely the same

1270

systems send out BOOTP requests at precisely the same

1271

moment (which would happen for instance at recovery

1271

moment (which would happen for instance at recovery

1272

from a power failure, when all systems will try to

1272

from a power failure, when all systems will try to

1273

boot, thus flooding the BOOTP server. Defining

1273

boot, thus flooding the BOOTP server. Defining

1274

CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be

1274

CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be

1275

inserted before sending out BOOTP requests. The

1275

inserted before sending out BOOTP requests. The

1276

following delays are inserted then:

1276

following delays are inserted then:

1277

1278

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

1278

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

1279

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

1279

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

1280

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

1280

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

1281

4th and following

1281

4th and following

1282

BOOTP requests: delay 0 ... 8 sec

1282

BOOTP requests: delay 0 ... 8 sec

1283

1284

- DHCP Advanced Options:

1284

- DHCP Advanced Options:

1285

You can fine tune the DHCP functionality by defining

1285

You can fine tune the DHCP functionality by defining

1286

CONFIG_BOOTP_* symbols:

1286

CONFIG_BOOTP_* symbols:

1287

1288

CONFIG_BOOTP_SUBNETMASK

1288

CONFIG_BOOTP_SUBNETMASK

1289

CONFIG_BOOTP_GATEWAY

1289

CONFIG_BOOTP_GATEWAY

1290

CONFIG_BOOTP_HOSTNAME

1290

CONFIG_BOOTP_HOSTNAME

1291

CONFIG_BOOTP_NISDOMAIN

1291

CONFIG_BOOTP_NISDOMAIN

1292

CONFIG_BOOTP_BOOTPATH

1292

CONFIG_BOOTP_BOOTPATH

1293

CONFIG_BOOTP_BOOTFILESIZE

1293

CONFIG_BOOTP_BOOTFILESIZE

1294

CONFIG_BOOTP_DNS

1294

CONFIG_BOOTP_DNS

1295

CONFIG_BOOTP_DNS2

1295

CONFIG_BOOTP_DNS2

1296

CONFIG_BOOTP_SEND_HOSTNAME

1296

CONFIG_BOOTP_SEND_HOSTNAME

1297

CONFIG_BOOTP_NTPSERVER

1297

CONFIG_BOOTP_NTPSERVER

1298

CONFIG_BOOTP_TIMEOFFSET

1298

CONFIG_BOOTP_TIMEOFFSET

1299

CONFIG_BOOTP_VENDOREX

1299

CONFIG_BOOTP_VENDOREX

1300

1301

CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip

1301

CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip

1302

environment variable, not the BOOTP server.

1302

environment variable, not the BOOTP server.

1303

1304

CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS

1304

CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS

1305

serverip from a DHCP server, it is possible that more

1305

serverip from a DHCP server, it is possible that more

1306

than one DNS serverip is offered to the client.

1306

than one DNS serverip is offered to the client.

1307

If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS

1307

If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS

1308

serverip will be stored in the additional environment

1308

serverip will be stored in the additional environment

1309

variable "dnsip2". The first DNS serverip is always

1309

variable "dnsip2". The first DNS serverip is always

1310

stored in the variable "dnsip", when CONFIG_BOOTP_DNS

1310

stored in the variable "dnsip", when CONFIG_BOOTP_DNS

1311

is defined.

1311

is defined.

1312

1313

CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable

1313

CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable

1314

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

1314

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

1315

need the hostname of the DHCP requester.

1315

need the hostname of the DHCP requester.

1316

If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content

1316

If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content

1317

of the "hostname" environment variable is passed as

1317

of the "hostname" environment variable is passed as

1318

option 12 to the DHCP server.

1318

option 12 to the DHCP server.

1319

1320

CONFIG_BOOTP_DHCP_REQUEST_DELAY

1320

CONFIG_BOOTP_DHCP_REQUEST_DELAY

1321

1322

A 32bit value in microseconds for a delay between

1322

A 32bit value in microseconds for a delay between

1323

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

1323

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

1324

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

1324

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

1325

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

1325

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

1326

AT91RM9200 processor running at 180MHz, this delay needed

1326

AT91RM9200 processor running at 180MHz, this delay needed

1327

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

1327

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

1328

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

1328

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

1329

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

1329

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

1330

that one of the retries will be successful but note that

1330

that one of the retries will be successful but note that

1331

the DHCP timeout and retry process takes a longer than

1331

the DHCP timeout and retry process takes a longer than

1332

this delay.

1332

this delay.

1333

1334

- CDP Options:

1334

- CDP Options:

1335

CONFIG_CDP_DEVICE_ID

1335

CONFIG_CDP_DEVICE_ID

1336

1337

The device id used in CDP trigger frames.

1337

The device id used in CDP trigger frames.

1338

1339

CONFIG_CDP_DEVICE_ID_PREFIX

1339

CONFIG_CDP_DEVICE_ID_PREFIX

1340

1341

A two character string which is prefixed to the MAC address

1341

A two character string which is prefixed to the MAC address

1342

of the device.

1342

of the device.

1343

1344

CONFIG_CDP_PORT_ID

1344

CONFIG_CDP_PORT_ID

1345

1346

A printf format string which contains the ascii name of

1346

A printf format string which contains the ascii name of

1347

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

1347

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

1348

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

1348

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

1349

1350

CONFIG_CDP_CAPABILITIES

1350

CONFIG_CDP_CAPABILITIES

1351

1352

A 32bit integer which indicates the device capabilities;

1352

A 32bit integer which indicates the device capabilities;

1353

0x00000010 for a normal host which does not forwards.

1353

0x00000010 for a normal host which does not forwards.

1354

1355

CONFIG_CDP_VERSION

1355

CONFIG_CDP_VERSION

1356

1357

An ascii string containing the version of the software.

1357

An ascii string containing the version of the software.

1358

1359

CONFIG_CDP_PLATFORM

1359

CONFIG_CDP_PLATFORM

1360

1361

An ascii string containing the name of the platform.

1361

An ascii string containing the name of the platform.

1362

1363

CONFIG_CDP_TRIGGER

1363

CONFIG_CDP_TRIGGER

1364

1365

A 32bit integer sent on the trigger.

1365

A 32bit integer sent on the trigger.

1366

1367

CONFIG_CDP_POWER_CONSUMPTION

1367

CONFIG_CDP_POWER_CONSUMPTION

1368

1369

A 16bit integer containing the power consumption of the

1369

A 16bit integer containing the power consumption of the

1370

device in .1 of milliwatts.

1370

device in .1 of milliwatts.

1371

1372

CONFIG_CDP_APPLIANCE_VLAN_TYPE

1372

CONFIG_CDP_APPLIANCE_VLAN_TYPE

1373

1374

A byte containing the id of the VLAN.

1374

A byte containing the id of the VLAN.

1375

1376

- Status LED: CONFIG_STATUS_LED

1376

- Status LED: CONFIG_STATUS_LED

1377

1378

Several configurations allow to display the current

1378

Several configurations allow to display the current

1379

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

1379

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

1380

fast while running U-Boot code, stop blinking as

1380

fast while running U-Boot code, stop blinking as

1381

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

1381

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

1382

start blinking slow once the Linux kernel is running

1382

start blinking slow once the Linux kernel is running

1383

(supported by a status LED driver in the Linux

1383

(supported by a status LED driver in the Linux

1384

kernel). Defining CONFIG_STATUS_LED enables this

1384

kernel). Defining CONFIG_STATUS_LED enables this

1385

feature in U-Boot.

1385

feature in U-Boot.

1386

1387

- CAN Support: CONFIG_CAN_DRIVER

1387

- CAN Support: CONFIG_CAN_DRIVER

1388

1389

Defining CONFIG_CAN_DRIVER enables CAN driver support

1389

Defining CONFIG_CAN_DRIVER enables CAN driver support

1390

on those systems that support this (optional)

1390

on those systems that support this (optional)

1391

feature, like the TQM8xxL modules.

1391

feature, like the TQM8xxL modules.

1392

1393

- I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C

1393

- I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C

1394

1395

These enable I2C serial bus commands. Defining either of

1395

These enable I2C serial bus commands. Defining either of

1396

(but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will

1396

(but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will

1397

include the appropriate I2C driver for the selected CPU.

1397

include the appropriate I2C driver for the selected CPU.

1398

1399

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

1399

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

1400

command line (as long as you set CONFIG_CMD_I2C in

1400

command line (as long as you set CONFIG_CMD_I2C in

1401

CONFIG_COMMANDS) and communicate with i2c based realtime

1401

CONFIG_COMMANDS) and communicate with i2c based realtime

1402

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

1402

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

1403

command line interface.

1403

command line interface.

1404

1405

CONFIG_HARD_I2C selects a hardware I2C controller.

1405

CONFIG_HARD_I2C selects a hardware I2C controller.

1406

1407

CONFIG_SOFT_I2C configures u-boot to use a software (aka

1407

CONFIG_SOFT_I2C configures u-boot to use a software (aka

1408

bit-banging) driver instead of CPM or similar hardware

1408

bit-banging) driver instead of CPM or similar hardware

1409

support for I2C.

1409

support for I2C.

1410

1411

There are several other quantities that must also be

1411

There are several other quantities that must also be

1412

defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.

1412

defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.

1413

1414

In both cases you will need to define CONFIG_SYS_I2C_SPEED

1414

In both cases you will need to define CONFIG_SYS_I2C_SPEED

1415

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

1415

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

1416

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

1416

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

1417

the CPU's i2c node address).

1417

the CPU's i2c node address).

1418

1419

Now, the u-boot i2c code for the mpc8xx

1419

Now, the u-boot i2c code for the mpc8xx

1420

(arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node

1420

(arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node

1421

and so its address should therefore be cleared to 0 (See,

1421

and so its address should therefore be cleared to 0 (See,

1422

eg, MPC823e User's Manual p.16-473). So, set

1422

eg, MPC823e User's Manual p.16-473). So, set

1423

CONFIG_SYS_I2C_SLAVE to 0.

1423

CONFIG_SYS_I2C_SLAVE to 0.

1424

1425

CONFIG_SYS_I2C_INIT_MPC5XXX

1425

CONFIG_SYS_I2C_INIT_MPC5XXX

1426

1427

When a board is reset during an i2c bus transfer

1427

When a board is reset during an i2c bus transfer

1428

chips might think that the current transfer is still

1428

chips might think that the current transfer is still

1429

in progress. Reset the slave devices by sending start

1429

in progress. Reset the slave devices by sending start

1430

commands until the slave device responds.

1430

commands until the slave device responds.

1431

1432

That's all that's required for CONFIG_HARD_I2C.

1432

That's all that's required for CONFIG_HARD_I2C.

1433

1434

If you use the software i2c interface (CONFIG_SOFT_I2C)

1434

If you use the software i2c interface (CONFIG_SOFT_I2C)

1435

then the following macros need to be defined (examples are

1435

then the following macros need to be defined (examples are

1436

from include/configs/lwmon.h):

1436

from include/configs/lwmon.h):

1437

1438

I2C_INIT

1438

I2C_INIT

1439

1440

(Optional). Any commands necessary to enable the I2C

1440

(Optional). Any commands necessary to enable the I2C

1441

controller or configure ports.

1441

controller or configure ports.

1442

1443

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

1443

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

1444

1445

I2C_PORT

1445

I2C_PORT

1446

1447

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

1447

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

1448

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

1448

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

1449

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

1449

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

1450

1451

I2C_ACTIVE

1451

I2C_ACTIVE

1452

1453

The code necessary to make the I2C data line active

1453

The code necessary to make the I2C data line active

1454

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

1454

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

1455

define can be null.

1455

define can be null.

1456

1457

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

1457

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

1458

1459

I2C_TRISTATE

1459

I2C_TRISTATE

1460

1461

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

1461

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

1462

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

1462

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

1463

define can be null.

1463

define can be null.

1464

1465

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

1465

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

1466

1467

I2C_READ

1467

I2C_READ

1468

1469

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

1469

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

1470

FALSE if it is low.

1470

FALSE if it is low.

1471

1472

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

1472

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

1473

1474

I2C_SDA(bit)

1474

I2C_SDA(bit)

1475

1476

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

1476

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

1477

is FALSE, it clears it (low).

1477

is FALSE, it clears it (low).

1478

1479

eg: #define I2C_SDA(bit) \

1479

eg: #define I2C_SDA(bit) \

1480

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

1480

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

1481

else immr->im_cpm.cp_pbdat &= ~PB_SDA

1481

else immr->im_cpm.cp_pbdat &= ~PB_SDA

1482

1483

I2C_SCL(bit)

1483

I2C_SCL(bit)

1484

1485

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

1485

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

1486

is FALSE, it clears it (low).

1486

is FALSE, it clears it (low).

1487

1488

eg: #define I2C_SCL(bit) \

1488

eg: #define I2C_SCL(bit) \

1489

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

1489

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

1490

else immr->im_cpm.cp_pbdat &= ~PB_SCL

1490

else immr->im_cpm.cp_pbdat &= ~PB_SCL

1491

1492

I2C_DELAY

1492

I2C_DELAY

1493

1494

This delay is invoked four times per clock cycle so this

1494

This delay is invoked four times per clock cycle so this

1495

controls the rate of data transfer. The data rate thus

1495

controls the rate of data transfer. The data rate thus

1496

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

1496

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

1497

like:

1497

like:

1498

1499

#define I2C_DELAY udelay(2)

1499

#define I2C_DELAY udelay(2)

1500

1501

CONFIG_SYS_I2C_INIT_BOARD

1501

CONFIG_SYS_I2C_INIT_BOARD

1502

1503

When a board is reset during an i2c bus transfer

1503

When a board is reset during an i2c bus transfer

1504

chips might think that the current transfer is still

1504

chips might think that the current transfer is still

1505

in progress. On some boards it is possible to access

1505

in progress. On some boards it is possible to access

1506

the i2c SCLK line directly, either by using the

1506

the i2c SCLK line directly, either by using the

1507

processor pin as a GPIO or by having a second pin

1507

processor pin as a GPIO or by having a second pin

1508

connected to the bus. If this option is defined a

1508

connected to the bus. If this option is defined a

1509

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

1509

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

1510

is run early in the boot sequence.

1510

is run early in the boot sequence.

1511

1512

CONFIG_SYS_I2C_BOARD_LATE_INIT

1512

CONFIG_SYS_I2C_BOARD_LATE_INIT

1513

1514

An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is

1514

An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is

1515

defined a custom i2c_board_late_init() routine in

1515

defined a custom i2c_board_late_init() routine in

1516

boards/xxx/board.c is run AFTER the operations in i2c_init()

1516

boards/xxx/board.c is run AFTER the operations in i2c_init()

1517

is completed. This callpoint can be used to unreset i2c bus

1517

is completed. This callpoint can be used to unreset i2c bus

1518

using CPU i2c controller register accesses for CPUs whose i2c

1518

using CPU i2c controller register accesses for CPUs whose i2c

1519

controller provide such a method. It is called at the end of

1519

controller provide such a method. It is called at the end of

1520

i2c_init() to allow i2c_init operations to setup the i2c bus

1520

i2c_init() to allow i2c_init operations to setup the i2c bus

1521

controller on the CPU (e.g. setting bus speed & slave address).

1521

controller on the CPU (e.g. setting bus speed & slave address).

1522

1523

CONFIG_I2CFAST (PPC405GP|PPC405EP only)

1523

CONFIG_I2CFAST (PPC405GP|PPC405EP only)

1524

1525

This option enables configuration of bi_iic_fast[] flags

1525

This option enables configuration of bi_iic_fast[] flags

1526

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

1526

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

1527

variable "i2cfast". (see also i2cfast)

1527

variable "i2cfast". (see also i2cfast)

1528

1529

CONFIG_I2C_MULTI_BUS

1529

CONFIG_I2C_MULTI_BUS

1530

1531

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

1531

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

1532

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

1532

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

1533

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

1533

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

1534

Note that bus numbering is zero-based.

1534

Note that bus numbering is zero-based.

1535

1536

CONFIG_SYS_I2C_NOPROBES

1536

CONFIG_SYS_I2C_NOPROBES

1537

1538

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

1538

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

1539

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

1539

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

1540

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

1540

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

1541

a 1D array of device addresses

1541

a 1D array of device addresses

1542

1543

e.g.

1543

e.g.

1544

#undef CONFIG_I2C_MULTI_BUS

1544

#undef CONFIG_I2C_MULTI_BUS

1545

#define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}

1545

#define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}

1546

1547

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

1547

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

1548

1549

#define CONFIG_I2C_MULTI_BUS

1549

#define CONFIG_I2C_MULTI_BUS

1550

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

1550

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

1551

1552

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

1552

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

1553

1554

CONFIG_SYS_SPD_BUS_NUM

1554

CONFIG_SYS_SPD_BUS_NUM

1555

1556

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

1556

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

1557

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

1557

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

1558

1559

CONFIG_SYS_RTC_BUS_NUM

1559

CONFIG_SYS_RTC_BUS_NUM

1560

1561

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

1561

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

1562

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

1562

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

1563

1564

CONFIG_SYS_DTT_BUS_NUM

1564

CONFIG_SYS_DTT_BUS_NUM

1565

1566

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

1566

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

1567

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

1567

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

1568

1569

CONFIG_SYS_I2C_DTT_ADDR:

1569

CONFIG_SYS_I2C_DTT_ADDR:

1570

1571

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

1571

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

1572

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

1572

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

1573

specified DTT device.

1573

specified DTT device.

1574

1575

CONFIG_FSL_I2C

1575

CONFIG_FSL_I2C

1576

1577

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

1577

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

1578

drivers/i2c/fsl_i2c.c.

1578

drivers/i2c/fsl_i2c.c.

1579

1580

CONFIG_I2C_MUX

1580

CONFIG_I2C_MUX

1581

1582

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

1582

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

1583

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

1583

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

1584

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

1584

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

1585

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

1585

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

1586

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

1586

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

1587

the muxes to activate this new "bus".

1587

the muxes to activate this new "bus".

1588

1589

CONFIG_I2C_MULTI_BUS must be also defined, to use this

1589

CONFIG_I2C_MULTI_BUS must be also defined, to use this

1590

feature!

1590

feature!

1591

1592

Example:

1592

Example:

1593

Adding a new I2C Bus reached over 2 pca9544a muxes

1593

Adding a new I2C Bus reached over 2 pca9544a muxes

1594

The First mux with address 70 and channel 6

1594

The First mux with address 70 and channel 6

1595

The Second mux with address 71 and channel 4

1595

The Second mux with address 71 and channel 4

1596

1597

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

1597

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

1598

1599

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

1599

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

1600

of I2C Busses with muxes:

1600

of I2C Busses with muxes:

1601

1602

=> i2c bus

1602

=> i2c bus

1603

Busses reached over muxes:

1603

Busses reached over muxes:

1604

Bus ID: 2

1604

Bus ID: 2

1605

reached over Mux(es):

1605

reached over Mux(es):

1606

pca9544a@70 ch: 4

1606

pca9544a@70 ch: 4

1607

Bus ID: 3

1607

Bus ID: 3

1608

reached over Mux(es):

1608

reached over Mux(es):

1609

pca9544a@70 ch: 6

1609

pca9544a@70 ch: 6

1610

pca9544a@71 ch: 4

1610

pca9544a@71 ch: 4

1611

=>

1611

=>

1612

1613

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

1613

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

1614

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

1614

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

1615

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

1615

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

1616

the channel 4.

1616

the channel 4.

1617

1618

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

1618

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

1619

usual, to communicate with your I2C devices behind

1619

usual, to communicate with your I2C devices behind

1620

the 2 muxes.

1620

the 2 muxes.

1621

1622

This option is actually implemented for the bitbanging

1622

This option is actually implemented for the bitbanging

1623

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

1623

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

1624

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

1624

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

1625

to add this option to other architectures.

1625

to add this option to other architectures.

1626

1627

CONFIG_SOFT_I2C_READ_REPEATED_START

1627

CONFIG_SOFT_I2C_READ_REPEATED_START

1628

1629

defining this will force the i2c_read() function in

1629

defining this will force the i2c_read() function in

1630

the soft_i2c driver to perform an I2C repeated start

1630

the soft_i2c driver to perform an I2C repeated start

1631

between writing the address pointer and reading the

1631

between writing the address pointer and reading the

1632

data. If this define is omitted the default behaviour

1632

data. If this define is omitted the default behaviour

1633

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

1633

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

1634

devices can use either method, but some require one or

1634

devices can use either method, but some require one or

1635

the other.

1635

the other.

1636

1637

- SPI Support: CONFIG_SPI

1637

- SPI Support: CONFIG_SPI

1638

1639

Enables SPI driver (so far only tested with

1639

Enables SPI driver (so far only tested with

1640

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

1640

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

1641

D/As on the SACSng board)

1641

D/As on the SACSng board)

1642

1643

CONFIG_SPI_X

1643

CONFIG_SPI_X

1644

1645

Enables extended (16-bit) SPI EEPROM addressing.

1645

Enables extended (16-bit) SPI EEPROM addressing.

1646

(symmetrical to CONFIG_I2C_X)

1646

(symmetrical to CONFIG_I2C_X)

1647

1648

CONFIG_SOFT_SPI

1648

CONFIG_SOFT_SPI

1649

1650

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

1650

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

1651

using hardware support. This is a general purpose

1651

using hardware support. This is a general purpose

1652

driver that only requires three general I/O port pins

1652

driver that only requires three general I/O port pins

1653

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

1653

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

1654

defined, the board configuration must define several

1654

defined, the board configuration must define several

1655

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

1655

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

1656

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

1656

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

1657

1658

CONFIG_HARD_SPI

1658

CONFIG_HARD_SPI

1659

1660

Enables a hardware SPI driver for general-purpose reads

1660

Enables a hardware SPI driver for general-purpose reads

1661

and writes. As with CONFIG_SOFT_SPI, the board configuration

1661

and writes. As with CONFIG_SOFT_SPI, the board configuration

1662

must define a list of chip-select function pointers.

1662

must define a list of chip-select function pointers.

1663

Currently supported on some MPC8xxx processors. For an

1663

Currently supported on some MPC8xxx processors. For an

1664

example, see include/configs/mpc8349emds.h.

1664

example, see include/configs/mpc8349emds.h.

1665

1666

CONFIG_MXC_SPI

1666

CONFIG_MXC_SPI

1667

1668

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

1668

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

1669

SoCs. Currently only i.MX31 is supported.

1669

SoCs. Currently only i.MX31 is supported.

1670

1671

- FPGA Support: CONFIG_FPGA

1671

- FPGA Support: CONFIG_FPGA

1672

1673

Enables FPGA subsystem.

1673

Enables FPGA subsystem.

1674

1675

CONFIG_FPGA_<vendor>

1675

CONFIG_FPGA_<vendor>

1676

1677

Enables support for specific chip vendors.

1677

Enables support for specific chip vendors.

1678

(ALTERA, XILINX)

1678

(ALTERA, XILINX)

1679

1680

CONFIG_FPGA_<family>

1680

CONFIG_FPGA_<family>

1681

1682

Enables support for FPGA family.

1682

Enables support for FPGA family.

1683

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

1683

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

1684

1685

CONFIG_FPGA_COUNT

1685

CONFIG_FPGA_COUNT

1686

1687

Specify the number of FPGA devices to support.

1687

Specify the number of FPGA devices to support.

1688

1689

CONFIG_SYS_FPGA_PROG_FEEDBACK

1689

CONFIG_SYS_FPGA_PROG_FEEDBACK

1690

1691

Enable printing of hash marks during FPGA configuration.

1691

Enable printing of hash marks during FPGA configuration.

1692

1693

CONFIG_SYS_FPGA_CHECK_BUSY

1693

CONFIG_SYS_FPGA_CHECK_BUSY

1694

1695

Enable checks on FPGA configuration interface busy

1695

Enable checks on FPGA configuration interface busy

1696

status by the configuration function. This option

1696

status by the configuration function. This option

1697

will require a board or device specific function to

1697

will require a board or device specific function to

1698

be written.

1698

be written.

1699

1700

CONFIG_FPGA_DELAY

1700

CONFIG_FPGA_DELAY

1701

1702

If defined, a function that provides delays in the FPGA

1702

If defined, a function that provides delays in the FPGA

1703

configuration driver.

1703

configuration driver.

1704

1705

CONFIG_SYS_FPGA_CHECK_CTRLC

1705

CONFIG_SYS_FPGA_CHECK_CTRLC

1706

Allow Control-C to interrupt FPGA configuration

1706

Allow Control-C to interrupt FPGA configuration

1707

1708

CONFIG_SYS_FPGA_CHECK_ERROR

1708

CONFIG_SYS_FPGA_CHECK_ERROR

1709

1710

Check for configuration errors during FPGA bitfile

1710

Check for configuration errors during FPGA bitfile

1711

loading. For example, abort during Virtex II

1711

loading. For example, abort during Virtex II

1712

configuration if the INIT_B line goes low (which

1712

configuration if the INIT_B line goes low (which

1713

indicated a CRC error).

1713

indicated a CRC error).

1714

1715

CONFIG_SYS_FPGA_WAIT_INIT

1715

CONFIG_SYS_FPGA_WAIT_INIT

1716

1717

Maximum time to wait for the INIT_B line to deassert

1717

Maximum time to wait for the INIT_B line to deassert

1718

after PROB_B has been deasserted during a Virtex II

1718

after PROB_B has been deasserted during a Virtex II

1719

FPGA configuration sequence. The default time is 500

1719

FPGA configuration sequence. The default time is 500

1720

ms.

1720

ms.

1721

1722

CONFIG_SYS_FPGA_WAIT_BUSY

1722

CONFIG_SYS_FPGA_WAIT_BUSY

1723

1724

Maximum time to wait for BUSY to deassert during

1724

Maximum time to wait for BUSY to deassert during

1725

Virtex II FPGA configuration. The default is 5 ms.

1725

Virtex II FPGA configuration. The default is 5 ms.

1726

1727

CONFIG_SYS_FPGA_WAIT_CONFIG

1727

CONFIG_SYS_FPGA_WAIT_CONFIG

1728

1729

Time to wait after FPGA configuration. The default is

1729

Time to wait after FPGA configuration. The default is

1730

200 ms.

1730

200 ms.

1731

1732

- Configuration Management:

1732

- Configuration Management:

1733

CONFIG_IDENT_STRING

1733

CONFIG_IDENT_STRING

1734

1735

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

1735

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

1736

version information (U_BOOT_VERSION)

1736

version information (U_BOOT_VERSION)

1737

1738

- Vendor Parameter Protection:

1738

- Vendor Parameter Protection:

1739

1740

U-Boot considers the values of the environment

1740

U-Boot considers the values of the environment

1741

variables "serial#" (Board Serial Number) and

1741

variables "serial#" (Board Serial Number) and

1742

"ethaddr" (Ethernet Address) to be parameters that

1742

"ethaddr" (Ethernet Address) to be parameters that

1743

are set once by the board vendor / manufacturer, and

1743

are set once by the board vendor / manufacturer, and

1744

protects these variables from casual modification by

1744

protects these variables from casual modification by

1745

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

1745

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

1746

and write or delete attempts are rejected. You can

1746

and write or delete attempts are rejected. You can

1747

change this behaviour:

1747

change this behaviour:

1748

1749

If CONFIG_ENV_OVERWRITE is #defined in your config

1749

If CONFIG_ENV_OVERWRITE is #defined in your config

1750

file, the write protection for vendor parameters is

1750

file, the write protection for vendor parameters is

1751

completely disabled. Anybody can change or delete

1751

completely disabled. Anybody can change or delete

1752

these parameters.

1752

these parameters.

1753

1754

Alternatively, if you #define _both_ CONFIG_ETHADDR

1754

Alternatively, if you #define _both_ CONFIG_ETHADDR

1755

_and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default

1755

_and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default

1756

Ethernet address is installed in the environment,

1756

Ethernet address is installed in the environment,

1757

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

1757

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

1758

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

1758

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

1759

read-only.]

1759

read-only.]

1760

1761

- Protected RAM:

1761

- Protected RAM:

1762

CONFIG_PRAM

1762

CONFIG_PRAM

1763

1764

Define this variable to enable the reservation of

1764

Define this variable to enable the reservation of

1765

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

1765

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

1766

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

1766

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

1767

kB you want to reserve for pRAM. You can overwrite

1767

kB you want to reserve for pRAM. You can overwrite

1768

this default value by defining an environment

1768

this default value by defining an environment

1769

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

1769

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

1770

reserve. Note that the board info structure will

1770

reserve. Note that the board info structure will

1771

still show the full amount of RAM. If pRAM is

1771

still show the full amount of RAM. If pRAM is

1772

reserved, a new environment variable "mem" will

1772

reserved, a new environment variable "mem" will

1773

automatically be defined to hold the amount of

1773

automatically be defined to hold the amount of

1774

remaining RAM in a form that can be passed as boot

1774

remaining RAM in a form that can be passed as boot

1775

argument to Linux, for instance like that:

1775

argument to Linux, for instance like that:

1776

1777

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

1777

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

1778

saveenv

1778

saveenv

1779

1780

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

1780

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

1781

either, which results in a memory region that will

1781

either, which results in a memory region that will

1782

not be affected by reboots.

1782

not be affected by reboots.

1783

1784

*WARNING* If your board configuration uses automatic

1784

*WARNING* If your board configuration uses automatic

1785

detection of the RAM size, you must make sure that

1785

detection of the RAM size, you must make sure that

1786

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

1786

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

1787

following board configurations are known to be

1787

following board configurations are known to be

1788

"pRAM-clean":

1788

"pRAM-clean":

1789

1790

ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,

1790

ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,

1791

HERMES, IP860, RPXlite, LWMON, LANTEC,

1791

HERMES, IP860, RPXlite, LWMON, LANTEC,

1792

PCU_E, FLAGADM, TQM8260

1792

PCU_E, FLAGADM, TQM8260

1793

1794

- Error Recovery:

1794

- Error Recovery:

1795

CONFIG_PANIC_HANG

1795

CONFIG_PANIC_HANG

1796

1797

Define this variable to stop the system in case of a

1797

Define this variable to stop the system in case of a

1798

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

1798

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

1799

This is probably NOT a good idea for an embedded

1799

This is probably NOT a good idea for an embedded

1800

system where you want the system to reboot

1800

system where you want the system to reboot

1801

automatically as fast as possible, but it may be

1801

automatically as fast as possible, but it may be

1802

useful during development since you can try to debug

1802

useful during development since you can try to debug

1803

the conditions that lead to the situation.

1803

the conditions that lead to the situation.

1804

1805

CONFIG_NET_RETRY_COUNT

1805

CONFIG_NET_RETRY_COUNT

1806

1807

This variable defines the number of retries for

1807

This variable defines the number of retries for

1808

network operations like ARP, RARP, TFTP, or BOOTP

1808

network operations like ARP, RARP, TFTP, or BOOTP

1809

before giving up the operation. If not defined, a

1809

before giving up the operation. If not defined, a

1810

default value of 5 is used.

1810

default value of 5 is used.

1811

1812

CONFIG_ARP_TIMEOUT

1812

CONFIG_ARP_TIMEOUT

1813

1814

Timeout waiting for an ARP reply in milliseconds.

1814

Timeout waiting for an ARP reply in milliseconds.

1815

1816

- Command Interpreter:

1816

- Command Interpreter:

1817

CONFIG_AUTO_COMPLETE

1817

CONFIG_AUTO_COMPLETE

1818

1819

Enable auto completion of commands using TAB.

1819

Enable auto completion of commands using TAB.

1820

1821

Note that this feature has NOT been implemented yet

1821

Note that this feature has NOT been implemented yet

1822

for the "hush" shell.

1822

for the "hush" shell.

1823

1824

1825

CONFIG_SYS_HUSH_PARSER

1825

CONFIG_SYS_HUSH_PARSER

1826

1827

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

1827

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

1828

Busybox) as command line interpreter, thus enabling

1828

Busybox) as command line interpreter, thus enabling

1829

powerful command line syntax like

1829

powerful command line syntax like

1830

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

1830

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

1831

constructs ("shell scripts").

1831

constructs ("shell scripts").

1832

1833

If undefined, you get the old, much simpler behaviour

1833

If undefined, you get the old, much simpler behaviour

1834

with a somewhat smaller memory footprint.

1834

with a somewhat smaller memory footprint.

1835

1836

1837

CONFIG_SYS_PROMPT_HUSH_PS2

1837

CONFIG_SYS_PROMPT_HUSH_PS2

1838

1839

This defines the secondary prompt string, which is

1839

This defines the secondary prompt string, which is

1840

printed when the command interpreter needs more input

1840

printed when the command interpreter needs more input

1841

to complete a command. Usually "> ".

1841

to complete a command. Usually "> ".

1842

1843

Note:

1843

Note:

1844

1845

In the current implementation, the local variables

1845

In the current implementation, the local variables

1846

space and global environment variables space are

1846

space and global environment variables space are

1847

separated. Local variables are those you define by

1847

separated. Local variables are those you define by

1848

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

1848

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

1849

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

1849

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

1850

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

1850

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

1851

directly type `$name' at the command prompt.

1851

directly type `$name' at the command prompt.

1852

1853

Global environment variables are those you use

1853

Global environment variables are those you use

1854

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

1854

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

1855

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

1855

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

1856

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

1856

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

1857

1858

To store commands and special characters in a

1858

To store commands and special characters in a

1859

variable, please use double quotation marks

1859

variable, please use double quotation marks

1860

surrounding the whole text of the variable, instead

1860

surrounding the whole text of the variable, instead

1861

of the backslashes before semicolons and special

1861

of the backslashes before semicolons and special

1862

symbols.

1862

symbols.

1863

1864

- Commandline Editing and History:

1864

- Commandline Editing and History:

1865

CONFIG_CMDLINE_EDITING

1865

CONFIG_CMDLINE_EDITING

1866

1867

Enable editing and History functions for interactive

1867

Enable editing and History functions for interactive

1868

commandline input operations

1868

commandline input operations

1869

1870

- Default Environment:

1870

- Default Environment:

1871

CONFIG_EXTRA_ENV_SETTINGS

1871

CONFIG_EXTRA_ENV_SETTINGS

1872

1873

Define this to contain any number of null terminated

1873

Define this to contain any number of null terminated

1874

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

1874

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

1875

the default environment compiled into the boot image.

1875

the default environment compiled into the boot image.

1876

1877

For example, place something like this in your

1877

For example, place something like this in your

1878

board's config file:

1878

board's config file:

1879

1880

#define CONFIG_EXTRA_ENV_SETTINGS \

1880

#define CONFIG_EXTRA_ENV_SETTINGS \

1881

"myvar1=value1\0" \

1881

"myvar1=value1\0" \

1882

"myvar2=value2\0"

1882

"myvar2=value2\0"

1883

1884

Warning: This method is based on knowledge about the

1884

Warning: This method is based on knowledge about the

1885

internal format how the environment is stored by the

1885

internal format how the environment is stored by the

1886

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

1886

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

1887

interface! Although it is unlikely that this format

1887

interface! Although it is unlikely that this format

1888

will change soon, there is no guarantee either.

1888

will change soon, there is no guarantee either.

1889

You better know what you are doing here.

1889

You better know what you are doing here.

1890

1891

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

1891

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

1892

discouraged. Make sure to check other ways to preset

1892

discouraged. Make sure to check other ways to preset

1893

the environment like the "source" command or the

1893

the environment like the "source" command or the

1894

boot command first.

1894

boot command first.

1895

1896

- DataFlash Support:

1896

- DataFlash Support:

1897

CONFIG_HAS_DATAFLASH

1897

CONFIG_HAS_DATAFLASH

1898

1899

Defining this option enables DataFlash features and

1899

Defining this option enables DataFlash features and

1900

allows to read/write in Dataflash via the standard

1900

allows to read/write in Dataflash via the standard

1901

commands cp, md...

1901

commands cp, md...

1902

1903

- SystemACE Support:

1903

- SystemACE Support:

1904

CONFIG_SYSTEMACE

1904

CONFIG_SYSTEMACE

1905

1906

Adding this option adds support for Xilinx SystemACE

1906

Adding this option adds support for Xilinx SystemACE

1907

chips attached via some sort of local bus. The address

1907

chips attached via some sort of local bus. The address

1908

of the chip must also be defined in the

1908

of the chip must also be defined in the

1909

CONFIG_SYS_SYSTEMACE_BASE macro. For example:

1909

CONFIG_SYS_SYSTEMACE_BASE macro. For example:

1910

1911

#define CONFIG_SYSTEMACE

1911

#define CONFIG_SYSTEMACE

1912

#define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000

1912

#define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000

1913

1914

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

1914

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

1915

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

1915

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

1916

1917

- TFTP Fixed UDP Port:

1917

- TFTP Fixed UDP Port:

1918

CONFIG_TFTP_PORT

1918

CONFIG_TFTP_PORT

1919

1920

If this is defined, the environment variable tftpsrcp

1920

If this is defined, the environment variable tftpsrcp

1921

is used to supply the TFTP UDP source port value.

1921

is used to supply the TFTP UDP source port value.

1922

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

1922

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

1923

number generator is used.

1923

number generator is used.

1924

1925

Also, the environment variable tftpdstp is used to supply

1925

Also, the environment variable tftpdstp is used to supply

1926

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

1926

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

1927

defined, the normal port 69 is used.

1927

defined, the normal port 69 is used.

1928

1929

The purpose for tftpsrcp is to allow a TFTP server to

1929

The purpose for tftpsrcp is to allow a TFTP server to

1930

blindly start the TFTP transfer using the pre-configured

1930

blindly start the TFTP transfer using the pre-configured

1931

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

1931

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

1932

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

1932

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

1933

the remainder of the TFTP transfer to proceed normally.

1933

the remainder of the TFTP transfer to proceed normally.

1934

A better solution is to properly configure the firewall,

1934

A better solution is to properly configure the firewall,

1935

but sometimes that is not allowed.

1935

but sometimes that is not allowed.

1936

1937

- Show boot progress:

1937

- Show boot progress:

1938

CONFIG_SHOW_BOOT_PROGRESS

1938

CONFIG_SHOW_BOOT_PROGRESS

1939

1940

Defining this option allows to add some board-

1940

Defining this option allows to add some board-

1941

specific code (calling a user-provided function

1941

specific code (calling a user-provided function

1942

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

1942

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

1943

the system's boot progress on some display (for

1943

the system's boot progress on some display (for

1944

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

1944

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

1945

the following checkpoints are implemented:

1945

the following checkpoints are implemented:

1946

1947

Legacy uImage format:

1947

Legacy uImage format:

1948

1949

Arg Where When

1949

Arg Where When

1950

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

1950

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

1951

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

1951

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

1952

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

1952

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

1953

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

1953

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

1954

3 common/cmd_bootm.c Image header has correct checksum

1954

3 common/cmd_bootm.c Image header has correct checksum

1955

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

1955

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

1956

4 common/cmd_bootm.c Image data has correct checksum

1956

4 common/cmd_bootm.c Image data has correct checksum

1957

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

1957

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

1958

5 common/cmd_bootm.c Architecture check OK

1958

5 common/cmd_bootm.c Architecture check OK

1959

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

1959

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

1960

6 common/cmd_bootm.c Image Type check OK

1960

6 common/cmd_bootm.c Image Type check OK

1961

-6 common/cmd_bootm.c gunzip uncompression error

1961

-6 common/cmd_bootm.c gunzip uncompression error

1962

-7 common/cmd_bootm.c Unimplemented compression type

1962

-7 common/cmd_bootm.c Unimplemented compression type

1963

7 common/cmd_bootm.c Uncompression OK

1963

7 common/cmd_bootm.c Uncompression OK

1964

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

1964

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

1965

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

1965

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

1966

1967

9 common/image.c Start initial ramdisk verification

1967

9 common/image.c Start initial ramdisk verification

1968

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

1968

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

1969

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

1969

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

1970

10 common/image.c Ramdisk header is OK

1970

10 common/image.c Ramdisk header is OK

1971

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

1971

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

1972

11 common/image.c Ramdisk data has correct checksum

1972

11 common/image.c Ramdisk data has correct checksum

1973

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

1973

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

1974

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

1974

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

1975

13 common/image.c Start multifile image verification

1975

13 common/image.c Start multifile image verification

1976

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

1976

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

1977

1978

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

1978

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

1979

1980

-30 arch/powerpc/lib/board.c Fatal error, hang the system

1980

-30 arch/powerpc/lib/board.c Fatal error, hang the system

1981

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

1981

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

1982

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

1982

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

1983

1984

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

1984

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

1985

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

1985

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

1986

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

1986

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

1987

-36 common/cmd_doc.c No boot device

1987

-36 common/cmd_doc.c No boot device

1988

36 common/cmd_doc.c correct boot device

1988

36 common/cmd_doc.c correct boot device

1989

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

1989

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

1990

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

1990

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

1991

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

1991

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

1992

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

1992

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

1993

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

1993

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

1994

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

1994

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

1995

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

1995

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

1996

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

1996

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

1997

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

1997

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

1998

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

1998

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

1999

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

1999

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

2000

-43 common/cmd_ide.c No boot device

2000

-43 common/cmd_ide.c No boot device

2001

43 common/cmd_ide.c boot device found

2001

43 common/cmd_ide.c boot device found

2002

-44 common/cmd_ide.c Device not available

2002

-44 common/cmd_ide.c Device not available

2003

44 common/cmd_ide.c Device available

2003

44 common/cmd_ide.c Device available

2004

-45 common/cmd_ide.c wrong partition selected

2004

-45 common/cmd_ide.c wrong partition selected

2005

45 common/cmd_ide.c partition selected

2005

45 common/cmd_ide.c partition selected

2006

-46 common/cmd_ide.c Unknown partition table

2006

-46 common/cmd_ide.c Unknown partition table

2007

46 common/cmd_ide.c valid partition table found

2007

46 common/cmd_ide.c valid partition table found

2008

-47 common/cmd_ide.c Invalid partition type

2008

-47 common/cmd_ide.c Invalid partition type

2009

47 common/cmd_ide.c correct partition type

2009

47 common/cmd_ide.c correct partition type

2010

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

2010

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

2011

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

2011

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

2012

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

2012

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

2013

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

2013

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

2014

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

2014

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

2015

50 common/cmd_ide.c Image header has correct checksum

2015

50 common/cmd_ide.c Image header has correct checksum

2016

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

2016

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

2017

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

2017

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

2018

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

2018

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

2019

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

2019

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

2020

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

2020

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

2021

-54 common/cmd_nand.c No boot device

2021

-54 common/cmd_nand.c No boot device

2022

54 common/cmd_nand.c boot device found

2022

54 common/cmd_nand.c boot device found

2023

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

2023

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

2024

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

2024

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

2025

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

2025

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

2026

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

2026

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

2027

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

2027

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

2028

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

2028

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

2029

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

2029

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

2030

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

2030

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

2031

2032

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

2032

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

2033

2034

64 net/eth.c starting with Ethernet configuration.

2034

64 net/eth.c starting with Ethernet configuration.

2035

-64 net/eth.c no Ethernet found.

2035

-64 net/eth.c no Ethernet found.

2036

65 net/eth.c Ethernet found.

2036

65 net/eth.c Ethernet found.

2037

2038

-80 common/cmd_net.c usage wrong

2038

-80 common/cmd_net.c usage wrong

2039

80 common/cmd_net.c before calling NetLoop()

2039

80 common/cmd_net.c before calling NetLoop()

2040

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

2040

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

2041

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

2041

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

2042

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

2042

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

2043

82 common/cmd_net.c trying automatic boot

2043

82 common/cmd_net.c trying automatic boot

2044

83 common/cmd_net.c running "source" command

2044

83 common/cmd_net.c running "source" command

2045

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

2045

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

2046

84 common/cmd_net.c end without errors

2046

84 common/cmd_net.c end without errors

2047

2048

FIT uImage format:

2048

FIT uImage format:

2049

2050

Arg Where When

2050

Arg Where When

2051

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

2051

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

2052

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

2052

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

2053

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

2053

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

2054

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

2054

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

2055

102 common/cmd_bootm.c Kernel unit name specified

2055

102 common/cmd_bootm.c Kernel unit name specified

2056

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

2056

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

2057

103 common/cmd_bootm.c Found configuration node

2057

103 common/cmd_bootm.c Found configuration node

2058

104 common/cmd_bootm.c Got kernel subimage node offset

2058

104 common/cmd_bootm.c Got kernel subimage node offset

2059

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

2059

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

2060

105 common/cmd_bootm.c Kernel subimage hash verification OK

2060

105 common/cmd_bootm.c Kernel subimage hash verification OK

2061

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

2061

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

2062

106 common/cmd_bootm.c Architecture check OK

2062

106 common/cmd_bootm.c Architecture check OK

2063

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

2063

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

2064

107 common/cmd_bootm.c Kernel subimage type OK

2064

107 common/cmd_bootm.c Kernel subimage type OK

2065

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

2065

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

2066

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

2066

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

2067

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

2067

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

2068

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

2068

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

2069

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

2069

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

2070

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

2070

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

2071

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

2071

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

2072

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

2072

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

2073

2074

120 common/image.c Start initial ramdisk verification

2074

120 common/image.c Start initial ramdisk verification

2075

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

2075

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

2076

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

2076

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

2077

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

2077

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

2078

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

2078

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

2079

123 common/image.c Ramdisk unit name specified

2079

123 common/image.c Ramdisk unit name specified

2080

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

2080

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

2081

125 common/image.c Got ramdisk subimage node offset

2081

125 common/image.c Got ramdisk subimage node offset

2082

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

2082

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

2083

126 common/image.c Ramdisk subimage hash verification OK

2083

126 common/image.c Ramdisk subimage hash verification OK

2084

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

2084

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

2085

127 common/image.c Architecture check OK

2085

127 common/image.c Architecture check OK

2086

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

2086

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

2087

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

2087

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

2088

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

2088

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

2089

-129 common/image.c Got ramdisk load address

2089

-129 common/image.c Got ramdisk load address

2090

2091

-130 common/cmd_doc.c Incorrect FIT image format

2091

-130 common/cmd_doc.c Incorrect FIT image format

2092

131 common/cmd_doc.c FIT image format OK

2092

131 common/cmd_doc.c FIT image format OK

2093

2094

-140 common/cmd_ide.c Incorrect FIT image format

2094

-140 common/cmd_ide.c Incorrect FIT image format

2095

141 common/cmd_ide.c FIT image format OK

2095

141 common/cmd_ide.c FIT image format OK

2096

2097

-150 common/cmd_nand.c Incorrect FIT image format

2097

-150 common/cmd_nand.c Incorrect FIT image format

2098

151 common/cmd_nand.c FIT image format OK

2098

151 common/cmd_nand.c FIT image format OK

2099

2100

- Automatic software updates via TFTP server

2100

- Automatic software updates via TFTP server

2101

CONFIG_UPDATE_TFTP

2101

CONFIG_UPDATE_TFTP

2102

CONFIG_UPDATE_TFTP_CNT_MAX

2102

CONFIG_UPDATE_TFTP_CNT_MAX

2103

CONFIG_UPDATE_TFTP_MSEC_MAX

2103

CONFIG_UPDATE_TFTP_MSEC_MAX

2104

2105

These options enable and control the auto-update feature;

2105

These options enable and control the auto-update feature;

2106

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

2106

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

2107

2108

- MTD Support (mtdparts command, UBI support)

2108

- MTD Support (mtdparts command, UBI support)

2109

CONFIG_MTD_DEVICE

2109

CONFIG_MTD_DEVICE

2110

2111

Adds the MTD device infrastructure from the Linux kernel.

2111

Adds the MTD device infrastructure from the Linux kernel.

2112

Needed for mtdparts command support.

2112

Needed for mtdparts command support.

2113

2114

CONFIG_MTD_PARTITIONS

2114

CONFIG_MTD_PARTITIONS

2115

2116

Adds the MTD partitioning infrastructure from the Linux

2116

Adds the MTD partitioning infrastructure from the Linux

2117

kernel. Needed for UBI support.

2117

kernel. Needed for UBI support.

2118

2119

2120

Modem Support:

2120

Modem Support:

2121

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

2121

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

2122

2123

[so far only for SMDK2400 and TRAB boards]

2123

[so far only for SMDK2400 and TRAB boards]

2124

2125

- Modem support enable:

2125

- Modem support enable:

2126

CONFIG_MODEM_SUPPORT

2126

CONFIG_MODEM_SUPPORT

2127

2128

- RTS/CTS Flow control enable:

2128

- RTS/CTS Flow control enable:

2129

CONFIG_HWFLOW

2129

CONFIG_HWFLOW

2130

2131

- Modem debug support:

2131

- Modem debug support:

2132

CONFIG_MODEM_SUPPORT_DEBUG

2132

CONFIG_MODEM_SUPPORT_DEBUG

2133

2134

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

2134

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

2135

for modem support. Useful only with BDI2000.

2135

for modem support. Useful only with BDI2000.

2136

2137

- Interrupt support (PPC):

2137

- Interrupt support (PPC):

2138

2139

There are common interrupt_init() and timer_interrupt()

2139

There are common interrupt_init() and timer_interrupt()

2140

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

2140

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

2141

for CPU specific initialization. interrupt_init_cpu()

2141

for CPU specific initialization. interrupt_init_cpu()

2142

should set decrementer_count to appropriate value. If

2142

should set decrementer_count to appropriate value. If

2143

CPU resets decrementer automatically after interrupt

2143

CPU resets decrementer automatically after interrupt

2144

(ppc4xx) it should set decrementer_count to zero.

2144

(ppc4xx) it should set decrementer_count to zero.

2145

timer_interrupt() calls timer_interrupt_cpu() for CPU

2145

timer_interrupt() calls timer_interrupt_cpu() for CPU

2146

specific handling. If board has watchdog / status_led

2146

specific handling. If board has watchdog / status_led

2147

/ other_activity_monitor it works automatically from

2147

/ other_activity_monitor it works automatically from

2148

general timer_interrupt().

2148

general timer_interrupt().

2149

2150

- General:

2150

- General:

2151

2152

In the target system modem support is enabled when a

2152

In the target system modem support is enabled when a

2153

specific key (key combination) is pressed during

2153

specific key (key combination) is pressed during

2154

power-on. Otherwise U-Boot will boot normally

2154

power-on. Otherwise U-Boot will boot normally

2155

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

2155

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

2156

board_init(). Currently key_pressed() is a dummy

2156

board_init(). Currently key_pressed() is a dummy

2157

function, returning 1 and thus enabling modem

2157

function, returning 1 and thus enabling modem

2158

initialization.

2158

initialization.

2159

2160

If there are no modem init strings in the

2160

If there are no modem init strings in the

2161

environment, U-Boot proceed to autoboot; the

2161

environment, U-Boot proceed to autoboot; the

2162

previous output (banner, info printfs) will be

2162

previous output (banner, info printfs) will be

2163

suppressed, though.

2163

suppressed, though.

2164

2165

GITLAB

Program net device MAC addresses after initializing

 #
 # (C) Copyright 2000 - 2009
 # 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:
 ====================
 /arch			Architecture specific files
   /arm			Files generic to ARM architecture
     /cpu		CPU specific files
       /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
       /ixp		Files specific to Intel XScale IXP CPUs
       /pxa		Files specific to Intel XScale PXA CPUs
       /s3c44b0		Files specific to Samsung S3C44B0 CPUs
       /sa1100		Files specific to Intel StrongARM SA1100 CPUs
     /lib		Architecture specific library files
   /avr32		Files generic to AVR32 architecture
     /cpu		CPU specific files
     /lib		Architecture specific library files
   /blackfin		Files generic to Analog Devices Blackfin architecture
     /cpu		CPU specific files
     /lib		Architecture specific library files
   /i386			Files generic to i386 architecture
     /cpu		CPU specific files
     /lib		Architecture specific library files
   /m68k			Files generic to m68k architecture
     /cpu		CPU specific files
       /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
     /lib		Architecture specific library files
   /microblaze		Files generic to microblaze architecture
     /cpu		CPU specific files
     /lib		Architecture specific library files
   /mips			Files generic to MIPS architecture
     /cpu		CPU specific files
     /lib		Architecture specific library files
   /nios			Files generic to Altera NIOS architecture
     /cpu		CPU specific files
     /lib		Architecture specific library files
   /nios2		Files generic to Altera NIOS2 architecture
     /cpu		CPU specific files
     /lib		Architecture specific library files
   /powerpc		Files generic to PowerPC architecture
     /cpu		CPU specific files
       /74xx_7xx		Files specific to Freescale MPC74xx and 7xx 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
       /ppc4xx		Files specific to AMCC PowerPC 4xx CPUs
     /lib		Architecture specific library files
   /sh			Files generic to SH architecture
     /cpu		CPU specific files
       /sh2		Files specific to sh2 CPUs
       /sh3		Files specific to sh3 CPUs
       /sh4		Files specific to sh4 CPUs
     /lib		Architecture specific library files
   /sparc		Files generic to SPARC architecture
     /cpu		CPU specific files
       /leon2		Files specific to Gaisler LEON2 SPARC CPU
       /leon3		Files specific to Gaisler LEON3 SPARC CPU
     /lib		Architecture specific library files
 /api			Machine/arch independent API for external apps
 /board			Board dependent files
 /common			Misc architecture independent functions
 /disk			Code for disk drive partition handling
 /doc			Documentation (don't expect too much)
 /drivers		Commonly used device drivers
 /examples		Example code for standalone applications, etc.
 /fs			Filesystem code (cramfs, ext2, jffs2, etc.)
 /include		Header Files
 /lib			Files generic to all architectures
   /libfdt		Library files to support flattened device trees
   /lzma			Library files to support LZMA decompression
   /lzo			Library files to support LZO decompression
 /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 (only required for
 			MPC512X and MPC5xxx based boards).
 		OF_SOC - The proper name of the soc node (only required for
 			MPC512X and MPC5xxx based boards).
 		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.
 		CONFIG_OF_IDE_FIXUP
 		U-Boot can detect if an IDE device is present or not.
 		If not, and this new config option is activated, U-Boot
 		removes the ATA node from the DTS before booting Linux,
 		so the Linux IDE driver does not probe the device and
 		crash. This is needed for buggy hardware (uc101) where
 		no pull down resistor is connected to the signal IDE5V_DD7.
 - 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_EDITENV	  edit env variable
 		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.
 		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_AT91EMAC
 		Support for AT91RM9200 EMAC.
 			CONFIG_RMII
 			Define this to use reduced MII inteface
 			CONFIG_DRIVER_AT91EMAC_QUIET
 			If this defined, the driver is quiet.
 			The driver doen't show link status messages.
 		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_SMC911X
 		Support for SMSC's LAN911x and LAN921x chips
 			CONFIG_SMC911X_BASE
 			Define this to hold the physical address
 			of the device (I/O space)
 			CONFIG_SMC911X_32_BIT
 			Define this if data bus is 32 bits
 			CONFIG_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_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.
 - Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8
 		If this option is set, 8-bit RLE compressed 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
 		(arch/powerpc/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_SYS_I2C_BOARD_LATE_INIT
 		An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is
 		defined a custom i2c_board_late_init() routine in
 		boards/xxx/board.c is run AFTER the operations in i2c_init()
 		is completed. This callpoint can be used to unreset i2c bus
 		using CPU i2c controller register accesses for CPUs whose i2c
 		controller provide such a method. It is called at the end of
 		i2c_init() to allow i2c_init operations to setup the i2c bus
 		controller on the CPU (e.g. setting bus speed & slave address).
 		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:
 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	arch/<arch>/lib/bootm.c	All preparation done, transferring control to OS
   -30	arch/powerpc/lib/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
 - 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.
 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_EEPROM_IS_ON_I2C
 	  define this, if you have I2C and SPI activated, and your
 	  EEPROM, which holds the environment, is on the I2C bus.
 	- CONFIG_I2C_ENV_EEPROM_BUS
 	  if you have an Environment on an EEPROM reached over
 	  I2C muxes, you can define here, how to reach this
 	  EEPROM. For example:
 	  #define CONFIG_I2C_ENV_EEPROM_BUS       "pca9547:70:d\0"
 	  EEPROM which holds the environment, is reached over
 	  a pca9547 i2c mux with address 0x70, channel 3.
 - 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_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 arch/powerpc/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.
 List of environment variables (most likely not complete):
   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
   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.
   tftpblocksize - Block size to use for TFTP transfers; if not set,
 		  we use the TFTP server's default block size
   tftptimeout	- Retransmission timeout for TFTP packets (in milli-
 		  seconds, minimum value is 1000 = 1 second). Defines
 		  when a packet is considered to be lost so it has to
 		  be retransmitted. The default is 5000 = 5 seconds.
 		  Lowering this value may make downloads succeed
 		  faster in networks with high packet loss rates or
 		  with unreliable TFTP servers.
   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.
+If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses
+will be programmed into hardware as part of the initialization process.  This
+may be skipped by setting the appropriate 'ethmacskip' environment variable.
+The naming convention is as follows:
+"ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc.
 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/powerpc/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/powerpc/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/powerpc/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/powerpc/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 R12 as internal GOT pointer. r12
 	is a volatile register so r12 needs to be reset when
 	going back and forth between asm and C)
     ==> 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.

 -----------------------
  Ethernet Driver Guide
 -----------------------
 The networking stack in Das U-Boot is designed for multiple network devices
 to be easily added and controlled at runtime.  This guide is meant for people
 who wish to review the net driver stack with an eye towards implementing your
 own ethernet device driver.  Here we will describe a new pseudo 'APE' driver.
 ------------------
  Driver Functions
 ------------------
 All functions you will be implementing in this document have the return value
 meaning of 0 for success and non-zero for failure.
  ----------
   Register
  ----------
 When U-Boot initializes, it will call the common function eth_initialize().
 This will in turn call the board-specific board_eth_init() (or if that fails,
 the cpu-specific cpu_eth_init()).  These board-specific functions can do random
 system handling, but ultimately they will call the driver-specific register
 function which in turn takes care of initializing that particular instance.
 Keep in mind that you should code the driver to avoid storing state in global
 data as someone might want to hook up two of the same devices to one board.
 Any such information that is specific to an interface should be stored in a
 private, driver-defined data structure and pointed to by eth->priv (see below).
 So the call graph at this stage would look something like:
 board_init()
 	eth_initialize()
 		board_eth_init() / cpu_eth_init()
 			driver_register()
 				initialize eth_device
 				eth_register()
 At this point in time, the only thing you need to worry about is the driver's
 register function.  The pseudo code would look something like:
 int ape_register(bd_t *bis, int iobase)
 {
 	struct ape_priv *priv;
 	struct eth_device *dev;
 	priv = malloc(sizeof(*priv));
 	if (priv == NULL)
 		return 1;
 	dev = malloc(sizeof(*dev));
 	if (dev == NULL) {
 		free(priv);
 		return 1;
 	}
 	/* setup whatever private state you need */
 	memset(dev, 0, sizeof(*dev));
 	sprintf(dev->name, "APE");
 	/* if your device has dedicated hardware storage for the
 	 * MAC, read it and initialize dev->enetaddr with it
 	 */
 	ape_mac_read(dev->enetaddr);
 	dev->iobase = iobase;
 	dev->priv = priv;
 	dev->init = ape_init;
 	dev->halt = ape_halt;
 	dev->send = ape_send;
 	dev->recv = ape_recv;
+	dev->write_hwaddr = ape_write_hwaddr;
 	eth_register(dev);
 #ifdef CONFIG_CMD_MII)
 	miiphy_register(dev->name, ape_mii_read, ape_mii_write);
 #endif
 	return 1;
 }
 The exact arguments needed to initialize your device are up to you.  If you
 need to pass more/less arguments, that's fine.  You should also add the
 prototype for your new register function to include/netdev.h.
 The return value for this function should be as follows:
 < 0 - failure (hardware failure, not probe failure)
 >=0 - number of interfaces detected
 You might notice that many drivers seem to use xxx_initialize() rather than
 xxx_register().  This is the old naming convention and should be avoided as it
 causes confusion with the driver-specific init function.
 Other than locating the MAC address in dedicated hardware storage, you should
 not touch the hardware in anyway.  That step is handled in the driver-specific
 init function.  Remember that we are only registering the device here, we are
 not checking its state or doing random probing.
  -----------
   Callbacks
  -----------
 Now that we've registered with the ethernet layer, we can start getting some
-real work done.  You will need four functions:
+real work done.  You will need five functions:
 	int ape_init(struct eth_device *dev, bd_t *bis);
 	int ape_send(struct eth_device *dev, volatile void *packet, int length);
 	int ape_recv(struct eth_device *dev);
 	int ape_halt(struct eth_device *dev);
+	int ape_write_hwaddr(struct eth_device *dev);
 The init function checks the hardware (probing/identifying) and gets it ready
 for send/recv operations.  You often do things here such as resetting the MAC
 and/or PHY, and waiting for the link to autonegotiate.  You should also take
 the opportunity to program the device's MAC address with the dev->enetaddr
 member.  This allows the rest of U-Boot to dynamically change the MAC address
 and have the new settings be respected.
 The send function does what you think -- transmit the specified packet whose
 size is specified by length (in bytes).  You should not return until the
 transmission is complete, and you should leave the state such that the send
 function can be called multiple times in a row.
 The recv function should process packets as long as the hardware has them
 readily available before returning.  i.e. you should drain the hardware fifo.
 For each packet you receive, you should call the NetReceive() function on it
 along with the packet length.  The common code sets up packet buffers for you
 already in the .bss (NetRxPackets), so there should be no need to allocate your
 own.  This doesn't mean you must use the NetRxPackets array however; you're
 free to call the NetReceive() function with any buffer you wish.  So the pseudo
 code here would look something like:
 int ape_recv(struct eth_device *dev)
 {
 	int length, i = 0;
 	...
 	while (packets_are_available()) {
 		...
 		length = ape_get_packet(&NetRxPackets[i]);
 		...
 		NetReceive(&NetRxPackets[i], length);
 		...
 		if (++i >= PKTBUFSRX)
 			i = 0;
 		...
 	}
 	...
 	return 0;
 }
 The halt function should turn off / disable the hardware and place it back in
 its reset state.  It can be called at any time (before any call to the related
 init function), so make sure it can handle this sort of thing.
+The write_hwaddr function should program the MAC address stored in dev->enetaddr
+into the Ethernet controller.
 So the call graph at this stage would look something like:
 some net operation (ping / tftp / whatever...)
 	eth_init()
 		dev->init()
 	eth_send()
 		dev->send()
 	eth_rx()
 		dev->recv()
 	eth_halt()
 		dev->halt()
 -----------------------------
  CONFIG_MII / CONFIG_CMD_MII
 -----------------------------
 If your device supports banging arbitrary values on the MII bus (pretty much
 every device does), you should add support for the mii command.  Doing so is
 fairly trivial and makes debugging mii issues a lot easier at runtime.
 After you have called eth_register() in your driver's register function, add
 a call to miiphy_register() like so:
 #if defined(CONFIG_MII) || defined(CONFIG_CMD_MII)
 	miiphy_register(dev->name, mii_read, mii_write);
 #endif
 And then define the mii_read and mii_write functions if you haven't already.
 Their syntax is straightforward:
 	int mii_read(char *devname, uchar addr, uchar reg, ushort *val);
 	int mii_write(char *devname, uchar addr, uchar reg, ushort val);
 The read function should read the register 'reg' from the phy at address 'addr'
 and store the result in the pointer 'val'.  The implementation for the write
 function should logically follow.

 ---------------------------------
  Ethernet Address (MAC) Handling
 ---------------------------------
 There are a variety of places in U-Boot where the MAC address is used, parsed,
 and stored.  This document covers proper usage of each location and the moving
 of data between them.
 -----------
  Locations
 -----------
 Here are the places where MAC addresses might be stored:
  - board-specific location (eeprom, dedicated flash, ...)
 	Note: only used when mandatory due to hardware design etc...
  - environment ("ethaddr", "eth1addr", ...) (see CONFIG_ETHADDR)
 	Note: this is the preferred way to permanently store MAC addresses
  - ethernet data (struct eth_device -> enetaddr)
 	Note: these are temporary copies of the MAC address which exist only
 	      after the respective init steps have run and only to make usage
 	      in other places easier (to avoid constant env lookup/parsing)
  - struct bd_info and/or device tree
 	Note: these are temporary copies of the MAC address only for the
 	      purpose of passing this information to an OS kernel we are about
 	      to boot
 Correct flow of setting up the MAC address (summarized):
 1. Read from hardware in initialize() function
 2. Read from environment in net/eth.c after initialize()
 3. Give priority to the value in the environment if a conflict
-4. Program hardware in the device's init() function.
+4. Program the address into hardware if the following conditions are met:
+	a) The relevant driver has a 'write_addr' function
+	b) The user hasn't set an 'ethmacskip' environment variable
+	c) The address is valid (unicast, not all-zeros)
-If somebody wants to subvert the design philosophy, this can be done
+Previous behavior had the MAC address always being programmed into hardware
-in the board-specific board_eth_init() function by calling eth_init()
+in the device's init() function.
-after all the NICs have been registered.
 -------
  Usage
 -------
 If the hardware design mandates that the MAC address is stored in some special
 place (like EEPROM etc...), then the board specific init code (such as the
 board-specific misc_init_r() function) is responsible for locating the MAC
 address(es) and initializing the respective environment variable(s) from it.
 Note that this shall be done if, and only if, the environment does not already
 contain these environment variables, i.e. existing variable definitions must
 not be overwritten.
 During runtime, the ethernet layer will use the environment variables to sync
 the MAC addresses to the ethernet structures.  All ethernet driver code should
 then only use the enetaddr member of the eth_device structure.  This is done
 on every network command, so the ethernet copies will stay in sync.
 Any other code that wishes to access the MAC address should query the
 environment directly.  The helper functions documented below should make
 working with this storage much smoother.
 ---------
  Helpers
 ---------
 To assist in the management of these layers, a few helper functions exist.  You
 should use these rather than attempt to do any kind of parsing/manipulation
 yourself as many common errors have arisen in the past.
 	* void eth_parse_enetaddr(const char *addr, uchar *enetaddr);
 Convert a string representation of a MAC address to the binary version.
 char *addr = "00:11:22:33:44:55";
 uchar enetaddr[6];
 eth_parse_enetaddr(addr, enetaddr);
 /* enetaddr now equals { 0x00, 0x11, 0x22, 0x33, 0x44, 0x55 } */
 	* int eth_getenv_enetaddr(char *name, uchar *enetaddr);
 Look up an environment variable and convert the stored address.  If the address
 is valid, then the function returns 1.  Otherwise, the function returns 0.  In
 all cases, the enetaddr memory is initialized.  If the env var is not found,
 then it is set to all zeros.  The common function is_valid_ether_addr() is used
 to determine address validity.
 uchar enetaddr[6];
 if (!eth_getenv_enetaddr("ethaddr", enetaddr)) {
 	/* "ethaddr" is not set in the environment */
 	... try and setup "ethaddr" in the env ...
 }
 /* enetaddr is now set to the value stored in the ethaddr env var */
 	* int eth_setenv_enetaddr(char *name, const uchar *enetaddr);
 Store the MAC address into the named environment variable.  The return value is
 the same as the setenv() function.
 uchar enetaddr[6] = { 0x00, 0x11, 0x22, 0x33, 0x44, 0x55 };
 eth_setenv_enetaddr("ethaddr", enetaddr);
 /* the "ethaddr" env var should now be set to "00:11:22:33:44:55" */
 	* the %pM format modifier
 The %pM format modifier can be used with any standard printf function to format
 the binary 6 byte array representation of a MAC address.
 uchar enetaddr[6] = { 0x00, 0x11, 0x22, 0x33, 0x44, 0x55 };
 printf("The MAC is %pM\n", enetaddr);
 char buf[20];
 sprintf(buf, "%pM", enetaddr);
 /* the buf variable is now set to "00:11:22:33:44:55" */

 /*
  *	LiMon Monitor (LiMon) - Network.
  *
  *	Copyright 1994 - 2000 Neil Russell.
  *	(See License)
  *
  *
  * History
  *	9/16/00	  bor  adapted to TQM823L/STK8xxL board, RARP/TFTP boot added
  */
 #ifndef __NET_H__
 #define __NET_H__
 #if defined(CONFIG_8xx)
 #include <commproc.h>
 # if !defined(CONFIG_NET_MULTI)
 #  if defined(FEC_ENET) || defined(SCC_ENET)
 #   define CONFIG_NET_MULTI
 #  endif
 # endif
 #endif	/* CONFIG_8xx */
 #if defined(CONFIG_MPC5xxx)
 # if !defined(CONFIG_NET_MULTI)
 #  if defined(CONFIG_MPC5xxx_FEC)
 #   define CONFIG_NET_MULTI
 #  endif
 # endif
 #endif	/* CONFIG_MPC5xxx */
 #if !defined(CONFIG_NET_MULTI) && defined(CONFIG_CPM2)
 #include <config.h>
 #if defined(CONFIG_ETHER_ON_FCC)
 #if defined(CONFIG_ETHER_ON_SCC)
 #error "Ethernet not correctly defined"
 #endif /* CONFIG_ETHER_ON_SCC */
 #define CONFIG_NET_MULTI
 #if (CONFIG_ETHER_INDEX == 1)
 #define	CONFIG_ETHER_ON_FCC1
 # define CONFIG_SYS_CMXFCR_MASK1	CONFIG_SYS_CMXFCR_MASK
 # define CONFIG_SYS_CMXFCR_VALUE1	CONFIG_SYS_CMXFCR_VALUE
 #elif (CONFIG_ETHER_INDEX == 2)
 #define	CONFIG_ETHER_ON_FCC2
 # define CONFIG_SYS_CMXFCR_MASK2	CONFIG_SYS_CMXFCR_MASK
 # define CONFIG_SYS_CMXFCR_VALUE2	CONFIG_SYS_CMXFCR_VALUE
 #elif (CONFIG_ETHER_INDEX == 3)
 #define	CONFIG_ETHER_ON_FCC3
 # define CONFIG_SYS_CMXFCR_MASK3	CONFIG_SYS_CMXFCR_MASK
 # define CONFIG_SYS_CMXFCR_VALUE3	CONFIG_SYS_CMXFCR_VALUE
 #endif /* CONFIG_ETHER_INDEX */
 #endif /* CONFIG_ETHER_ON_FCC */
 #endif /* !CONFIG_NET_MULTI && CONFIG_8260 */
 #include <asm/byteorder.h>	/* for nton* / ntoh* stuff */
 /*
  *	The number of receive packet buffers, and the required packet buffer
  *	alignment in memory.
  *
  */
 #ifdef CONFIG_SYS_RX_ETH_BUFFER
 # define PKTBUFSRX	CONFIG_SYS_RX_ETH_BUFFER
 #else
 # define PKTBUFSRX	4
 #endif
 #define PKTALIGN	32
 typedef ulong		IPaddr_t;
 /*
  * The current receive packet handler.  Called with a pointer to the
  * application packet, and a protocol type (PORT_BOOTPC or PORT_TFTP).
  * All other packets are dealt with without calling the handler.
  */
 typedef void	rxhand_f(uchar *, unsigned, unsigned, unsigned);
 /*
  *	A timeout handler.  Called after time interval has expired.
  */
 typedef void	thand_f(void);
 #define NAMESIZE 16
 enum eth_state_t {
 	ETH_STATE_INIT,
 	ETH_STATE_PASSIVE,
 	ETH_STATE_ACTIVE
 };
 struct eth_device {
 	char name[NAMESIZE];
 	unsigned char enetaddr[6];
 	int iobase;
 	int state;
 	int  (*init) (struct eth_device*, bd_t*);
 	int  (*send) (struct eth_device*, volatile void* packet, int length);
 	int  (*recv) (struct eth_device*);
 	void (*halt) (struct eth_device*);
 #ifdef CONFIG_MCAST_TFTP
 	int (*mcast) (struct eth_device*, u32 ip, u8 set);
 #endif
+	int  (*write_hwaddr) (struct eth_device*);
 	struct eth_device *next;
 	void *priv;
 };
 extern int eth_initialize(bd_t *bis);	/* Initialize network subsystem */
 extern int eth_register(struct eth_device* dev);/* Register network device */
 extern void eth_try_another(int first_restart);	/* Change the device */
 #ifdef CONFIG_NET_MULTI
 extern void eth_set_current(void);		/* set nterface to ethcur var */
 #endif
 extern struct eth_device *eth_get_dev(void);	/* get the current device MAC */
 extern struct eth_device *eth_get_dev_by_name(char *devname); /* get device */
 extern struct eth_device *eth_get_dev_by_index(int index); /* get dev @ index */
 extern int eth_get_dev_index (void);		/* get the device index */
 extern void eth_parse_enetaddr(const char *addr, uchar *enetaddr);
 extern int eth_getenv_enetaddr(char *name, uchar *enetaddr);
 extern int eth_setenv_enetaddr(char *name, const uchar *enetaddr);
 extern int eth_getenv_enetaddr_by_index(int index, uchar *enetaddr);
 extern int eth_init(bd_t *bis);			/* Initialize the device */
 extern int eth_send(volatile void *packet, int length);	   /* Send a packet */
 #ifdef CONFIG_API
 extern int eth_receive(volatile void *packet, int length); /* Receive a packet*/
 #endif
 extern int eth_rx(void);			/* Check for received packets */
 extern void eth_halt(void);			/* stop SCC */
 extern char *eth_get_name(void);		/* get name of current device */
 #ifdef CONFIG_MCAST_TFTP
 int eth_mcast_join( IPaddr_t mcast_addr, u8 join);
 u32 ether_crc (size_t len, unsigned char const *p);
 #endif
 /**********************************************************************/
 /*
  *	Protocol headers.
  */
 /*
  *	Ethernet header
  */
 typedef struct {
 	uchar		et_dest[6];	/* Destination node		*/
 	uchar		et_src[6];	/* Source node			*/
 	ushort		et_protlen;	/* Protocol or length		*/
 	uchar		et_dsap;	/* 802 DSAP			*/
 	uchar		et_ssap;	/* 802 SSAP			*/
 	uchar		et_ctl;		/* 802 control			*/
 	uchar		et_snap1;	/* SNAP				*/
 	uchar		et_snap2;
 	uchar		et_snap3;
 	ushort		et_prot;	/* 802 protocol			*/
 } Ethernet_t;
 #define ETHER_HDR_SIZE	14		/* Ethernet header size		*/
 #define E802_HDR_SIZE	22		/* 802 ethernet header size	*/
 /*
  *	Ethernet header
  */
 typedef struct {
 	uchar		vet_dest[6];	/* Destination node		*/
 	uchar		vet_src[6];	/* Source node			*/
 	ushort		vet_vlan_type;	/* PROT_VLAN			*/
 	ushort		vet_tag;	/* TAG of VLAN			*/
 	ushort		vet_type;	/* protocol type		*/
 } VLAN_Ethernet_t;
 #define VLAN_ETHER_HDR_SIZE	18	/* VLAN Ethernet header size	*/
 #define PROT_IP		0x0800		/* IP protocol			*/
 #define PROT_ARP	0x0806		/* IP ARP protocol		*/
 #define PROT_RARP	0x8035		/* IP ARP protocol		*/
 #define PROT_VLAN	0x8100		/* IEEE 802.1q protocol		*/
 #define IPPROTO_ICMP	 1	/* Internet Control Message Protocol	*/
 #define IPPROTO_UDP	17	/* User Datagram Protocol		*/
 /*
  *	Internet Protocol (IP) header.
  */
 typedef struct {
 	uchar		ip_hl_v;	/* header length and version	*/
 	uchar		ip_tos;		/* type of service		*/
 	ushort		ip_len;		/* total length			*/
 	ushort		ip_id;		/* identification		*/
 	ushort		ip_off;		/* fragment offset field	*/
 	uchar		ip_ttl;		/* time to live			*/
 	uchar		ip_p;		/* protocol			*/
 	ushort		ip_sum;		/* checksum			*/
 	IPaddr_t	ip_src;		/* Source IP address		*/
 	IPaddr_t	ip_dst;		/* Destination IP address	*/
 	ushort		udp_src;	/* UDP source port		*/
 	ushort		udp_dst;	/* UDP destination port		*/
 	ushort		udp_len;	/* Length of UDP packet		*/
 	ushort		udp_xsum;	/* Checksum			*/
 } IP_t;
 #define IP_OFFS		0x1fff /* ip offset *= 8 */
 #define IP_FLAGS	0xe000 /* first 3 bits */
 #define IP_FLAGS_RES	0x8000 /* reserved */
 #define IP_FLAGS_DFRAG	0x4000 /* don't fragments */
 #define IP_FLAGS_MFRAG	0x2000 /* more fragments */
 #define IP_HDR_SIZE_NO_UDP	(sizeof (IP_t) - 8)
 #define IP_HDR_SIZE		(sizeof (IP_t))
 /*
  *	Address Resolution Protocol (ARP) header.
  */
 typedef struct
 {
 	ushort		ar_hrd;		/* Format of hardware address	*/
 #   define ARP_ETHER	    1		/* Ethernet  hardware address	*/
 	ushort		ar_pro;		/* Format of protocol address	*/
 	uchar		ar_hln;		/* Length of hardware address	*/
 	uchar		ar_pln;		/* Length of protocol address	*/
 	ushort		ar_op;		/* Operation			*/
 #   define ARPOP_REQUEST    1		/* Request  to resolve  address	*/
 #   define ARPOP_REPLY	    2		/* Response to previous request	*/
 #   define RARPOP_REQUEST   3		/* Request  to resolve  address	*/
 #   define RARPOP_REPLY	    4		/* Response to previous request */
 	/*
 	 * The remaining fields are variable in size, according to
 	 * the sizes above, and are defined as appropriate for
 	 * specific hardware/protocol combinations.
 	 */
 	uchar		ar_data[0];
 #if 0
 	uchar		ar_sha[];	/* Sender hardware address	*/
 	uchar		ar_spa[];	/* Sender protocol address	*/
 	uchar		ar_tha[];	/* Target hardware address	*/
 	uchar		ar_tpa[];	/* Target protocol address	*/
 #endif /* 0 */
 } ARP_t;
 #define ARP_HDR_SIZE	(8+20)		/* Size assuming ethernet	*/
 /*
  * ICMP stuff (just enough to handle (host) redirect messages)
  */
 #define ICMP_ECHO_REPLY		0	/* Echo reply			*/
 #define ICMP_REDIRECT		5	/* Redirect (change route)	*/
 #define ICMP_ECHO_REQUEST	8	/* Echo request			*/
 /* Codes for REDIRECT. */
 #define ICMP_REDIR_NET		0	/* Redirect Net			*/
 #define ICMP_REDIR_HOST		1	/* Redirect Host		*/
 typedef struct icmphdr {
 	uchar		type;
 	uchar		code;
 	ushort		checksum;
 	union {
 		struct {
 			ushort	id;
 			ushort	sequence;
 		} echo;
 		ulong	gateway;
 		struct {
 			ushort	__unused;
 			ushort	mtu;
 		} frag;
 	} un;
 } ICMP_t;
 /*
  * Maximum packet size; used to allocate packet storage.
  * TFTP packets can be 524 bytes + IP header + ethernet header.
  * Lets be conservative, and go for 38 * 16.  (Must also be
  * a multiple of 32 bytes).
  */
 /*
  * AS.HARNOIS : Better to set PKTSIZE to maximum size because
  * traffic type is not always controlled
  * maximum packet size =  1518
  * maximum packet size and multiple of 32 bytes =  1536
  */
 #define PKTSIZE			1518
 #define PKTSIZE_ALIGN		1536
 /*#define PKTSIZE		608*/
 /*
  * Maximum receive ring size; that is, the number of packets
  * we can buffer before overflow happens. Basically, this just
  * needs to be enough to prevent a packet being discarded while
  * we are processing the previous one.
  */
 #define RINGSZ		4
 #define RINGSZ_LOG2	2
 /**********************************************************************/
 /*
  *	Globals.
  *
  * Note:
  *
  * All variables of type IPaddr_t are stored in NETWORK byte order
  * (big endian).
  */
 /* net.c */
 /** BOOTP EXTENTIONS **/
 extern IPaddr_t		NetOurGatewayIP;	/* Our gateway IP addresse	*/
 extern IPaddr_t		NetOurSubnetMask;	/* Our subnet mask (0 = unknown)*/
 extern IPaddr_t		NetOurDNSIP;	 /* Our Domain Name Server (0 = unknown)*/
 #if defined(CONFIG_BOOTP_DNS2)
 extern IPaddr_t		NetOurDNS2IP;	 /* Our 2nd Domain Name Server (0 = unknown)*/
 #endif
 extern char		NetOurNISDomain[32];	/* Our NIS domain		*/
 extern char		NetOurHostName[32];	/* Our hostname			*/
 extern char		NetOurRootPath[64];	/* Our root path		*/
 extern ushort		NetBootFileSize;	/* Our boot file size in blocks	*/
 /** END OF BOOTP EXTENTIONS **/
 extern ulong		NetBootFileXferSize;	/* size of bootfile in bytes	*/
 extern uchar		NetOurEther[6];		/* Our ethernet address		*/
 extern uchar		NetServerEther[6];	/* Boot server enet address	*/
 extern IPaddr_t		NetOurIP;		/* Our    IP addr (0 = unknown)	*/
 extern IPaddr_t		NetServerIP;		/* Server IP addr (0 = unknown)	*/
 extern volatile uchar * NetTxPacket;		/* THE transmit packet		*/
 extern volatile uchar * NetRxPackets[PKTBUFSRX];/* Receive packets		*/
 extern volatile uchar * NetRxPacket;		/* Current receive packet	*/
 extern int		NetRxPacketLen;		/* Current rx packet length	*/
 extern unsigned		NetIPID;		/* IP ID (counting)		*/
 extern uchar		NetBcastAddr[6];	/* Ethernet boardcast address	*/
 extern uchar		NetEtherNullAddr[6];
 #define VLAN_NONE	4095			/* untagged			*/
 #define VLAN_IDMASK	0x0fff			/* mask of valid vlan id	*/
 extern ushort		NetOurVLAN;		/* Our VLAN			*/
 extern ushort		NetOurNativeVLAN;	/* Our Native VLAN		*/
 extern uchar		NetCDPAddr[6];		/* Ethernet CDP address		*/
 extern ushort		CDPNativeVLAN;		/* CDP returned native VLAN	*/
 extern ushort		CDPApplianceVLAN;	/* CDP returned appliance VLAN	*/
 extern int		NetState;		/* Network loop state		*/
 #define NETLOOP_CONTINUE	1
 #define NETLOOP_RESTART		2
 #define NETLOOP_SUCCESS		3
 #define NETLOOP_FAIL		4
 #ifdef CONFIG_NET_MULTI
 extern int		NetRestartWrap;		/* Tried all network devices	*/
 #endif
 typedef enum { BOOTP, RARP, ARP, TFTP, DHCP, PING, DNS, NFS, CDP, NETCONS, SNTP } proto_t;
 /* from net/net.c */
 extern char	BootFile[128];			/* Boot File name		*/
 #if defined(CONFIG_CMD_DNS)
 extern char *NetDNSResolve;		/* The host to resolve  */
 extern char *NetDNSenvvar;		/* the env var to put the ip into */
 #endif
 #if defined(CONFIG_CMD_PING)
 extern IPaddr_t	NetPingIP;			/* the ip address to ping		*/
 #endif
 #if defined(CONFIG_CMD_CDP)
 /* when CDP completes these hold the return values */
 extern ushort CDPNativeVLAN;
 extern ushort CDPApplianceVLAN;
 #endif
 #if defined(CONFIG_CMD_SNTP)
 extern IPaddr_t	NetNtpServerIP;			/* the ip address to NTP	*/
 extern int NetTimeOffset;			/* offset time from UTC		*/
 #endif
 /* Initialize the network adapter */
 extern int	NetLoop(proto_t);
 /* Shutdown adapters and cleanup */
 extern void	NetStop(void);
 /* Load failed.	 Start again. */
 extern void	NetStartAgain(void);
 /* Get size of the ethernet header when we send */
 extern int	NetEthHdrSize(void);
 /* Set ethernet header; returns the size of the header */
 extern int	NetSetEther(volatile uchar *, uchar *, uint);
 /* Set IP header */
 extern void	NetSetIP(volatile uchar *, IPaddr_t, int, int, int);
 /* Checksum */
 extern int	NetCksumOk(uchar *, int);	/* Return true if cksum OK	*/
 extern uint	NetCksum(uchar *, int);		/* Calculate the checksum	*/
 /* Set callbacks */
 extern void	NetSetHandler(rxhand_f *);	/* Set RX packet handler	*/
 extern void	NetSetTimeout(ulong, thand_f *);/* Set timeout handler		*/
 /* Transmit "NetTxPacket" */
 extern void	NetSendPacket(volatile uchar *, int);
 /* Transmit UDP packet, performing ARP request if needed */
 extern int	NetSendUDPPacket(uchar *ether, IPaddr_t dest, int dport, int sport, int len);
 /* Processes a received packet */
 extern void	NetReceive(volatile uchar *, int);
 /*
  * The following functions are a bit ugly, but necessary to deal with
  * alignment restrictions on ARM.
  *
  * We're using inline functions, which had the smallest memory
  * footprint in our tests.
  */
 /* return IP *in network byteorder* */
 static inline IPaddr_t NetReadIP(volatile void *from)
 {
 	IPaddr_t ip;
 	memcpy((void*)&ip, (void*)from, sizeof(ip));
 	return ip;
 }
 /* return ulong *in network byteorder* */
 static inline ulong NetReadLong(ulong *from)
 {
 	ulong l;
 	memcpy((void*)&l, (void*)from, sizeof(l));
 	return l;
 }
 /* write IP *in network byteorder* */
 static inline void NetWriteIP(void *to, IPaddr_t ip)
 {
 	memcpy(to, (void*)&ip, sizeof(ip));
 }
 /* copy IP */
 static inline void NetCopyIP(volatile void *to, void *from)
 {
 	memcpy((void*)to, from, sizeof(IPaddr_t));
 }
 /* copy ulong */
 static inline void NetCopyLong(ulong *to, ulong *from)
 {
 	memcpy((void*)to, (void*)from, sizeof(ulong));
 }
 /**
  * is_zero_ether_addr - Determine if give Ethernet address is all zeros.
  * @addr: Pointer to a six-byte array containing the Ethernet address
  *
  * Return true if the address is all zeroes.
  */
 static inline int is_zero_ether_addr(const u8 *addr)
 {
 	return !(addr[0] | addr[1] | addr[2] | addr[3] | addr[4] | addr[5]);
 }
 /**
  * is_multicast_ether_addr - Determine if the Ethernet address is a multicast.
  * @addr: Pointer to a six-byte array containing the Ethernet address
  *
  * Return true if the address is a multicast address.
  * By definition the broadcast address is also a multicast address.
  */
 static inline int is_multicast_ether_addr(const u8 *addr)
 {
 	return (0x01 & addr[0]);
 }
 /**
  * is_valid_ether_addr - Determine if the given Ethernet address is valid
  * @addr: Pointer to a six-byte array containing the Ethernet address
  *
  * Check that the Ethernet address (MAC) is not 00:00:00:00:00:00, is not
  * a multicast address, and is not FF:FF:FF:FF:FF:FF.
  *
  * Return true if the address is valid.
  */
 static inline int is_valid_ether_addr(const u8 * addr)
 {
 	/* FF:FF:FF:FF:FF:FF is a multicast address so we don't need to
 	 * explicitly check for it here. */
 	return !is_multicast_ether_addr(addr) && !is_zero_ether_addr(addr);
 }
 /* Convert an IP address to a string */
 extern void	ip_to_string (IPaddr_t x, char *s);
 /* Convert a string to ip address */
 extern IPaddr_t string_to_ip(char *s);
 /* Convert a VLAN id to a string */
 extern void	VLAN_to_string (ushort x, char *s);
 /* Convert a string to a vlan id */
 extern ushort string_to_VLAN(char *s);
 /* read a VLAN id from an environment variable */
 extern ushort getenv_VLAN(char *);
 /* copy a filename (allow for "..." notation, limit length) */
 extern void	copy_filename (char *dst, char *src, int size);
 /* get a random source port */
 extern unsigned int random_port(void);
 /**********************************************************************/
 #endif /* __NET_H__ */

 /*
  * (C) Copyright 2001-2010
  * 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>
 #include <command.h>
 #include <net.h>
 #include <miiphy.h>
 void eth_parse_enetaddr(const char *addr, uchar *enetaddr)
 {
 	char *end;
 	int i;
 	for (i = 0; i < 6; ++i) {
 		enetaddr[i] = addr ? simple_strtoul(addr, &end, 16) : 0;
 		if (addr)
 			addr = (*end) ? end + 1 : end;
 	}
 }
 int eth_getenv_enetaddr(char *name, uchar *enetaddr)
 {
 	eth_parse_enetaddr(getenv(name), enetaddr);
 	return is_valid_ether_addr(enetaddr);
 }
 int eth_setenv_enetaddr(char *name, const uchar *enetaddr)
 {
 	char buf[20];
 	sprintf(buf, "%pM", enetaddr);
 	return setenv(name, buf);
 }
 int eth_getenv_enetaddr_by_index(int index, uchar *enetaddr)
 {
 	char enetvar[32];
 	sprintf(enetvar, index ? "eth%daddr" : "ethaddr", index);
 	return eth_getenv_enetaddr(enetvar, enetaddr);
 }
+static int eth_mac_skip(int index)
+{
+	char enetvar[15];
+	char *skip_state;
+	sprintf(enetvar, index ? "eth%dmacskip" : "ethmacskip", index);
+	return ((skip_state = getenv(enetvar)) != NULL);
+}
 #ifdef CONFIG_NET_MULTI
 /*
  * CPU and board-specific Ethernet initializations.  Aliased function
  * signals caller to move on
  */
 static int __def_eth_init(bd_t *bis)
 {
 	return -1;
 }
 int cpu_eth_init(bd_t *bis) __attribute__((weak, alias("__def_eth_init")));
 int board_eth_init(bd_t *bis) __attribute__((weak, alias("__def_eth_init")));
 extern int mv6436x_eth_initialize(bd_t *);
 extern int mv6446x_eth_initialize(bd_t *);
 #ifdef CONFIG_API
 extern void (*push_packet)(volatile void *, int);
 static struct {
 	uchar data[PKTSIZE];
 	int length;
 } eth_rcv_bufs[PKTBUFSRX];
 static unsigned int eth_rcv_current = 0, eth_rcv_last = 0;
 #endif
 static struct eth_device *eth_devices, *eth_current;
 struct eth_device *eth_get_dev(void)
 {
 	return eth_current;
 }
 struct eth_device *eth_get_dev_by_name(char *devname)
 {
 	struct eth_device *dev, *target_dev;
 	if (!eth_devices)
 		return NULL;
 	dev = eth_devices;
 	target_dev = NULL;
 	do {
 		if (strcmp(devname, dev->name) == 0) {
 			target_dev = dev;
 			break;
 		}
 		dev = dev->next;
 	} while (dev != eth_devices);
 	return target_dev;
 }
 struct eth_device *eth_get_dev_by_index(int index)
 {
 	struct eth_device *dev, *target_dev;
 	int idx = 0;
 	if (!eth_devices)
 		return NULL;
 	dev = eth_devices;
 	target_dev = NULL;
 	do {
 		if (idx == index) {
 			target_dev = dev;
 			break;
 		}
 		dev = dev->next;
 		idx++;
 	} while (dev != eth_devices);
 	return target_dev;
 }
 int eth_get_dev_index (void)
 {
 	struct eth_device *dev;
 	int num = 0;
 	if (!eth_devices) {
 		return (-1);
 	}
 	for (dev = eth_devices; dev; dev = dev->next) {
 		if (dev == eth_current)
 			break;
 		++num;
 	}
 	if (dev) {
 		return (num);
 	}
 	return (0);
 }
 int eth_register(struct eth_device* dev)
 {
 	struct eth_device *d;
 	if (!eth_devices) {
 		eth_current = eth_devices = dev;
 #ifdef CONFIG_NET_MULTI
 		/* update current ethernet name */
 		{
 			char *act = getenv("ethact");
 			if (act == NULL || strcmp(act, eth_current->name) != 0)
 				setenv("ethact", eth_current->name);
 		}
 #endif
 	} else {
 		for (d=eth_devices; d->next!=eth_devices; d=d->next)
 			;
 		d->next = dev;
 	}
 	dev->state = ETH_STATE_INIT;
 	dev->next  = eth_devices;
 	return 0;
 }
 int eth_initialize(bd_t *bis)
 {
 	unsigned char env_enetaddr[6];
 	int eth_number = 0;
 	eth_devices = NULL;
 	eth_current = NULL;
 	show_boot_progress (64);
 #if defined(CONFIG_MII) || defined(CONFIG_CMD_MII)
 	miiphy_init();
 #endif
 	/* Try board-specific initialization first.  If it fails or isn't
 	 * present, try the cpu-specific initialization */
 	if (board_eth_init(bis) < 0)
 		cpu_eth_init(bis);
 #if defined(CONFIG_DB64360) || defined(CONFIG_CPCI750)
 	mv6436x_eth_initialize(bis);
 #endif
 #if defined(CONFIG_DB64460) || defined(CONFIG_P3Mx)
 	mv6446x_eth_initialize(bis);
 #endif
 	if (!eth_devices) {
 		puts ("No ethernet found.\n");
 		show_boot_progress (-64);
 	} else {
 		struct eth_device *dev = eth_devices;
 		char *ethprime = getenv ("ethprime");
 		show_boot_progress (65);
 		do {
 			if (eth_number)
 				puts (", ");
 			printf("%s", dev->name);
 			if (ethprime && strcmp (dev->name, ethprime) == 0) {
 				eth_current = dev;
 				puts (" [PRIME]");
 			}
 			eth_getenv_enetaddr_by_index(eth_number, env_enetaddr);
 			if (memcmp(env_enetaddr, "\0\0\0\0\0\0", 6)) {
 				if (memcmp(dev->enetaddr, "\0\0\0\0\0\0", 6) &&
 				    memcmp(dev->enetaddr, env_enetaddr, 6))
 				{
 					printf ("\nWarning: %s MAC addresses don't match:\n",
 						dev->name);
 					printf ("Address in SROM is         %pM\n",
 						dev->enetaddr);
 					printf ("Address in environment is  %pM\n",
 						env_enetaddr);
 				}
 				memcpy(dev->enetaddr, env_enetaddr, 6);
+			}
+			if (dev->write_hwaddr &&
+				!eth_mac_skip(eth_number) &&
+				is_valid_ether_addr(dev->enetaddr)) {
+				dev->write_hwaddr(dev);
 			}
 			eth_number++;
 			dev = dev->next;
 		} while(dev != eth_devices);
 #ifdef CONFIG_NET_MULTI
 		/* update current ethernet name */
 		if (eth_current) {
 			char *act = getenv("ethact");
 			if (act == NULL || strcmp(act, eth_current->name) != 0)
 				setenv("ethact", eth_current->name);
 		} else
 			setenv("ethact", NULL);
 #endif
 		putc ('\n');
 	}
 	return eth_number;
 }
 #ifdef CONFIG_MCAST_TFTP
 /* Multicast.
  * mcast_addr: multicast ipaddr from which multicast Mac is made
  * join: 1=join, 0=leave.
  */
 int eth_mcast_join( IPaddr_t mcast_ip, u8 join)
 {
  u8 mcast_mac[6];
 	if (!eth_current || !eth_current->mcast)
 		return -1;
 	mcast_mac[5] = htonl(mcast_ip) & 0xff;
 	mcast_mac[4] = (htonl(mcast_ip)>>8) & 0xff;
 	mcast_mac[3] = (htonl(mcast_ip)>>16) & 0x7f;
 	mcast_mac[2] = 0x5e;
 	mcast_mac[1] = 0x0;
 	mcast_mac[0] = 0x1;
 	return eth_current->mcast(eth_current, mcast_mac, join);
 }
 /* the 'way' for ethernet-CRC-32. Spliced in from Linux lib/crc32.c
  * and this is the ethernet-crc method needed for TSEC -- and perhaps
  * some other adapter -- hash tables
  */
 #define CRCPOLY_LE 0xedb88320
 u32 ether_crc (size_t len, unsigned char const *p)
 {
 	int i;
 	u32 crc;
 	crc = ~0;
 	while (len--) {
 		crc ^= *p++;
 		for (i = 0; i < 8; i++)
 			crc = (crc >> 1) ^ ((crc & 1) ? CRCPOLY_LE : 0);
 	}
 	/* an reverse the bits, cuz of way they arrive -- last-first */
 	crc = (crc >> 16) | (crc << 16);
 	crc = (crc >> 8 & 0x00ff00ff) | (crc << 8 & 0xff00ff00);
 	crc = (crc >> 4 & 0x0f0f0f0f) | (crc << 4 & 0xf0f0f0f0);
 	crc = (crc >> 2 & 0x33333333) | (crc << 2 & 0xcccccccc);
 	crc = (crc >> 1 & 0x55555555) | (crc << 1 & 0xaaaaaaaa);
 	return crc;
 }
 #endif
 int eth_init(bd_t *bis)
 {
 	int eth_number;
 	struct eth_device *old_current, *dev;
 	if (!eth_current) {
 		puts ("No ethernet found.\n");
 		return -1;
 	}
 	/* Sync environment with network devices */
 	eth_number = 0;
 	dev = eth_devices;
 	do {
 		uchar env_enetaddr[6];
 		if (eth_getenv_enetaddr_by_index(eth_number, env_enetaddr))
 			memcpy(dev->enetaddr, env_enetaddr, 6);
 		++eth_number;
 		dev = dev->next;
 	} while (dev != eth_devices);
 	old_current = eth_current;
 	do {
 		debug("Trying %s\n", eth_current->name);
 		if (eth_current->init(eth_current,bis) >= 0) {
 			eth_current->state = ETH_STATE_ACTIVE;
 			return 0;
 		}
 		debug("FAIL\n");
 		eth_try_another(0);
 	} while (old_current != eth_current);
 	return -1;
 }
 void eth_halt(void)
 {
 	if (!eth_current)
 		return;
 	eth_current->halt(eth_current);
 	eth_current->state = ETH_STATE_PASSIVE;
 }
 int eth_send(volatile void *packet, int length)
 {
 	if (!eth_current)
 		return -1;
 	return eth_current->send(eth_current, packet, length);
 }
 int eth_rx(void)
 {
 	if (!eth_current)
 		return -1;
 	return eth_current->recv(eth_current);
 }
 #ifdef CONFIG_API
 static void eth_save_packet(volatile void *packet, int length)
 {
 	volatile char *p = packet;
 	int i;
 	if ((eth_rcv_last+1) % PKTBUFSRX == eth_rcv_current)
 		return;
 	if (PKTSIZE < length)
 		return;
 	for (i = 0; i < length; i++)
 		eth_rcv_bufs[eth_rcv_last].data[i] = p[i];
 	eth_rcv_bufs[eth_rcv_last].length = length;
 	eth_rcv_last = (eth_rcv_last + 1) % PKTBUFSRX;
 }
 int eth_receive(volatile void *packet, int length)
 {
 	volatile char *p = packet;
 	void *pp = push_packet;
 	int i;
 	if (eth_rcv_current == eth_rcv_last) {
 		push_packet = eth_save_packet;
 		eth_rx();
 		push_packet = pp;
 		if (eth_rcv_current == eth_rcv_last)
 			return -1;
 	}
 	if (length < eth_rcv_bufs[eth_rcv_current].length)
 		return -1;
 	length = eth_rcv_bufs[eth_rcv_current].length;
 	for (i = 0; i < length; i++)
 		p[i] = eth_rcv_bufs[eth_rcv_current].data[i];
 	eth_rcv_current = (eth_rcv_current + 1) % PKTBUFSRX;
 	return length;
 }
 #endif /* CONFIG_API */
 void eth_try_another(int first_restart)
 {
 	static struct eth_device *first_failed = NULL;
 	char *ethrotate;
 	/*
 	 * Do not rotate between network interfaces when
 	 * 'ethrotate' variable is set to 'no'.
 	 */
 	if (((ethrotate = getenv ("ethrotate")) != NULL) &&
 	    (strcmp(ethrotate, "no") == 0))
 		return;
 	if (!eth_current)
 		return;
 	if (first_restart) {
 		first_failed = eth_current;
 	}
 	eth_current = eth_current->next;
 #ifdef CONFIG_NET_MULTI
 	/* update current ethernet name */
 	{
 		char *act = getenv("ethact");
 		if (act == NULL || strcmp(act, eth_current->name) != 0)
 			setenv("ethact", eth_current->name);
 	}
 #endif
 	if (first_failed == eth_current) {
 		NetRestartWrap = 1;
 	}
 }
 #ifdef CONFIG_NET_MULTI
 void eth_set_current(void)
 {
 	static char *act = NULL;
 	static int  env_changed_id = 0;
 	struct eth_device* old_current;
 	int	env_id;
 	if (!eth_current)	/* XXX no current */
 		return;
 	env_id = get_env_id();
 	if ((act == NULL) || (env_changed_id != env_id)) {
 		act = getenv("ethact");
 		env_changed_id = env_id;
 	}
 	if (act != NULL) {
 		old_current = eth_current;
 		do {
 			if (strcmp(eth_current->name, act) == 0)
 				return;
 			eth_current = eth_current->next;
 		} while (old_current != eth_current);
 	}
 	setenv("ethact", eth_current->name);
 }
 #endif
 char *eth_get_name (void)
 {
 	return (eth_current ? eth_current->name : "unknown");
 }
 #else /* !CONFIG_NET_MULTI */
 #warning Ethernet driver is deprecated.  Please update to use CONFIG_NET_MULTI
 extern int at91rm9200_miiphy_initialize(bd_t *bis);
 extern int mcf52x2_miiphy_initialize(bd_t *bis);
 extern int ns7520_miiphy_initialize(bd_t *bis);
 int eth_initialize(bd_t *bis)
 {
 #if defined(CONFIG_MII) || defined(CONFIG_CMD_MII)
 	miiphy_init();
 #endif
 #if defined(CONFIG_AT91RM9200)
 	at91rm9200_miiphy_initialize(bis);
 #endif
 #if defined(CONFIG_MCF52x2)
 	mcf52x2_miiphy_initialize(bis);
 #endif
 #if defined(CONFIG_DRIVER_NS7520_ETHERNET)
 	ns7520_miiphy_initialize(bis);
 #endif
 	return 0;
 }
 #endif