0

Apple developer documentation says:

If your hardware communicates entirely using standards-based protocols, you can ship a driver that matches your hardware to one of the built-in system drivers.

Is this possible to do if macOS itself has the driver implemented as a dext?

Particularly, I'm interested in providing support for an FTDI device with a custom product ID in my application. I've understood that macOS implements the FTDI driver as a dext (/System/Library/DriverExtensions/com.apple.DriverKit-AppleUSBFTDI.dext).

khuttun
  • 683
  • 1
  • 4
  • 14
  • To clarify: do you simply want to use the existing driver but add matching for your custom VID/PID pair(s)? Or do you actually want to "extend" the functionality as the question title suggests? I think the former should be possible to do using a "codeless" dext. (Though codeless dexts do actually contain a dummy executable unlike codeless kexts.) The latter is substantially more tricky and probably not possible, depending on what you're trying to do. – pmdj Nov 25 '20 at 10:39
  • @pmdj The former: use the existing driver for new VID/PID – khuttun Nov 25 '20 at 11:13
  • I edited the question title to be more descriptive. – khuttun Nov 25 '20 at 11:15
  • I have the same issue: use existing FTDI driver w/ new VID/PID -- were you able to find the resolution? – Andriy Gerasika Jun 09 '21 at 21:46
  • @AndriyGerasika Kind of. We made a request to Apple to add our VID/PID to their driver and now it supports the devices out-of-the-box. – khuttun Jun 10 '21 at 10:28

0 Answers0