X-Git-Url: https://git.kernelconcepts.de/?p=karo-tx-uboot.git;a=blobdiff_plain;f=README;h=d70d2af29a5f33dca99fe2f09396e5c6c8a7a9f1;hp=6a011cb38c87dca00c02ea72bdcdc38d384fa34f;hb=4d75a504d00e65253229e1d1b798a7c37041f078;hpb=43d9616cffb4a130e1620e3e33fc9bc1bcabe399 diff --git a/README b/README index 6a011cb38c..d70d2af29a 100644 --- a/README +++ b/README @@ -145,6 +145,8 @@ Directory Hierarchy: - cpu/mpc8260 Files specific to Motorola MPC8260 CPU - cpu/ppc4xx Files specific to IBM 4xx CPUs +- board/LEOX/ Files specific to boards manufactured by The LEOX team +- board/LEOX/elpt860 Files specific to ELPT860 boards - board/RPXClassic Files specific to RPXClassic boards - board/RPXlite Files specific to RPXlite boards @@ -338,7 +340,7 @@ The following options need to be configured: CONFIG_GTH, CONFIG_RPXClassic, CONFIG_rsdproto, CONFIG_IAD210, CONFIG_RPXlite, CONFIG_sbc8260, CONFIG_EBONY, CONFIG_sacsng, CONFIG_FPS860L, - CONFIG_V37 + CONFIG_V37, CONFIG_ELPT860 ARM based boards: ----------------- @@ -624,7 +626,9 @@ The following options need to be configured: CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx CONFIG_RTC_PCF8563 - use Philips PCF8563 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_DS164x - use Dallas DS164x RTC - Timestamp Support: @@ -897,6 +901,17 @@ The following options need to be configured: controls the rate of data transfer. The data rate thus is 1 / (I2C_DELAY * 4). + CFG_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. + - SPI Support: CONFIG_SPI Enables SPI driver (so far only tested with @@ -1043,7 +1058,7 @@ The following options need to be configured: If CONFIG_ENV_OVERWRITE is #defined in your config file, the write protection for vendor parameters is - completely disabled. Anybody can change or delte + completely disabled. Anybody can change or delete these parameters. Alternatively, if you #define _both_ CONFIG_ETHADDR @@ -1704,6 +1719,7 @@ configurations; the following names are supported: FPS850L_config Sandpoint8240_config sbc8260_config GENIETV_config TQM823L_config PIP405_config GEN860T_config EBONY_config FPS860L_config + ELPT860_config Note: for some board special configuration names may exist; check if additional information is available from the board vendor; for