coreboot April 2008

coreboot@coreboot.org

75 participants
404 discussions

Re: [coreboot] [PATCH] v3: fix bugs in Geode LX RAMinit
by Mart Raudsepp 18 Apr '08

18 Apr '08

> On Fri, Apr 18, 2008 at 7:57 AM, Ward Vandewege <ward(a)gnu.org> wrote: > >> >> I don't have a dbe62 but I do have alix.1c and 2c3. Have we established >> if >> the MFGPT problem manifests itself on all LX boards? > > only seen on my alix so far but that's just because I'm not really > booting on the dbe62 yet; still trying to figure out how we load the > dbe62 up when the onboard flash is empty (and using the factory bios > to load it and then switching to coreboot is not an acceptable answer > :-) With the help of the LPC dongle for instance? I typically rarely care about what is on the onboard flash - I only burn something different on there for convenience if I need to boot the same firmware many times in a row, which doesn't happen exactly often during coreboot testing. Other times, just booting off the dongle. Regards, Mart Raudsepp Artec Design LLC

2 1

Re: [coreboot] [PATCH] v3: fix bugs in Geode LX RAMinit
by Mart Raudsepp 18 Apr '08

18 Apr '08

> On Fri, Apr 18, 2008 at 3:09 PM, Mart Raudsepp > <mart.raudsepp(a)artecdesign.ee> wrote: > >> With the help of the LPC dongle for instance? >> I typically rarely care about what is on the onboard flash - I only >> burn >> something different on there for convenience if I need to boot the same >> firmware many times in a row, which doesn't happen exactly often during >> coreboot testing. Other times, just booting off the dongle. >> > > I would feel much more comfortable having something that does not > require cracking the case open. how do we do that? I think etherboot > more and more is the answer. Even though I don't really like it. I've been also able to get the dongle working with just having the small left side of the ThinCan removed, but I don't deal with boards that are in cases not that often either. The LPC connection is on the very side, so the cable fits in there with some twisting, but that's probably more risky than having a bare mainboard, unless you have a header soldered on the LPC connection, in which case I'm not sure if the ribbon cable can be attached without removing the top of the case. Btw, if the top part of the case is removed, you just need to pay attention to the bottom - the front side supporting the front side of the board is gone then and could shortcircuit things from the bottom, so need a paper between the case and board or something like that if don't want to remove the whole case. Without the dongle, you obviously need a way to flash the onboard ROM (which could wear out with lots of work), and flashrom since rev3110 or so should work great for that. So whatever means you can do to get into a Linux system that just has msr/mem support and flashrom, be it over etherboot, included in the dongle in 4MB memory mode (v3 got a patch committed recently to enable that), residing in the NAND flash, or whatever else can be conceived and booted with whatever onboard ROM is burnt in before reflashing :) Regards, Mart Raudsepp Artec Design LLC

1 0

[PATCH] Simplify check for --build-id linker option
by Ed Swierk 18 Apr '08

18 Apr '08

This patch replaces buildtarget's check for --build-id with something a bit less awkward (pun intended). Signed-off-by: Ed Swierk <eswierk(a)arastra.com>

2 3

[PATCH] Use cross-compiler when checking for --build-id
by Ed Swierk 18 Apr '08

18 Apr '08

This patch alters buildtarget to invoke the cross-compiler when checking for --build-id, if the user has specified one by setting CC in the environment; there's no point in checking the native linker in this case. Signed-off-by: Ed Swierk <eswierk(a)arastra.com>

2 2

r3243 - trunk/coreboot-v2/targets
by svn＠coreboot.org 18 Apr '08

18 Apr '08

Author: eswierk Date: 2008-04-18 22:48:22 +0200 (Fri, 18 Apr 2008) New Revision: 3243 Modified: trunk/coreboot-v2/targets/buildtarget Log: Replace buildtarget's check for --build-id with something a bit less awkward (pun intended). Signed-off-by: Ed Swierk <eswierk(a)arastra.com> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/coreboot-v2/targets/buildtarget =================================================================== --- trunk/coreboot-v2/targets/buildtarget 2008-04-18 20:47:11 UTC (rev 3242) +++ trunk/coreboot-v2/targets/buildtarget 2008-04-18 20:48:22 UTC (rev 3243) @@ -69,9 +69,7 @@ rm -rf .$$.tmp -$CC -Wl,--help | awk '{for (i=1;i<=NF;i++) if ($i ~ /build-id/){n++} }; END {exit n}' -build_id=$? -if [ $build_id -ge 1 ] ; then +if $CC -Wl,--help | grep -q build-id; then EXTRA_LFLAGS="$EXTRA_LFLAGS -Wl,--build-id=none" fi

1 0

r3242 - trunk/coreboot-v2/targets
by svn＠coreboot.org 18 Apr '08

18 Apr '08

