On 23/07/2015 16:19, Nikita Kiryanov wrote:
U-Boot does not explicitly assign the display to an IPU interface. Instead, it
relies on the power-on default of DI0.
Since the kernel reassigns HDMI display to DI1, after a warm reset the HDMI
display no longer works in U-Boot.
Fix this by
On 07/26/2015 11:48 AM, Nikita Kiryanov wrote:
On Thu, Jul 23, 2015 at 08:54:25PM +0300, Nikolay Dimitrov wrote:
Hi Nikita,
On 07/23/2015 05:19 PM, Nikita Kiryanov wrote:
U-Boot does not explicitly assign the display to an IPU interface. Instead, it
relies on the power-on default of DI0.
On Thu, Jul 23, 2015 at 08:54:25PM +0300, Nikolay Dimitrov wrote:
Hi Nikita,
On 07/23/2015 05:19 PM, Nikita Kiryanov wrote:
U-Boot does not explicitly assign the display to an IPU interface. Instead,
it
relies on the power-on default of DI0.
Since the kernel reassigns HDMI display to
Hi Nikita,
On 07/23/15 17:19, Nikita Kiryanov wrote:
U-Boot does not explicitly assign the display to an IPU interface. Instead, it
relies on the power-on default of DI0.
Since the kernel reassigns HDMI display to DI1, after a warm reset the HDMI
display no longer works in U-Boot.
Fix
U-Boot does not explicitly assign the display to an IPU interface. Instead, it
relies on the power-on default of DI0.
Since the kernel reassigns HDMI display to DI1, after a warm reset the HDMI
display no longer works in U-Boot.
Fix this by explicitly assigning HDMI to IPU1 DI0 in U-Boot.
Cc:
Hi Nikita,
On 07/23/2015 05:19 PM, Nikita Kiryanov wrote:
U-Boot does not explicitly assign the display to an IPU interface. Instead, it
relies on the power-on default of DI0.
Since the kernel reassigns HDMI display to DI1, after a warm reset the HDMI
display no longer works in U-Boot.
Fix
6 matches
Mail list logo