<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [vdpau,uvd] kernel oops, Unable to handle kernel paging request at virtual address"
href="https://bugs.freedesktop.org/show_bug.cgi?id=83708#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [vdpau,uvd] kernel oops, Unable to handle kernel paging request at virtual address"
href="https://bugs.freedesktop.org/show_bug.cgi?id=83708">bug 83708</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=83708#c15">comment #15</a>)
<span class="quote">> 1. I do not add cpu_to_le32() first ,but when I trace the messages from
> printk,the value of msg_type is reversed.</span >
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.
<span class="quote">> 2. #if 0 ...#endif is the original code from kernel. #if 1 ...#endif is
> changed code.</span >
Ah right, never mind, I misread that hunk before.
<span class="quote">> By the way, u said writel() and readl() already convert to/from little
> endian. is based on the X86 arch implement?</span >
It's the same on all architectures: writel() takes a datum in host byte order
and writes it in little endian. readl() reads a little endian datum and returns
it in host byte order. (This means that on little endian hosts such as x86, the
datum is transferred unchanged)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>