Re: Compiling Darwin for MacBook Pro
Re: Compiling Darwin for MacBook Pro
- Subject: Re: Compiling Darwin for MacBook Pro
- From: Michael Smith <email@hidden>
- Date: Wed, 6 Jun 2007 22:50:24 -0700
On Jun 6, 2007, at 12:12 PM, John Criswell wrote:
Has anyone compiled a Darwin kernel and successfully run it on an
Intel
Mac laptop
Yes.
I should have been more explicit in my question. I assume this
includes
the Macbook Pro with Intel Core 2 Duo processor, correct?
You can generally safely assume that a Darwin source release that
post-dates the release date of your hardware will work.
Are there any drivers required for the machine that are not part of
the open source Darwin project?
Yes.
I assume that this is also true for the desktop machines. Correct?
Yes.
Having looked over the Darwin download page, I'm guessing that the
network and hard disk drivers are kernel level modules,
IONetworkingFamily, IOStorageFamily and their respective hardware-
specific drivers are all built as kernel extensions, yes.
and the video
driver for Darwin is a user-space component of the X11 distribution,
correct?
I'm not familiar with X11 for Darwin. MacOS X video drivers are
supplied in binary-only form and typically comprise several kernel
extensions.
Our project requires being able to do compiler analysis of the
entire
kernel source.
Drivers are not part of the kernel, per se. They, and their
supporting libraries ("Families") are handled as loadable modules.
I see. That may be a problem, but I imagine we can work around
it. The
Darwin kernel we build from the open source sources should be able to
load and use these drivers, correct?
Yes, that's correct. You will want to be careful about applying
software updates to your system, as interface versions do
occasionally get bumped, but for the most part you should not have
any problems here.
= Mike
_______________________________________________
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