dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82455] Failed to allocate virtual address for buffer
Date: Tue, 19 Aug 2014 14:16:38 +0000	[thread overview]
Message-ID: <bug-82455-502-amf0W4zxZb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82455-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 780 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=82455

--- Comment #15 from Christian König <deathsimple@vodafone.de> ---
(In reply to comment #14)
> (In reply to comment #13)
> > (In reply to comment #12)
> > > Don't we need to endian-swap the whole IB for big endian?
> > 
> > That depends on which engine you use. IIRC the CP, DMA and UVD till SI can
> > do endian swap in hardware, but the support got removed for DMA with CIK.
> 
> SDMA on CIK can still do endian swaps for IBs.

Than that was another engine, anyway you guys should test without the DMA
initially to rule out any problems.

Basically first try to get the most simple use case working, e.g. X with just
glxgears.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1764 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-08-19 14:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11  9:16 [Bug 82455] New: Failed to allocate virtual address for buffer bugzilla-daemon
2014-08-11  9:22 ` [Bug 82455] " bugzilla-daemon
2014-08-11  9:36 ` bugzilla-daemon
2014-08-11 11:47 ` bugzilla-daemon
2014-08-11 11:55 ` bugzilla-daemon
2014-08-12  1:20 ` bugzilla-daemon
2014-08-12  1:22 ` bugzilla-daemon
2014-08-12  1:26 ` bugzilla-daemon
2014-08-12  1:33 ` bugzilla-daemon
2014-08-14  9:07 ` bugzilla-daemon
2014-08-15  2:29 ` bugzilla-daemon
2014-08-15  7:17 ` bugzilla-daemon
2014-08-19  9:23 ` bugzilla-daemon
2014-08-19  9:59 ` bugzilla-daemon
2014-08-19 10:01 ` bugzilla-daemon
2014-08-19 13:37 ` bugzilla-daemon
2014-08-19 14:16 ` bugzilla-daemon [this message]
2014-08-20  1:54 ` bugzilla-daemon
2014-08-20  2:43 ` bugzilla-daemon
2014-08-20  3:38 ` bugzilla-daemon
2014-08-20 13:23 ` bugzilla-daemon
2014-08-21  9:35 ` bugzilla-daemon
2014-08-27  3:36 ` bugzilla-daemon
2014-08-27  6:26 ` bugzilla-daemon
2014-08-27  8:12 ` bugzilla-daemon
2014-08-27  8:15 ` bugzilla-daemon
2014-08-27  8:19 ` bugzilla-daemon
2014-08-27  9:13 ` bugzilla-daemon
2014-08-28  2:46 ` bugzilla-daemon
2014-08-28  3:31 ` bugzilla-daemon
2014-08-28 13:58 ` bugzilla-daemon
2014-08-29  1:18 ` bugzilla-daemon
2014-08-29  1:19 ` bugzilla-daemon
2014-09-01  6:43 ` bugzilla-daemon
2014-09-15  8:25 ` bugzilla-daemon
2014-09-17  6:57 ` bugzilla-daemon
2015-08-02 10:53 ` [Bug 82455] [SPARC] " bugzilla-daemon
2018-08-31  6:17 ` bugzilla-daemon

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=bug-82455-502-amf0W4zxZb@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).