Re: RE:Ndis Miniport Driver for a NIC card with multiple ethernet ports

Is private interface route is like IOCTL Communication?

On Mon, Apr 27, 2015 at 12:02 PM, Doron Holan
wrote:

> No, you can’t. the interfaces to arbitrate those pci resources are not
> documented, you have to go the private interface route
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Sachindranath p.v
> Sent: Sunday, April 26, 2015 11:28 PM
> To: Windows System Software Devs Interest List
> Subject: Re: RE:[ntdev] Ndis Miniport Driver for a NIC card with
> multiple ethernet ports
>
>
>
> Write a custom bus driver to manually do the carving yourself (for
> complex resource allocation or interdependencies), as discussed above
> (although you can get by with just 2 drivers and not necessarily 3)

>
>
>
> If we are creating child PDO from custom bus driver, Can we use
> *EvtDeviceResourcesQuery(*WDF_PDO_EVENT_CALLBACKS) calbacks to export
> resource descriptor(by creating or dividing manually) to its child devices?
>
>
>
>
>
>
>
> On Sat, Oct 12, 2013 at 1:57 AM, Jeffrey Tippet <
> xxxxx@microsoft.com> wrote:
>
> No - the “port” concept provided by NdisMAllocatePort is not meant to deal
> with hardware that has multiple physical ports. Hardware that has multiple
> physical ports should either:
>
> (a) Expose each port as a separate PCI function, so the OS automatically
> carves up the hardware into multiple independent NICs
>
> (b) Use mf.sys to explicitly carve up the hardware into independent NICs
> (assuming static resource allocation); or
>
> (c) Write a custom bus driver to manually do the carving yourself (for
> complex resource allocation or interdependencies), as discussed above
> (although you can get by with just 2 drivers and not necessarily 3)
>
>
> The “port” concept provided by NdisMAllocatePort is meant for other
> abstractions. Its usage is contextual: for a wireless NIC, a port is a way
> to select virtual MACs. Above an Ethernet NIC, ports are reserved for the
> operating system’s NIC Teaming or Bridging features.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
>
>
> –
>
> Regards
>
> Sachindranath
>
> http:
>
>
>
>
>
> — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See
> http://www.osr.com/careers For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>


Regards
Sachindranath
http:</http:></http:>