On 06/13/2018 03:52 PM, Fabio Estevam wrote:
> On Wed, Jun 13, 2018 at 9:38 AM, Stefan Agner wrote:
>
>> It seems to me a rather extreme measure though, given we could fix the
>> situation rather easily.
>
> There are dtb's using the fbdev mxsfb driver like for example:
> arch/arm/boot/dts/imx28
On Wed, Jun 13, 2018 at 9:38 AM, Stefan Agner wrote:
> It seems to me a rather extreme measure though, given we could fix the
> situation rather easily.
There are dtb's using the fbdev mxsfb driver like for example:
arch/arm/boot/dts/imx28-evk.dts
If we kill the fbdev mxsfb driver then the disp
[adding Sascha and Bartlomiej]
On 13.06.2018 09:17, Marek Vasut wrote:
> On 06/13/2018 09:16 AM, Stefan Agner wrote:
>> On 13.06.2018 01:08, Marek Vasut wrote:
>>> On 06/12/2018 06:01 PM, Fabio Estevam wrote:
On Tue, Jun 12, 2018 at 11:35 AM, Stefan Agner wrote:
> There are two driv
On 06/12/2018 06:01 PM, Fabio Estevam wrote:
> On Tue, Jun 12, 2018 at 11:35 AM, Stefan Agner wrote:
>
>> There are two drivers for the LCDIF/MXSFB peripheral. If the DRM
>> and fbdev are compiled in, the registration of the second driver
>> fails:
>> mxs-dma 3300.dma-apbh: initialized
>>
On 06/13/2018 09:16 AM, Stefan Agner wrote:
> On 13.06.2018 01:08, Marek Vasut wrote:
>> On 06/12/2018 06:01 PM, Fabio Estevam wrote:
>>> On Tue, Jun 12, 2018 at 11:35 AM, Stefan Agner wrote:
>>>
There are two drivers for the LCDIF/MXSFB peripheral. If the DRM
and fbdev are compiled in,
On 13.06.2018 01:08, Marek Vasut wrote:
> On 06/12/2018 06:01 PM, Fabio Estevam wrote:
>> On Tue, Jun 12, 2018 at 11:35 AM, Stefan Agner wrote:
>>
>>> There are two drivers for the LCDIF/MXSFB peripheral. If the DRM
>>> and fbdev are compiled in, the registration of the second driver
>>> fails:
>>
On Tue, Jun 12, 2018 at 11:35 AM, Stefan Agner wrote:
> There are two drivers for the LCDIF/MXSFB peripheral. If the DRM
> and fbdev are compiled in, the registration of the second driver
> fails:
> mxs-dma 3300.dma-apbh: initialized
> mxsfb 3073.lcdif: 3073.lcdif supply lcd not f
