coreboot June 2012

coreboot@coreboot.org

41 participants
241 discussions

VGA Option ROM
by Wolfgang Kamp - datakamp 07 Jun '12

07 Jun '12

Hello, I'm using Coreboot with Seabios on the AMD Persimmon platform. In the current versions I found a problem with the VGA Option ROM initialization. Normally Seabios should be configured to initialize the VGA Option ROM and Coreboot should not. But in this scenario Coreboot does not copy the VGA ROM in the right place at C000:0, so Seabios could not find it. If I configure Coreboot to initialize the VGA ROM it will copy the VGA ROM to C000:0 and calls it. Now Seabios which is configured to call Option ROMs will find the VGA ROM and also calls it. But the double initialization leads to a VGA failure. In the older versions coreboot puts the VGA ROM always in the right place and Seabios finds it. Could anyone help me? Thank you Regards Wolfgang

1 0

Supported Motherboards with SMM
by Fengwei Zhang 07 Jun '12

07 Jun '12

Hi All, My name is Fengwei. For one of my research project, I need a relative new Coreboot supported board with SMM working. I am wondering if there is a list of Coreboot supported boards with SMM working. I have been working with board ASUS M2V-MX_SE, which supports SMM by applying Ruldof's patch. However, this board is very old, and I am unable to find it on the market now. I would appreciate if anyone could give me some suggestions. Regards, Fengwei

3 2

Patch merged into filo/master: 4193fd9 Make booting from ATAPI drives more resilient.
by gerrit＠coreboot.org 06 Jun '12

06 Jun '12

the following patch was just integrated into master: commit 4193fd9b4921a78831f9346b02cbb004b69b16e3 Author: Nico Huber <nico.huber(a)secunet.com> Date: Fri May 25 11:34:08 2012 +0200 Make booting from ATAPI drives more resilient. This fixes a semantic error, where the ATAPI driver requested sense from the drive instead of retrying a failed command (i.e. the actual command had been overwritten). The count of retries and delays are also adapted to behave more like the Linux kernel driver. Change-Id: Iabf20120c841bbc277af4efa48c6594804f60205 Signed-off-by: Patrick Georgi <patrick.georgi(a)secunet.com> Build-Tested: build bot (Jenkins) at Fri Jun 1 14:02:21 2012, giving +1 Reviewed-By: Stefan Reinauer <stefan.reinauer(a)coreboot.org> at Wed Jun 6 22:00:43 2012, giving +2 See http://review.coreboot.org/1087 for details. -gerrit

1 0

Re: [coreboot] Support for HP Compaq NC6320
by Idwer Vollering 06 Jun '12

06 Jun '12

2012/6/6 Ross McDonald <ross0mcdonald(a)gmail.com>: > Hello! I would like to use CoreBoot on my laptop. It is an HP Compaq NC6320. > The board vendor is HP. It is a > HP 30AA motherboard with an Intel 945GM Chipset (ICH7-M southbridge and i945 > northbridge). The CPU is an Intel Core 2 Duo T5600. It has a SMSC LPC47N217 > SuperIO chip (that is the output of SuperIOTool). > > # flashrom -V > flashrom v0.9.5.2-r1515 on Linux 3.4.0-1-ARCH (x86_64), built with libpci > 3.1.9, GCC 4.6.3, little endian > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OS timer resolution is 1 usecs, 1803M loops per > second, 10 myus = 11 us, 100 myus = 99 us, 1000 myus = 1002 us, 10000 myus = > 9991 us, 4 myus = 5 us, OK. > Initializing internal programmer > No coreboot table found. > DMI string system-manufacturer: "Hewlett-Packard" > DMI string system-product-name: "HP Compaq nc6320 (RN442AWR#ABA)" > DMI string system-version: "F.0E" > DMI string baseboard-manufacturer: "Hewlett-Packard" > DMI string baseboard-product-name: "30AA" > DMI string baseboard-version: "KBC Version 58.13" > DMI string chassis-type: "Notebook" > Laptop detected via DMI. > ======================================================================== > WARNING! You seem to be running flashrom on an unsupported laptop. > Laptops, notebooks and netbooks are difficult to support and we > recommend to use the vendor flashing utility. The embedded controller > (EC) in these machines often interacts badly with flashing. > See http://www.flashrom.org/Laptops for details. > > If flash is shared with the EC, erase is guaranteed to brick your laptop > and write may brick your laptop. > Read and probe may irritate your EC and cause fan failure, backlight > failure and sudden poweroff. > You have been warned. > ======================================================================== > Aborting. > > I can open up the case to find out what BIOS chip I have. Or you can run flashrom like this (as root): flashrom -V -p internal:laptop=force_I_want_a_brick Passing additional parameters, such as reading or writing/erasing, is not necessary (is potentionally invasive/destructive). Idwer

