On Mon, Jul 13, 2015 at 03:59:25PM +0530, Archit Taneja wrote:
>
>
> On 07/13/2015 01:37 PM, Daniel Vetter wrote:
> >On Mon, Jul 13, 2015 at 12:07:56PM +0530, Archit Taneja wrote:
> >>DRM drivers using drm_fb_helpers still call some fbdev core functions.
> >>This makes the driver depend on CONFIG
On 07/13/2015 01:37 PM, Daniel Vetter wrote:
> On Mon, Jul 13, 2015 at 12:07:56PM +0530, Archit Taneja wrote:
>> DRM drivers using drm_fb_helpers still call some fbdev core functions.
>> This makes the driver depend on CONFIG_FB, resulting in complicated
>> Kconfig options, and preventing us from
DRM drivers using drm_fb_helpers still call some fbdev core functions.
This makes the driver depend on CONFIG_FB, resulting in complicated
Kconfig options, and preventing us from creating a top level drm config
option to enable/disable FBDEV emulation.
Create new drm_fb_helper functions that repla
On Mon, Jul 13, 2015 at 2:37 AM, Archit Taneja
wrote:
> DRM drivers using drm_fb_helpers still call some fbdev core functions.
> This makes the driver depend on CONFIG_FB, resulting in complicated
> Kconfig options, and preventing us from creating a top level drm config
> option to enable/disable
On Mon, Jul 13, 2015 at 12:07:56PM +0530, Archit Taneja wrote:
> DRM drivers using drm_fb_helpers still call some fbdev core functions.
> This makes the driver depend on CONFIG_FB, resulting in complicated
> Kconfig options, and preventing us from creating a top level drm config
> option to enable/
