Re:plugin to query hardware status
Re:plugin to query hardware status
- Subject: Re:plugin to query hardware status
- From: david tay <email@hidden>
- Date: Tue, 9 May 2006 14:05:21 -0700
One easy way to do this is to just use the IORegistry. The user-land
code would just get/set values in the IORegistry entries of your
driver objects. The upside of this is that it is really easy to
implement both in user-space and in your kernel objects. The downside
of it is that the IORegistry has to do a lot of work to move the data
between the kernel and user-space. So, you wouldn't want to do it
this way if you are expecting to have to query/change this
information a lot.
I'm able to set the values just fine. However, when getting values,
those values must first be set in the IORegistry.
Would it be possible to override some function to provide access to
the user client object?
Most, if not all, applications aren't going to know a single thing
about your custom properties. As such, it would be unwise to rely on
the applications to do the right thing (or really do anything) with
them. If you are trying to expose some aspect of your hardware that
isn't covered by the standard set of properties, your best bet is to
just write an application yourself that can do the right thing, like
what MotU or Metric Halo do. Otherwise, your great hardware feature
will languish in anonymity.
When speaking of application developers, I was referring to internal
developers. The custom properties are most likely going to remain
private.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden