* Re: [BUG(?)] Kconfig warning when selecting ARCH_OMAP1
[not found] <CA+B2V-+GLEiRcJqVA4=2GX5iY1cWjDd4vWdumD_9ALpxuspg9Q@mail.gmail.com>
@ 2014-09-08 15:35 ` Tony Lindgren
0 siblings, 0 replies; 2+ messages in thread
From: Tony Lindgren @ 2014-09-08 15:35 UTC (permalink / raw)
To: Andreas Ruprecht; +Cc: Russell King, linux-omap
* Andreas Ruprecht <rupran@einserver.de> [140907 11:39]:
> Hi all,
>
> I found the following inconsistency in the Kconfig dependencies for
> ARCH_OMAP1 during my research, and as I don't know the exact requirements
> for the OMAP configuration (and how the dependencies could be restructured
> to get rid of the warning), I figured you might be able to help me out.
>
> When selecting ARCH_OMAP1 as the system type, Kconfig issues a warning:
> "warning: (ARCH_OMAP1) selects ARCH_OMAP which has unmet direct
> dependencies (ARCH_MULTI_V6 || ARCH_MULTI_V7)"
>
> When I investigated this further, I found the reason to be as follows:
> - ARCH_OMAP1 selects ARCH_OMAP
> - ARCH_OMAP depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
> - ARCH_MULTI_V{6,7} depend on ARCH_MULTIPLATFORM
> - ARCH_MULTIPLATFORM is in the same choice (System Type -> ARM system type)
> as ARCH_OMAP1, and thus the two can never be enabled at the same time.
>
> Might there be an easy way to resolve this inconsistency by restructuring
> the Kconfig dependencies?
Probably to move the config ARCH_OMAP to plat-omap/Kconfig. Suggested fix
being discussed in the "[PATCH] ARM: omap: fix Kconfig warning" thread FYI.
Regards,
Tony
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [BUG(?)] Kconfig warning when selecting ARCH_OMAP1
@ 2014-09-07 18:42 Andreas Ruprecht
0 siblings, 0 replies; 2+ messages in thread
From: Andreas Ruprecht @ 2014-09-07 18:42 UTC (permalink / raw)
To: linux-omap
Hi all,
I found the following inconsistency in the Kconfig dependencies for
ARCH_OMAP1 during my research, and as I don't know the exact
requirements for the OMAP configuration (and how the dependencies
could be restructured to get rid of the warning), I figured you might
be able to help me out.
When selecting ARCH_OMAP1 as the system type, Kconfig issues a warning:
"warning: (ARCH_OMAP1) selects ARCH_OMAP which has unmet direct
dependencies (ARCH_MULTI_V6 || ARCH_MULTI_V7)"
When I investigated this further, I found the reason to be as follows:
- ARCH_OMAP1 selects ARCH_OMAP
- ARCH_OMAP depends on ARCH_MULTI_V6 || ARCH_MULTI_V7
- ARCH_MULTI_V{6,7} depend on ARCH_MULTIPLATFORM
- ARCH_MULTIPLATFORM is in the same choice (System Type -> ARM system
type) as ARCH_OMAP1, and thus the two can never be enabled at the same
time.
Might there be an easy way to resolve this inconsistency by
restructuring the Kconfig dependencies?
Regards,
Andreas
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-09-08 15:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CA+B2V-+GLEiRcJqVA4=2GX5iY1cWjDd4vWdumD_9ALpxuspg9Q@mail.gmail.com>
2014-09-08 15:35 ` [BUG(?)] Kconfig warning when selecting ARCH_OMAP1 Tony Lindgren
2014-09-07 18:42 Andreas Ruprecht
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).