[BUG] Linux-2.4.12 does not build (Sparc-64 & DRM)

[BUG] Linux-2.4.12 does not build (Sparc-64 & DRM)

[Leif Sawyer]

Just a quick bug report -- I haven't had time
to track this one down yet.

Enabling DRM/DRI support on a Sparc64 kernel
with Creator/Creator3D graphics does not build
correctly:

ld -m elf64_sparc -T arch/sparc64/vmlinux.lds arch/sparc64/kernel/head.o
arch/sparc64/kernel/init_task.o init/main.o init/version.o \
	--start-group \
	arch/sparc64/kernel/kernel.o arch/sparc64/mm/mm.o kernel/kernel.o
mm/mm.o fs/fs.o ipc/ipc.o arch/sparc64/math-emu/math-emu.o \
	 drivers/char/char.o drivers/block/block.o drivers/misc/misc.o
drivers/net/net.o drivers/media/media.o drivers/char/drm/drm.o
drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o
drivers/sbus/sbus_all.o drivers/video/video.o drivers/input/inputdrv.o \
	net/network.o \
	/usr/src/linux/lib/lib.a /usr/src/linux/lib/lib.a
/usr/src/linux/arch/sparc64/prom/promlib.a
/usr/src/linux/arch/sparc64/lib/lib.a \
	--end-group \
	-o vmlinux
drivers/char/drm/drm.o: In function `ffb_vm_shm_nopage':
drivers/char/drm/drm.o(.text+0x4ba8): undefined reference to
`virt_to_bus_not_defined_use_pci_map'
drivers/char/drm/drm.o: In function `ffb_vm_dma_nopage':
drivers/char/drm/drm.o(.text+0x4e4c): undefined reference to
`virt_to_bus_not_defined_use_pci_map'
make: *** [vmlinux] Error 1

This makes correctly on 2.4.10 and earlier.

Re: [BUG] Linux-2.4.12 does not build (Sparc-64 & DRM)

[David S. Miller]

   From: Leif Sawyer <lsawyer@gci.com>
   Date: Thu, 11 Oct 2001 15:52:01 -0800

   Just a quick bug report -- I haven't had time
   to track this one down yet.
   
   Enabling DRM/DRI support on a Sparc64 kernel
   with Creator/Creator3D graphics does not build
   correctly:
   
I've tried to contact the DRM folks (specifically Jeff Hartman) on
many occaisions (at least 3 times) about the fact that using
virt_to_bus/bus_to_virt generically in the DRM broke the build on
several platforms.

As stated often, virt_to_bus/bus_to_virt are deprecated interfaces.
Yet, it is use explicitly in the debugging macros.

Not only has it not been fixed, all of my queries to Jeff have fallen
on deaf ears and I get no response whatsoever.

Franks a lot,
David S. Miller
davem@redhat.com