From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=49266 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PGUHp-0006qo-Tj for qemu-devel@nongnu.org; Thu, 11 Nov 2010 05:21:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PGUHo-0003Wu-Ug for qemu-devel@nongnu.org; Thu, 11 Nov 2010 05:21:45 -0500 Received: from mx1.redhat.com ([209.132.183.28]:5229) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PGUHo-0003Wp-O6 for qemu-devel@nongnu.org; Thu, 11 Nov 2010 05:21:44 -0500 Message-ID: <4CDBC3B3.8040007@redhat.com> Date: Thu, 11 Nov 2010 11:21:39 +0100 From: Gerd Hoffmann MIME-Version: 1.0 References: <1289409261-5418-1-git-send-email-gleb@redhat.com> In-Reply-To: <1289409261-5418-1-git-send-email-gleb@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCHv3 00/14] boot order specification List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: kvm@vger.kernel.org, mst@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com, blauwirbel@gmail.com, alex.williamson@redhat.com On 11/10/10 18:14, Gleb Natapov wrote: > This is current sate of the patch series for people to comment on. > I am using open firmware naming scheme to specify device path names. > > Names look like this on pci machine: > /pci@i0cf8/ide@1,1/drive@1/disk@0 > /pci@i0cf8/isa@1/fdc@03f1/floppy@1 > /pci@i0cf8/isa@1/fdc@03f1/floppy@0 > /pci@i0cf8/ide@1,1/drive@1/disk@1 > /pci@i0cf8/ide@1,1/drive@0/disk@0 > /pci@i0cf8/scsi@3/disk@0 > /pci@i0cf8/ethernet@4/ethernet-phy@0 > /pci@i0cf8/ethernet@5/ethernet-phy@0 > /pci@i0cf8/ide@1,1/drive@0/disk@1 > /pci@i0cf8/isa@1/ide@01e8/drive@0/disk@0 > /pci@i0cf8/usb@1,2/network@0/ethernet@0 > /pci@i0cf8/usb@1,2/hub@1/network@0/ethernet@0 Good stuff overall, but see replies to patches for some nits. IIRC some powerpc (+sparc?) boards pass a device tree to the guest. So with this (and maybe some more bits) we might be able to dynamically generate a device tree from our qdev tree? Any comments from the ppc/sparc folks on this? cheers, Gerd