kernel i386 linux/highmem.h:34:2: error: implicit declaration of function 'PHYS_TO_DMAP'
i386 kernel compilation using latest master after
Date: Thu Aug 14 09:09:59 2014 +0200
drm/i915: Fix display corruption issues on Haswell
In file included from /usr/src/sys/dev/drm/i915/i915_gem_execbuffer.c:31:0:
/usr/src/sys/dev/drm/i915/../../../dev/drm/include/linux/highmem.h: In function 'kmap_atomic':
/usr/src/sys/dev/drm/i915/../../../dev/drm/include/linux/highmem.h:34:2: error: implicit declaration of function 'PHYS_TO_DMAP' [-Werror=implicit-function-declaration]
/usr/src/sys/dev/drm/i915/../../../dev/drm/include/linux/highmem.h:34:2: error: nested extern declaration of 'PHYS_TO_DMAP' [-Werror=nested-externs]
#2 Updated by davshao about 2 years ago
- File restore_i386_i915.diff added
The attached patch restores i915 drm functionality at least for an i386 Lenovo Ideapad with Intel 945 graphics. It also should have identical functionality for x86_64 machines. The patch has been tested for x86_64 Intel integrated graphics G45 and HD Graphics. Basically the kmap / kunmap functions for i386 only are replaced by the previously used sf_buf functions.
The patch is against
Date: Fri Aug 15 10:05:21 2014 -0700
kernel - Reduce ig4 receive errors
#3 Updated by ftigeot about 2 years ago
The whole point of using the kmap API is to reduce differences with Linux; I won't be reintroducing sf_buf usage.
Besides, the i386 architecture is now deprecated.
If you still want to use i386 hardware with DragonFly, you should consider moving to a stable 3.8.x release.