coreboot May 2008

coreboot@coreboot.org

79 participants
387 discussions

Allow payloads to write over Coreboot tables, add a warning
by Myles Watson 22 May '08

22 May '08

This is a simple patch which allows payloads to be placed in memory in the range of 0xf0000-0x100000, where the Coreboot tables live in v2. As long as the payload doesn't need the tables, it seems harmless, so why not just print a warning? This allows v2 to load "legacybios" without having to have a separate loader. Signed-off-by: Myles Watson <mylesgw(a)gmail.com> Thanks, Myles

3 5

OpenExpo 2008 participation deadline
by Carl-Daniel Hailfinger 22 May '08

22 May '08

Hi, if we want to have a booth or talks at *the OpenExpo in Zürich, Switzerland, 24./25. September 2008, we'd better hurry. The application deadline is May 31.* http://www.openexpo.ch/openexpo-2008-zuerich/call-for-participation/ I don't have time to apply for a booth because I'm completely busy with LinuxTag preparations, but since OpenExpo hosts the Hackontest where coreboot is one of the candidates, we might want to combine efforts and make sure visitors seeing us participating in Hackontest can also ask questions at a booth. Regards, Carl-Daniel

1 0

r3343 - trunk/coreboot-v2/src/boot
by svn＠coreboot.org 22 May '08

22 May '08

Author: myles Date: 2008-05-22 00:10:38 +0200 (Thu, 22 May 2008) New Revision: 3343 Modified: trunk/coreboot-v2/src/boot/elfboot.c Log: This is a simple patch which allows payloads to be placed in memory in the range of 0xf0000-0x100000, where the Coreboot tables live in v2. As long as the payload doesn't need the tables, it seems harmless, so why not just print a warning? This allows v2 to load "legacybios" without having to have a separate loader. Signed-off-by: Myles Watson <mylesgw(a)gmail.com> It'll be fine for testing and doesn't really break anything that did work before... Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/coreboot-v2/src/boot/elfboot.c =================================================================== --- trunk/coreboot-v2/src/boot/elfboot.c 2008-05-21 13:49:03 UTC (rev 3342) +++ trunk/coreboot-v2/src/boot/elfboot.c 2008-05-21 22:10:38 UTC (rev 3343) @@ -227,6 +227,10 @@ if ((mtype == LB_MEM_RAM) && (start < mend) && (end > mstart)) { break; } + if ((mtype == LB_MEM_TABLE) && (start < mend) && (end > mstart)) { + printk_err("Payload is overwriting Coreboot tables.\n"); + break; + } } if (i == mem_entries) { printk_err("No matching ram area found for range:\n");

1 0

New Board?: CK804K8MA-KS
by Klaus Zimmermann 21 May '08

21 May '08

Hello *, I'd like to start support for my old board, the CK804K8MA-KS On IRC I was told to post 'lspci -tvnn', 'superiotool -dV' and I'll add 'lspci -vvv'. I also got my bios (a SST49LF004B 4Mbit Flash) socketed and am now waiting for my spare chips to arrive. Is there something I can do inbetween? What's next? Cheers, Klaus

5 5

How to test RAM beyond 640 kByte boundary
by llandre 21 May '08

21 May '08

I have a question about the ram_check function. All the board specific codes invoke it like this: ram_check(0x00000000, 640 * 1024); I had a look with JTAG debugger and indeed the RAM beyond 640 KByte boundary is not accessible. Why? Is it possible to enable and test all the RAM available? TIA, llandre DAVE Electronics System House - R&D Department web: http://www.dave.eu email: r&d2(a)dave-tech.it

4 6

r3342 build service
by coreboot information 21 May '08

21 May '08

Dear coreboot readers! This is the automated build check service of coreboot. The developer "uwe" checked in revision 3342 to the coreboot source repository and caused the following changes: Change Log: Add KEY_ESC (trivial). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Build Log: Compilation of via:epia-cn is still broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3342&device=epia-cn&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

buildrom
by qchwu 21 May '08

21 May '08

