From: Thierry Reding <thierry.reding@gmail.com>
To: "Christian König" <deathsimple@vodafone.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/amdgpu: enable DKMS build
Date: Tue, 24 Nov 2015 11:33:18 +0100 [thread overview]
Message-ID: <20151124103318.GE6149@ulmo> (raw)
In-Reply-To: <56543707.9090909@vodafone.de>
[-- Attachment #1.1: Type: text/plain, Size: 2019 bytes --]
On Tue, Nov 24, 2015 at 11:08:07AM +0100, Christian König wrote:
> On 24.11.2015 10:36, Thierry Reding wrote:
> >On Tue, Nov 24, 2015 at 09:59:09AM +0100, Daniel Vetter wrote:
> >>On Tue, Nov 24, 2015 at 04:55:19PM +0800, Jammy Zhou wrote:
> >>>This series enable the DKMS build of amdgpu driver.
> >>For the curious: What's DKMS?
> >I believe in this context it's "Dynamic Kernel Module Support":
> >
> > https://wiki.debian.org/KernelDKMS
>
> Yeah, correct.
>
> >
> >I'm somewhat surprised that one would have to do something special to
> >the kernel build system to "enable" such a build. But perhaps this is
> >completely unrelated.
>
> I'm a bit torn apart on this. On the one hand I'm not sure if we have
> drivers upstream explicitly supporting this as well?
It's been a long time since I last used Debian and worked with DKMS, but
wasn't the original idea for DKMS to be used on out-of-tree modules? Why
the need to build in-tree modules with DKMS? Shouldn't that be done as
part of a regular linux-image/linux-modules build?
> On the other hand it's just the Makefiles which need to be written in a way
> which makes them relocatable. E.g. no absolute path like
> drivers/gpu/drm/amd/... in them and that's a good idea anyway.
To clarify, I'm not opposing the change, I just thought it weird that
the kernel build had to be modified to support an external build system.
But in general it seems to be rare that drivers even need to specific
additional ccflags, which would explain my surprise.
There's precedent for using $(src), see drivers/gpu/drm/Makefile, so I
don't see any reason why this would be objectionable.
> Maybe just changing the commit message to "don't use absolute paths in the
> makefiles" would be sufficient?
I don't mind the mention of DKMS either, but perhaps extending the
commit message with a few words about what DKMS is and why the change
needs to happen (i.e. $(src) used for relocation) would be a good idea
anyway.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-11-24 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 8:55 [PATCH 0/3] drm/amdgpu: enable DKMS build Jammy Zhou
2015-11-24 8:55 ` [PATCH 1/3] drm/amdgpu: use $(src) in Makefile Jammy Zhou
2015-11-30 20:36 ` Alex Deucher
2015-11-24 8:55 ` [PATCH 2/3] drm/amd/acp: " Jammy Zhou
2015-11-24 8:55 ` [PATCH 3/3] drm/amd/powerplay: enable dkms build Jammy Zhou
2015-11-24 8:59 ` [PATCH 0/3] drm/amdgpu: enable DKMS build Daniel Vetter
2015-11-24 9:36 ` Thierry Reding
2015-11-24 10:08 ` Christian König
2015-11-24 10:33 ` Thierry Reding [this message]
2015-11-24 10:34 ` Daniel Vetter
2015-11-25 5:21 ` Zhou, Jammy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151124103318.GE6149@ulmo \
--to=thierry.reding@gmail.com \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.