From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LmJ1W-0008GL-5K for qemu-devel@nongnu.org; Tue, 24 Mar 2009 22:39:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LmJ1R-00084i-BW for qemu-devel@nongnu.org; Tue, 24 Mar 2009 22:39:21 -0400 Received: from [199.232.76.173] (port=37330 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LmJ1R-000846-3d for qemu-devel@nongnu.org; Tue, 24 Mar 2009 22:39:17 -0400 Received: from qw-out-1920.google.com ([74.125.92.147]:40702) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LmJ1Q-0002dv-PA for qemu-devel@nongnu.org; Tue, 24 Mar 2009 22:39:16 -0400 Received: by qw-out-1920.google.com with SMTP id 5so1357219qwf.4 for ; Tue, 24 Mar 2009 19:39:16 -0700 (PDT) Message-ID: <49C9994F.2040803@codemonkey.ws> Date: Tue, 24 Mar 2009 21:39:11 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] svn 6658 broke powerpc. References: <200903171857.42875.rob@landley.net> <200903211344.55267.rob@landley.net> <200903242130.29317.rob@landley.net> In-Reply-To: <200903242130.29317.rob@landley.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Blue Swirl , The OpenBIOS Mailinglist Rob Landley wrote: > On Sunday 22 March 2009 11:54:22 Blue Swirl wrote: > >>> So the bug was introduced (or at least triggered) by revision 452: >>> >>> http://tracker.coreboot.org/trac/openbios/changeset/452/openbios-devel >>> >>> Anything in there look broken to you? >>> >> Fixed in r481. I removed the PCI encode-unit/decode-unit methods for >> non-bus devices, now get-instance-path works. >> > > > Cool! > > Is there a procedure to ask how to queue this up for qemu 0.10.2? :) > > Rob > > (By the way: qemu is shipping a gpled bios binary without accompanying source > code. I realize that the maintainer of said binary checked it in, but what > exactly is the rationale here?) > IANAL, but from the FSF GPL FAQ, you just have to make sure the source code is available. Since Blue Swirl is an Open BIOS maintainer, I think we can say with confidence that the openbios code will always be available. If that situation changed for some reason, we'd have to mirror their code. Regards, Anthony Liguori