1 0

Re: [coreboot] Support for HP Compaq NC6320
by Denis 'GNUtoo' Carikli 06 Jun '12

06 Jun '12

On Wed, 2012-06-06 at 18:51 +0200, Ross McDonald wrote: > Hello! I would like to use CoreBoot on my laptop. It is an HP Compaq > NC6320. The board vendor is HP. I've the same laptop. I've made an internal picture of it: http://www.flashrom.org/File:Serduino_laptop.jpeg > # flashrom -V > flashrom v0.9.5.2-r1515 on Linux 3.4.0-1-ARCH (x86_64), built with libpci > 3.1.9, GCC 4.6.3, little endian > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OS timer resolution is 1 usecs, 1803M loops per > second, 10 myus = 11 us, 100 myus = 99 us, 1000 myus = 1002 us, 10000 myus > = 9991 us, 4 myus = 5 us, OK. > Initializing internal programmer > No coreboot table found. > DMI string system-manufacturer: "Hewlett-Packard" > DMI string system-product-name: "HP Compaq nc6320 (RN442AWR#ABA)" > DMI string system-version: "F.0E" > DMI string baseboard-manufacturer: "Hewlett-Packard" > DMI string baseboard-product-name: "30AA" > DMI string baseboard-version: "KBC Version 58.13" > DMI string chassis-type: "Notebook" > Laptop detected via DMI. > ======================================================================== > WARNING! You seem to be running flashrom on an unsupported laptop. > Laptops, notebooks and netbooks are difficult to support and we > recommend to use the vendor flashing utility. The embedded controller > (EC) in these machines often interacts badly with flashing. > See http://www.flashrom.org/Laptops for details. > > If flash is shared with the EC, erase is guaranteed to brick your laptop > and write may brick your laptop. > Read and probe may irritate your EC and cause fan failure, backlight > failure and sudden poweroff. > You have been warned. > ======================================================================== > Aborting. > > I can open up the case to find out what BIOS chip I have. # ./flashrom -V -p internal:laptop=force_I_want_a_brick flashrom v0.9.5.2-r1539 on Linux 3.0.0-20-generic (x86_64), built with libpci 3.1.7, GCC 4.6.1, little endian flashrom is free software, get the source code at http://www.flashrom.org Command line (3 args): ./flashrom -V -p internal:laptop=force_I_want_a_brick Calibrating delay loop... OS timer resolution is 1 usecs, 1991M loops per second, 10 myus = 11 us, 100 myus = 101 us, 1000 myus = 1015 us, 10000 myus = 9996 us, 4 myus = 6 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Hewlett-Packard" DMI string system-product-name: " " DMI string system-version: "F.0E" DMI string baseboard-manufacturer: "Hewlett-Packard" DMI string baseboard-product-name: "30AA" DMI string baseboard-version: "KBC Version 58.13" DMI string chassis-type: "Notebook" Laptop detected via DMI. ======================================================================== WARNING! You seem to be running flashrom on an unsupported laptop. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH7M" with PCI ID 8086:27b9. Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode disabled 0xffe00000/0xffa00000 FWH decode disabled 0xffd80000/0xff980000 FWH decode disabled 0xffd00000/0xff900000 FWH decode disabled 0xffc80000/0xff880000 FWH decode disabled 0xffc00000/0xff800000 FWH decode disabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 Root Complex Register Block address = 0xfed90000 GCS = 0x30460: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed90000 + 0x3020 0x00: 0x8004 (SPIS) 0x02: 0x4200 (SPIC) 0x04: 0x00000000 (SPIA) 0x08: 0x00148020 (SPID0) 0x0c: 0x00000000 (SPID0+4) 0x10: 0x00000000 (SPID1) 0x14: 0x00000000 (SPID1+4) 0x18: 0x00000000 (SPID2) 0x1c: 0x00000000 (SPID2+4) 0x20: 0x00000000 (SPID3) 0x24: 0x00000000 (SPID3+4) 0x28: 0x00000000 (SPID4) 0x2c: 0x00000000 (SPID4+4) 0x30: 0x00000000 (SPID5) 0x34: 0x00000000 (SPID5+4) 0x38: 0x00000000 (SPID6) 0x3c: 0x00000000 (SPID6+4) 0x40: 0x00000000 (SPID7) 0x44: 0x00000000 (SPID7+4) 0x50: 0x00000000 (BBAR) 0x54: 0x5006 (PREOP) 0x56: 0x7f48 (OPTYPE) 0x58: 0x0405039f (OPMENU) 0x5c: 0x0102d852 (OPMENU+4) 0x60: 0x00000000 (PBR0) 0x64: 0x00000000 (PBR1) 0x68: 0x00000000 (PBR2) WARNING: SPI Configuration Lockdown activated. Reading OPCODES... done SPI Read Configuration: prefetching disabled, caching enabled, OK. The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Chip status register is 00 Found Numonyx flash chip "M25PE80" (1024 kB, SPI) at physical address 0xfff00000. Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx N25Q064, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25LF040A, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25LF080A, 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25VF010, 128 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25VF040, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25VF040B.REMS, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Unknown SFDP-capable chip, 0 kB: Invalid OPCODE 0x5a, will not execute. Receiving SFDP signature failed. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Generic unknown SPI chip (REMS), 0 kB: Invalid OPCODE 0x90, will not execute. Found Numonyx flash chip "M25PE80" (1024 kB, SPI). No operations were specified. Restoring MMIO space at 0x7f991c460070 Restoring PCI config space for 00:1f:0 reg 0xdc Don't try such things if you don't have a way to recover(such as the way in the picture). Denis.

