From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83708] [vdpau,uvd] kernel oops, Unable to handle kernel paging request at virtual address
Date: Thu, 25 Sep 2014 07:26:35 +0000 [thread overview]
Message-ID: <bug-83708-502-aa41JztnWA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83708-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 876 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83708
--- Comment #17 from Christian König <deathsimple@vodafone.de> ---
(In reply to comment #16)
> (In reply to comment #15)
> > 1. I do not add cpu_to_le32() first ,but when I trace the messages from
> > printk,the value of msg_type is reversed.
>
> That's in radeon_uvd_cs_msg()? Sounds like the Mesa UVD code writes the
> messages in host byte order, not in little endian. Maybe Christian can
> clarify which byte order should be used for them.
The hardware supports byte swapping for the message and feedback buffer, but I
think always writing/reading it in little endian will be simpler to get
working.
The userspace code currently doesn't supports big endian hosts and so will
probably write it in the wrong byte order.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1879 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
next prev parent reply other threads:[~2014-09-25 7:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 11:02 [Bug 83708] New: mplayer plays video using gpu hardware acceleraing(vdpau,uvd) kernel panic, Unable to handle kernel paging request at virtual address bugzilla-daemon
2014-09-11 2:15 ` [Bug 83708] [vdpau,uvd] kernel oops, " bugzilla-daemon
2014-09-18 6:54 ` bugzilla-daemon
2014-09-18 6:55 ` bugzilla-daemon
2014-09-18 6:55 ` bugzilla-daemon
2014-09-18 6:56 ` bugzilla-daemon
2014-09-18 7:18 ` bugzilla-daemon
2014-09-18 7:28 ` bugzilla-daemon
2014-09-18 12:41 ` bugzilla-daemon
2014-09-20 4:09 ` bugzilla-daemon
2014-09-20 4:09 ` bugzilla-daemon
2014-09-20 4:10 ` bugzilla-daemon
2014-09-22 8:59 ` bugzilla-daemon
2014-09-23 13:00 ` bugzilla-daemon
2014-09-24 9:28 ` bugzilla-daemon
2014-09-24 15:18 ` bugzilla-daemon
2014-09-25 2:18 ` bugzilla-daemon
2014-09-25 7:26 ` bugzilla-daemon [this message]
2014-09-28 12:01 ` bugzilla-daemon
2014-09-29 7:16 ` bugzilla-daemon
2019-11-19 8:55 ` 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-83708-502-aa41JztnWA@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).