• 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: Errors from driver
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Errors from driver


  • Subject: Re: Errors from driver
  • From: Matthew Xavier Mora <email@hidden>
  • Date: Mon, 1 Nov 2004 13:17:20 -0700

At 1:05 PM -0800 11/1/04, Jeff Moore wrote:
The HAL uses the return value from the kernel trap only to signify whether or not it needs to resynchronize. Other than that, the error goes off into the ether since there is no mechanism in the HAL to report it to an interested client.

If you are trying to debug something in your driver, you can use the telemetry in HALLab to see the error being returned to the HAL. It will show up as one of the data points to the telemetry event that marks the return from the kernel trap.

Only the input clip routine errors will show up. The error on the output side is swallowed up by IOAudioFamily. I wrote a bug on that and it should be fixed when a new IOAudioFamily rolls out.





Matt _______________________________________________ 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
References: 
 >Errors from driver (From: Mark Cookson <email@hidden>)
 >Re: Errors from driver (From: Jeff Moore <email@hidden>)

  • Prev by Date: Re: Errors from driver
  • Next by Date: kStereoMixerParam_PreAveragePower
  • Previous by thread: Re: Errors from driver
  • Next by thread: kStereoMixerParam_PreAveragePower
  • Index(es):
    • Date
    • Thread