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 23:34:38 +1100 [thread overview]
Message-ID: <24082.1009110878@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 23 Dec 2001 13:28:24 BST." <20011223132824.A23866@caldera.de>
On Sun, 23 Dec 2001 13:28:24 +0100,
Christoph Hellwig <hch@caldera.de> wrote:
>On Sun, Dec 23, 2001 at 10:48:36AM +1100, Keith Owens wrote:
>> Only if the new version cleans up the horrible drm 4.0 Makefile.
>
>I am more than happy to do so. In fact I already did in 2.4.0-test times
>and got flamed by the drm crew..
Don't see why. drm 4.1 uses a sane makefile, apart from a few dead
references to $(lib) which do nothing. The separate copy of drmlib in
each object was meant to allow migration to a new format, it obviously
failed in its task, drm 4.1 is not compatible. From drm 4.0 Makefile
# The upside is that if the DRM support library ever becomes insufficient
# for new families of cards, a new library can be implemented for those new
# cards without impacting the drivers for the old cards. This is significant,
# because testing architectural changes to old cards may be impossible, and
# may delay the implementation of a better architecture. We've traded slight
# memory waste (in the dual-head case) for greatly improved long-term
# maintainability.
Nice definition of long term, it survived 0 new releases. Kill it.
next prev parent reply other threads:[~2001-12-23 12:35 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
2001-12-23 12:28 ` Christoph Hellwig
2001-12-23 12:34 ` Keith Owens [this message]
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=24082.1009110878@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®