From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PW4Vx-0001Mx-Ev for garchives@archives.gentoo.org; Fri, 24 Dec 2010 10:04:45 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EB822E0656 for ; Fri, 24 Dec 2010 10:04:44 +0000 (UTC) Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 40EB0E05F5 for ; Fri, 24 Dec 2010 09:59:21 +0000 (UTC) Received: by gyh3 with SMTP id 3so4514185gyh.40 for ; Fri, 24 Dec 2010 01:59:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=KwL+7FIIBvtAqluB8X7DXaHfbokanxOUfOlXUqGG6t4=; b=JsKSGDL2APHMULSmWNAdDmiCo47Stc0bUXP/3ydZ9w7x8tcKifn4zRMC15K1dA5R6w qZWQasGGDn+3+CHSyIBueqX61m7HPHWLzwcC9W5aMyAYUCmpTV4VlBI3h0/WPD28Zdtf uewUhCrUo2Zo4jado50eJ3V4ByF6iaPqwl5A0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=AB4orjkm14maz+WEZ0idOdXUKe1sUVYiA8RYtuDs9XQKYwrDDbWAv3/UY8Wj3FFlUf ujQ/PMR80tGRhL9eA7jwcu1bKDtB5byEqz4bwcs3JKl1Dx3qkE65mmKmY/Ms61pdzWFb tGViuHe8eYjSbp0AxZGdsOiUaLN0brTJItMtA= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-embedded@lists.gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org MIME-Version: 1.0 Received: by 10.236.110.12 with SMTP id t12mr18180720yhg.6.1293184761591; Fri, 24 Dec 2010 01:59:21 -0800 (PST) Received: by 10.236.110.38 with HTTP; Fri, 24 Dec 2010 01:59:21 -0800 (PST) In-Reply-To: <20101224081654.13380.qmail@stuge.se> References: <20101223115307.26305.qmail@stuge.se> <20101224081654.13380.qmail@stuge.se> Date: Fri, 24 Dec 2010 11:59:21 +0200 Message-ID: Subject: Re: [gentoo-embedded] Re: boot linux without a bios on intel platform From: Kfir Lavi To: gentoo-embedded@lists.gentoo.org Content-Type: multipart/alternative; boundary=0023547c921557f8330498250a74 X-Archives-Salt: c0a8a2f0-4d8b-4f29-ad82-9403b19091f6 X-Archives-Hash: 40e36be21ea36969d61397318a0eceab --0023547c921557f8330498250a74 Content-Type: text/plain; charset=UTF-8 On Fri, Dec 24, 2010 at 10:16 AM, Peter Stuge wrote: > Kfir Lavi wrote: > > Thanks for your lengthy replay. Very interesting talk. > > I'm glad you liked it! > > > > I loved the push pins idea. > > Hehe, yes, it's really handy. :) > > > > Now I'm asking myself, how I didn't thought about it myself. I used > > a paper clip, but it is awkward. > > Yep. I like the pushpin idea a lot but I actually continue to use a > small screwdriver myself. > > > > I have a kontron board with an intel cpu. How can I get the spec > > with the parts in order to check if I will be able to use coreboot? > > Attached is the lspci of the board. > > 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory > Controller Hub (rev 07) > > lspci is a good first bit of info! This chipset is not supported at > all. The only modern-ish Intel chipset that is supported is the i945. > Compare the other Kontron with Intel in the list of supported boards. > > > > I would also like to know (if it is possible) how hard is to create > > support for this board myself. > > For an experienced coreboot developer I would estimate an absolute > minimum of eight man-months of work. This assumes that Intel NDAs and > document retrieval requests are processed instantly. It took 9 months > just to get NDAs processed for the coreboot developer who went > through that process. On the other hand, one Intel FAE I talked to > mentioned only weeks needed in some of his projects. > > You will also benefit from test equipment that will allow you to > study DRAM signals, and CPU state. These are 100k pricetag items. > > Learning how to initialize CPU, northbridge and memory controller > takes significant effort, and FAEs usually can not help. > > Is this Mobile 4 Series chipset (whatever that means, you could try > to look for some more low-level product codes for the chipset) part > of Intel's Embedded division? If so, you may be able to find much > inforation at edc.intel.com, but only after going through some > approval process there. > > It can certainly be worthwhile to do the coreboot work also for > something completely unsupported like this, but you need a fairly > large series production. > > On the other hand, maybe you can just choose a different board that > is already supported. I would try hard to do just that. > > > //Peter > > Hi Peter, Time is very short for my project. I think replacing the board is the best and quickest option. Hope in this stage, I'll be able to do it. It is my advice but not my decision. Another way is to reduce boot time of the bios by kontron. Is it possible to achive good boot times with ami bios? Thanks, Kfir --0023547c921557f8330498250a74 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Fri, Dec 24, 2010 at= 10:16 AM, Peter Stuge <peter@stuge.se> wrote:
Kfir Lavi wrote:
> Thanks for your lengthy replay. Very interesting talk.

I'm glad you liked it!


> I loved the push pins idea.

Hehe, yes, it's really handy. :)


> Now I'm asking myself, how I didn't thought about it myself. I= used
> a paper clip, but it is awkward.

Yep. I like the pushpin idea a lot but I actually continue to use a small screwdriver myself.


> I have a kontron board with an intel cpu. How can I get the spec
> with the parts in order to check if I will be able to use coreboot? > Attached is the lspci of the board.
> 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset M= emory Controller Hub (rev 07)

lspci is a good first bit of info! This chipset is not supported at
all. The only modern-ish Intel chipset that is supported is the i945.
Compare the other Kontron with Intel in the list of supported boards.


> I would also like to know (if it is possible) how hard is to create > support for this board myself.

For an experienced coreboot developer I would estimate an absolute minimum of eight man-months of work. This assumes that Intel NDAs and
document retrieval requests are processed instantly. It took 9 months
just to get NDAs processed for the coreboot developer who went
through that process. On the other hand, one Intel FAE I talked to
mentioned only weeks needed in some of his projects.

You will also benefit from test equipment that will allow you to
study DRAM signals, and CPU state. These are 100k pricetag items.

Learning how to initialize CPU, northbridge and memory controller
takes significant effort, and FAEs usually can not help.

Is this Mobile 4 Series chipset (whatever that means, you could try
to look for some more low-level product codes for the chipset) part
of Intel's Embedded division? If so, you may be able to find much
inforation at edc.intel.= com, but only after going through some
approval process there.

It can certainly be worthwhile to do the coreboot work also for
something completely unsupported like this, but you need a fairly
large series production.

On the other hand, maybe you can just choose a different board that
is already supported. I would try hard to do just that.


//Peter

Hi Peter,
Time is very short for my project. I= think replacing the board is the best and quickest option.
Hope in thi= s stage, I'll be able to do it. It is my advice but not my decision.
Another way is to reduce boot time of the bios by kontron.
Is it po= ssible to achive good boot times with ami bios?

Thanks,
Kfir
<= /div> --0023547c921557f8330498250a74--