site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Hello, bInterfaceClass: 255 bInterfaceProtocol: 255 bInterfaceSubClass: 255 CFBundleIdentifier: com.ProjectNitro.PrismWireless idProduct: 8723 idVendor: 1643 IOClass: PrismWireless IOKitDebug: 65535 IOProviderClass: IOUSBDevice --ness _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I am writing a wireless driver for Prism2 chipsets, though I'm having a small problem. I picked up some info from a slightly modified Prism2 configuration off USB Prober (such as configuration descriptors, etc.) Now that I've modified it to work with my plist, I kextload'd the driver. tail comes up with this: Sep 18 17:00:47 localhost kernel: OHCI Root Hub Simulation: family specific matching fails Sep 18 17:00:47 localhost kernel: IOUSBDevice: family specific matching fails Sep 18 17:00:47 localhost kernel: OHCI Root Hub Simulation: family specific matching fails Sep 18 17:00:47 localhost kernel: OHCI Root Hub Simulation: family specific matching fails Sep 18 17:00:47 localhost kernel: EHCI Root Hub Simulation: family specific matching fails Sep 18 17:00:47 localhost kernel: iPod : family specific matching fails Sep 18 17:00:47 localhost kernel: Matching service count = 1 Sep 18 17:00:47 localhost kernel: IOUSBCompositeDevice: match category IODefaultMatchCategory exists And nothing else happens. My driver's init command isn't called, nothing. It just loads the kext and it's silent. For those who want to know what the used personality is: This email sent to site_archiver@lists.apple.com