coreboot April 2007

coreboot@coreboot.org

76 participants
281 discussions

[LinuxBIOS] r2613 build service
by LinuxBIOS information 22 Apr '07

22 Apr '07

Dear LinuxBIOS readers! This is the automated build check service of LinuxBIOS. The developer "uwe" checked in revision 2613 to the LinuxBIOS source repository and caused the following changes: Change Log: Update URL for the PCI IRQ Routing Table Specification (trivial). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Build Log: Compilation of arima:hdama is still broken Compilation of gigabyte:m57sli is still broken Compilation of ibm:e325 is still broken Compilation of ibm:e326 is still broken Compilation of iwill:dk8_htx is still broken Compilation of iwill:dk8s2 is still broken Compilation of iwill:dk8x is still broken Compilation of nvidia:l1_2pvv is still broken Compilation of tyan:s2912 is still broken 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 will be backed out. Yours truely, LinuxBIOS automatic build system

1 0

[LinuxBIOS] Fwd: Intel Southbridge ROM Protection mechanism
by Darmawan Salihun 22 Apr '07

22 Apr '07

---------- Forwarded message ---------- From: Darmawan Salihun <darmawan.salihun(a)gmail.com> Date: Apr 22, 2007 8:15 AM Subject: Re: [LinuxBIOS] Intel Southbridge ROM Protection mechanism To: Stefan Reinauer <stepan(a)coresystems.de> On 4/20/07, Stefan Reinauer <stepan(a)coresystems.de> wrote: > > * Darmawan Salihun <darmawan.salihun(a)gmail.com> [070419 19:22]: > > the matter, does Intel ICH5 southbridge (or other newer Inte > southbridge) > > still protects (probably mirrors) the last 8KB block (bootblock) in the > BIOS > > chip even when the protection bits in Block Locking Registers (BLRs) has > been > > disabled? > > I experienced weird results between several flashing attempts using > > flashrom in Linux. SOme succeeded, some retain the original values. > Anyone has > > an explanation on the issue? > > Some flash chips support "write protecting" their boot block (and/or other > blocks). I think the data sheets have more details on this. > > What flash chip are you using? > Winbond W39V040FA Usually if the south bridge or a GPIO does the protection, you'd be able > to write all or nothing. AFAIK > > At some points I couldn't write at all. Maybe there is a a timing issue in the code that I added. Gonna check it again. > -- > coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. > Tel.: +49 761 7668825 • Fax: +49 761 7664613 > Email: info(a)coresystems.de • http://www.coresystems.de/ > -- -------------------------------------------------------------------- -= Human knowledge belongs to the world =- -- -------------------------------------------------------------------- -= Human knowledge belongs to the world =-

1 0

[LinuxBIOS] r2613 - trunk/LinuxBIOSv2/util/getpir
by svn＠openbios.org 22 Apr '07

22 Apr '07

Author: uwe Date: 2007-04-22 03:17:36 +0200 (Sun, 22 Apr 2007) New Revision: 2613 Modified: trunk/LinuxBIOSv2/util/getpir/code_gen.c Log: Update URL for the PCI IRQ Routing Table Specification (trivial). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/LinuxBIOSv2/util/getpir/code_gen.c =================================================================== --- trunk/LinuxBIOSv2/util/getpir/code_gen.c 2007-04-21 18:17:50 UTC (rev 2612) +++ trunk/LinuxBIOSv2/util/getpir/code_gen.c 2007-04-22 01:17:36 UTC (rev 2613) @@ -9,7 +9,7 @@ " * Contains the IRQ Routing Table dumped directly from your\n", " * memory, which BIOS sets up.\n", " *\n", - " * Documentation at: http://www.microsoft.com/hwdev/busbios/PCIIRQ.HTM\n */\n\n", + " * Documentation at: http://www.microsoft.com/whdc/archive/pciirq.mspx\n */\n\n", "#ifdef GETPIR\n", "#include \"pirq_routing.h\"\n", "#else\n"

1 0

[LinuxBIOS] r2612 build service
by LinuxBIOS information 21 Apr '07

21 Apr '07

Dear LinuxBIOS readers! This is the automated build check service of LinuxBIOS. The developer "uwe" checked in revision 2612 to the LinuxBIOS source repository and caused the following changes: Change Log: Make the output of getpir look a bit less crappy (trivial). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Build Log: Compilation of arima:hdama is still broken Compilation of gigabyte:m57sli is still broken Compilation of ibm:e325 is still broken Compilation of ibm:e326 is still broken Compilation of iwill:dk8_htx is still broken Compilation of iwill:dk8s2 is still broken Compilation of iwill:dk8x is still broken Compilation of nvidia:l1_2pvv is still broken Compilation of tyan:s2912 is still broken 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 will be backed out. Yours truely, LinuxBIOS automatic build system

1 0

[LinuxBIOS] r2612 - trunk/LinuxBIOSv2/util/getpir
by svn＠openbios.org 21 Apr '07

21 Apr '07