1 0

Re: [coreboot] Support for laptop HP Compaq NC6320
by Paul Menzel 06 Jun '12

06 Jun '12

Dear Ross, thank you for your message. First three off-topic things. 1. Please send just plain text messages and no HTML. This is covered in the netiquette [1]. 2. When pasting stuff please turn off line wrapping. This is not possible with the Google Mail Web interface as far as I know. So either attach this stuff as text files or use a good mail user agent like Thunderbird/Iceweasel, Mutt, …. 3. The project name is spelled all lower case: coreboot. Am Mittwoch, den 06.06.2012, 18:51 +0200 schrieb Ross McDonald: > Hello! I would like to use CoreBoot on my laptop. It is an HP Compaq > NC6320. The board vendor is HP. Ok, this a laptop for everyone. > It is a HP 30AA motherboard with an Intel 945GM Chipset (ICH7-M > southbridge and i945 northbridge). The CPU is an Intel Core 2 Duo > T5600. It has a SMSC LPC47N217 SuperIO chip (that is the output of > SuperIOTool). […] If I am not mistaken, this is the same chipset as for example used in the Lenovo X60 or T60 and 986LCD-M/mITX [2]. So make sure you have a way to recover. Easiest way is when the flash chip is socketed to get some spare flash chips. Since this is a laptop you probably need to solder a socket or an adapter to the board like was done with the X60 or T60 [3][4]. You also need to find out if an embedded controller is used and how it works. Lastly you also need the laptop board schematics I think to set everything up. Then you should be able to do the port pretty easily I think. Look at the commits for the X60 and T60. Thanks, Paul [1] http://en.opensuse.org/openSUSE:Mailing_list_netiquette [2] http://www.coreboot.org/Supported_Motherboards [3] http://thread.gmane.org/gmane.linux.bios/69354 [4] http://thread.gmane.org/gmane.linux.bios.flashrom/575

1 1

Support for HP Compaq NC6320
by Ross McDonald 06 Jun '12

06 Jun '12

