If you only need to make calls from driver A to driver B then just load driver B first.
If you need to make calls both ways then you need to pass the address of the function(s) in A as a parameter on a call to B. Load B first then A and have A call into B passing its entry point(s) so that afterwards B can call A. ____________________________________________________ Richard Hilditch SNAP-IX Group Data Connection Ltd. Tel: +44 20 8366 1177 Mail: richard dot hilditch at dataconnection.com Fax: +44 20 8367 8501 Web: http://www.dataconnection.com > -----Original Message----- > From: Andy Winton [mailto:[EMAIL PROTECTED] > Sent: 02 April 2004 16:20 > To: linux streams > Subject: [Linux-streams] Communicating between a module and a driver > (not connected) > > > hi guys, > > Here's a question I hope you can help me with. > > (It's not really to do with LiS but more a streams > question) > > I have a STREAMS module, and I want to talk to > userspace. So I thought I'd make a floating driver > which would sit next to the module, and then I'd > talk with function calls between the two, and then > the driver would be able to talk directly to a daemon > in userspace. > > However, I have the module and driver as two separate > entities. And when I try to load up the module into > unixware kernel, it complains because there is an > unresolved symbol (the function which is in the driver > I wish to call). > > (I can't communicate via the stream which the module > is pushed on.) > > Is there a clever way to get this to work? > > thanks again, > > andy > > > > _______________________________________________ > Linux-streams mailing list > [EMAIL PROTECTED] > http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams > _______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
