coreboot June 2009

coreboot@coreboot.org

84 participants
500 discussions

[flashrom] r617 - trunk
by svn＠coreboot.org 21 Jun '09

21 Jun '09

Author: uwe Date: 2009-06-21 22:50:22 +0200 (Sun, 21 Jun 2009) New Revision: 617 Modified: trunk/board_enable.c Log: Add board-enable for Elitegroup K7VTA3 (trivial, tested on hardware). The board can decode 256 KB only (i.e., not 512 KB) it seems. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/board_enable.c =================================================================== --- trunk/board_enable.c 2009-06-21 15:45:34 UTC (rev 616) +++ trunk/board_enable.c 2009-06-21 20:50:22 UTC (rev 617) @@ -729,7 +729,9 @@ } /** - * Suited for Shuttle AK38N: VIA KT333CF + VIA VT8235 + ITE IT8705F + * Suited for: + * - Shuttle AK38N: VIA KT333CF + VIA VT8235 + ITE IT8705F + * - Elitegroup K7VTA3: VIA Apollo KT266/A/333 + VIA VT8235 + ITE IT8705F */ static int it8705f_write_enable_2e(const char *name) { @@ -835,6 +837,7 @@ {0x8086, 0x1a30, 0x1043, 0x8070, 0x8086, 0x244b, 0x1043, 0x8028, NULL, NULL, "ASUS", "P4B266", ich2_gpio22_raise}, {0x10B9, 0x1541, 0, 0, 0x10B9, 0x1533, 0, 0, "asus", "p5a", "ASUS", "P5A", board_asus_p5a}, {0x1106, 0x3149, 0x1565, 0x3206, 0x1106, 0x3344, 0x1565, 0x1202, NULL, NULL, "BioStar", "P4M80-M4", board_biostar_p4m80_m4}, + {0x1106, 0x3038, 0x1019, 0x0996, 0x1106, 0x3177, 0x1019, 0x0996, NULL, NULL, "Elitegroup", "K7VTA3", it8705f_write_enable_2e}, {0x1106, 0x3177, 0x1106, 0x3177, 0x1106, 0x3059, 0x1695, 0x3005, NULL, NULL, "EPoX", "EP-8K5A2", board_epox_ep_8k5a2}, {0x8086, 0x7110, 0, 0, 0x8086, 0x7190, 0, 0, "epox", "ep-bx3", "EPoX", "EP-BX3", board_epox_ep_bx3}, {0x1039, 0x0761, 0, 0, 0, 0, 0, 0, "gigabyte", "2761gxdk", "GIGABYTE", "GA-2761GXDK", it87xx_probe_spi_flash}, @@ -867,6 +870,7 @@ {0x1106, 0x0259, 0x1106, 0x3227, 0x1106, 0x3065, 0x1106, 0x3149, "via", "epia-n", "VIA", "EPIA-N/NL", board_via_epia_n}, /* TODO: remove coreboot ids */ {0x1106, 0x3227, 0x1106, 0xAA01, 0x1106, 0x0259, 0x1106, 0xAA01, NULL, NULL, "VIA", "EPIA SP", board_via_epia_sp}, {0x1106, 0x5337, 0x1458, 0xb003, 0x1106, 0x287e, 0x1106, 0x337e, "via", "pc3500g", "VIA", "PC3500G", it87xx_probe_spi_flash}, + { 0, 0, 0, 0, 0, 0, 0, 0, NULL, NULL, NULL, NULL, NULL}, /* end marker */ }; @@ -964,7 +968,6 @@ { "Biostar", "M6TBA", }, { "Boser", "HS-6637", }, { "DFI", "855GME-MGF", }, - { "Elitegroup", "K7VTA3", }, { "FIC", "VA-502", }, { "GIGABYTE", "GA-7ZM", }, { "MSI", "MS-6178", },

1 0

build service results for r4368
by coreboot information 21 Jun '09

21 Jun '09

