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@xxxxxxxxxx> 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
Attachment:
pgpCYJk4C218U.pgp
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
