coreboot March 2011

coreboot@coreboot.org

71 participants
210 discussions

[PATCH 4/7] SuperMicro H8SCM support (AMD SP5100 remove legacy)
by Bao, Zheng 25 Mar '11

25 Mar '11

Since the SB700 has changed to sb7xx_51xx, change legacy name in other mainboard. Signed-off-by: Zheng Bao <zheng.bao(a)amd.com>

4 3

[PATCH 3/7] SuperMicro H8SCM support (Add entries AMD SR5650 SP5100)
by Bao, Zheng 25 Mar '11

25 Mar '11

2 1

[PATCH 2/7] SuperMicro H8SCM support (AMD SP5100)
by Bao, Zheng 25 Mar '11

25 Mar '11

SP5100's code is based on SB700. Change the legacy sb700 of sb7xx_51xx. Signed-off-by: Zheng Bao <zheng.bao(a)amd.com>

3 2

[PATCH 1/7] SuperMicro H8SCM support (AMD SR5650)
by Bao, Zheng 25 Mar '11

25 Mar '11

Add AMD SR56x0 support. Signed-off-by: Zheng Bao <zheng.bao(a)amd.com>

3 2

[PATCH 5/7] SuperMicro H8SCM support (AMD C32)
by Bao, Zheng 25 Mar '11

25 Mar '11

Add AMD C32 support. It is based on other existing Fam10 code. Signed-off-by: Zheng Bao <zheng.bao(a)amd.com>

2 3

What does "!! Resource didn't fit !!" mean?
by Alex G. 25 Mar '11

25 Mar '11

I'm seeing people on IRC hit this: !! Resource didn't fit !! aligned base 400 size 8 limit 200 407 needs to be <= 200 (limit) PCI: 00:07.0 18 * [0x2868 - 0x286f] io PCI: 00:07.0 18 * [0x2868 - 0x286f] io What does it mean? What are the implications? Is this a bug, something fixable? How is the limit of "0x200" decided? Alex

2 1

Conflicting default options - option ROM exec and SeaBIOS
by Alex G. 25 Mar '11

25 Mar '11

Right now, the default options in Kconfig are to pull SeaBIOS stable, AND enable option ROM execution. This leaves people with a system that has option ROMs executing twice. As you might have imagined, this results in undefined behavior. Some people are lucky and their systems still run, while others,... Default options should be changed to disable option ROM execution when SeaBIOS is built in-tree. Alex

1 0

BIOS Saviour
by Alexandr Frolov 25 Mar '11

25 Mar '11

Hello all, I am wondering about using the BIOS Saviour device (IOSS RD1). If I understood it correctly the 'original' flash card is at the bottom and 'experimental' one is at the top. The 'original' comes with IOSS RD1 kit attached to the PLCC socket and could not be removed. The experimental is an any kind of flash chip of appropriate ROM type (in my case PLCC), for example the one which was installed in my motherboard before. The experimental is removable. The reason that the origninal is used as 'back up' makes one to choose the device with approprite flash size. In my board I have SST49LF080A 8 Mbit, should I use IOSS RD1-LPC8 which is 8 MBit also? On the http://www.coreboot.org/Developer_Manual/Tools#BIOS_Savior it is said that 'This device helps to minimize the amount of hot swapping required and reduces mechanical and electrical stress on the BIOS chips'. Actually I dont fully understand this. The exerimental flash chip is still have to be unplugged to be reprogrammed by flash programmer. This phrase makes sense to me only if in-circuit reprogramming is used (like 'hot-swap'). Could anybody share his expeirience with this device? How do you use it? Is it still possible to buy? It seems that manufacturer is out of bussiness now. Best regards, Alexander

3 3

870 attempt
by Jonathan A. Kollasch 24 Mar '11

24 Mar '11

Hi, I've attempted to use the rs780 and sb800 code on a AM3 870 + SB850 board. Raminit seems to go okay, as does the first bits of ramstage. However, ramstage fails after the first two passes through rs780_enable(). It stalls in get_vid_did() reading PCI config space of device 2 (or 4). Also, the rs780 HT init code thinks the link should run at 200MHz, maybe that's related. I'm aware that this code wasn't exactly intended for the 870, but maybe someone has some hints of what to try next. Jonathan Kollasch

9 30

Re: [coreboot] [GSoC] Coreboot Spice Payload
by Hao Li 23 Mar '11

23 Mar '11

Hi Leandro, Are you talking about implementing the Spice protocol client in the coreboot? Does it rely on QEMU? I think the scenario you are talking about, or Spice protocol itself, it quite similar to RDP (Remote Desktop Protocol) protocol, isn't it? In the typical client-server model, for example, a Network Computer (with limited hardware resource) running a tiny Linux allows you to "rdesktop" to any server supporting RDP protocol. Maybe you need to think of a more appealing scenario. :) Best Regards, Hao Li Peking University --------------------------------------------------- Date: Tue, 22 Mar 2011 14:50:59 -0400 From: Leandro Dorileo <ldorileo(a)gmail.com> To: Marc Jones <marcj303(a)gmail.com> Cc: Coreboot <coreboot(a)coreboot.org> Subject: Re: [coreboot] [GSoC] Coreboot Spice Payload Message-ID: <AANLkTimkw=ArXZ8-qiZAHzT6qwSxCCup3-0X+-GNR0tJ(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi Marc On Tue, Mar 22, 2011 at 11:26 AM, Marc Jones <marcj303(a)gmail.com> wrote: > On Mon, Mar 21, 2011 at 11:49 AM, Leandro Dorileo <ldorileo(a)gmail.com> wrote: >> Hi Guys! >> >> I saw coreboot was accepted as mentoring organization for GSoC this >> year once again. I want to participate this year again as student and >> I came with the idea of a Coreboot Spice Payload. I wrote a small >> text[1] describing the idea. >> >> I would like to hear from you what you think. I have discussed with >> some guys already but would like to open it a bit more. >> >> [1] - http://vps.dorilex.net/~dorileo/coreboot-spice-payload.txt >> >> Thanks.... >> >> -- >> Leandro Dorileo > > Hi Leandro, > > Yes, coreboot is accepting student applications for GSoC again this > year. Your idea looks very interesting. I think that expanding the > payload offerings for coreboot and developing with libpayload would > make a good project. Have you thought about what kind of hardware you > would develop on? All I need is something with a ethernet, video, serial and keyboard devices - no special requirements on that. I own a coreboot supported mainboard - the one I used in 2009. But I`m considering to buy an allix.* + flexyice - I haven`t decided yet, can you suggest anything? > Who uses Spice today? Spice is mainly supported by RedHat, it was developed by Qumranet who used originally supported spice on their desktop virtualization product named SolidIce. Now RedHat has implemented spice on open source products like qemu to support server side and their enterprise desktop clients. > What type of systems or users > would take advantage of a Spice Payload? Once we`re talking about remote desktop virtualization anyone who wants do shrink the expenses with hardware and hardware upgrades on desktops. The real operating system runs in the server which off loads the heavy CPU tasks, you can have a small and cheap piece of hardware capable of running any modern and powerful desktop operating system. -- Leandro Dorileo

2 3

← Newer
1
...
4
5
6
7
8
9
10
...
21
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 March 2011