All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@caldera.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Linux 2.4.17-pre6 drm-4.0
Date: Sat, 08 Dec 2001 12:31:56 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805662@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805654@msgid-missing>

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.


  parent reply	other threads:[~2001-12-08 12:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 23:27 [Linux-ia64] Re: Linux 2.4.17-pre6 drm-4.0 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 11:35 ` Alan Cox
2001-12-08 11:35 ` Alan Cox
2001-12-08 12:31 ` Christoph Hellwig [this message]
2001-12-08 15:34 ` Alan Cox
2001-12-09 16:42 ` Christoph Hellwig
2001-12-14 19:13 ` David Mosberger
2001-12-15 10:19 ` Christoph Hellwig
2001-12-17 16:14 ` Marcelo Tosatti
2001-12-17 22:46 ` Juan Quintela
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07 23:20 Keith Owens
2001-12-08 11:35 ` Alan Cox
2001-12-08 12:31   ` [Linux-ia64] " Christoph Hellwig
2001-12-08 15:34     ` 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=marc-linux-ia64-105590698805662@msgid-missing \
    --to=hch@caldera.de \
    --cc=linux-ia64@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.