Hi,
Le 16/08/2015 21:59, Misha Komarovskiy a écrit :
Hello,
Maybe we can disable only Exynos IOMMU in configs for now? Same way it
is disabled in current exynos_defconfig here
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/configs/exynos_defconfig?id=6562f3bd396ab6d2c9b455e95c67e33bab73bff5
As i understand it is broken for all exynos devices not only snow.
That is exactly what I would like to do since I read this thread:
https://lkml.org/lkml/2015/2/17/163
Before submitting the idea here, I wanted to check if disabling Exynos IOMMU in
config was enough.
I had only time to test the exynos_defconfig with openSUSE kernel and it was OK
(boot messages and login prompt displayed).
Guillaume
---
Best Regards,
Misha Komarovskiy
zombahatgmaildotcom
On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <[email protected]> wrote:
Am 23.07.2015 um 15:15 schrieb Andreas Färber <[email protected]>:
Am 23.07.2015 um 15:12 schrieb Alexander Graf:
On 07/23/15 14:43, Andreas Färber wrote:
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet:
Maybe some config options compiled as module (which?) and blacklisted
for chromebooks could be ok?
Maybe. Someone with a Chromebook needs to sit down and try. :)
Hrm, rather than disable it one way or another manually, couldn't we
just blacklist it inside the kernel? I doubt that we can load iommu as
module...
You mean as in patch the iommu probe code to check for "google,snow",
"google,spring", etc.?
For example - or remove the respective dt node. Or as a property to the IOMMU
dt node...
Alex
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
