From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=50767 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PDwNp-00047V-An
	for qemu-devel@nongnu.org; Thu, 04 Nov 2010 05:45:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1PDwNm-0006f4-5j
	for qemu-devel@nongnu.org; Thu, 04 Nov 2010 05:45:25 -0400
Received: from mx1.redhat.com ([209.132.183.28]:26983)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1PDwNl-0006eu-V3
	for qemu-devel@nongnu.org; Thu, 04 Nov 2010 05:45:22 -0400
Date: Thu, 4 Nov 2010 11:45:16 +0200
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCHv2 0/8 RFC] boot order specification
Message-ID: <20101104094516.GD6018@redhat.com>
References: <1288525209-3303-1-git-send-email-gleb@redhat.com>
	<20101031222553.GA16443@morn.localdomain>
	<20101101075351.GX26191@redhat.com>
	<m3sjzhphk2.fsf@blackfin.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m3sjzhphk2.fsf@blackfin.pond.sub.org>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin O'Connor <kevin@koconnor.net>, qemu-devel@nongnu.org, kvm@vger.kernel.org

On Thu, Nov 04, 2010 at 10:24:45AM +0100, Markus Armbruster wrote:
> Gleb Natapov <gleb@redhat.com> writes:
> 
> > On Sun, Oct 31, 2010 at 06:25:53PM -0400, Kevin O'Connor wrote:
> >> On Sun, Oct 31, 2010 at 01:40:01PM +0200, Gleb Natapov wrote:
> >> > This is current sate of the patch series for people to comment on.
> >> > I tried to use open firmware naming scheme to specify device path names.
> >> > 
> >> > The patch series produce names like these:
> >> > for pci machine:
> >> > /pci@i0cf8/pci-isa-bridge@1/fdc@03f1/floppy@0
> >> > /pci@i0cf8/pci-isa-bridge@1/fdc@03f1/floppy@1
> >> > /pci@i0cf8/ata@1,1/ata-disk@1:0
> >> > /pci@i0cf8/ata@1,1/ata-disk@1:1
> >> > /pci@i0cf8/virtio-blk@3/virtio-disk@0
> >> > /pci@i0cf8/ethernet@4/ethernet-phy@0
> >> > /pci@i0cf8/ethernet@5/ethernet-phy@0
> >> > 
> >> > for isa machine:
> >> > adding '/isa/fdc@03f1/floppy@0' at index 2
> >> > adding '/isa/fdc@03f1/floppy@1' at index 1
> >> > adding '/isa/ata@0170/ata-disk@0:0' at index 0
> >> > adding '/isa/ata@0170/ata-disk@0:1' at index 3
> >> 
> >> Hi Gleb,
> >> 
> >> How will USB drives be identified?
> >> 
> > USB bus has Open Firmware binding. I haven't look at the spec yet, but it
> > should be easy.
> >
> >> I'm not sure how SeaBIOS will be able to line up something like
> >> "/pci@i0cf8/ethernet@4/ethernet-phy@0" to an optionrom BEV.  Also, if
> >> there is an optionrom with BCVs (eg, a scsi card), I'm not sure how
> >> that would that would be identified.
> >
> > The way to parse  "/pci@i0cf8/ethernet@4/ethernet-phy@0" is this: each
> > element (between /.../) consist of node-name@unit-address. node-name
> > describes device/bus. unit-address is a device address on preceding node.
> > So pci@i0cf8 tells us that this is pci bus accessible through io
> > register 0x0cf8, ethernet@4 tells us that this is ethernet device in pci
> > slot 4 function 0, (ata@1,1 means ata device in slot 1 function 1).
> 
> Aren't "ethernet" and "ata" redundant there?
> 
In case of PCI bus yes. If parent bus does not allow to query device
type they are not.

--
			Gleb.