<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Den 17-05-2011 10:41, Андрей Клаус skrev:
<blockquote
cite="mid:BANLkTinh+A2H3V-OU8WdhqbZYsD3tXcC-w@mail.gmail.com"
type="cite"><br>
<div class="gmail_quote">Hello everybody,<br>
<br>
I'm thinking about porting coreboot to my motherboard (epox
9NPA3I / 9NPA3J / 9NPAJ-3 / 9NPA3 Ultra Series). My chipset
(CK804) and my superio (F71872F/FG) are in supported list.
According to this page (<a moz-do-not-send="true"
href="http://www.coreboot.org/Support">http://www.coreboot.org/Support</a>)
port "might be easy" (exactly: "If you find those in our list of
<a moz-do-not-send="true"
href="http://www.coreboot.org/Supported_Chipsets_and_Devices"
title="Supported Chipsets and Devices">Supported Chipsets and
Devices</a> a port might be easy").<br>
<br>
I need roughly<span></span> estimation for "easy" to decide is
it possible for me to port coreboot or not (in time-consuming
terms). So, is "easy" up to 8 hours for coreboot expert, or is
it up to 40 hours for coreboot expert? Will be great if you
could give me estimation for 'worst' and 'best' variant.<br>
<br>
Thank you very much,<br>
Andrey<br>
</div>
<br>
</blockquote>
It took me less then 8 hours to make my first port, and I'm not even
a C programmer, mine was a best case senario as there was a sibling
board already ported. I have also ported some where just the
component where supported, that didn't take to long either, probably
7-10 hours.<br>
<br>
Working on a board where only legacy code and docs are available I
have probably spend around 12 hours to get to ram init.<br>
<br>
I think the key to sussess is to have an easy way to reflash the
bios when your image failes.<br>
<br>
-Anders<br>
</body>
</html>