[coreboot] Modifying Coreboot to support a new processor

[Dsouza, Malcolm]

Thanks Corey,


 1.  I agree that before reading through the code, it is better to first check if the BIOS guides are available. However I would still like the answer to my question if I wish to carry on with the investigation for now.
 2.  I am trying to work out an overview of the changes required for a start; a bird's eye view of what the changes could turn out to be. What is the best approach for this?

Please ignore any footer that comes along with this mail:).

Regards,
Malcolm

________________________________
From: Corey Osgood [mailto:corey.osgood at gmail.com]
Sent: Tuesday, August 09, 2011 4:56 AM
To: Dsouza, Malcolm
Cc: coreboot at coreboot.org
Subject: Re: [coreboot] Modifying Coreboot to support a new processor

On Mon, Aug 8, 2011 at 8:33 AM, Dsouza, Malcolm <malcolm.dsouza at igatepatni.com<mailto:malcolm.dsouza at igatepatni.com>> wrote:
Hi Everyone,

I trust all are in the best of health. I am planning to use Coreboot as the BIOS for the new Intel 2nd Generation Processors. However Coreboot does not support this processor or its associated chipset. To better understand the efforts needed in the respective areas, I have hence begun comparing various features present in the datasheets of the Intel chipsets Coreboot presently supports with the chipset I plan to use. Based on these findings I am trying to come to the conclusion about the areas in the code that will require modifications. Is this the right approach? Or should I try differently? Please send me your suggestions.

Thanks and Regards!

Before you even bother looking into coreboot, contact your local Intel representative about getting the BIOS programming guides for the CPUs and chipsets you're interested in. They're covered by RS-NDA (Restriced Secret Non-Disclosure Agreement), and there's a pretty good chance they won't hand them out unless you've got a pretty darn good business case, especially given their involvement with EFI. Not to dissuade you from Coreboot, but I don't want to waste your time looking into it just to find out you can't get the info you need to make it work.

Also, footers proclaiming the email confidential on messages to mailing lists, especially publicly archived ones, are rather ridiculous ;)

-Corey

________________________________
Information contained and transmitted by this e-mail is confidential and proprietary to iGATE Patni and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailadmin at igatepatni.com. iGATE Patni does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of iGATE Patni. iGATE Patni is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While iGATE Patni has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about iGATE Patni please visit www.igatepatni.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20110809/dd2f0fc3/attachment.html>