From: Keith Owens <kaos@ocs.com.au>
To: Christoph Hellwig <hch@caldera.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DRM 4.0 support for kernel 2.4.17
Date: Sun, 23 Dec 2001 10:48:36 +1100 [thread overview]
Message-ID: <17474.1009064916@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 22 Dec 2001 20:36:02 BST." <20011222203602.A15825@caldera.de>
On Sat, 22 Dec 2001 20:36:02 +0100,
Christoph Hellwig <hch@caldera.de> wrote:
>I've placed a patch to allow optional drm 4.0 support in kernel 2.4.17
>at:
>
>ftp.kernel.org/pub/linux/kernel/people/hch/patches/v2.4/2.4.17/linux-2.4.17-drm40.patch.bz2
>
>Please report any fedback to me. It has been submitted to Marcelo for inclusion
>into 2.4.18.
Only if the new version cleans up the horrible drm 4.0 Makefile. The
separate copy of drmlib in each object and/or the kernel goes against
the rest of the kbuild design, needs an ugly makefile and AFAICT nobody
needs the separate copy of drmlib. I will not maintain that crud into
kbuild 2.5.
drivers/char/drm-4.0/Makefile below uses the standard kbuild design.
One copy of drmlib-4.0 which is built into the kernel if any drm 4.0
drivers are built in, otherwise drmlib-4.0 is a module if there are any
drm 4.0 modules. Totally untested.
Some of the code in $(drmlib-4.0-objs) will need EXPORT_SYMBOLS to work
when drm 4.0 drivers are compiled as modules.
#
# Makefile for the drm device driver. This driver provides support for
# the Direct Rendering Infrastructure (DRI) in XFree86 4.x.
#
O_TARGET := drm.o
export-objs := gamma_drv.o tdfx_drv.o r128_drv.o ffb_drv.o mga_drv.o \
i810_drv.o
list-multi := gamma.o tdfx.o r128.o ffb.o mga.o i810.o drmlib-4.0
gamma-objs := gamma_drv.o gamma_dma.o
tdfx-objs := tdfx_drv.o tdfx_context.o
r128-objs := r128_drv.o r128_cce.o r128_context.o r128_bufs.o r128_state.o
ffb-objs := ffb_drv.o ffb_context.o
mga-objs := mga_drv.o mga_dma.o mga_context.o mga_bufs.o mga_state.o
i810-objs := i810_drv.o i810_dma.o i810_context.o i810_bufs.o
radeon-objs := radeon_drv.o radeon_cp.o radeon_context.o radeon_bufs.o radeon_state.o
drmlib-4.0-objs := init.o memory.o proc.o auth.o context.o drawable.o bufs.o \
lists.o lock.o ioctl.o fops.o vm.o dma.o ctxbitmap.o
ifneq ($(subst n,,$(CONFIG_AGP)),)
drmlib-4.0-objs += agpsupport.o
endif
obj-$(CONFIG_DRM40_GAMMA) += gamma.o drmlib-4.0.o
obj-$(CONFIG_DRM40_TDFX) += tdfx.o drmlib-4.0.o
obj-$(CONFIG_DRM40_R128) += r128.o drmlib-4.0.o
obj-$(CONFIG_DRM40_RADEON)+= radeon.o drmlib-4.0.o
obj-$(CONFIG_DRM40_FFB) += ffb.o drmlib-4.0.o
obj-$(CONFIG_DRM40_MGA) += mga.o drmlib-4.0.o
obj-$(CONFIG_DRM40_I810) += i810.o drmlib-4.0.o
include $(TOPDIR)/Rules.make
drmlib-4.0.o: $(drmlib-4.0-objs)
$(LD) -r -o $@ $^
gamma.o: $(gamma-objs)
$(LD) -r -o $@ $^
tdfx.o: $(tdfx-objs)
$(LD) -r -o $@ $^
mga.o: $(mga-objs)
$(LD) -r -o $@ $^
i810.o: $(i810-objs)
$(LD) -r -o $@ $^
r128.o: $(r128-objs)
$(LD) -r -o $@ $^
radeon.o: $(radeon-objs)
$(LD) -r -o $@ $^
ffb.o: $(ffb-objs)
$(LD) -r -o $@ $^
next prev parent reply other threads:[~2001-12-22 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 19:36 Christoph Hellwig
2001-12-22 23:48 ` Keith Owens [this message]
2001-12-23 12:28 ` Christoph Hellwig
2001-12-23 12:34 ` Keith Owens
2001-12-23 12:54 ` Christoph Hellwig
2001-12-23 13:34 ` Keith Owens
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=17474.1009064916@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®