linux-kernel - Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 04 Mar 2015 09:50:14 +0100
From:	Marek Szyprowski <m.szyprowski@...sung.com>
To:	Kevin Hilman <khilman@...nel.org>,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>
Cc:	Kukjin Kim <kgene@...nel.org>, Olof Johansson <olof@...om.net>,
	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	Andreas Faerber <afaerber@...e.de>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	tyler.baker@...aro.org, Andrzej Hajda <a.hajda@...sung.com>,
	Inki Dae <daeinki@...il.com>
Subject: Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support

Hello,

On 2015-03-03 21:36, Kevin Hilman wrote:
> Javier Martinez Canillas <javier.martinez@...labora.co.uk> writes:
>
>> Enabling Exynos DRM IOMMU support for Exynos is currently broken and
>> causes a BUG on exynos-iommu driver. This was not an issue since the
>> options was disabled in exynos_defconfig but after commit 8dcc14f82f06
>> ("drm/exynos: IOMMU support should not be selectable by user"), it is
>> selected if EXYNOS_IOMMU is enabled which is in exynos_defconfig.
>>
>> So a kernel built using exynos_defconfig after the mentioned commit
>> fails to boot [0]. Disable IOMMU support in Exynos defconfig until
>> things get sorted out.
> So some other exynos boards started failing in next-20150303[1], and
> appear are DRM failures.
>
> Interestingly, (re)enabling CONFIG_EXYNOS_IOMMU for these cause things to
> work again.  Even more intersting, with IOMMU enabled, peach-pi is
>
> I'm starting to think it's the DRM driver that needs to be disabled
> until it actually gets some testing, rathre than disabling IOMMU.

Well, this only shows that broken patch has been merged to exynos-drm-next
kernel tree. I think that we should keep Exynos DRM enabled and give Exynos
DRM developers a chance to fix their stuff and then test their stuff.

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/