Dear coreboot readers! This is the automatic build system of coreboot. The developer "ruik" checked in revision 4368 to the coreboot repository. This caused the following changes: Change Log: This patch adds a proper namestring generation to our ACPIgen generator. Its used for Name and Scope and Processor now. As bonus, it allows to create a multi name paths too. Like Scope(\ALL.YOUR.BASE). Signed-off-by: Rudolf Marek <r.marek(a)assembler.cz> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Build Log: Compilation of motorola:sandpointx3_altimus_mpc7410 is still broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=4368&device=sandpointx3_al… Compilation of via:epia-m700 is still broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=4368&device=epia-m700&vend… If something broke during this checkin please be a pain in ruik'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

[PATCH] remove namestring trickery
by Rudolf Marek 21 Jun '09

21 Jun '09

Hello, The namestring handling in ACPIgen was a big trickery. We were pasing the strings as it was a bytestream already. This was a reason for instead of _PR one had to write _PR_ Or \_SB.PCI0 was in fact \_SB_PCI0. This patch adds a proper namestring generation to our ACPIgen generator. Its used for Name and Scope and Processor now. As bonus, it allows to create a multi name paths too. Like Scope(\ALL.YOUR.BASE). Signed-off-by: Rudolf Marek <r.marek(a)assembler.cz> I have no board now, so I cannot test it on real HW. I did some tests which a ACPIgen testbench which I'm attaching for future reference. I dont know what happen to fam10 code, but I think it will need similar change. Rudolf

4 5

[v2] r4368 - in trunk/coreboot-v2/src: arch/i386/boot arch/i386/include/arch cpu/amd/model_fxx northbridge/amd/amdk8
by svn＠coreboot.org 21 Jun '09

21 Jun '09

