• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Getting Notifications of Device Arrival and Departure without IOKit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting Notifications of Device Arrival and Departure without IOKit


  • Subject: Re: Getting Notifications of Device Arrival and Departure without IOKit
  • From: Terry Lambert <email@hidden>
  • Date: Sun, 5 Nov 2006 12:57:19 -0800

On Nov 4, 2006, at 12:27 AM, NAHieu wrote:

Hello,

I am writing a plain KEXT which is not based on IOKit. Is there any
way to get notified in kernelspace when an external device (such as
USBkey) is connected to machine?

I found related documentation at
http://developer.apple.com/documentation/DeviceDrivers/Conceptual/AccessingHardware/index.html .
Unfortunately the proposed method relies on IOKit, which is not used
in my project.


Any pointer is highly appreciated.

Many thanks.

The event notification framework is part of IOKit.

If you want to have a driver outside of IOKit do this, then you will need to provide at least an IOKit stub to talk to your device and forward notifications (e.g. via callback function registration between the KEXTs).

My recommendation is that you use IOKit.

-- Terry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Getting Notifications of Device Arrival and Departure without IOKit (From: NAHieu <email@hidden>)

  • Prev by Date: Re: pseudo-device pty >32
  • Next by Date: Re: pseudo-device pty >32
  • Previous by thread: Getting Notifications of Device Arrival and Departure without IOKit
  • Next by thread: TCP_KEEPALIVE
  • Index(es):
    • Date
    • Thread