Eric Sultan wrote:
> Randy Fishel wrote:
>> ...
>> Suspend/Resume is a core feature, and drivers are expected to
>> support DDI_SUSPEND/DDI_RESUME, such that silence implies the project
>> will implement them. So if this project does not intend to support
>> this feature at initial integration, it needs to describe in the case
>> why it will not and/or the plan for implementing them.
>>
>
> Yes, agreed. The project team intends to provide
> DDI_SUSPEND/DDI_RESUME. I wasn't sure when I replied earlier.
>
>
>> As Seb sort of implied in another case, quiesce() is also a required
>> interface, so it is expected that this project will also implement
>> this entry point, unless it provides equivilent information as would
>> be expected for non-support of DDI_SUSPEND/DDI_RESUME.
>
> Quiesce? It doesn't show up in my copy of Writing Device Drivers. A
> new interface, I presume, and not one currently offered in any of the
> other Sun SPARC graphics device drivers. I'll look into quiesce(),
> but I'm pretty sure that it wouldn't be implemented in Solaris 10
> drivers, unless they're equipped with a #pragma weak construct to
> determine whether it's available. Is #pragma weak an acceptable way
> of determining things like this?
Actually, since it is just an extra field at the end of dev_ops, you
can't #pragma weak it. Source probably won't compile on S10, but it is
possible that the binaries compiled on S11 will work okay (sans quiesce
support) on S10.
-- Garrett
>
> -- Eric
>
>
>
