Sorry, but this cutom driver aka rename/injection 'trick' apply only to usb class audio drivers and not to other kexts. If you like to have it renamed anyway you might need to create an aggregated device.
Note:Â This document was previously titled Working With USB Device Interfaces. The I/O Kit provides a device interface mechanism that allows applications to communicate with and control hardware from outside the kernel. This document focuses on how to use that mechanism to create an application that detects the attachment of a USB device, communicates with it, and detects its detachment. This document does not describe how to develop an in-kernel driver for a USB modem or networking device.
If you need to do this, refer to the documentation and sample code listed in. See Also The ADC Reference Library contains several documents on device driver development for OS X and numerous sample drivers and applications. describes various ways to access devices from outside the kernel, including the device interface mechanism provided by the I/O Kit. For an overview of the I/O Kit terms and concepts used in this document, read the chapter. contains API reference for I/O Kit methods and functions and for specific device families. includes both application-level and in-kernel code samples.
Of particular relevance to this document is the application-level sample. OS X Man Pages provides access to existing reference documentation for BSD and POSIX functions and tools in a convenient HTML format. The mailing list provides a forum for discussing technical issues relating to USB devices in OS X.
If you need to develop an in-kernel driver for a USB modem or networking device, refer to the following:. describes the architecture of the I/O Kit, the object-oriented framework for developing OS X device drivers. ADC members can view the AppleUSBCDCDriver project in the source code for OS X v10.3.7 and later, available at. To find the source code, select a version of OS X equal to or greater than v10.3.7 and click Source (choose the source for the PPC version, if there's a choice). This displays a new page, which lists the open source projects available for the version of OS X you've chosen. Scroll down to AppleUSBCDCDriver and click it to view the source.
Be prepared to supply your ADC member name and password. Additional code samples that demonstrate specific in-kernel driver programming techniques are included as part of the OS X Developer Tools installation package in /Developer/Examples/Kernel/IOKit/usb. If you're ready to create a universal binary version of your USB device-access application to run in an Intel-based Macintosh, see. The Universal Binary Programming Guidelines describes the differences between the Intel and PowerPC architectures and provides tips for developing a universal binary. If you are working with a device that complies with the USB mass storage specification but declares its device class to be vendor specific, see for information on how to ensure the correct built-in driver loads for the device. Apple provides additional USB information (including the OS X USB Debug Kits) at.
A detailed description of the USB device specification is beyond the scope of this document—for more information, see Universal Serial Bus Specification Revision 2.0 available at.
The RT Systems ADMS-FT2D Radio Programming System includes the RT Systems FT-2D programming software and the RT Systems USB-68 cable. The RT Systems Programming software makes it easy to set up memory channel details including names and tones. Limit memories for Programmable Scanning functions, memory banks, DTMF memories, pager tones and options for Fusion are set easily from the screens of the program.
No more 'function key frustration' as you try to set up a feature from the face of the radio. This is an RT Systems programmer with all the editing ease and file interaction that you have come to love. Available for either Windows OS or Mac OS.
![Device Device](http://joelinoff.com/blog/wp-content/uploads/2012/03/img14.png)
The radio does not program using the cable that comes with it. The cable in the radio box is for firmware upgrades only. Use the USB-68 from RT Systems (shown here), the SCU-18 or SCU-19 from Yaesu (that you might have left over from your FT-1D radio), or an appropriate micro SD Card (Class 4 works best) to transfer details from the programmer to the radio.