<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c18">Comment # 18</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 <a class="email" href="mailto:zduo006@163.com" title="Jack <zduo006@163.com>"> Jack</a> <pre>(In reply to <a href="show_bug.cgi?id=83708#c17">comment #17</a>) > (In reply to <a href="show_bug.cgi?id=83708#c16">comment #16</a>) > > (In reply to <a href="show_bug.cgi?id=83708#c15">comment #15</a>) > > > 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. I think you are right. The patch I give it it's not the original point.So I have some work to do on userspace, such as mesa. A huge project! By the way, which version of mesa add big endian support.or you have some plans to do it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>