Re: Compiling Darwin for MacBook Pro
Re: Compiling Darwin for MacBook Pro
- Subject: Re: Compiling Darwin for MacBook Pro
- From: John Criswell <email@hidden>
- Date: Wed, 06 Jun 2007 14:12:14 -0500
- Organization: University of Illinois
Michael Smith wrote:
Thanks for your answers. I still have a few more questions below:
>
> On Jun 6, 2007, at 7:31 AM, John Criswell wrote:
>
>> Our research group is looking to buy a Macbook Pro (2.16 GHz Intel Core
>> 2 Duo) for some research that we are doing. Our work involves
>> modifications to the Darwin kernel.
>>
>> I'd like to gain some confidence that if we buy this machine, we can
>> expect to compile our own kernels and have them work on the machine.
>
> Modulo the complexity of building the open-source kernel releases,
> yes, this generally works.
>
>> 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?
>
>> 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?
Having looked over the Darwin download page, I'm guessing that the
network and hard disk drivers are kernel level modules, and the video
driver for Darwin is a user-space component of the X11 distribution,
correct?
>
>> 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?
>
> = Mike
>
>
>
-- John Criswell
_______________________________________________
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