Hello! I would like to use CoreBoot on my laptop. It is an HP Compaq NC6320. The board vendor is HP. It is a HP 30AA motherboard with an Intel 945GM Chipset (ICH7-M southbridge and i945 northbridge). The CPU is an Intel Core 2 Duo T5600. It has a SMSC LPC47N217 SuperIO chip (that is the output of SuperIOTool). # lspci -tvnn -[0000:00]-+-00.0 Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] +-02.0 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] +-02.1 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] +-1b.0 Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] +-1c.0-[08]----00.0 Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] +-1c.2-[18]-- +-1c.3-[20]-- +-1d.0 Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] +-1d.1 Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] +-1d.2 Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] +-1d.3 Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] +-1d.7 Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] +-1e.0-[02-06]--+-06.0 Texas Instruments PCIxx12 Cardbus Controller [104c:8039] | +-06.1 Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller [104c:803a] | +-06.2 Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) [104c:803b] | +-06.3 Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller [104c:803c] | +-06.4 Texas Instruments PCIxx12 GemCore based SmartCard controller [104c:803d] | \-0e.0 Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet [14e4:169c] +-1f.0 Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] +-1f.1 Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] \-1f.2 Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [AHCI mode] [8086:27c5] # superiotool -dV superiotool r6637 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=0x8400, id=0x0026 Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff 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=standard) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=standard) at 0x2e... Failed. Returned data: id=0x2600, rev=0x0 Probing for ITE Super I/O (init=it8502e) at 0x2e... Failed. Returned data: id=0x2600, rev=0x0 Probing for ITE Super I/O (init=it8761e) at 0x2e... Failed. Returned data: id=0x2600, rev=0x0 Probing for ITE Super I/O (init=it8228e) at 0x2e... Failed. Returned data: id=0x2600, rev=0x0 Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0x2600, rev=0x0 Probing for ITE Super I/O (init=standard) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) 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 ITE Super I/O (init=legacy/it8661f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=legacy/it8671f) at 0x370... 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 NSC Super I/O at 0x15c... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x164e... Failed. Returned data: port=0xff, port+1=0xff Probing for Nuvoton Super I/O at 0x164e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x164e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for Nuvoton Super I/O at 0x2e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x2e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for Nuvoton Super I/O at 0x4e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x4e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0x26, rev=0x00 Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Found SMSC LPC47N217 (id=0x7a, rev=0x03) at 0x4e No dump available for this Super I/O 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... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff 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 Probing for VIA Super I/O at 0x3f0... PCI device 1106:0686 not found. Probing for Server Engines Super I/O at 0x2e... Failed. Returned data: id=0xffff, rev=0xff # flashrom -V flashrom v0.9.5.2-r1515 on Linux 3.4.0-1-ARCH (x86_64), built with libpci 3.1.9, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 1803M loops per second, 10 myus = 11 us, 100 myus = 99 us, 1000 myus = 1002 us, 10000 myus = 9991 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Hewlett-Packard" DMI string system-product-name: "HP Compaq nc6320 (RN442AWR#ABA)" DMI string system-version: "F.0E" DMI string baseboard-manufacturer: "Hewlett-Packard" DMI string baseboard-product-name: "30AA" DMI string baseboard-version: "KBC Version 58.13" DMI string chassis-type: "Notebook" Laptop detected via DMI. ======================================================================== WARNING! You seem to be running flashrom on an unsupported laptop. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Aborting. I can open up the case to find out what BIOS chip I have.

1 0

[flashrom] Creating a nonprofit
by Carl-Daniel Hailfinger 05 Jun '12

05 Jun '12

Hi, the flashrom project gets donation offers roughly twice a month, and quite a few times people wanted to donate more than 50 EUR / 60 USD. We can't accept those donations right now because there is no legal entity behind the flashrom project. At the same time, we could use some money to improve flasher support by buying some flash chips and programmers so all developers can easily test changes. Besides that, posters/handouts for LinuxTag/FOSDEM/... booths are currently paid for by those flashrom guys who go to those exhibitions. My proposal is to create a nonprofit club in Germany (eingetragener Verein) in the same way as KDE and OpenEmbedded did it. Given that the majority of the flashrom team lives somewhere in the EU, starting or joining a nonprofit in the USA wouldn't make sense. An informal request for comments among those who are involved in flashrom did yield some noticeable interest, and I guess now is the time to make this plan public. coreboot is not an immediate target of this nonprofit club because I don't want to interfere with any plans which may be ongoing on the coreboot side. Nonwithstanding the above, if the coreboot project leaders decide that participating in a nonprofit in Germany would make sense, there's no reason not to do this together. Then again, the majority of coreboot developers live in the USA and a nonprofit outside the USA might not make sense for them. Side note: We (coreboot/flashrom) won a substantial amount of money (to be redeemed in hardware) in a "project beauty contest" held by Thomas-Krenn.com, a nice server manufacturer. We need a legal entity to accept that hardware. Comments? Regards, Carl-Daniel

