From: Christoph Hellwig <hch@caldera.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Keith Owens <kaos@ocs.com.au>,
linux-ia64@linuxia64.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-ia64] Re: Linux 2.4.17-pre6 drm-4.0
Date: Sat, 8 Dec 2001 13:31:56 +0100 [thread overview]
Message-ID: <20011208133156.A22531@caldera.de> (raw)
In-Reply-To: <4494.1007767210@ocs3.intra.ocs.com.au> <E16Cflf-00019F-00@the-village.bc.nu>
In-Reply-To: <E16Cflf-00019F-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Dec 08, 2001 at 11:35:43AM +0000
On Sat, Dec 08, 2001 at 11:35:43AM +0000, Alan Cox wrote:
> > to get rid of them asap. The SiS direct render is only for drm 4.1 so
> > now is a good time to question if 4.0 is still required.
>
> That argument doesnt fly. The 4.0 DRM is the only working GMX renderer..
So what DRM can build out of tree easily - e.g. the Caldera LTP
(3.1 early access) had a DRM package built completly out of tree.
David, would you remove drm-4.0 from the ia64 patch if I'd do the work
again and package an up-to-date and ia64-capable drm 4.0 out-of-tree?
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-12-08 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 23:20 Linux 2.4.17-pre6 drm-4.0 Keith Owens
2001-12-07 23:27 ` Robert Love
2001-12-07 23:32 ` Keith Owens
2001-12-07 23:42 ` Robert Love
2001-12-08 0:12 ` Barry K. Nathan
2001-12-08 1:03 ` Eyal Lebedinsky
2001-12-08 11:35 ` Alan Cox
2001-12-07 23:38 ` [Linux-ia64] " David Mosberger
2001-12-08 0:25 ` Keith Owens
2001-12-08 11:35 ` Alan Cox
2001-12-08 12:31 ` Christoph Hellwig [this message]
2001-12-08 15:34 ` [Linux-ia64] " Alan Cox
2001-12-09 16:42 ` Christoph Hellwig
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=20011208133156.A22531@caldera.de \
--to=hch@caldera.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaos@ocs.com.au \
--cc=linux-ia64@linuxia64.org \
--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