The first question in buildrom is solved,thanks for ward.But i encount a new question during the make processing.The following is the wrong message: ---------------------------------------------------- make[1]:Leaving directory "/bios/buildrom/buildrom-devel/work/nrv2b/svn" Unpacking filo... patching filo... /bios/buildrom/buildrom-devel/doquilt.sh:line 39:quilt:command not found make:***[/bios/buildrom-devel/work/filo/stamps/.patched] 错误127 ------------------------------------------------------ Ithink the fault is caused by lake of command "quilt". I download the quilt-0.46.tar.gz and install it.Then, I make it ,the following messages appear. ------------------------------------------------------- Unpacking filo... Patching filo... Applying patch make.patch Now at patch make.patch make[1]: Entering directory `/bios/buildrom/buildrom-devel/work/filo/svn' rm -f include/arch ln -s ../i386/include include/arch test -f Config && mv Config Config.bak || true cat defconfig i386/defconfig >>Config *** Default Config file is created *** *** Now you examine this file and edit it as you like *** make[1]: Leaving directory `/bios/buildrom/buildrom-devel/work/filo/svn' Building filo... make[1]: Entering directory `/bios/buildrom/buildrom-devel/work/filo/svn' Makefile:63: 警告：覆盖关于目标“clean”的命令 makerules:46: 警告：忽略关于目标“clean”的旧命令 echo '#define PROGRAM_NAME "FILO"' > main/version.h echo '#define PROGRAM_VERSION "0.5 (root@localhost) Wed May 21 03:25:00 CST 2008"' >> main/version.h make -C main make[2]: Entering directory `/bios/buildrom/buildrom-devel/work/filo/svn/main' /bin/echo -e '/* GENERATED FILE, DO NOT EDIT */\n' >../config.h sed -e 's/#.*//' -e '/=/!d' -e 's/$[^[:space:]]*$[[:space:]]*=[[:space:]]*$.*$.*/#define \1 \2/' -e 's/^#define $[^ ]*$ 0$/#undef \1/' ../Config >>../config.h gcc -m32 -nostdinc -Os -isystem /bios/buildrom/buildrom-devel/staging/include -isystem /include -fno-stack-protector -Wall -Os -fomit-frame-pointer -fno-common -ffreestanding -fno-strict-aliasing -Wno-pointer-sign -Wno-unused - nostdinc -imacros ../config.h -I../include -I安装：/usr/local/gcc-4.2.2/lib/gcc/i386-redhat-linux/4.2.2/include -MD -c filo.c -o filo.o 在包含自 filo.c：1 的文件中: ../include/lib.h:4:20: 错误：stddef.h：没有那个文件或目录 In file included from filo.c:1: ../include/lib.h:36: 错误：expected ‘)’ before ‘size’ ../include/lib.h:38: 错误：expected ‘)’ before ‘nmemb’ ../include/lib.h:39: 错误：expected declaration specifiers or ‘...’ before ‘size_t’ ../include/lib.h:42: 错误：expected ‘)’ before ‘size’ ../include/lib.h:46: 错误：expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘strnlen’ ../include/lib.h:47: 错误：expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘strlen’ ../include/lib.h:49: 错误：expected declaration specifiers or ‘...’ before ‘size_t’ ../include/lib.h:50: 错误：expected declaration specifiers or ‘...’ before ‘size_t’ ../include/lib.h:51: 错误：expected declaration specifiers or ‘...’ before ‘size_t’ ../include/lib.h:52: 错误：expected declaration specifiers or ‘...’ before ‘size_t’ make[2]: *** [filo.o] 错误 1 make[2]: Leaving directory `/bios/buildrom/buildrom-devel/work/filo/svn/main' make[1]: *** [main/builtin.o] 错误 2 make[1]: Leaving directory `/bios/buildrom/buildrom-devel/work/filo/svn' make: *** [/bios/buildrom/buildrom-devel/work/filo/svn/filo.elf] 错误 2 [root@localhost buildrom-devel]# ----------------------------------------------------- the "make distclean"is used before the make.How can i clear this fault. thanks, chenghu qing

2 1

buildrom
by qchwu 21 May '08

21 May '08

I set the menuconfig for AMD and FILO for coreboot-V2,when I make it,the wrong message is following : -------------------------------------- gcc -m32 -nostdinc -Os -isystem /bios/buildrom/buildrom-devel/staging/include -isystem /include -fno-stack-protector -Wall -Os -fomit-frame-pointer -fno-common -ffreestanding -fno-strict-aliasing -Wno-pointer-sign -Wno-unused -nostdinc -imacros ../config.h -I../include -I安装：/usr/local/gcc-4.2.2/lib/gcc/i386-redhat-linux/4.2.2/include -MD -c filo.c -o filo.o 在包含自 filo.c：1 的文件中: ../include/lib.h:4:20: error：stddef.h：file is not found. In file included from filo.c:1: filo.c: 在函数‘init’中： filo.c:36: 警告：隐式声明函数‘delay’ make[2]: *** [filo.o] 错误 1 make[2]: Leaving directory `/bios/buildrom/buildrom-devel/work/filo/svn/main' make[1]: *** [main/builtin.o] 错误 2 make[1]: Leaving directory `/bios/buildrom/buildrom-devel/work/filo/svn' make: *** [/bios/buildrom/buildrom-devel/work/filo/svn/filo.elf] 错误 2 --------------------------------------- In the message, the "stddef.h" is not in the "/bios/buildrom/buildrom-devel/work/filo/svn/include".But,the work folder is created by "make".So,it seems that the "stddef.h" was not created. How can i fix this bug? thanks. chenghu qin

