Nils Goroll wrote:
> (side note: This thread seems not to have made it into Jive yet... :-( )
>
> Hi Artem and all,
>
> I have thought again about the initial idea:
>
> What I need is a different behavior for the streams my driver provides
> (serial
> vs. net). What do you think about using two additional STREAMS modules which
> take over on the individual streams when those are opened? Could I insert
> them
> on top of the driver or is it allowed to modify the qinit structures for the
> stream to redirect to the other module's service routines?
>
Another reasonable approach for this kind of device might be to create a
nexus driver. Unfortunately, the nexus interfaces are not at all
public, and it would be difficult to do for an unbundled driver.
-- Garrett
> What do you think?
>
> Nils
> _______________________________________________
> driver-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
