-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recent commits break multi-platform v6+v7 builds #2173
Comments
|
Understood. I'll look for a solution tomorrow. |
|
Can you build okay now? |
|
This does build now, but since both CONFIG_CPU_CACHE_V7 and CONFIG_CPU_CACHE_V6 are defined, the v7 assembly will be run on a v6 platform. Since these are separate versions of the function, I'd assume that a v6 core is not intended to run v7_dma_inv_range. If you want to export these functions, you might look to the implementation of other exported functions to see how to handle this safely, particularly if you ever intend for this modification to be submitted upstream. |
|
This will not be upstreamed (certainly in current form). |
|
Offhand, there are the CPU ID functions in arch/arm/kernel/setup.c that are used for /proc/cpuinfo. |
|
How about something like this? I have to admit, when we start talking assembly its out of my wheelhouse, but this seems logical to me. Pretty much all android kernels use these APIs this way. However, there's about 3 changes there that can, and probably should, be split into separate commits. |
The commits 3aaac88 and c2def2a by @popcornmix break building the kernel in a multi-platform v6+v7 configuration, which has worked for the entire 4.9 release:
giving the following errors, which are obvious from looking at the second commit listed above:
The text was updated successfully, but these errors were encountered: