Home
last modified time | relevance | path

Searched hist:"9 a0f4004caa057ba227292e544b67ca3d03ffd89" (Results 1 – 7 of 7) sorted by relevance

/rk3399_rockchip-uboot/include/configs/
H A Dti_armv7_omap.h9a0f4004caa057ba227292e544b67ca3d03ffd89 Wed Jul 22 23:05:41 UTC 2015 Nishanth Menon <nm@ti.com> configs: split ti_armv7_common into a omap generic header

TI armv7 based SoCs are based on two architectures - one based on OMAP
generation architecture and others based on Keystone architecture.

Many of the options are architecture specific, however a lot are common
with v7 architecture. So, step 1 will be to move out OMAP specific stuff
from ti_armv7_common into a ti_armv7_omap.h header which is then used
by all the relevant architecture headers.

Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
H A Dti_omap3_common.h9a0f4004caa057ba227292e544b67ca3d03ffd89 Wed Jul 22 23:05:41 UTC 2015 Nishanth Menon <nm@ti.com> configs: split ti_armv7_common into a omap generic header

TI armv7 based SoCs are based on two architectures - one based on OMAP
generation architecture and others based on Keystone architecture.

Many of the options are architecture specific, however a lot are common
with v7 architecture. So, step 1 will be to move out OMAP specific stuff
from ti_armv7_common into a ti_armv7_omap.h header which is then used
by all the relevant architecture headers.

Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
H A Dti_am335x_common.h9a0f4004caa057ba227292e544b67ca3d03ffd89 Wed Jul 22 23:05:41 UTC 2015 Nishanth Menon <nm@ti.com> configs: split ti_armv7_common into a omap generic header

TI armv7 based SoCs are based on two architectures - one based on OMAP
generation architecture and others based on Keystone architecture.

Many of the options are architecture specific, however a lot are common
with v7 architecture. So, step 1 will be to move out OMAP specific stuff
from ti_armv7_common into a ti_armv7_omap.h header which is then used
by all the relevant architecture headers.

Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
H A Dti_omap4_common.h9a0f4004caa057ba227292e544b67ca3d03ffd89 Wed Jul 22 23:05:41 UTC 2015 Nishanth Menon <nm@ti.com> configs: split ti_armv7_common into a omap generic header

TI armv7 based SoCs are based on two architectures - one based on OMAP
generation architecture and others based on Keystone architecture.

Many of the options are architecture specific, however a lot are common
with v7 architecture. So, step 1 will be to move out OMAP specific stuff
from ti_armv7_common into a ti_armv7_omap.h header which is then used
by all the relevant architecture headers.

Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
H A Dti_omap5_common.h9a0f4004caa057ba227292e544b67ca3d03ffd89 Wed Jul 22 23:05:41 UTC 2015 Nishanth Menon <nm@ti.com> configs: split ti_armv7_common into a omap generic header

TI armv7 based SoCs are based on two architectures - one based on OMAP
generation architecture and others based on Keystone architecture.

Many of the options are architecture specific, however a lot are common
with v7 architecture. So, step 1 will be to move out OMAP specific stuff
from ti_armv7_common into a ti_armv7_omap.h header which is then used
by all the relevant architecture headers.

Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
H A Dti_armv7_common.h9a0f4004caa057ba227292e544b67ca3d03ffd89 Wed Jul 22 23:05:41 UTC 2015 Nishanth Menon <nm@ti.com> configs: split ti_armv7_common into a omap generic header

TI armv7 based SoCs are based on two architectures - one based on OMAP
generation architecture and others based on Keystone architecture.

Many of the options are architecture specific, however a lot are common
with v7 architecture. So, step 1 will be to move out OMAP specific stuff
from ti_armv7_common into a ti_armv7_omap.h header which is then used
by all the relevant architecture headers.

Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
H A Dam43xx_evm.h9a0f4004caa057ba227292e544b67ca3d03ffd89 Wed Jul 22 23:05:41 UTC 2015 Nishanth Menon <nm@ti.com> configs: split ti_armv7_common into a omap generic header

TI armv7 based SoCs are based on two architectures - one based on OMAP
generation architecture and others based on Keystone architecture.

Many of the options are architecture specific, however a lot are common
with v7 architecture. So, step 1 will be to move out OMAP specific stuff
from ti_armv7_common into a ti_armv7_omap.h header which is then used
by all the relevant architecture headers.

Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>