Author: uwe Date: 2007-04-21 20:17:50 +0200 (Sat, 21 Apr 2007) New Revision: 2612 Modified: trunk/LinuxBIOSv2/util/getpir/code_gen.c Log: Make the output of getpir look a bit less crappy (trivial). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/LinuxBIOSv2/util/getpir/code_gen.c =================================================================== --- trunk/LinuxBIOSv2/util/getpir/code_gen.c 2007-04-14 16:34:32 UTC (rev 2611) +++ trunk/LinuxBIOSv2/util/getpir/code_gen.c 2007-04-21 18:17:50 UTC (rev 2612) @@ -3,10 +3,13 @@ #include "pirq_routing.h" static char *preamble[] = { - "/* This file was generated by getpir.c, do not modify! \n (but if you do, please run checkpir on it to verify)\n", - " * Contains the IRQ Routing Table dumped directly from your memory, which BIOS sets up\n", + "/* This file was generated by getpir.c, do not modify!\n", + " * (but if you do, please run checkpir on it to verify)\n", " *\n", - " * Documentation at : http://www.microsoft.com/hwdev/busbios/PCIIRQ.HTM\n*/\n\n", + " * Contains the IRQ Routing Table dumped directly from your\n", + " * memory, which BIOS sets up.\n", + " *\n", + " * Documentation at: http://www.microsoft.com/hwdev/busbios/PCIIRQ.HTM\n */\n\n", "#ifdef GETPIR\n", "#include \"pirq_routing.h\"\n", "#else\n" @@ -33,7 +36,7 @@ while (*code) fprintf(fpir, "%s", *code++); - fprintf(fpir, "\t32+16*%d, /* there can be total %d devices on the bus */\n", + fprintf(fpir, "\t32+16*%d, /* There can be total %d devices on the bus */\n", ts, ts); fprintf(fpir, "\t0x%02x, /* Where the interrupt router lies (bus) */\n", rt->rtr_bus); @@ -46,7 +49,7 @@ fprintf(fpir, "\t%#x, /* Crap (miniport) */\n", rt->miniport_data); fprintf(fpir, "\t{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }, /* u8 rfu[11] */\n"); - fprintf(fpir, "\t%#x, /* u8 checksum , this hase to set to some value that would give 0 after the sum of all bytes for this structure (including checksum) */\n", + fprintf(fpir, "\t%#x, /* u8 checksum. This has to be set to some\n value that would give 0 after the sum of all\n bytes for this structure (including checksum) */\n", rt->checksum); fprintf(fpir, "\t{\n"); fprintf(fpir, "\t\t/* bus, dev|fn, {link, bitmap}, {link, bitmap}, {link, bitmap}, {link, bitmap}, slot, rfu */\n");

1 0

[LinuxBIOS] #77: hang on the "Jumping to LinuxBIOS" step on via epia-m with 4-chip 128Mbyte ddr module
by LinuxBIOS 21 Apr '07

21 Apr '07

#77: hang on the "Jumping to LinuxBIOS" step on via epia-m with 4-chip 128Mbyte ddr module -------------------------------------------------------------+-------------- Reporter: bam80(a)mail.ru | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: code | Version: v2 Keywords: via epia-m ram init jumping to linuxbios hang | Dependencies: Patchstatus: there is no patch | -------------------------------------------------------------+-------------- with 4-chip 128Mbyte single-sided ddr-400 module via epia-m hangs on the "Jumping to LinuxBIOS". With legacy via's bios no problem with this module. After changing to 256Mb 8-chips single-sided module the problem gone away. 512Mb 16-chips dual-sided module works also. 128mb module's chips have following label: KINGMAX KDL668P4LA-50 I used linuxbios image r2611 taken from http://qa.linuxbios.org/overview.php -- Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/77> LinuxBIOS <http://www.linuxbios.org/>

1 5

[LinuxBIOS] Iwill DK8-HTX now runs under LinuxBIOS r2587 (Thanks)
by Alexei I. Adamovich 21 Apr '07

21 Apr '07

Hi! At last I've got Normal image loading (with release 2587). Seems, the important difference between processes of Normal and Fallback images loading is that former obey CMOS data and later--not (uses compiled-in defaults). Is this written somewhere? So tweaking the CMOS data--leaved by the standard BIOS--with lxbios I get able to load normally. Thanks to all who replied, in particular: Stefan Reinauer Perry Wang Peter Stuge BTW, VGA problem was resolved also (with Anton Borisov's AmiDeco tool). Onboard VGA rom size is indeed 36K--not 32 got with dd. Best regards, Alexei I. Adamovich

2 3

[LinuxBIOS] You've got to be crazy when...
by roger 21 Apr '07

21 Apr '07

You take the time to write an entire o/s in Assembly. :-) http://www.hermann-uwe.de/ http://www.menuetos.net/ -- Roger http://www.eskimo.com/~roger/index.html Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61 Fri Apr 20 13:14:21 PDT 2007

4 3

[LinuxBIOS] DFI P2XBL Motherboard Target (440BX)
by roger 20 Apr '07

20 Apr '07

I just built Uwe's s1846 target and saw no output on /dev/ttyS* (serial port). What differences should I be concerned about using the s1846 target for this motherboard 440BX based motherboard in order to get debug output? (Box acts like no bios is plugged into the motherboard.) (When I get time, I'll yank parts out of this Tyan 1832DL to see if the s1832 built flash boots on it.) -- Roger http://www.eskimo.com/~roger/index.html Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61 Thu Apr 19 04:06:55 PDT 2007

3 8

[LinuxBIOS] Instructions: GA-M57SLI-S4 dual linux bios
by ST 20 Apr '07

20 Apr '07

Hi As promised you will find the instructions at: http://private.vlsi.informatik.tu-darmstadt.de/st/instructions.html If you have any suggestions/corrections whatever please let me know. I haven't had the time testing flashing the flash-roms, but i can switch between the two chips which have currently differen original bios versions on them. Since i am going to start tinkering with linux bios real soon now, i would like to know if the instructions compiled by Ward are still the way to go? ST

5 12

← Newer
1
...
7
8
9
10
11
12
13
...
29
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 2007