OMAP3: use a single board file for IGEP devices
authorJavier Martinez Canillas <javier@dowhile0.org>
Thu, 27 Dec 2012 01:35:56 +0000 (01:35 +0000)
committerTom Rini <trini@ti.com>
Thu, 7 Feb 2013 15:36:25 +0000 (10:36 -0500)
commit77eea280744c8adf040d5949c677d905a70d3cf3
treea0507c86a87d1f9607545dc0860856f303d2d3eb
parent5bedf884a8508f1b2f5b8f74e67d987a81ff05ed
OMAP3: use a single board file for IGEP devices

Even when the IGEPv2 board and the IGEP Computer-on-Module
are different from a form factor point of view, they are
very similar in the fact that share many components and how
they are wired.

So, it is possible (and better) to have a single board file
for both devices and just use the CONFIG_MACH_TYPE to make
a differentiation between each board when needed.

This change avoids code duplication by removing 298 lines of
code and makes future maintenance easier.

Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Acked-by: Igor Grinberg <grinberg@compulab.co.il>
board/isee/igep0020/Makefile [deleted file]
board/isee/igep0020/igep0020.c [deleted file]
board/isee/igep0020/igep0020.h [deleted file]
board/isee/igep0030/Makefile [deleted file]
board/isee/igep0030/igep0030.c [deleted file]
board/isee/igep0030/igep0030.h [deleted file]
board/isee/igep00x0/Makefile [new file with mode: 0644]
board/isee/igep00x0/igep00x0.c [new file with mode: 0644]
board/isee/igep00x0/igep00x0.h [new file with mode: 0644]
boards.cfg
include/configs/igep00x0.h