2 1

r3342 - trunk/payloads/coreinfo
by svn＠coreboot.org 21 May '08

21 May '08

Author: uwe Date: 2008-05-21 15:49:03 +0200 (Wed, 21 May 2008) New Revision: 3342 Modified: trunk/payloads/coreinfo/coreinfo.c Log: Add KEY_ESC (trivial). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/payloads/coreinfo/coreinfo.c =================================================================== --- trunk/payloads/coreinfo/coreinfo.c 2008-05-21 07:10:15 UTC (rev 3341) +++ trunk/payloads/coreinfo/coreinfo.c 2008-05-21 13:49:03 UTC (rev 3342) @@ -22,6 +22,8 @@ #define SCREEN_Y 25 #define SCREEN_X 80 +#define KEY_ESC 27 + extern struct coreinfo_module cpuinfo_module; extern struct coreinfo_module pci_module; extern struct coreinfo_module coreboot_module; @@ -256,7 +258,7 @@ } } - if (key == 0x1B) + if (key == KEY_ESC) return; handle_category_key(&categories[curwin], key);

1 0

A-trend ATC-6240 - sorry for late
by shadow . 21 May '08

21 May '08

hi, sorry for late lspci -tvnn : -[0000:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] +-01.0-[0000:01]----00.0 ATI Technologies Inc Rage 128 Pro Ultra TF [1002:5446] +-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] +-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] +-07.2 Intel Corporation 82371AB/EB/MB PIIX4 USB [8086:7112] +-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] -0c.0 Ensoniq ES1371 [AudioPCI-97] [1274:1371] superiotool -dV : superiotool r3293 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0xffff, rev=0xff Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Found Winbond W83627HF/F/HG/G (id=0x52, rev=0xf4) at 0x3f0 Register dump: idx 02 07 20 21 22 23 24 25 26 28 29 2a 2b 2c 2e 2f val ff 0b 52 f4 ff fe c0 00 00 00 ff 00 00 00 00 ff def 00 NA 52 NA ff 00 MM 00 00 00 00 7c c0 00 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 01 03 f0 06 02 0c 00 ff 00 00 def 01 03 f0 06 02 0e 00 ff 00 00 LDN 0x01 (Parallel port) idx 30 60 61 70 74 f0 val 01 03 78 07 03 02 def 01 03 78 07 04 3f LDN 0x02 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 01 03 f8 04 00 LDN 0x03 (COM2) idx 30 60 61 70 f0 f1 val 01 02 f8 03 00 00 def 01 02 f8 03 00 00 LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 72 f0 val 01 00 60 00 64 01 0c 42 def 01 00 60 00 64 01 0c 80 LDN 0x06 (Consumer IR) idx 30 60 61 70 val 00 00 00 00 def 00 00 00 00 LDN 0x07 (Game port, MIDI port, GPIO 1) idx 30 60 61 62 63 70 f0 f1 f2 val 00 00 00 00 00 00 ff 00 ff def 00 02 01 03 30 09 ff 00 00 LDN 0x08 (GPIO 2, Watchdog timer) idx 30 f0 f1 f2 f3 f5 f6 f6 f7 val 01 00 ff 00 00 ff ff ff ff def 00 ff 00 00 00 00 00 00 00 LDN 0x09 (GPIO 3) idx 30 f0 f1 f2 f3 val 00 ff ff ff ff def 00 ff 00 00 00 LDN 0x0a (ACPI) idx 30 70 e0 e1 e2 e3 e4 e5 e6 e7 f0 f1 f3 f4 f6 f7 f9 fe ff val 00 00 00 00 08 00 00 00 00 00 00 8f 37 00 00 00 00 00 00 def 00 00 00 00 NA NA 00 00 00 00 00 00 00 00 00 00 00 00 00 LDN 0x0b (Hardware monitor) idx 30 60 61 70 f0 val 01 ff ff ff ff def 00 00 00 00 00 Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff getpir : # make gcc -O2 -D_GNU_SOURCE -DGETPIR -Wall -c -o getpir.o getpir.c gcc -O2 -D_GNU_SOURCE -DGETPIR -Wall -c -o checksum.o checksum.c gcc -O2 -D_GNU_SOURCE -DGETPIR -Wall -c -o code_gen.o code_gen.c gcc -O2 -D_GNU_SOURCE -DGETPIR -Wall -o getpir getpir.o checksum.o code_gen.o ./getpir Probing PIRQ table in memory. Found PCI IRQ routing table signature at 0xfdef0. Validating... checksum is ok. Creating irq_tables.c ... Done, you can move the file to the coreboot tree now. gcc -O2 -D_GNU_SOURCE -DGETPIR -Wall -c -o irq_tables.o irq_tables.c irq_tables.c:42: error: expected identifier or ‘(’ before ‘unsigned’ make: *** [irq_tables.o] Error 1 # ./getpir Probing PIRQ table in memory. Found PCI IRQ routing table signature at 0xfdef0. Validating... checksum is ok. Creating irq_tables.c ... Done, you can move the file to the coreboot tree now. getpir build with error but it seems generate the file so it is: cat ~/getpir/irq_tables.c : /* This file was generated by getpir.c, do not modify! * (but if you do, please run checkpir on it to verify) * * Contains the IRQ Routing Table dumped directly from your * memory, which BIOS sets up. * * Documentation at: http://www.microsoft.com/whdc/archive/pciirq.mspx */ #ifdef GETPIR #include "pirq_routing.h" #else #include <arch/pirq_routing.h> #endif const struct irq_routing_table intel_irq_routing_table = { PIRQ_SIGNATURE, /* u32 signature */ PIRQ_VERSION, /* u16 version */ 32+16*7, /* There can be total 7 devices on the bus */ 0x00, /* Where the interrupt router lies (bus) */ (0x07<<3)|0x0, /* Where the interrupt router lies (dev) */ 0xc20, /* IRQs devoted exclusively to PCI usage */ 0x8086, /* Vendor */ 0x7000, /* Device */ 0, /* Crap (miniport) */ { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }, /* u8 rfu[11] */ 0x44, /* u8 checksum. This has to be set to some value that would give 0 after the sum of all bytes for this structure (including checksum) */ { /* bus, dev|fn, {link, bitmap}, {link, bitmap}, {link, bitmap}, {link, bitmap}, slot, rfu */ {0x00,(0x0a<<3)|0x0, {{0x60, 0xdeb8}, {0x61, 0xdeb8}, {0x62, 0xdeb8}, {0x63, 0x0deb8}}, 0x1, 0x0}, {0x00,(0x0e<<3)|0x0, {{0x63, 0xdeb8}, {0x60, 0xdeb8}, {0x61, 0xdeb8}, {0x62, 0x0deb8}}, 0x2, 0x0}, {0x00,(0x0b<<3)|0x0, {{0x61, 0xdeb8}, {0x62, 0xdeb8}, {0x63, 0xdeb8}, {0x60, 0x0deb8}}, 0x3, 0x0}, {0x00,(0x0c<<3)|0x0, {{0x62, 0xdeb8}, {0x63, 0xdeb8}, {0x60, 0xdeb8}, {0x61, 0x0deb8}}, 0x4, 0x0}, {0x00,(0x0d<<3)|0x0, {{0x63, 0xdeb8}, {0x60, 0xdeb8}, {0x61, 0xdeb8}, {0x62, 0x0deb8}}, 0x5, 0x0}, {0x00,(0x07<<3)|0x1, {{0x60, 0xdeb8}, {0x61, 0xdeb8}, {0x62, 0xdeb8}, {0x63, 0x0deb8}}, 0x0, 0x0}, {0x00,(0x01<<3)|0x0, {{0x60, 0xdeb8}, {0x61, 0xdeb8}, {0x62, 0xdeb8}, {0x63, 0x0deb8}}, 0x0, 0x0}, } }; unsigned long write_pirq_routing_table(unsigned long addr) { return copy_pirq_routing_table(addr); } Do you have a null-modem cable for debugging and a spare ROM chip you can use for testing coreboot? i have an old RS-232 serial convertor cabel modem (25-pin to 9-pin) use it for my external modem, can i use it , if can not i will buy one . yes i have spare ROM chip . thanks . ------------------------- Get the latest football news, matches results, upcoming games, team standings and much more…. All at Maktoob Football http://www.maktoob.com/football

2 2

← Newer
1
...
9
10
11
12
13
14
15
...
39
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 May 2008