All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Dave Airlie <airlied@gmail.com>, Alex Deucher <alexdeucher@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/radeon: Ignore RADEON_GEM_GTT_WC on 32-bit x86
Date: Wed, 03 Dec 2014 16:47:55 +0900	[thread overview]
Message-ID: <547EC02B.5080601@daenzer.net> (raw)
In-Reply-To: <CAPM=9tyxdACPHYLJcSuhrZszL=4tar4Gn9F_Bj0UiA8xfgY1Hw@mail.gmail.com>

On 03.12.2014 08:28, Dave Airlie wrote:
> On 1 December 2014 at 14:02, Alex Deucher <alexdeucher@gmail.com> wrote:
>> On Thu, Nov 27, 2014 at 4:00 AM, Michel Dänzer <michel@daenzer.net> wrote:
>>> From: Michel Dänzer <michel.daenzer@amd.com>
>>>
>>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=84627
>>> Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
>>
>> Applied to my -fixes tree.
>
> Btw while I'm okay to merge this as a workaround, I'd really like to know
> if someone cares enough to fix it.
>
> Because there is no reason WC mappings should be broken on 32-bit,
> and its quite likely they are broken on 64-bit too just more subtly.

It would definitely be nice to get to the bottom of this, but I'm not 
sure where to dig next. Given that basically the same 64-bit kernel 
seems to fail when built on a 32-bit host but works fine when built on a 
64-bit host, I suspect it might be something from the host toolchain / 
build environment leaking into the resulting binaries somehow.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2014-12-03  7:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  9:00 [PATCH] drm/radeon: Ignore RADEON_GEM_GTT_WC on 32-bit x86 Michel Dänzer
2014-12-01  4:02 ` Alex Deucher
2014-12-02 23:28   ` Dave Airlie
2014-12-03  7:47     ` Michel Dänzer [this message]

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=547EC02B.5080601@daenzer.net \
    --to=michel@daenzer.net \
    --cc=airlied@gmail.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.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.