mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Oliver Pinter" <oliver.pntr@gmail.com>
To: "Dave Airlie" <airlied@skynet.ie>
Cc: torvalds@linux-foundation.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	stable@kernel.org
Subject: Re: [git pull] drm radeon fix for 2.6.27-rc1
Date: Tue, 15 Jul 2008 12:56:48 +0200	[thread overview]
Message-ID: <6101e8c40807150356t5ecb0885ud0249eff1ec03e77@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.0.82.0807150702330.6038@skynet.skynet.ie>

Hi David,

it affects stable (2.6.26) too?

On 7/15/08, Dave Airlie <airlied@skynet.ie> wrote:
>
> Hi Linus,
>
> Please pull the 'drm-fixes' branch from
> ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git
> drm-fixes
>
> It appears we have a PAT incomPATibility, with how the radeon driver was
> mapping some VRAM.
>
> Dave.
>
>  drivers/gpu/drm/drm_memory.c       |    5 +++++
>  drivers/gpu/drm/radeon/radeon_cp.c |    2 +-
>  include/drm/drmP.h                 |    1 +
>  3 files changed, 7 insertions(+), 1 deletions(-)
>
> commit 242e3df80b8d25ed681c278512df0993725f25dd
> Author: Dave Airlie <airlied@linux.ie>
> Date:   Tue Jul 15 15:48:05 2008 +1000
>
>     drm/radeon: fixup issue with radeon and PAT support.
>
>     With new userspace libpciaccess we can get a conflicting mapping
>     on the PCIE GART table in the video RAM. Always try and map it _wc.
>
>     Signed-off-by: Dave Airlie <airlied@redhat.com>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


-- 
Thanks,
Oliver

  reply	other threads:[~2008-07-15 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  6:03 Dave Airlie
2008-07-15 10:56 ` Oliver Pinter [this message]
2008-07-15 11:56   ` Dave Airlie

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=6101e8c40807150356t5ecb0885ud0249eff1ec03e77@mail.gmail.com \
    --to=oliver.pntr@gmail.com \
    --cc=airlied@skynet.ie \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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®