[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150703123246.GA29257@ulmo.nvidia.com>
Date: Fri, 3 Jul 2015 14:32:48 +0200
From: Thierry Reding <thierry.reding@...il.com>
To: Daniel Vetter <daniel@...ll.ch>
Cc: Benjamin Gaignard <benjamin.gaignard@...aro.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Linux Fbdev development list <linux-fbdev@...r.kernel.org>,
Tomi Valkeinen <tomi.valkeinen@...com>,
Thierry Reding <treding@...dia.com>
Subject: Re: [RFC 1/6] drm: Add top level Kconfig option for DRM fbdev
emulation
On Tue, Jun 30, 2015 at 11:04:45AM +0200, Daniel Vetter wrote:
> On Tue, Jun 30, 2015 at 10:31 AM, Benjamin Gaignard
> <benjamin.gaignard@...aro.org> wrote:
> > I think that what have been done by Rob with module_param is also a good idea:
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/msm/msm_drv.c?id=e90dfec78ec288d6c89a7b508a5c5d4ae8b7f934
> >
> > Can you mix compilation flag and module param ?
>
> Hm, the point of the kconfig is to not require all the legacy baggage
> from fbdev. But I guess a module option could be added later on too.
> bochs has it too.
I think the option would primarily be useful for testing. I've often
needed to test modesetting code without fbdev getting in the way and the
only way to currently do that is by recompiling with legacy fbdev
disabled. The option would allow an fbdev-enabled kernel to be used but
disable the fbdev code if desired.
Thierry
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists