On Wed, Aug 26, 2009 at 1:35 PM, Tim Roberts <timr@xxxxxxxxx> wrote: > Would this be suitable for two devices that are cooperating with each other > (ie. in a master/slave relationship, akin to pseudo-ttys in unix)? If so, > how would I establish a relationship between the master device (who would be > playing the bus driver, I guess) and the dynamically created slave device > that gets loaded when demanded by the master? > > > I believe that's exactly what I described above. Think of USB as a model. > The USB bus driver notices that a new USB device has plugged in. It builds > a plug-and-play ID from the device's descriptors, and exposes it through the > bus relations, as I described above. Plug-and-play finds the driver in its > INF files based on the device ID, the driver is loaded, and everybody is > happy. When the device unplugs, the USB bus driver again notifies that its > bus relations have changed, and this time plug-and-play starts the removal > process on the upper level driver. > Either I'm not understanding your answer or you're not understanding my question. Let me try to rephrase: If I want to have two devices, one acting as a master and one as a slave such that the master acts as a bus driver and causes new slaves to appear in the system, how can I connect these two driver objects together such that they can share data structures and call into each others private functions? If the two are separately loaded drivers would I be limited to communicating between them with standard channels such as by using device iocontrol messages? > Tim Roberts, timr@xxxxxxxxx > Providenza & Boekelheide, Inc. > > -Tim