1 0

Re: [coreboot] Regarding contribution for coreboot
by Paul Menzel 05 Jun '12

05 Jun '12

Dear Manasa, please excuse the late replay and thank you for your patience. Am Montag, den 04.06.2012, 18:24 +0530 schrieb manasa gv: > I am new and interested to work on coreboot.I have gone through the > coreboot website. > I am trying to do patch review.. But I am taking more time to come up > with the solution compared to others.. that is to be expected when getting into coreboot. Do not let this demotivate you. Sorry for the lack of replies. I am not up to date, but I think you tried to do patch review over the list only which is not how it is done in coreboot currently. A Gerrit instance [1] is used for that. You need to log in with an OpenID (from Google Mail(?)) and leave comments there for example. [2] > So,Please let me know any other ways to contribute for coreboot apart > from patch review?? I guess the best thing to get going is probably to get it running on some hardware. The Toshiba laptop you asked about is currently not supported [3]. Getting the chipset support done is probably to much work, so you should get a different system. The ASRock E350M1 is pretty good supported. Otherwise get some other AMD based system. If that is not possible you could try QEMU although this is better to play with payloads. You could try to get Tint running with QEMU and probably port some more programs to libpayload. It is pretty difficult to suggest something not knowing what your background and interests are. Can you also share where you are located? Maybe some coreboot user lives near by you could get in touch with. Please also feel free to join the IRC channel [4] to get more information. Thanks, Paul [1] http://review.coreboot.org/ [2] http://www.coreboot.org/Git [3] http://www.coreboot.org/pipermail/coreboot/2012-May/069976.html [4] http://www.coreboot.org/IRC

1 0

Re: [coreboot] http://review.coreboot.org/#/c/493/: Add mainboard supermicro x7db8
by Paul Menzel 05 Jun '12

05 Jun '12

Dear Manasa, I am sorry for the late reply and thank you for your contributions. Before going further please make sure you disable digest mode in your Mailman preferences [1], so that threading is kept when you reply to messages. Unfortunately you took a patch for review, which was not meant to be committed. Sven commented the following [2]. Unfinished, only pushed for backup purposes Am Mittwoch, den 23.05.2012, 17:55 +0530 schrieb manasa gv: > From: Manasa GV <manasa671989(a)gmail.com> > > This patch is to file x7db8.Build(Jenkins) results failed for patch > set1 in patch493.Test results showing error. So i added cmos.layout > file.Later i done abuild,then also it is showing errors. Errors are- > need to add smbus.c, smbus.h ,early_setup.c file for Southbridge > i63xx. > So please suggest me to add these files. I think there are two options. 1. Either contact Sven Schnelle and ask him, if he can use your contributions and how you can help. 2. Or, register with Gerrit and push an updated patch with the change ID in the commit message of the patch you are updating. > Signed-off-by: manasa gv<manasa671989(a)gmail.com> Please add a space before the email address. You can add Signed-off-by lines with Git by appending `-s` to most commands. Two examples: $ git commit -s $ git format-patch -s -1 But currently Gerrit is used for patch review in coreboot. > --- > src/mainboard/supermicro/x7db8/cmos.layout | 72 ++++++++++++++++++++++++++++ > 1 files changed, 72 insertions(+), 0 deletions(-) > create mode 100644 src/mainboard/supermicro/x7db8/cmos.layout […] Thanks, Paul [1] http://www.coreboot.org/mailman/options/coreboot [2] http://review.coreboot.org/#/c/493/

1 0

← Newer
1
...
18
19
20
21
22
23
24
25
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 2012