I'm not sure how to do it, but this seems like a very strange
programming model. Why would you make two separate modules if they are
dependent on each other? Why not just make one module?
Avishay Traeger
http://www.fsl.cs.sunysb.edu/~avishay/
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
On 11/22/06, Jeongki Min <jeong...@gmail.com> wrote:
> The new module manages some information from the mac driver,
> so, they need
> to communicate each other.
Why? Isn't the MAC driver dealing mainly with its lower-level
drivers/layers rather than its upper layer drivers/subsystems. That is
the idea behind a layered design where data flows from the application
down to hardware.
If you have dependancies between the two, then you need to build the
object files together as a single module.
SK
--
Shakthi Kannan
http://www.shakthimaan.com
Umm well it does happen that Module A has dependencies on Module B,
but having interdependencies is well a bit unfortunate on the design
part.
But you can always have a model where module A directly depend on
module B and having module B calling functions of A through
callbacks. This way B can be loaded without requiring module A.
Of course best design would be to avoid this interdependency.
Hope this helps.
--
Ranjan
this is a good sign that they shouldn't be separate modules at all...
after all you gain nothing in this scenario anyway.
Can you give a pointer to the full source code so that we can help you
better?
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
Thank you so much for taking your time, and I really appreciate it.
Jeong Ki Min