From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111103] [Patch] to compile amdgpu-dkms 19.20 on debian stretch & buster
Date: Thu, 11 Jul 2019 06:55:55 +0000 [thread overview]
Message-ID: <bug-111103-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1343 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111103
Bug ID: 111103
Summary: [Patch] to compile amdgpu-dkms 19.20 on debian stretch
& buster
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu-pro
Assignee: dri-devel@lists.freedesktop.org
Reporter: fabstz-it@yahoo.fr
Created attachment 144757
--> https://bugs.freedesktop.org/attachment.cgi?id=144757&action=edit
[Patch] to compile amdgpu-dkms 19.20 on debian stretch & buster
Hello,
Please find attached a patch so that one can compile the amdgpu-dkms 19.20
driver toward kernel 4.19 on debian stretch (with stretch-backports), and also
on debian buster (version 10) which runs linux-4.19
The patch is made of:
- a change to the Makefile so that it can compile well on debian and find the
kernel version (using [make kernelversion])
- a few changes to the code in file amdgpu_mn.c
Appearently, in 19.20 there are still some problems to compile towards 4.19
because some #ifdef don't seem correct because "mmu_notifier_range" doesn't
exist in 4.19.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2967 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-07-11 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 6:55 bugzilla-daemon [this message]
2019-07-29 20:00 ` [Bug 111103] [Patch] to compile amdgpu-dkms 19.20 on debian stretch & buster bugzilla-daemon
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=bug-111103-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--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.