From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 83708] [vdpau,uvd] kernel oops, Unable to handle kernel paging request at virtual address Date: Sun, 28 Sep 2014 12:01:59 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0946884066==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 235F889BBD for ; Sun, 28 Sep 2014 05:01:59 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0946884066== Content-Type: multipart/alternative; boundary="1411905719.0bBA1Bde0.25046"; charset="us-ascii" --1411905719.0bBA1Bde0.25046 Date: Sun, 28 Sep 2014 12:01:59 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=83708 --- Comment #18 from Jack --- (In reply to comment #17) > (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. 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. -- You are receiving this mail because: You are the assignee for the bug. --1411905719.0bBA1Bde0.25046 Date: Sun, 28 Sep 2014 12:01:59 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 18 on bug 83708 from 
(In reply to comment #17)
> (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.

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.

You are receiving this mail because:
  • You are the assignee for the bug.
--1411905719.0bBA1Bde0.25046-- --===============0946884066== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0946884066==--