Author: eswierk Date: 2008-04-18 22:47:11 +0200 (Fri, 18 Apr 2008) New Revision: 3242 Modified: trunk/coreboot-v2/targets/buildtarget Log: Alter buildtarget to invoke the cross-compiler when checking for --build-id, if the user has specified one by setting CC in the environment; there's no point in checking the native linker in this case. Signed-off-by: Ed Swierk <eswierk(a)arastra.com> Acked-by: Ronald G. Minnich <rminnich(a)gmail.com> Modified: trunk/coreboot-v2/targets/buildtarget =================================================================== --- trunk/coreboot-v2/targets/buildtarget 2008-04-16 00:46:08 UTC (rev 3241) +++ trunk/coreboot-v2/targets/buildtarget 2008-04-18 20:47:11 UTC (rev 3242) @@ -69,7 +69,7 @@ rm -rf .$$.tmp -ld --help | awk '{for (i=1;i<=NF;i++) if ($i ~ /build-id/){n++} }; END {exit n}' +$CC -Wl,--help | awk '{for (i=1;i<=NF;i++) if ($i ~ /build-id/){n++} }; END {exit n}' build_id=$? if [ $build_id -ge 1 ] ; then EXTRA_LFLAGS="$EXTRA_LFLAGS -Wl,--build-id=none"

1 0

Re: [coreboot] using grub with coreboot
by Patrick Georgi 18 Apr '08

18 Apr '08

Am Freitag, den 18.04.2008, 20:20 +0400 schrieb Mikhail Savchenko: > Hi and thank you again for help, no I'm ok with getting grub.cfg and > other files on diskimage, but can I ask you one more question? > The question is - how can I configure to boot kernel from disk, > standards way, or any special issues, cause if right understand it's Write a grub.cfg that loads the kernel from disk, done :-) I want to add a configure flag to grub2, to make it look for grub.cfg on the hard disk by default. > ata.mod for this thing, but may be any special configs, at the moment > I'm only try get kernel from diskimage, cause sata disk in my test > server doesn't support (?) That's the hard bit, as there is no driver for the various sata devices yet. An AHCI module for grub2 would be useful, but it still won't cover the non-AHCI controllers - and worst of all, it doesn't exist yet. Regards, Patrick

1 0

[buildrom] [PATCH] fix lar building for v3
by Ward Vandewege 18 Apr '08

18 Apr '08

-- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

2 3

r148 - buildrom-devel
by svn＠coreboot.org 18 Apr '08

18 Apr '08

Author: ward Date: 2008-04-18 18:07:53 +0200 (Fri, 18 Apr 2008) New Revision: 148 Modified: buildrom-devel/Makefile Log: A few fixes for the v3 LAR handling: use LAR_PAYLOAD_FLAGS for all payloads, and remove duplicate payload addition. Signed-off-by: Ward Vandewege <ward(a)gnu.org> Acked-by: Ronald G. Minnich <rminnich(a)gmail.com> Modified: buildrom-devel/Makefile =================================================================== --- buildrom-devel/Makefile 2008-04-17 15:21:08 UTC (rev 147) +++ buildrom-devel/Makefile 2008-04-18 16:07:53 UTC (rev 148) @@ -84,15 +84,14 @@ rom: $(HOSTTOOLS-y) payload $(COREBOOT-y) @ cp $(CBV3_OUTPUT) $(TARGET_ROM_FILE) - @ $(STAGING_DIR)/bin/lar $(LAR_PAYLOAD_FLAGS) $(TARGET_ROM_FILE) $(CBV3_PAYLOAD_TARGET):normal/payload ifeq ($(CONFIG_VSA_LEGACY),y) - @ $(STAGING_DIR)/bin/lar -a $(TARGET_ROM_FILE) $(SOURCE_DIR)/amd_vsa_lx_1.01.bin:blob/vsa + @ $(STAGING_DIR)/bin/lar $(LAR_PAYLOAD_FLAGS) $(TARGET_ROM_FILE) $(SOURCE_DIR)/amd_vsa_lx_1.01.bin:blob/vsa endif ifeq ($(CONFIG_VSA_OPENVSA),y) @ echo "Adding OpenVSA: TODO FIXME - let's actually implement this?" endif @ for file in `ls $(ROM_DIR)`; do \ - $(STAGING_DIR)/bin/lar -a $(TARGET_ROM_FILE) $(ROM_DIR)/$$file:$$file; \ + $(STAGING_DIR)/bin/lar $(LAR_PAYLOAD_FLAGS) $(TARGET_ROM_FILE) $(ROM_DIR)/$$file:$$file; \ done @ $(STAGING_DIR)/bin/lar -z $(TARGET_ROM_FILE) endif

1 0

Alix2c3 MB support (Geode LX800)
by Darmawan Salihun 18 Apr '08

18 Apr '08

Hi Guys, I saw that Alix1.c is supported by Coreboot v3. Is it hard to port the support for Alix2c3? The chipset is the same with Alix1.c. Or is it better to port Coreboot v2 to this board? The board comes with tinyBIOS but if I couldn't handle the current problem with tinyBIOS, I might port coreboot instead. Regards, Darmawan Salihun -------------------------------------------------------------------- -= Human knowledge belongs to the world =-

3 4

← Newer
1
...
18
19
20
21
22
23
24
...
41
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 April 2008