• 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: audio driver build process
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: audio driver build process


  • Subject: Re: audio driver build process
  • From: Mark Cookson <email@hidden>
  • Date: Fri, 13 Sep 2002 11:05:11 -0700

To unload a driver, use kextunload.

Usage:

sudo kextunload /System/Library/Extensions/MyDriver.kext

You can actually unload the driver from anywhere, it doesn't have to be the original one. I frequently delete the original, then unload the original by calling kextunload on the kext that PB just built and that's sitting in my build directory and not the Extensions folder. kextunload has lots of options as well, including one that unloads the kext using its objects name, useful if you don't have the binary file around anymore. man kextunload will tell all.

Don't forget kextstat as a useful tool to see what's loaded as well.

Regards,
Mark
--
Mark Cookson
Engineering Droid
Apple Computer, Inc.
Core Audio CPU Software
6 Infinite Loop MS 306-2CW
Cupertino, CA 95014

On Friday, September 13, 2002, at 10:39 AM, Matt Gonzalez wrote:

It's pretty easy to automate this whole process with a script; I got this from another
guy on the Darwin drivers list:

sudo rm -r /tmp/MyDriver.kext
ditto MyDriver.kext /tmp/MyDriver.kext
chmod -R 755 /tmp/MyDriver.kext
sudo chown -R root.wheel /tmp/MyDriver.kext
sudo kextload -v /tmp/MyDriver.kext

Just save that as a script somehwere. You could also add a line to unload the driver if
it's already loaded. This makes it fairly painless - just build, switch to Terminal,
and run the script.

Matt

Michel wrote:

On Friday 13 September 2002 09:56, Laurent Humbert wrote:
Any suggestions how to improve this, anyone ? I'm thinking of working
as "root" and get ProjectBuilder's build command to somehow generate
the driver directly in /System/Library/Extensions/. Would that be
possible ? I just want to hit Command-B and let PB get on with it.

You don't need your driver in /System/Library/Extensions. You can use
'kextload' to load the one from your build directory. The only catch is that
you need to change it's permissions with
chown -R root.wheel <yourdriver>.kext

It is still a bit of a pain, since if you are using project builder as your
own username, you need to remember to chown the .kext back to your user
before building, and change it back to root before loading....

Thats still pretty annoying, I wish there was a "stop bothering me when I'm
developing" flags to kextload!

Michel

--
Linux yawn 2.4.19-ac4 #49 Tue Aug 6 10:13:51 BST 2002 i686
_______________________________________________
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: audio driver build process
      • From: Laurent Humbert <email@hidden>
References: 
 >Re: audio driver build process (From: Matt Gonzalez <email@hidden>)

  • Prev by Date: Re: audio driver build process
  • Next by Date: Re: Weird 3D mixer bug
  • Previous by thread: Re: audio driver build process
  • Next by thread: Re: audio driver build process
  • Index(es):
    • Date
    • Thread