Hello Nick, in order to help you, I need to understand what your primary goal is. I have developed a lot of USB code, and rarely found it necessary for it to live in Kernel space. If your code does not need to live in Kernel space, that would immediately solve your issue, correct?
Alex Am 20.10.2014 um 09:29 schrieb Nick Yao <[email protected]>: > Dear Alex > add subject. > My leader has assigned the driver task to me. So It's kind of an order. > I just want to know the interface through which upper applications > talk to device driver. > I cannot find these interfaces in IOKit Classes. > > Thanks. > > Nick > > On 10/20/14, Alexander von Below <[email protected]> wrote: >> Exactly what is your goal? Why does your USB code need to live in kernel >> space in the first place? >> >> Alex >> >> Von meinem iPhone gesendet >> >>> Am 20.10.2014 um 09:00 schrieb Nick Yao <[email protected]>: >>> >>> Hello experts, >>> >>> I'm new to MAC development with some linux device driver >>> experience, and I am working on developing an usb device driver. >>> I have already read iokit fundamental, but still very confused. >>> how does kext get request form upper applications？Every base >>> Class in iokit have different functions. >>> It gives me the expression that iokit does't expose the same >>> uniform interface to upper applications. >>> Is there anything like read/write file operations functions in Linux? >>> >>> >>> Thanks. >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Usb mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/usb/below%40mac.com >>> >>> This email sent to [email protected] >> _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
