site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Jul 27, 2007, at 6:35 AM, Quinn wrote: It kinda depends on whether you're building an I/O Kit KEXT or some other form of KEXT. For an I/O Kit KEXT, you can stash these sorts of parameters in the personality in your "Info.plist", and I/O Kit will transfer these properties to your I/O registry entry. It's nice, but it's not as useful as you might think. For example, your shouldn't go modifying your "Info.plist" on a user's machine out in the field as a matter of course. That way lies revision control madness. Thus, these properties are typically only useful for debugging and for setting really obscure options. Hmmm.... Can you elaborate on that? One of the kext's I worked on in a previous life had some basic settings the user would tweak depending on his needs. The solution I ended up settling on was to provide an app that modified my kext, touch Extensions, then requested a reboot (I forget whether it required a reboot, or also did a setProperty call to pass the new setting into the loaded driver, but the principle is the same either way...). Anecdotally, it seemed to work fairly well, especially considering the alternative of requiring a StartupItem (or launchd thingy) simply to load static preferences. Clearly modifying other peoples plists lies somewhere between stupid and insane depending on use case, but if your talking about your own driver this didn't seem particularly bad. Is their some gotcha I should be aware of with this, or were you speaking more generically? _______________________________________________ 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