summaryrefslogtreecommitdiff
path: root/board/RPXlite
diff options
context:
space:
mode:
authorThomas Chou <thomas@wytron.com.tw>2010-06-16 14:39:30 +0800
committerScott McNutt <smcnutt@psyent.com>2010-07-12 11:40:12 -0400
commita3c09f66b2b84e98333c317ffb24a95f88ee5a10 (patch)
tree26cec31aa0f6e1ccdd7f7fa639eeb8ff866d25c7 /board/RPXlite
parent551265f0df9e7a1c6098ff4eec435218423f365b (diff)
downloadu-boot-imx-a3c09f66b2b84e98333c317ffb24a95f88ee5a10.zip
u-boot-imx-a3c09f66b2b84e98333c317ffb24a95f88ee5a10.tar.gz
u-boot-imx-a3c09f66b2b84e98333c317ffb24a95f88ee5a10.tar.bz2
nios2: remove EP1C20, EP1S10, EP1S40 boards
The example configuration files of nios2-generic board can generated binary to run on the EP1C20, EP1S10, and EP1S40 boards. So the three boards can be removed. With nios2-generic approach, the fpga parameter header file can be generated from hardware designs using tools. Porting u-boot for nios2 boards is simplified. Vendors can supply their fpga parameter file or patches to add a new nios2-generic board instance. There is no need to include other boards support for nios2 in the u-boot mainline. Signed-off-by: Thomas Chou <thomas@wytron.com.tw> Signed-off-by: Scott McNutt <smcnutt@psyent.com>
Diffstat (limited to 'board/RPXlite')
0 files changed, 0 insertions, 0 deletions