coreboot October 2009

coreboot@coreboot.org

63 participants
534 discussions

Re: [coreboot] [Qemu-devel] Release plan for 0.12.0
by Carl-Daniel Hailfinger 02 Oct '09

02 Oct '09

Hi Jordan, I have to admit that I'm not the expert for coreboot+EFI solutions. I know they exist and work, but I'll defer to other developers on the coreboot list to give you detailed answers. Please see below for what I think I know (but I'll gladly accept any corrections). On 02.10.2009 22:57, Jordan Justen wrote: > Carl-Daniel, > > Interesting. So, where can I download a QEMU bios rom to boot a UEFI > OS with this solution? > > Can you explain what coreboot+tianocore means? Which parts of > tianocore do you use in this situation? > This mail is CC: to the coreboot list and I'm sure someone who knows more than I can respond. The documentation about Tianocore/UEFI/EFI is not entirely clear about the names of each part of the stack, but if I understand correctly, there is a hardware init part (OVMF for Qemu) and parts which boot EFI enabled operating systems, provide EFI services to the operating system, or give users a shell to work from. coreboot is pure hardware init (CPU, RAM, chipset, PCI), it has no drivers whatsoever. It does provide ACPI tables for the hardware and a memory map. Once coreboot finishes hardware initialization, it passes control to a payload (which has drivers, boots the OS, provides services). That payload is hardware-independent unless it explicitly wants to contain non-generic drivers. It is possible to use the exact same SeaBIOS binary as coreboot payload on Qemu, Pentium III systems with i440BX chipset, AMD Phenom systems with 690G chipset, Via Nano systems with VX800 chipset, and Intel Core 2 Duo systems with i945 chipset. Unless I'm mistaken, OVMF and coreboot have pretty much the same purpose. > If your solution can accomplish all of what you say, I'm not sure how > OVMF would be able to compete against in terms of being included with > QEMU. Part of the reason for starting OVMF was to help enable UEFI > support within VM's such as QEMU. If OVMF was utilized by QEMU it > definitely would have been a bit of a boost for our efforts, but if > QEMU accomplishes UEFI support via another path, then overall we will > still be happy. > Please don't get me wrong. The number of developers in the open source firmware space is small and I'm happy that you're such a developer. My main worry is splitting one task among too many projects, with the danger of frustation if only one project is accepted into Qemu. I don't have an axe to grind against EFI (which is desired by many people) or OVMF (which is purpose-built for UEFI in Qemu). That's why I want to understand your goals and hope to find a way to accomplish your goals, coreboot goals and at the same time have Qemu get the best firmware possible. > Thanks, > > -Jordan > Regards, Carl-Daniel > On Fri, Oct 2, 2009 at 11:45, Carl-Daniel Hailfinger > <c-d.hailfinger.devel.2006(a)gmx.net> wrote: > >> On 02.10.2009 18:58, Jordan Justen wrote: >> >>> On Fri, Oct 2, 2009 at 06:29, Anthony Liguori <anthony(a)codemonkey.ws> wrote: >>> >>> >>>> So I think the best way forward is to hold off on UEFI in mainline until we >>>> can provide a single unified stack. >>>> >>>> >>> While it is true that a separate machine type could potentially be >>> viewed as increasing the testing requirements, I am not so sure. If >>> QEMU has a UEFI+CSM solution, wouldn't we still have to test both UEFI >>> based OS boot and the CSM based legacy OS boot? >>> >>> >> Given that you can easily pack coreboot+SeaBIOS+UEFI into one ROM and >> have coreboot boot either SeaBIOS (BIOS interface) or UEFI (EFI >> interface), wouldn't that solve all problems in one go? You get an >>

1 0

patch: remove embeddedplanet
by ron minnich 02 Oct '09

02 Oct '09

attached.

4 4

[v2] r4710 - in trunk/coreboot-v2: src/mainboard targets
by svn＠coreboot.org 02 Oct '09

02 Oct '09

Author: myles Date: 2009-10-02 17:46:10 +0200 (Fri, 02 Oct 2009) New Revision: 4710 Removed: trunk/coreboot-v2/src/mainboard/embeddedplanet/ trunk/coreboot-v2/targets/embeddedplanet/ Modified: trunk/coreboot-v2/src/mainboard/Kconfig Log: Remove the Embedded Planet board. Signed-off-by: Ronald G. Minnich <rminich(a)gmail.com> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Myles Watson <mylesgw(a)gmail.com> Modified: trunk/coreboot-v2/src/mainboard/Kconfig =================================================================== --- trunk/coreboot-v2/src/mainboard/Kconfig 2009-10-02 12:45:18 UTC (rev 4709) +++ trunk/coreboot-v2/src/mainboard/Kconfig 2009-10-02 15:46:10 UTC (rev 4710) @@ -38,8 +38,6 @@ bool "DIGITAL-LOGIC" config VENDOR_EAGLELION bool "EagleLion" -config VENDOR_EMBEDDED_PLANET - bool "Embedded Planet" config VENDOR_EMULATION bool "Emulation" config VENDOR_GIGABYTE @@ -184,11 +182,6 @@ config MAINBOARD_VENDOR string - default "Embedded Planet" - depends on VENDOR_EMBEDDED_PLANET - -config MAINBOARD_VENDOR - string default "Emulation" depends on VENDOR_EMULATION @@ -349,7 +342,6 @@ source "src/mainboard/dell/Kconfig" source "src/mainboard/digitallogic/Kconfig" source "src/mainboard/eaglelion/Kconfig" -source "src/mainboard/embeddedplanet/Kconfig" source "src/mainboard/emulation/Kconfig" source "src/mainboard/gigabyte/Kconfig" source "src/mainboard/hp/Kconfig" @@ -361,7 +353,6 @@ source "src/mainboard/kontron/Kconfig" source "src/mainboard/lippert/Kconfig" source "src/mainboard/mitac/Kconfig" -source "src/mainboard/motorola/Kconfig" source "src/mainboard/msi/Kconfig" source "src/mainboard/nec/Kconfig" source "src/mainboard/newisys/Kconfig"

1 0

Re: [coreboot] Not supported mobo, compile for a similar one?
by Myles Watson 02 Oct '09

02 Oct '09

On Fri, Oct 2, 2009 at 7:40 AM, Knut Kujat <knuku(a)gap.upv.es> wrote: >> Each Opteron (amdk8) has three links: 0,1,&2. On this board the mcp55 is on >> link 2. For your board you at least need to know if the 8132 is on the same >> link as the mcp55, or a different one. After you get that right it >> shouldn't be too hard to fix up the rest since the boards are so similar. >> > THX, for ur reply! No problem. According to the manual, the 8132 is on a link attached to a different processor, so you probably would get debug output from the board with an unmodified h8dmr image. Myles

1 0

proposal: remove Config.lb from dell s1850
by ron minnich 02 Oct '09

02 Oct '09

Nobody but me cares about the board. I am wondering about making the Dell the pioneer here: remove Options.lb and Config.lb so that it can no longer be built the old way. Comments? ron

3 4

Not supported mobo, compile for a similar one?
by Knut Kujat 02 Oct '09

02 Oct '09

Hi, first of all I'm new to the coreboot project and just wanted to say Hello! :) Now here my question: I have the supermicro mobo *H8QME-2+ http://www.supermicro.com/Aplus/motherboard/Opteron8000/MCP55/H8QME-2+.cfm *that is not supported by coreboot but there is a similar one at the coreboot v2 list: H8dmr http://www.supermicro.com/Aplus/motherboard/Opteron2000/MCP55/H8DMR-i2.cfm. What would happen if i compile a coreboot.rom for the H8dmr and flash into the H8QME-2+? What kind of changes do i have to do? THX and ciao.

2 1

build service results for r4709
by coreboot information 02 Oct '09

02 Oct '09

Dear coreboot readers! This is the automatic build system of coreboot. The developer "uwe" checked in revision 4709 to the coreboot repository. This caused the following changes: Change Log: Remove left-over targets/motorola/*, fix Dell PowerEdge 1850 name. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Build Log: Compilation of embeddedplanet:ep405pc is still broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=4709&device=ep405pc&vendor… If something broke during this checkin please be a pain in uwe's neck until the issue is fixed. If this issue is not fixed within 24h the revision should be backed out. Best regards, coreboot automatic build system

1 0

[v2] r4709 - in trunk/coreboot-v2: src/mainboard/dell/s1850 targets
by svn＠coreboot.org 02 Oct '09

02 Oct '09

Author: uwe Date: 2009-10-02 14:45:18 +0200 (Fri, 02 Oct 2009) New Revision: 4709 Removed: trunk/coreboot-v2/targets/motorola/ Modified: trunk/coreboot-v2/src/mainboard/dell/s1850/Kconfig Log: Remove left-over targets/motorola/*, fix Dell PowerEdge 1850 name. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/coreboot-v2/src/mainboard/dell/s1850/Kconfig =================================================================== --- trunk/coreboot-v2/src/mainboard/dell/s1850/Kconfig 2009-10-02 03:36:30 UTC (rev 4708) +++ trunk/coreboot-v2/src/mainboard/dell/s1850/Kconfig 2009-10-02 12:45:18 UTC (rev 4709) @@ -1,5 +1,5 @@ config BOARD_DELL_S1850 - bool "S1850" + bool "PowerEdge 1850" select ARCH_X86 select CPU_INTEL_SOCKET_MPGA604 select NORTHBRIDGE_INTEL_E7520 @@ -8,7 +8,7 @@ select SUPERIO_NSC_PC8374 select PIRQ_TABLE help - Dell S1850 mainboard. + Dell PowerEdge 1850 mainboard. config MAINBOARD_DIR string

1 0

serialice PCI capture
by Joseph Smith 02 Oct '09

02 Oct '09

Just a thought. YABEL can capture PCI read/writes from an option ROM, how hard would it be to get serialice to do the same with the bios? This would solve many of life's mysteries..... -- Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org

4 12

Supermicro X7SLA-H supported? (Intel 945GC + ICH7R)
by Sander 02 Oct '09

02 Oct '09

Hello all, I'm planning on building an adsl2+ server with a Traverse Solos PCI ADSL2+ card[1] on a Supermicro X7SLA-H motherboard[2]. The chipsets of the X7SLA-H are Intel 945GC + ICH7R which are listed as WIP on "Devices supported in coreboot v3"[3] What are the changes of getting Coreboot v3 to work on this motherboard? What makes v3 'alpha'? I can't seem to figure it out from reading the wiki. I consider myself an experienced Linux user but I have no hardware tools for flash or debug. Would I be able to play with Coreboot and be of any use to the community? Btw, I am open for any suggestions regarding a better motherboard with possible (future) Coreboot support. I'm looking for a small size, relative low power, two core, 64bit system with a pci slot for the Solos card. I've read the 'Supported Motherboard' section but it was last modified at 6 July 2009 so that might be outdated. Sander [1] http://www.traverse.com.au/productview.php?product_id=116 [2] http://www.supermicro.com/products/motherboard/ATOM/945/X7SLA.cfm [3] http://www.coreboot.org/Supported_Chipsets_and_Devices -- Humilis IT Services and Solutions http://www.humilis.net

3 4

← Newer
1
...
47
48
49
50
51
52
53
54
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot October 2009