Re: Multiple Services provided by a single driver

• Subject: Re: Multiple Services provided by a single driver
• From: Anthony Malizia <email@hidden>
• Date: Fri, 8 Apr 2005 14:24:15 -0400
• Delivered-to: email@hidden
• Delivered-to: email@hidden

I was trying to summarize the general case, not necessarily John's example.
(IOPCIDevice - nub)
-> (IOService derived - multifunction driver) [creates func1 and func2 nubs, attaches, and registerService]
-> (IOService derived - func1 nub)
-> (IOService derived - func1 driver) [matching to possibly another kext]
-> (IOService derived - func2 nub)
-> (IOService derived - func2 driver) [matching to possibly yet another kext]
Or?
(IOPCIDevice - nub)
-> (IOService derived - multifunction driver) [creates func1 and func2 drivers, attaches, and registerService]
-> (IOService derived - func1 driver) [must be in same kext as multifunction driver?]
-> (IOService derived - func2 driver) [must be in same kext as multifunction driver?]
What about user clients? How do they get created and attached?
Thanks again.
On 8-Apr-05, at 1:17 PM, Dean Reece wrote:

Actually, they can be either nubs OR complete drivers. The way you decide which it use depends on where the support for the next layer up comes from. In the multi-slot flash reader example, the objects being published are IOMedia nubs, and they get registered for matching and IOKit takes over and does the rest. In this case, you don't want to provide the higher-layers of functionality in your driver; you want IOKit to find the best consumer for your services and wire everything up.
In a case where your kext is providing the functionality and there is no reason to use IOKit matching to find the best consumer, then you can directly instantiate the desired driver object, then attach() it and start() it. This is done in the Apple16X50Serial driver for multi-UART devices: A bus controller matches against the physical device (PCI or PCCard) and creates a UART driver object for each UART it finds (up to 4 in the current implementation). Of course, these UART driver object(s) register for matching and are consumed by IOSerialFamily, so these objects are both drivers and nubs.
Cheers,
- Dean

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

• Follow-Ups:
  • Creating and attaching user clients.
    • From: Godfrey van der Linden <email@hidden>

• Prev by Date: Re: Ethernet Network adapter drivers for Mac OS X 10.3
• Next by Date: Shared Memory Mapping
• Previous by thread: Re: Multiple Services provided by a single driver
• Next by thread: Creating and attaching user clients.
• Index(es):
  • Date
  • Thread