linux-kernel - Re: DRM_TEGRA not buildable as a module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131118091042.GB13322@ulmo.nvidia.com>
Date:	Mon, 18 Nov 2013 10:10:42 +0100
From:	Thierry Reding <treding@...dia.com>
To:	Josh Boyer <jwboyer@...oraproject.org>
CC:	Terje Bergstrom <tbergstrom@...dia.com>,
	Dave Airlie <airlied@...hat.com>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: DRM_TEGRA not buildable as a module

On Sat, Nov 16, 2013 at 03:25:09PM +0100, Josh Boyer wrote:
> Hi All,
> 
> The commit below seems to have made the Tegra DRM driver a bool option
> instead of tristate:
> 
> commit dee8268f8fb218c9e9b604a40f7dbdd395e910f9
> Author: Thierry Reding <treding@...dia.com>
> Date:   Wed Oct 9 10:32:49 2013 +0200
> 
>     drm/tegra: Move driver to DRM tree
> 
>     In order to make subsystem-wide changes easier, move the Tegra DRM
>     driver back into the DRM tree.
> 
>     Signed-off-by: Thierry Reding <treding@...dia.com>
> 
> That means you can't build the driver as a module.  Was this intended?
>  The changelog doesn't mention anything about that and the existing
> help text on the option seems to imply it should be buildable as a
> module.

This was intended yes. And it wasn't really a change at all, since prior
to the commit you mention above the DRM driver was always built into the
host1x driver. That's why I didn't think it necessary to mention it in
the commit message.

I have some patches queued for 3.14 to enable the driver to be built as
a module. There are some dependencies such as symbols that need to be
exported so that the modules can be linked, so it'll require some amount
of coordination to make that work out within one release cycle, but I'm
hopeful that we can do it.

Thierry

Content of type "application/pgp-signature" skipped