Hi Michael,
Michael Hagemann wrote:
> I am also very new to this mailinglist
Welcome to the coreboot community.
> and would like to know how we can get our latest Ivy Bridge
> Mainboards from Kontron tested for coreboot and into the
> compatibility list.
You'll need to do the work to "port" coreboot to the KTQM77, at a
minimum you'll need to add some files to the coreboot source tree in
order to add the board into the coreboot build system, but most
likely some ACPI source code and PIR interrupt routing information
will also be needed. If you have custom hardware peripherals on the
board then they may require some code to be initialized.
coreboot uses git for source control, the same tool that is used for
Linux kernel source control, so if you have experience from working
with the Linux kernel community then you'll recognize many things
while working in the coreboot community.
You'll use git to create some commits with your changes to the
coreboot source tree, you'll then register on the
http://review.coreboot.org/ website which is a Gerrit instance
that we use for the code review and code integration processes.
You will need an OpenID in order to register with Gerrit, please let
me know if you would like me to create one for you, I would be happy
to do so, but perhaps you already have an OpenID from somewhere else,
it does not matter where you get it from.
Then you'll push your commits to the Gerrit system, publishing them
to seek review from the coreboot community. If you get no feedback
you'll probably nag individual developers with knowledge about the
parts of coreboot that are relevant for this new board, so that they
will take a look at your changes.
If after discussion there is agreement that some of your changes need
modifications then you'll modify your commits, maybe using the crazy
powerful 'interactive rebase' feature of git, and then push new
versions of the commits to Gerrit for a second round of review.
If you have experience with the various tools then the process is
quite easy. If you have never used any of these tools and
technologies you'll certainly have to spend some time to learn how to
use them - and then you will possibly never want to use anything
else. :)
> In the past this was handled by a colleague of mine who is not in
> the company anymore.
Too bad if the colleague left without transfering any knowledge -
that could probably have helped save you a lot of time. The community
is generally helpful, but is based on volunteer effort, and not
always available to assist on the schedule that you would need.
> In detail we would like to get our mini-ITX board KTQM77/mITX
> approved for coreboot.
Great! If you push some nice and clean commits to Gerrit then the
rest is fast and easy. Of course creating those commits can be
difficult.
> If anybody could suggest something to me I would be very happy.
It is not clear what your current state of coreboot is on the board.
Have you already done the porting and coreboot works for you on the
board, or are you just now starting the process of porting coreboot?
Both are good - and in fact if you are just now starting then I think
you can save a lot of time by staying in touch with the community
throughout the process. Feel free to also join the #coreboot chat on
irc.freenode.net for live discussion.
//Peter
Hallo together,
I am also very new to this mailinglist and would like to know how we can get our latest Ivy Bridge Mainboards from Kontron tested for coreboot and into the compatibility list. In the past this was handled by a colleague of mine who is not in the company anymore.
In detail we would like to get our mini-ITX board KTQM77/mITX approved for coreboot.
If anybody could suggest something to me I would be very happy.
best regards,
Michael Hagemann
Technical Sales Engineer
Kontron Technology A/S
Hamburger Str. 181
22083 Hamburg, Germany
e-mail: Michael.Hagemann(a)kontron.com<mailto:Michael.Hagemann@kontron.com>
www.kontron.com<http://www.kontron.com/>
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen und ist Eigentum von Kontron.
Die Verwendung und Weitergabe von jeglichen Inhalten ist ohne ausdrückliche schriftliche Genehmigung von Kontron strikt untersagt. Wenn Sie diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten diese Mail und enthaltene Dokumente.
Informationen indeholdt i dette dokument er FORTROLIGT og tilhører Kontron. Enhver uautoriseret gennemgang, brug, offentliggørelse eller videregivelse er ikke tilladt uden skriftligt samtykke fra Kontron. Er De ikke rette modtager, bedes De venligst underrette afsender herom og derefter slette alle kopier af denne email inklusive eventuelle vedhæftede filer.
The information in this document is CONFIDENTIAL and property of Kontron. Any unauthorized review, use, disclosure or distribution is prohibited without express written consent of Kontron. If you are not the intended recipient, please contact the sender and destroy all copies of the original message and enclosed attachments.
the following patch was just integrated into master:
commit 5b06291ce9afba67ab62732d8fb5e62080b143fe
Author: Patrick Georgi <patrick(a)georgi-clan.de>
Date: Thu Sep 13 22:13:33 2012 +0200
Isolate Kconfig host compiler options
This reverts commit 645f2dd5d97ffbaa80da7fbd776a08a76eb758e3.
Instead of adding a special case to nvramtool to avoid it
picking up Kconfig's regex.h, have the host compiler only
consider util/kconfig for includes (ie. -Iutil/kconfig)
for kconfig related object files.
Change-Id: Ie4f97ce38cb3e911f6e6c1e5b6f86f6998d93f69
Signed-off-by: Patrick Georgi <patrick(a)georgi-clan.de>
Build-Tested: build bot (Jenkins) at Thu Sep 13 22:47:13 2012, giving +1
Reviewed-By: Anton Kochkov <anton.kochkov(a)gmail.com> at Fri Sep 14 07:33:06 2012, giving +2
See http://review.coreboot.org/1509 for details.
-gerrit
the following patch was just integrated into master:
commit bc23c3d880781472401907f4e7ac623b5c639ddd
Author: Dave Frodin <dave.frodin(a)se-eng.com>
Date: Tue Aug 21 16:56:12 2012 -0600
Mahogany_Fam10: Fixes an apparent ACPI VGA resource collision.
Without this change 64 bit versions of Windows will BSOD.
Change-Id: If39627a179c24184b6c956b3a50f692f8a034d2f
Signed-off-by: Dave Frodin <dave.frodin(a)se-eng.com>
See http://review.coreboot.org/1476 for details.
-gerrit
the following patch was just integrated into master:
commit 87c44b6c3511ae8ba6e56e45a6282e5b8ce1cfe7
Author: Rudolf Marek <r.marek(a)assembler.cz>
Date: Tue Sep 11 15:07:14 2012 +0200
Fix ramstage location in trace scripts
The ramstage location has been changed. Reflect this in the script.
Change-Id: I76c9b38a8ffe2188e94146e845d23536625c0979
Signed-off-by: Rudolf Marek <r.marek(a)assembler.cz>
See http://review.coreboot.org/1504 for details.
-gerrit
the following patch was just integrated into master:
commit fe0353ef3ddd89f44acb084580507893160d337f
Author: Rudolf Marek <r.marek(a)assembler.cz>
Date: Tue Sep 11 15:06:17 2012 +0200
Fix tracing compilation on SMM enabled targets.
Disallow tracing while in SMM.
Change-Id: Icde17629bb06a615cc48f017fd0cd1f7b720e62d
Signed-off-by: Rudolf Marek <r.marek(a)assembler.cz>
See http://review.coreboot.org/1503 for details.
-gerrit