Is it now necessary to prepare () an IOMemoryDescriptor before calling mapDeviceMemoryWithIndex? That is, where one had, in the past, been doing something like this: IOMemoryMap *mem = provider->mapDeviceMemoryWithIndex (0); Is it now necessary to do something like this: provider->getDeviceMemoryWithIndex (0)->prepare (); IOMemoryMap *mem = provider->mapDeviceMemoryWithIndex (0); Also, is it important to know whether somebody else has already called prepare () on the IOMemoryDescriptor? That is, is there any problem in calling it twice (if, for instance, a superclass has already called it, or that sort of thing). Also, where the memory mapping is going to be used for the entire life of the kernel extension, and the kernel extension cannot be unloaded, is it important to call IOMemoryDescriptor::release at some point? What would be the appropriate point--I suppose during stop ()? _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.