Bug#756810: linux-image-3.16-rc6-armmp: HDMI on wandboard/cubox-i no longer works

2014-08-12 Thread Vagrant Cascadian
On 2014-08-11, Vagrant Cascadian wrote: I think this is caused by dropping CONFIG_DRM_IMX_IPUV3_CORE=m, which was moved out of staging into drivers/gpu/ipu-v3/Kconfig. And the configuration option was also renamed to CONFIG_IMX_IPUV3_CORE... I've tested that the following patch on a Cubox-i

Bug#756810: linux-image-3.16-rc6-armmp: HDMI on wandboard/cubox-i no longer works

2014-08-12 Thread maximilian attems
On Mon, Aug 11, 2014 at 11:43:15PM -0700, Vagrant Cascadian wrote: On 2014-08-11, Vagrant Cascadian wrote: I think this is caused by dropping CONFIG_DRM_IMX_IPUV3_CORE=m, which was moved out of staging into drivers/gpu/ipu-v3/Kconfig. And the configuration option was also renamed to

Bug#756810: linux-image-3.16-rc6-armmp: HDMI on wandboard/cubox-i no longer works

2014-08-11 Thread Vagrant Cascadian
Control: tags -1 patch On 2014-08-01, Vagrant Cascadian wrote: With linux-image-3.15-trunk-armmp 3.15.5-1~exp1 which included patches applied from upstream, HDMI video output worked for me on both the Cubox i4pro and Wandboard Quad. The console framebuffer showed output, X with fbdev

Bug#756810: linux-image-3.16-rc6-armmp: HDMI on wandboard/cubox-i no longer works

2014-08-01 Thread Vagrant Cascadian
Package: src:linux Version: 3.16~rc6-1~exp1 Severity: normal With linux-image-3.15-trunk-armmp 3.15.5-1~exp1 which included patches applied from upstream, HDMI video output worked for me on both the Cubox i4pro and Wandboard Quad. The console framebuffer showed output, X with fbdev worked... Now