From: Christoph Hellwig <hch@caldera.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DRM 4.0 support for kernel 2.4.17
Date: Sun, 23 Dec 2001 13:54:17 +0100 [thread overview]
Message-ID: <20011223135417.A24968@caldera.de> (raw)
In-Reply-To: <20011222203602.A15825@caldera.de> <17474.1009064916@ocs3.intra.ocs.com.au>
In-Reply-To: <17474.1009064916@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Sun, Dec 23, 2001 at 10:48:36AM +1100
On Sun, Dec 23, 2001 at 10:48:36AM +1100, Keith Owens wrote:
> 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.
ftp.kernel.org/pub/linux/kernel/people/hch/patches/v2.4/2.4.17/linux-2.4.17-drm40-1.patch.bz2
Is a version that is (build-) tested and very similar to your versions, based
on my 2.4.0-test Makefile.
> Some of the code in $(drmlib-4.0-objs) will need EXPORT_SYMBOLS to work
> when drm 4.0 drivers are compiled as modules.
I don't consider that a good use of drm 4.0. If someone wants to fix it
anyway he/she should do it. I don't think this compatiblity code needs
so much attention.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-12-23 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 19:36 [PATCH] DRM 4.0 support for kernel 2.4.17 Christoph Hellwig
2001-12-22 23:48 ` Keith Owens
2001-12-23 12:28 ` Christoph Hellwig
2001-12-23 12:34 ` Keith Owens
2001-12-23 12:54 ` Christoph Hellwig [this message]
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=20011223135417.A24968@caldera.de \
--to=hch@caldera.de \
--cc=kaos@ocs.com.au \
--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 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.