3 ms·
Didn't NeXTSTEP already have DriverKit? That for some reason they didn't want ObjC in the kernel, so it was replaced with IOKit? Edit: lol, yep. http://www.n
by monocasa 7y ago
Didn't NeXTSTEP already have DriverKit? That for some reason they didn't want ObjC in the kernel, so it was replaced with IOKit?
Edit: lol, yep. http://www.nextcomputers.org/NeXTfiles/Docs/Developer/DriverKit/DriverKit.pdf http://www.nextcomputers.org/NeXTfiles/Docs/Developer/Driver...
You'd think they wouldn't name it something that literally conflicts their previous deprecated framework.
- mrpippy 7y agoYep, it's amusing that both these APIs recycle the names of what Mac OS X's parents used (DriverKit for NeXTSTEP, and the infamous System Extensions of classic Mac OS). Obviously no technical recycling going on though; the new DriverKit allows user-mode drivers, not ObjC in the kernel or willy-nilly patching of the OS.
- jjtheblunt 7y agoNeXT's driverkit allowed user-mode drivers, as I recall, having written one in 1993.
- urda 7y agoConsidering NeXTSTEP is long gone, why does it matter if the name conflicts? The name has no bearing on this discussion.
- monocasa 7y agoI mean, it's the previous driver framework for the XNU kernel before the current one IOKit. Which they are deprecating in favor of another DriverKit. Like, the XNU kernel has now had three driver frameworks. Two of them are named DriverKit but are completely separate, and not even back to back.
- pjmlp 7y agoYou can do some archeology here, https://www.geeklair.net/~dluke/PCIdevice_tutorial.txt https://www.geeklair.net/~dluke/PCIdevice_tutorial.txt