On Mon, Nov 15, 2010 at 10:06:13AM +0200, Michael S. Tsirkin wrote:
> On Mon, Nov 15, 2010 at 04:30:43PM +0900, Isaku Yamahata wrote:
> > introduce a function to parse pci device path of
> > the format, [Domain:]Slot.Function:Slot.Function....:Slot.Function.
> >
> > Signed-off-by: Isaku Yamahata <[email protected]>
>
> Hmm.
> How about we use openfirmware path like what Gleb's patch does,
> with a fallback to bus:dev.fn for when it's unambiguous?
Okay, let me check my understanding of the format.
The openfirmware path in pci case looks like
/pci@<ioport>/<device name>@<slot>,<func>/.../<device name>@<slot>,<func>
"pci@<ioport>" corresponds to pci domain. So <mmio address> should be
also supported in addition to <ioport>.
Maybe we'd like "<device name>@" to be optional.
So the parser would accept something like
/{<ioport>, <mmio addr>}/<slot>,<func>/.../<slot>,<func>
--
yamahata
