site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware At 15:27 -0500 9/7/07, billy lau wrote: Does anyone knows a way to work around this? I don't think there's any way to make your approach work. Instead, I'd recommend that you have the kernel call through some function pointers and then export those function pointers. When your KEXT loads, it can modify the function pointers to point into itself. If you don't care too much about the details [1], this should be pretty easy. [1] For example, if you care about binary compatibility, you'd want to export setter functions for the function pointers rather than direct access to the variables. Also, you'd have to define a thread model for these callouts. And if you want to support unloading, you have to define a way for threads to drain out of these callouts. So, if you think about this too hard, it gets quite complex. Hence, don't think about it too hard (-: _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com