mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Matthew Reppert <arashi@sacredchao.net>
Cc: dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	airlied@linux.ie
Subject: Re: G33 graphics broken after 2.6.23-rc6
Date: Sat, 6 Oct 2007 01:34:10 -0400	[thread overview]
Message-ID: <20071006053410.GB14767@fattire.cabal.ca> (raw)
In-Reply-To: <20071006044221.GA14767@fattire.cabal.ca>

On Sat, Oct 06, 2007 at 12:42:21AM -0400, Kyle McMartin wrote:
> commit f443675affe3f16dd428e46f0f7fd3f4d703eeab
>     intel_agp: fix stolen mem range on G33
>     G33 GTT stolen memory is below graphics data stolen memory and be seperate,
>     so don't subtract it in stolen mem counting.
>     

Found it, without this corresponding change to xf86-video-intel, this
breaks utterly:

commit 2a8592f2ebcba86b1127aa889155d58a3dc186ca
Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
Date:   Wed Sep 5 14:52:56 2007 +0800

    Fix G33 GTT stolen mem range
    
    G33 GTT table lives in seperate stolen mem with
    graphics data stolen mem.

I think this should be reverted for 2.6.23, it certainly doesn't seem to have
been appropriate for 2.6.23-rc6.

Cheers,
	Kyle M.

  reply	other threads:[~2007-10-06  5:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-06  0:20 Matthew Reppert
2007-10-06  4:42 ` Kyle McMartin
2007-10-06  5:34   ` Kyle McMartin [this message]
2007-10-06  5:42     ` Revert "intel_agp: fix stolen mem range on G33" Kyle McMartin
2007-10-06 10:41       ` Jiri Slaby
2007-10-06 15:59         ` Linus Torvalds
2007-10-06 19:29           ` Keith Packard
2007-10-07 10:05             ` Jiri Slaby
2007-10-07 12:17         ` Daniel Stone

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=20071006053410.GB14767@fattire.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=airlied@linux.ie \
    --cc=arashi@sacredchao.net \
    --cc=dri-devel@lists.sourceforge.net \
    --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®