On 2015-08-07 00:54, Luca Boccassi wrote:
Yes, undefining CONFIG_XEN and CONFIG_XEN_DOM0 works on 3.16 too, as you
suggested. The patch header has been updated as you asked as well.
Thanks for the tip!
Good. Can you backport this to branches/340?
Do you have a contact in the kernel team to
On 2015-08-06 01:50, Luca Boccassi wrote:
Works on 4.0 and 4.1, but not on 3.16 due to this error:
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'xen_start_info'
/usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.modpost:90:
recipe for target '__modpost' failed
On Thu, 2015-08-06 at 10:34 +0200, Andreas Beckmann wrote:
On 2015-08-06 01:50, Luca Boccassi wrote:
Works on 4.0 and 4.1, but not on 3.16 due to this error:
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'xen_start_info'
On Mon, 2015-08-03 at 11:58 +0200, Andreas Beckmann wrote:
On 2015-08-03 02:21, Luca Boccassi wrote:
I already addressed 2 problems and committed to the SVN repo (patch
nv-linux.h and enable dma_ops for arm in
conftest.h, but the final problem is that the armhf kernel ships with
On Mon, 2015-08-03 at 11:58 +0200, Andreas Beckmann wrote:
On 2015-08-03 02:21, Luca Boccassi wrote:
Testing the build of nvidia-kernel-dkms in an armhf chroot (via qemu static
binaries) results in build failure
for kernels 3.16 (jessie) and 4.0 (sid). Cannot test 4.1 as the armhf build
On 2015-08-03 02:21, Luca Boccassi wrote:
Testing the build of nvidia-kernel-dkms in an armhf chroot (via qemu static
binaries) results in build failure
for kernels 3.16 (jessie) and 4.0 (sid). Cannot test 4.1 as the armhf build
of linux-kbuild-4.1 is missing.
Does any other of the armhf
Package: nvidia-kernel-dkms
Version: 352.30-0.4
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was
7 matches
Mail list logo
