Hi Laszlo,
When I 'connect 7b', MNP drivers support function is getting called. That is
why I am confused why it is not getting call on system boot.
> Date: Thu, 7 Aug 2014 22:03:03 +0200
> From: ler...@redhat.com
> To: edk2-devel@lists.sourceforge.net
> Subject: Re: [edk2] UEFI Shell Command "ifconfig" Error
>
> On 08/07/14 20:17, Chris Cuthbert wrote:
> > Hi Laszlo,
> >
> > I believe that is exactly what you have done in VirtioNetDxe driver and
> > I am following that exactly. I believe this dump from 'devtree' command
> > proves that I have populated the child handle 0x7B. Your example of SNP
> > from OVMF platform does show a couple of children with exact same MAC
> > address not sure if that is making any difference in terms of MNF
> > binding to it.
> >
> > Ctrl[33] PciRoot(0x2)
> > Ctrl[78] PciRoot(0x2)/Pci(0x1,0x0)
> > Ctrl[79] PciRoot(0x2)/Pci(0x2,0x0)
> > Ctrl[7A] PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)
> > Ctrl[7B] PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(121212121212,0x1)
> >
> > Shell> dh -v -d 7a
> > 7A: 7F33A118
> > PCIIO
> > DevicePath
> > PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)
> > Controller Name : PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)
> > Device Path : PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)
> > Controller Type : BUS
> > Configuration : NO
> > Diagnostics : NO
> > Managed by :
> > Drv[54] : FvFile(AC7E2A1E-B975-4C79-8ADA-C9EEFC55A407)
> > Parent Controllers :
> > Parent[33] : PciRoot(0x2)
> > Child Controllers :
> > Child[7B] :
> > PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(121212121212,0x1)
> >
> > Shell> dh -v -d 7b
> > 7B: 7F338518
> > DevicePath
> > PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(121212121212,0x1)
> > SimpleNetwork
> > Controller Name :
> > PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(121212121212,0x1)
> > Device Path :
> > PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(121212121212,0x1)
> > Controller Type : DEVICE
> > Configuration : NO
> > Diagnostics : NO
> > Managed by : <None>
> > Parent Controllers :
> > Parent[7A] : PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)
> > Child Controllers : <None>
> > Shell>
> >
> > Shell> dh -v -d -p simplenetwork
> > 7B: DevicePath
> > PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(121212121212,0x1) SimpleNetwork
> > Controller Name :
> > PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(121212121212,0x1)
> > Device Path :
> > PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(121212121212,0x1)
> > Controller Type : DEVICE
> > Configuration : NO
> > Diagnostics : NO
> > Managed by : <None>
> > Parent Controllers :
> > Parent[7A] : PciRoot(0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)
> > Child Controllers : <None>
> > Shell>
>
> I don't know what to suggest. Did you try "connect -r 7B"?
>
> In OVMF I'd probably add some DEBUG() calls to CoreConnectController()
> and to MNP's Supported() and Start() functions, to see where it goes
> wrong. I'd log the new child handle (the address) in my own Start(), and
> see if it turns up in CoreConnectController() somewhere, and if it's
> passed to MNP.
>
> Not sure if you can easily do that on your platform.
>
> Laszlo
>
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
