From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48241) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Svp10-0004bG-O7 for qemu-devel@nongnu.org; Mon, 30 Jul 2012 08:24:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Svp0s-0003fY-EC for qemu-devel@nongnu.org; Mon, 30 Jul 2012 08:24:02 -0400 Received: from gate.crashing.org ([63.228.1.57]:57952) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Svp0p-0003f9-QY for qemu-devel@nongnu.org; Mon, 30 Jul 2012 08:23:54 -0400 Message-ID: <1343651011.2498.6.camel@pasglop> From: Benjamin Herrenschmidt Date: Mon, 30 Jul 2012 22:23:31 +1000 In-Reply-To: <50167AE9.6000902@redhat.com> References: <1343629462.21647.32.camel@pasglop> <50165D0A.6060608@redhat.com> <1343647217.21647.40.camel@pasglop> <50166F2A.1040507@redhat.com> <1343649267.21647.44.camel@pasglop> <501676D7.3010504@redhat.com> <1343650087.2498.4.camel@pasglop> <50167AE9.6000902@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Subject: Re: [Qemu-devel] Cirrus bugs vs endian: how two bugs cancel each other out List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: qemu-devel@nongnu.org On Mon, 2012-07-30 at 15:15 +0300, Avi Kivity wrote: > > Something tells me that getting that spice/qxl gunk will be more than a > > trivial effort (but I might be wrong) and I'm reluctant to start > > committing effort on it since so far I yet have to see it being actually > > picked up by people. > > I think it's prudent to wait until it's merged upstream, then we can > take another look to see why ppc is so special that it can't just use it > after fixing any endianness issues. If it flies there's no reason why ppc can't use it, I'm just dubious at this stage but we'll see. I'd love to spend some time endian-fix it (some of that fixing can be pretty hard when/if things aren't designed "properly" from the start) but at this stage I don't have the bandwidth to dive into it, understand the code in details etc... so that will have to wait unless I can find somebody else to deal with it within the community or my employer :-) Cheers, Ben.