Searched hist:"77 eea280744c8adf040d5949c677d905a70d3cf3" (Results 1 – 3 of 3) sorted by relevance
| /rk3399_rockchip-uboot/board/isee/igep00x0/ |
| H A D | Makefile | 77eea280744c8adf040d5949c677d905a70d3cf3 Thu Dec 27 01:35:56 UTC 2012 Javier Martinez Canillas <javier@dowhile0.org> 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>
|
| H A D | igep00x0.h | 77eea280744c8adf040d5949c677d905a70d3cf3 Thu Dec 27 01:35:56 UTC 2012 Javier Martinez Canillas <javier@dowhile0.org> 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>
|
| H A D | igep00x0.c | 77eea280744c8adf040d5949c677d905a70d3cf3 Thu Dec 27 01:35:56 UTC 2012 Javier Martinez Canillas <javier@dowhile0.org> 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>
|