• 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: Streaming OS X audio over network
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Streaming OS X audio over network


  • Subject: Re: Streaming OS X audio over network
  • From: Jeff Moore <email@hidden>
  • Date: Tue, 27 Jan 2004 18:43:01 -0800

On Jan 27, 2004, at 4:40 PM, Tim Hollingsworth wrote:

BTW, the author mentions numerous crashes and reboot when developing this driver. An important advantage of the "user land" driver is precisely to be easily debuggable and to not crash the whole computer when something going wrong.

I'm trying to contact the Author on these issues. Apart from frustrating development, crashes and cold reboots could destabilise my whole system right?

A panic would prevent any file system data that was cached in RAM to not get flushed out to disk. While this might lead to some lost data in an unsaved document, the file system damage that might be incurred is repaired as part of the boot sequence (fsck is your friend).

How much help is journalling?

Journaling will help speed up booting because there is less work to figuring out what needs fixing among other things. I have journalling turned on for all my volumes except those that I use for media data.

Is it worth developing on a separate partition?

I keep my source code and pretty much everything that isn't installed with the OS on a different partition than the boot partition. The reason I do it is because I install the OS a lot (kind of goes with the job I guess). I don't think that it will help in terms of speeding up compile time or what have you, but it does make doing clean installs all the time easier.

Could I develop a "user land" driver and then port it to a kernel extension?

No, probably not. The two driver models are very very different and have essentially no overlap. In fact, the speed up you'd gain in the compile-run-crash-debug-fix cycle will be totally outweighed by the extra time it takes to deal with the additional complexity of writing a user-land driver.

The guidance I like to give is that folks should do a kernel driver unless there are some very extreme circumstances that prevent a kernel driver from being practical. In the grand scheme of things, the kernel driver will give you better integration with the system.

--

Jeff Moore
Core Audio
Apple
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Streaming OS X audio over network
      • From: Philippe Wicker <email@hidden>
References: 
 >Re: Streaming OS X audio over network (From: Philippe Wicker <email@hidden>)
 >Re: Streaming OS X audio over network (From: Tim Hollingsworth <email@hidden>)

  • Prev by Date: Re: Streaming OS X audio over network
  • Next by Date: Re: Altivec FFT
  • Previous by thread: Re: Streaming OS X audio over network
  • Next by thread: Re: Streaming OS X audio over network
  • Index(es):
    • Date
    • Thread