Device attaches on Solaris 10

Question

Hello,
We have a device driver that's been working on Solaris 7 and higher for some time. We're seeing different behavior on Solaris 10 that is causing us problems. We are running on Sparcs.
Our driver has one pseudo device and one or more physical devices.
Normally when the driver loads, the attach function is called for the pseudo device and the physical devices (in some not necessarily predictable order).
This loading would usually take place when the pseudo device was opened, but could be due to the driver initially being installed or sometimes when the system boots.
With Solaris 10, after rebooting the system, sometimes the pseudo device access only causes the pseudo device to be attached, and not the physical devices.
Our driver is actually accessed by applications soley via the pseudo device, rather than by individual devices, so this causes a big problem for us.
Is there anything we can do to cause the behavior to revert back to what it was before? Anything which causes the physical devices to all be attached would be fine, such as some call the attach for the pseudo device could make. Or something to put in our .conf file, etc.
Thanks,
Nathan

Answer 1

Thank you for your response.
Setting the "ddi-forceattach" property in Pseudo driver .conf file will not
help. Solaris does not "attach" Pseudo drivers which do not have ".conf"
children (even though the Pseudo driver conf file has "ddi-forceattach=1"
property set). Opening the Pseudo device file will attach the Pseudo driver.I'm confused... We have a .conf file, as mentioned, but what makes
it a "Pseudo driver .conf" rather than just a "driver .conf"?
From what I undestand of your requirement, the following should be sufficient :
1. Set property : "ddi-forceattach=1" for all physical devices that is
required by Pseudo driver.
2. Application opens the Pseudo device node.
Let me know if you have any queries / issues. I do have further questions.
Included below is a version of our .conf file modified to protect the
names of the guilty.
As you can see, there is part of it which defines a pseudo device,
and then a set of properties that apply to all devices. Or that's the
intention.
In #1, you said to set the ddi-forceattach property for all "physical
devices", but how do I do this, if it's not what I'm already doing? And what
do you mean "required by Pseudo driver"?
name="foobar" parent="pseudo" instance=1000 FOOBAR_PSEUDO=1;
ddi-forceattach=1
FOOBAR_SYM1=1
FOOBAR_SYM2=2
FOOBAR_SYM3=3;
On a Solaris 9 system of mine, recently I believe I have seen multiple cases
where I've booted, and a physical device has not gotten attached, but if I
reboot, it will be attached the next time.
Thanks,
Nathan