exynos boot falures in linux-next
Kevin Hilman
khilman at kernel.org
Wed Nov 19 09:01:21 PST 2014
On Mon, Nov 17, 2014 at 7:49 PM, Kevin Hilman <khilman at kernel.org> wrote:
> Javier Martinez Canillas <javier.martinez at collabora.co.uk> writes:
>
>> Hello Kevin,
>>
>> On 11/17/2014 11:24 PM, Kevin Hilman wrote:
>>>
>>> As might have been expected, reverting the change that enables the
>>> DRM/display options in exynos_defconfig fixes the problem.
>>>
>>> Kevin
>>>
>>
>> I'm sorry for causing a boot failure but when I first posted that patch,
>> the Exynos DRM driver was working correctly (at least on the Exynos boards
>> I've access to)
>
> Yeah, I tested it at the time as well, so I know it was working.
>
>> so it seems the regression was introduced while the patch
>> was posted but not yet picked.
>>
>> I'm not sure what is the correct step in this case but I'm OK with
>> reverting the patch until the Exynos DRM driver bug is fixed.
>
> I didn't have time to dig, but I'd rather someone track down the DRM
> problem and fix that, since it was known to be working. I'm guessing
> it's something simple that can be fixed before the merge window opens.
OK, so this DRM problem is turning out to be non-trivial, so I think
the defconfig patch should be reverted until the DRM issue is sorted
out.
Otherwise, we risk having boot failures in linux-next which may be
hiding other problems.
Kevin
More information about the linux-arm-kernel
mailing list