Hello Krzysztof, On 03/28/2016 01:14 AM, Javier Martinez Canillas wrote: > > On 03/28/2016 12:28 AM, Krzysztof Kozlowski wrote: >> On 25.03.2016 12:15, Javier Martinez Canillas wrote: >>>> >>>> How about doing the same for multi_v7? >>>> >>> >>> I didn't consider multi_v7 because media drivers aren't necessary for >>> booting >>> the boards and so it could increase build times for not real benefits in >>> most >>> machines. But I can enable it in multi_v7 as a follow-up if you think that >>> it >>> makes sense there too. >> >> I consider use cases of multi_v7 the same as exynos (except the >> difference in policy: use always modules). This means that if it makes >> sense to enable some media drivers on exynos (for build coverage, boot >> testing and real usage) then it makes sense to do the same for multi_v7. >> > > Ok, thanks a lot for your suggestion. I'll post a patch for multi_v7 then. > >> In ideal future we would move entirely from exynos-specific image to one >> common image for testing: the multi_v7. It would make things simpler. >> >> Best regards, >> Krzysztof >> >
Tobias mentioned on IRC that the exynos4-is driver conflicts with the Exynos DRM driver since both exynos_drm_fimc and exynos-fimc-is use the FIMC block. So I think we should just discard $SUBJECT and instead add a Kconfig check to not allow both drivers to be built as suggested by Tobias. Like is the case for the other components (G2D, GSC, Mixer, etc). Best regards, -- Javier Martinez Canillas Open Source Group Samsung Research America