Author: ruik Date: 2009-06-21 22:26:13 +0200 (Sun, 21 Jun 2009) New Revision: 4368 Modified: trunk/coreboot-v2/src/arch/i386/boot/acpigen.c trunk/coreboot-v2/src/arch/i386/include/arch/acpigen.h trunk/coreboot-v2/src/cpu/amd/model_fxx/powernow_acpi.c trunk/coreboot-v2/src/northbridge/amd/amdk8/amdk8_acpi.c Log: This patch adds a proper namestring generation to our ACPIgen generator. Its used for Name and Scope and Processor now. As bonus, it allows to create a multi name paths too. Like Scope(\ALL.YOUR.BASE). Signed-off-by: Rudolf Marek <r.marek(a)assembler.cz> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/coreboot-v2/src/arch/i386/boot/acpigen.c =================================================================== --- trunk/coreboot-v2/src/arch/i386/boot/acpigen.c 2009-06-19 21:18:14 UTC (rev 4367) +++ trunk/coreboot-v2/src/arch/i386/boot/acpigen.c 2009-06-21 20:26:13 UTC (rev 4368) @@ -147,22 +147,111 @@ return size; } +/* The NameString are bit tricky, each element can be 4 chars, if + less its padded with underscore. Check 18.2.2 and 18.4 + and 5.3 of ACPI specs 3.0 for details +*/ + +static int acpigen_emit_simple_namestring(char *name) { + int i, len = 0; + char ud[] = "____"; + for (i = 0; i < 4; i++) { + if ((name[i] == '\0') || (name[i] == '.')) { + len += acpigen_emit_stream(ud, 4 - i); + break; + } else { + len += acpigen_emit_byte(name[i]); + } + } + return len; +} + +static int acpigen_emit_double_namestring(char *name, int dotpos) { + int len = 0; + /* mark dual name prefix */ + len += acpigen_emit_byte(0x2e); + len += acpigen_emit_simple_namestring(name); + len += acpigen_emit_simple_namestring(&name[dotpos + 1]); + return len; +} + +static int acpigen_emit_multi_namestring(char *name) { + int len = 0, count = 0; + unsigned char *pathlen; + /* mark multi name prefix */ + len += acpigen_emit_byte(0x2f); + len += acpigen_emit_byte(0x0); + pathlen = ((unsigned char *) acpigen_get_current()) - 1; + + while (name[0] != '\0') { + len += acpigen_emit_simple_namestring(name); + /* find end or next entity */ + while ((name[0] != '.') && (name[0] != '\0')) + name++; + /* forward to next */ + if (name[0] == '.') + name++; + count++; + } + + pathlen[0] = count; + return len; +} + + +int acpigen_emit_namestring(char *namepath) { + int dotcount = 0, i; + int dotpos; + int len = 0; + + /* we can start with a \ */ + if (namepath[0] == '\\') { + len += acpigen_emit_byte('\\'); + namepath++; + } + + /* and there can be any number of ^ */ + while (namepath[0] == '^') { + len += acpigen_emit_byte('^'); + namepath++; + } + + ASSERT(namepath[0] != '\0'); + + i = 0; + while (namepath[i] != '\0') { + if (namepath[i] == '.') { + dotcount++; + dotpos = i; + } + i++; + } + + if (dotcount == 0) { + len += acpigen_emit_simple_namestring(namepath); + } else if (dotcount == 1) { + len += acpigen_emit_double_namestring(namepath, dotpos); + } else { + len += acpigen_emit_multi_namestring(namepath); + } + return len; +} + int acpigen_write_name(char *name) { - int len = strlen(name); + int len; /* name op */ - acpigen_emit_byte(0x8); - acpigen_emit_stream(name, len); - return len + 1; + len = acpigen_emit_byte(0x8); + return len + acpigen_emit_namestring(name); } int acpigen_write_scope(char *name) { int len; /* scope op */ - acpigen_emit_byte(0x10); - len = acpigen_write_len_f(); - return len + acpigen_emit_stream(name, strlen(name)) + 1; + len = acpigen_emit_byte(0x10); + len += acpigen_write_len_f(); + return len + acpigen_emit_namestring(name); } int acpigen_write_processor(u8 cpuindex, u32 pblock_addr, u8 pblock_len) @@ -178,8 +267,8 @@ acpigen_emit_byte(0x83); len = acpigen_write_len_f(); - sprintf(pscope, "\\._PR_CPU%x", (unsigned int) cpuindex); - len += acpigen_emit_stream(pscope, strlen(pscope)); + sprintf(pscope, "\\_PR.CPU%x", (unsigned int) cpuindex); + len += acpigen_emit_namestring(pscope); acpigen_emit_byte(cpuindex); acpigen_emit_byte(pblock_addr & 0xff); acpigen_emit_byte((pblock_addr >> 8) & 0xff); @@ -238,7 +327,7 @@ /* method op */ acpigen_emit_byte(0x14); len = acpigen_write_len_f(); - len += acpigen_emit_stream("_PPC", 4); + len += acpigen_emit_namestring("_PPC"); /* no fnarg */ acpigen_emit_byte(0x00); /* return */ Modified: trunk/coreboot-v2/src/arch/i386/include/arch/acpigen.h =================================================================== --- trunk/coreboot-v2/src/arch/i386/include/arch/acpigen.h 2009-06-19 21:18:14 UTC (rev 4367) +++ trunk/coreboot-v2/src/arch/i386/include/arch/acpigen.h 2009-06-21 20:26:13 UTC (rev 4368) @@ -29,6 +29,7 @@ int acpigen_write_byte(unsigned int data); int acpigen_emit_byte(unsigned char data); int acpigen_emit_stream(char *data, int size); +int acpigen_emit_namestring(char *namepath); int acpigen_write_dword(unsigned int data); int acpigen_write_qword(uint64_t data); int acpigen_write_name(char *name); Modified: trunk/coreboot-v2/src/cpu/amd/model_fxx/powernow_acpi.c =================================================================== --- trunk/coreboot-v2/src/cpu/amd/model_fxx/powernow_acpi.c 2009-06-19 21:18:14 UTC (rev 4367) +++ trunk/coreboot-v2/src/cpu/amd/model_fxx/powernow_acpi.c 2009-06-21 20:26:13 UTC (rev 4368) @@ -376,7 +376,7 @@ int amd_model_fxx_generate_powernow(u32 pcontrol_blk, u8 plen, u8 onlyBSP) { int lens; - char pscope[] = "\\_PR_"; + char pscope[] = "\\_PR"; lens = acpigen_write_scope(pscope); lens += pstates_algorithm(pcontrol_blk, plen, onlyBSP); Modified: trunk/coreboot-v2/src/northbridge/amd/amdk8/amdk8_acpi.c =================================================================== --- trunk/coreboot-v2/src/northbridge/amd/amdk8/amdk8_acpi.c 2009-06-19 21:18:14 UTC (rev 4367) +++ trunk/coreboot-v2/src/northbridge/amd/amdk8/amdk8_acpi.c 2009-06-21 20:26:13 UTC (rev 4368) @@ -270,7 +270,7 @@ { int lens; msr_t msr; - char pscope[] = "\\._SB_PCI0"; + char pscope[] = "\\_SB.PCI0"; lens = acpigen_write_scope(pscope); lens += k8acpi_write_pci_data(4, "BUSN", 0xe0);

1 0

[PATCH] flashrom: Add board-enable for Shuttle AK38N
by Uwe Hermann 21 Jun '09

21 Jun '09

See patch. Thanks to Luc Verhaegen and Peter Stuge for help and suggestions on IRC. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org

2 2

Open source project, braindead "leaders"
by Noone Nowhere 21 Jun '09

21 Jun '09

Coreboot Systems GmbH is just a new AMI-Phoenix ?. OK, we did not get a Wiki account "_yet_", as YOU ARE DEFINITELY SURE IT WILL BE WASTED!!! You don't get it, do you? The things we prepared for coreboot REQUIRE Wiki acount. Since you judge with no facts(you bet against us, without even knowing us), you aren't getting a thing, it's your right to see in the past and ignoring the future!!! To set things right, the initial wiki requests were sent to rminnich at gmail.com at 20 and 21 December 2007. The one sent on the 21st was answered at December 26.The Wiki is closed for non company employees. After all, see what anyone has offered/ will offer and remove the account if it just wastes space. To inform you, the really silly patch (a typo really, but really stupid to make) we sent was the easiest we could catch in order to test your response and attitude towards other developers, as the refusal of giving a wiki account in the first place set us thinking. YOU REALLY SUCK!!! EVERY CONTRIBUTION WE HAVE PREPARED BUT NOT SENT IS SUSPENDED. EVERY DEVELOPER CAN BE BETTER THAN YOU, YOU CANNOT JUDGE UNTIL YOU SEE WAS HE/SEE HAS TO GIVE. WE WILL ALSO UNSUBSCRIBE FROM THE MAILING LIST SOON. No wonder why only 30+ mobos are opened up and not 100+, you are uncooperative with the rest of world (outside of your company). Remember your words, as you will hear about us again.Only time will show whether we deserved it and didn't take it or you were too narrow minded...Time is too precious to waste it for your shit. Finally, we never beg anyone and for nothing, whether the name is Western Digital,Seagate,Hitachi,Coresystems,Intel,nVIDIA,ATi. We always DEMAND AND ALWAYS GET WHAT WE WANT. That's why we wanted to help you dorks, never mind...

7 8

[flashrom] r616 - trunk
by svn＠coreboot.org 21 Jun '09

21 Jun '09

Author: uwe Date: 2009-06-21 17:45:34 +0200 (Sun, 21 Jun 2009) New Revision: 616 Modified: trunk/board_enable.c Log: Add board-enable code for the Shuttle AK38N. FYI, this board can only decode 256 KB chips (not 512 KB ones) unfortunately. The highest address line (A18) is not connected on this board. The it8705f_write_enable() is kept generic enough so it can be reused for other board-enables, possibly in the board_biostar_p4m80_m4() for example, but that shouldn't be touched for now, unless someone can test the code. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Luc Verhaegen <libv(a)skynet.be> Modified: trunk/board_enable.c =================================================================== --- trunk/board_enable.c 2009-06-20 01:21:38 UTC (rev 615) +++ trunk/board_enable.c 2009-06-21 15:45:34 UTC (rev 616) @@ -719,7 +719,24 @@ return 0; } +static int it8705f_write_enable(uint8_t port, const char *name) +{ + enter_conf_mode_ite(port); + sio_mask(port, 0x24, 0x04, 0x04); /* Flash ROM I/F Writes Enable */ + exit_conf_mode_ite(port); + + return 0; +} + /** + * Suited for Shuttle AK38N: VIA KT333CF + VIA VT8235 + ITE IT8705F + */ +static int it8705f_write_enable_2e(const char *name) +{ + return it8705f_write_enable(0x2e, name); +} + +/** * Find the runtime registers of an SMSC Super I/O, after verifying its * chip ID. * @@ -842,6 +859,7 @@ {0x1106, 0x0571, 0x1462, 0x7120, 0, 0, 0, 0, "msi", "kt4v", "MSI", "MS-6712 (KT4V)", board_msi_kt4v}, {0x8086, 0x2658, 0x1462, 0x7046, 0x1106, 0x3044, 0x1462, 0x046d, NULL, NULL, "MSI", "MS-7046", ich6_gpio19_raise}, {0x10de, 0x005e, 0, 0, 0, 0, 0, 0, "msi", "k8n-neo3", "MSI", "MS-7135 (K8N Neo3)", w83627thf_gpio4_4_raise_4e}, + {0x1106, 0x3104, 0x1297, 0xa238, 0x1106, 0x3059, 0x1297, 0xc063, NULL, NULL, "Shuttle", "AK38N", it8705f_write_enable_2e}, {0x1106, 0x3038, 0x0925, 0x1234, 0x1106, 0x3058, 0x15DD, 0x7609, NULL, NULL, "Soyo", "SY-7VCA", board_soyo_sy_7vca}, {0x8086, 0x1076, 0x8086, 0x1176, 0x1106, 0x3059, 0x10f1, 0x2498, NULL, NULL, "Tyan", "S2498 (Tomcat K7M)", board_asus_a7v8x_mx}, {0x1106, 0x0314, 0x1106, 0xaa08, 0x1106, 0x3227, 0x1106, 0xAA08, NULL, NULL, "VIA", "EPIA-CN", board_via_epia_sp},

1 0

GA-P35-DS3L - supported? (Console output included)
by Drew Diller 21 Jun '09

21 Jun '09

My system sits on a Gigabyte GA-P35-DS3L mainboard with an Intel Core 2 Duo E6750 CPU. I am wondering if you think it will work / anecdotally know it will work with coreboot, as I did not see the model on the "supported mainboards" page. Specs are down a ways, after my three questions: First: What's a guy to do if I screw the BIOS up? The BIOS chip is a SOP8 (I think?). It's soldered on, at any rate. I don't have a floppy drive. Searching (broader internet) has yielded varied and questionable results. Second: I am aware from prior experience that I have to set the RAM voltage to something other than the mainboard's factory default. I am confused where in the process of installing coreboot this sort of customization ability is afforded. A "newb, here's a link you overlooked" will suffice. Third: I see a lot more support for AMD than Intel. I didn't know about coreboot when purchasing parts two years ago. Should I generally be buying AMD hardware if I want to use coreboot in the long run? I don't have brand loyalty. I apologize up front that "I only know what I know", so I might ask some stupid questions. I'm a Javascript author by trade (I wrote the DD_belatedPNG library, for example), I can read documentation... I just feel like I've missed something, as there is a _lot_ of it available on coreboot.org. My motivation for using coreboot is (1) Ubuntu 9.04 boots in less time than my default BIOS routine takes, as a 10,000 RPM hard drive is pretty snappy and (2) I'll be buying a Sandisk G3 when they're finally available, which will make the default BIOS routine look even MORE ridiculous, and (3) I turn off power strips on a nightly basis. That said, Manufacturer's information: http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?Prod… ~# lspci -tvnn -[0000:00]-+-00.0 Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] +-01.0-[0000:01]----00.0 nVidia Corporation GeForce 8800 GT [10de:0611] +-1a.0 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] +-1a.1 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] +-1a.2 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] +-1a.7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] +-1b.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] +-1c.0-[0000:02]-- +-1c.3-[0000:03]----00.0 JMicron Technologies, Inc. JMB368 IDE controller [197b:2368] +-1c.4-[0000:04]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] +-1d.0 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] +-1d.1 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] +-1d.2 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] +-1d.7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] +-1e.0-[0000:05]-- +-1f.0 Intel Corporation 82801IB (ICH9) LPC Interface Controller [8086:2918] +-1f.2 Intel Corporation 82801IB (ICH9) 2 port SATA IDE Controller [8086:2921] +-1f.3 Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] \-1f.5 Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller [8086:2926] ~# superiotool -dV Found ITE IT8718F (id=0x8718, rev=0x4) at 0x2e Register dump: idx 20 21 22 23 24 2b val 87 18 04 10 00 00 def 87 18 01 00 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 val 01 03 f0 06 02 00 80 def 00 03 f0 06 02 00 00 LDN 0x01 (COM1) idx 30 60 61 70 f0 f1 f2 f3 val 01 03 f8 04 00 50 00 7f def 00 03 f8 04 00 50 00 7f LDN 0x02 (COM2) idx 30 60 61 70 f0 f1 f2 f3 val 00 00 00 00 00 50 00 7f def 00 02 f8 03 00 50 00 7f LDN 0x03 (Parallel port) idx 30 60 61 62 63 70 74 f0 val 01 03 78 00 00 07 04 08 def 00 03 78 07 78 07 03 03 LDN 0x04 (Environment controller) idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 val 01 02 90 00 00 00 80 00 0a 00 a0 00 ff def 00 02 90 02 30 09 00 00 00 00 00 NA NA LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 71 f0 val 01 00 60 00 64 01 02 68 def 01 00 60 00 64 01 02 00 LDN 0x06 (Mouse) idx 30 70 71 f0 val 01 0c 02 00 def 00 0c 02 00 LDN 0x07 (GPIO) idx 25 26 27 28 29 2a 2c 60 61 62 63 64 65 70 71 72 73 74 b0 b1 b2 b3 b4 b5 b8 b9 ba bb bc bd c0 c1 c2 c3 c4 c5 c8 c9 ca cb cc e0 e1 e2 e3 e4 e5 e6 e7 f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff val 41 df 00 03 88 01 1d 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 81 c0 00 00 01 00 40 1f 00 03 08 00 00 11 00 03 08 00 00 00 00 00 00 00 00 10 40 00 00 00 00 08 00 00 00 00 00 2a 00 00 00 def 01 00 00 40 00 00 00 00 00 00 00 00 00 00 00 20 38 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 40 00 00 01 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA 00 00 00 LDN 0x0a (Consumer IR) idx 30 60 61 70 f0 val 00 03 10 0b 06 def 00 03 10 0b 00 ~# flashrom -V Calibrating delay loop... 760M loops per second, 100 myus = 200 us. OK. No coreboot table found. Found chipset "Intel ICH9", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 Root Complex Register Block address = 0xfed1c000 GCS = 0x464: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x00: 0x1fff (HSFS) FLOCKDN 1, FDV 1, FDOPSS 0, SCIP 0, BERASE 0, AEL 0, FCERR 0, FDONE 0 0x50: 0x00000202 (FRAP) BMWAG 0, BMRAG 0, BRWA 2, BRRA 2 0x54: 0x00001fff (FREG0) 0x58: 0x00001fff (FREG1) 0x5C: 0x00001fff (FREG2) 0x60: 0x00001fff (FREG3) 0x64: 0x00001fff (FREG4) 0x74: 0x00000000 (PR0) 0x78: 0x00000000 (PR1) 0x7C: 0x00000000 (PR2) 0x80: 0x00000000 (PR3) 0x84: 0x00000000 (PR4) 0xB0: 0x00000000 (FDOC) Programming OPCODES... done SPI Read Configuration: prefetching disabled, caching enabled, OK. Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT25DF021, 256 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF041A, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF081, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF161, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF321, 4096 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF321A, 4096 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF641, 8192 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25F512B, 64 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25FS010, 128 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25FS040, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF041, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF081A, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF161, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF161A, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26F004, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT45CS1282, 16896 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB011D, 128 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB021D, 256 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB041D, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB081D, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB161D, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB321C, 4224 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB321D, 4096 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB642D, 8192 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMIC A25L40P, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x24, id2 0x89 Probing for Macronix MX25L512, 64 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1005, 128 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L2005, 256 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L4005, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L8005, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Chip status register is 00 Chip status register: Status Register Write Disable (SRWD) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 / Block Protect 3 (BP3) is not set Chip status register: Bit 4 / Block Protect 2 (BP2) is not set Chip status register: Bit 3 / Block Protect 1 (BP1) is not set Chip status register: Bit 2 / Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Found chip "Macronix MX25L8005" (1024 KB) at physical address 0xfff00000. Probing for Macronix MX25L1605, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L3205, 4096 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L6405, 8192 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0x24, id2 0x89 Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0x24, id2 0x89 Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0x24, id2 0x89 Probing for Numonyx M25PE10, 128 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE20, 256 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE40, 256 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE80, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE16, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV010, 128 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV016B, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV020, 256 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV040, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV080B, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV512, 64 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0x24, id2 0x89 Probing for Spansion S25FL016A, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF016B, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF032B, 4096 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF040B, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF080B, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x24, id2 0x89 Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x24, id2 0x89 Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0x24, id2 0x89 Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0x24, id2 0x89 Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0x24, id2 0x89 Probing for ST M25P05-A, 64 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P10-A, 128 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P20, 256 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P40, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P40-old, 512 KB: RDID returned c2 20 14. Probing for ST M25P80, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P16, 2048 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P32, 4096 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P64, 8192 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P128, 16384 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0x24, id2 0x89 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for ST M29W010B, 128 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0x24, id2 0x89 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0x24, id2 0x89 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0x24, id2 0x89 Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0x24, id2 0x89 Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x24, id2 0x89 Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0x24, id2 0x89 Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x24, id2 0x89 Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x24, id2 0x89 Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W25x10, 128 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25x20, 256 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25x40, 512 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25x80, 1024 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W29EE011, 128 KB: === Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. === Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x24, id2 0x89, id1 parity violation Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0x24, did 0x89 Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: vid 0x24, did 0x89 Probing for Atmel unknown Atmel SPI chip, 0 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for EON unknown EON SPI chip, 0 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix unknown Macronix SPI chip, 0 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC unknown PMC SPI chip, 0 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST unknown SST SPI chip, 0 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST unknown ST SPI chip, 0 KB: RDID returned c2 20 14. probe_spi_rdid_generic: id1 0xc2, id2 0x2014 No operations were specified.

3 2

ACPI support on M57SLI
by Harald Gutmann 21 Jun '09

21 Jun '09

Hello once more! Here is my patch to activate ACPI on M57SLI. This patch solves the following issues on this mainboard: * ACPI support is added * PowerNow! for fam10 CPU's is activated * Soft-Poweroff works What this patch does not: * ACPI support which is accepted by windows. Take care on the following: *** WARNING *** * This patch needs as dependency the IRQ mptable fix patch[1] (which is right now not committed) in order to work! [1] http://www.coreboot.org/pipermail/coreboot/2009-June/049570.html I have ATM no space to try a windows installation, and I don't own a windows license and therefore I didn't cared on windows related ACPI problems. It should be quite easy to complete this, that windows also will like it. If anyone is interested in doing that, please contact me. I've an IRC-Log from the discussion with Rudolf Marek related to ACPI on windows and what will be needed to get it right. Please be so kindly and review it, so that it can get commited. Signed-off-by: Harald Gutmann <harald.gutmann(a)gmx.net> Kind regards, Harald Gutmann

4 13

useful hardware - dip8 to soic8 adapter
by Warren Turkal 20 Jun '09

20 Jun '09

Here's[1] a useful piece of hardware that I found. I had a somewhat difficult time finding one, so I just wanted to share it with everyone. It's an adapter that allows the use of a dip8 chip in place of a soic8 surface mount chip. [1]http://www.epboard.com/eproducts/protoadapter3.htm wt

5 9

← Newer
1
...
17
18
19
20
21
22
23
...
50
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 June 2009