Varad Gautam | 5 Mar 16:43 2015
Picon

[GSoC-2015] Interested in Participating - Discussing Ideas

Hi,

I would like to participate in Google Summer of Code 2015 with coreboot to 
work on one of the following ideas:

- Enable coreboot + Tianocore over an ARM board: The Ideas page mentions 
something similar [1], but I think the hardware details are to be finalized. I 
worked on adding BeagleBone Black support to Tianocore during GSoC-2014 with 
Linaro, and so have some experience with JTAG, ARM bringup and bootloaders. 
Which mainboard would be the intended target? I have a HiKey board (HiSilicon 
Kirin 6220 Cortex-A53 ARM64) [2] which could be used - I'm checking if 
coreboot already supports a similar SoC to base the port on.

- Eliminate Video BIOS requirement for AMD/ATI graphics init: I understand 
this would involve dumping AtomBIOS ROM and performing those initializations 
under coreboot. I came across atomdis [3] and am looking for a Video BIOS ROM 
I could try disassembling. I need some input on how I could go about the 
implementation of this idea - what hardware would be suitable / what the boot 
flow would be. Although I haven't worked with the Linux graphics stack yet, I 
would like to get my hands dirty. I am currently looking through the resources 
at [4].

I recently tried running coreboot + SeaBIOS + SYSLINUX under QEMU (as 
suggested on the Easy tasks page [5]), and it seems to work alright - but is 
it possible to find a SYSLINUX ELF image so I can eliminate SeaBIOS?

I would be glad to have your suggestions on how I could get started.

[1] http://www.coreboot.org/Project_Ideas#coreboot_ARM_SoC.27s_mainboard_port
[2] https://www.96boards.org/products/hikey/
(Continue reading)

Marc Jones | 5 Mar 02:08 2015
Picon

coreboot GSoC 2015

coreboot has been accepted as a GSoC project . Woot!

Please see the following announcement:
http://blogs.coreboot.org/blog/2015/03/02/coreboot-gsoc-2015/

Interested students and mentors should visit the coreboot GSoC page:

Regards,
Marc




--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
David Englund | 3 Mar 19:43 2015

ASUS F2A85-M2

Should "ASUS F2A85-M2" be removed from 
http://www.coreboot.org/Board:asus/f2a85-m

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

David Englund | 3 Mar 19:42 2015

ASUS F2A85-M PRO

Is this board supported?

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Alexandru Gagniuc | 3 Mar 07:06 2015
Picon

Long license headers (ANGER WARNING)

There's this thing called a copyright notice, which is pretty cool. When 
coding on 24" monitors or larger, it's this tiny thing that keeps some legal 
history of a file. The world is perfect and there are no issues!

Then FSF comes and teaches us to be in-your-face with a 20+ line copyright 
notice, and laptops happen. And 14" screens become a long-forgotten glory. Now 
you have to *BLEEP*ing scroll down every time you open a file just to get to 
the real content. It becomes so annoying, that I will personally stop giving 
positive gerrit scores on any CL that introduces such a file.

Then we get to situations where we waste all that copyright notice space for 
one line of code [1]. This madness has to stop.

Tell me what the file does, add your (C) line, tell me how you license the 
file, and move on! Start coding already for *BLEEP*'s sake! Here:

/*
 * On copyright notices: Angry email to coreboot mailing list
 *
 * Copyright (C) Some really pissed off guy <angry <at> mad.com>
 * Licensed under WTFPL, or, at your option, Allah Akbar public license.
 */

There, you've achieved the same thing as that abomination of notice that we 
need to change whenever some third party moves its headquarters. Now I can 
open a file and see

/*
 * On the subject of flowers and sunny skies
 *
...

and I immediately know I'm in the wrong place. Be pragmatic! Be practical! 
Tell me what your file does. Talk about it. Document stuff. It's a much better 
use of space. I could probably kidnap any of you, torture you asking for your 
bank information, and you'd be much more likely to recite, without error, all 
versions of the GPL.

And once that's settled, we can start migrating all files to concise notices, 
while keeping the exact same information we had before.

TL;DR

1) Tell me about your file
2) Add your (C) line
3) Document the license of your choosing (in 1 line)
4) Move on to coding!

[1] http://review.coreboot.org/#/c/8488/10/src/cpu/amd/model_10xxx/ram_calc.h

Alex
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Alexander Couzens | 2 Mar 17:37 2015
Picon

jolla tabletswith or without intel boot guard?

Hi,

FYI: I've created a ticket in jolla's ticket system. When I've received an answer I'll paste it here too.

Best,
lynxis
-- 
Alexander Couzens

mail: lynxis <at> fe80.eu
jabber: lynxis <at> jabber.ccc.de
mobile: +4915123277221

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Darmawan Salihun | 2 Mar 15:24 2015
Picon

Intel Q45 chipset support

Hi,

I have checked the list of supported chipset and board but it seems
that Intel Q45 is not yet in the list. I recall, this chipset is the
same family with Intel gm45. Anyway, the specific board I'm going to
port into is Gigabyte GA-EQ45M-S2 Rev.1. This board has Intel Q45
northbridge and ICH10(DO) southbridge, SuperIO ITE8720F

Questions:
1. Which part of the code that I need to read to add support for this
Intel Q45 and i82801J-DO?
I've been reading the coreboot/src/northbridge/intel/gm45/ section and
coreboot/src/southbridge/intel/i82801ix so far.
2. The SuperIO (ITE 8720F) is also not in the source code it seems. I
saw ITE 8721F in there but no ITE 8720F

Thanks in advance.

Kind Regards,

Darmawan
--------------------------------------------------------------------
-= Знания людей принадлежат миру =-
[-Human knowledge belongs to the world-]

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
scan-admin | 27 Feb 23:51 2015

New Defects reported by Coverity Scan for coreboot


Hi,

Please find the latest report on new defect(s) introduced to coreboot found with Coverity Scan.

3 new defect(s) introduced to coreboot found with Coverity Scan.
10 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by
Coverity Scan.

New defect(s) Reported-by: Coverity Scan
Showing 3 of 3 defect(s)

** CID 1271711:    (DEADCODE)
/src/include/device/hypertransport_def.h: 25 in offset_unit_id()
/src/include/device/hypertransport_def.h: 25 in offset_unit_id()

________________________________________________________________________________________________________
*** CID 1271711:    (DEADCODE)
/src/include/device/hypertransport_def.h: 25 in offset_unit_id()
19     #define HT_FREQ_VENDOR  15  /* AMD defines this to be 100Mhz */
20     
21     
22     static inline bool offset_unit_id(bool is_sb_ht_chain)
23     {
24     	bool need_offset = (CONFIG_HT_CHAIN_UNITID_BASE != 1) || (CONFIG_HT_CHAIN_END_UNITID_BASE != 0x20);
>>>     CID 1271711:    (DEADCODE)
>>>     Execution cannot reach the expression "0" inside this statement: "return need_offset && (0 ||...".
25     	return need_offset && (!CONFIG_SB_HT_CHAIN_UNITID_OFFSET_ONLY || is_sb_ht_chain);
26     }
27     
/src/include/device/hypertransport_def.h: 25 in offset_unit_id()
19     #define HT_FREQ_VENDOR  15  /* AMD defines this to be 100Mhz */
20     
21     
22     static inline bool offset_unit_id(bool is_sb_ht_chain)
23     {
24     	bool need_offset = (CONFIG_HT_CHAIN_UNITID_BASE != 1) || (CONFIG_HT_CHAIN_END_UNITID_BASE != 0x20);
>>>     CID 1271711:    (DEADCODE)
>>>     Execution cannot reach the expression "1" inside this statement: "return need_offset && (1 ||...".
25     	return need_offset && (!CONFIG_SB_HT_CHAIN_UNITID_OFFSET_ONLY || is_sb_ht_chain);
26     }
27     

________________________________________________________________________________________________________
To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/1016?tab=overview

To manage Coverity Scan email notifications for "coreboot <at> coreboot.org", click
https://scan.coverity.com/subscriptions/edit?email=coreboot%40coreboot.org&token=8ddd1fe26945626880b796e94d465567 .

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Emilian Bold | 26 Feb 16:23 2015
Picon

Coreboot reproducible builds

Hello,

I was trying to duplicate a coreboot build back in November and I noticed I couldn't get my ROM file to be identical to the one I found online.

It seems that Coreboot doesn't have reproducible builds yet.

Debian has been looking into this for a while https://wiki.debian.org/ReproducibleBuilds and I think Coreboot should adopt this concept.

It seems like we are halfway there with INCLUDE_CONFIG_FILE but what I've noticed is that even if I extract the CONFIG_ values the build still needs some manual tweaking.

Ideally we should record the tools used (crossgcc version, etc), the coreboot git revision id, the CONFIG_ values and the build info for the payloads (for the auto-downloaded SeaBIOS I think just the git revision id would be enough). If the timestamps and such are cleaned we should get a reproducible ROM.

Is there anyone willing to help me with this (or already working on this)?

--emi
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
cjn | 19 Feb 21:44 2015
Picon

Need help with MSI MS-7260 (K9N Neo) / MSI MS-7250 (K9N SLI)

Hi,

I'd like to run coreboot on my MSI MS-7250 (K9N SLI) mainboard. This 
board is apparently quite similar to the MSI MS-7260 (K9N Neo) which is 
already supported:

http://www.coreboot.org/Board:msi/ms7260

This is what my board looks like, though mine is a version 2.2:

http://www.msi.com/product/mb/K9N_SLI.html#hero-specification

I tried booting the board with a coreboot ROM built for the MS-7260 
(and an "AMD Athlon(tm) 64 X2 Dual Core Processor 5000+" CPU, 4 1GB DIMM 
sticks, and a Radeon 7000 graphics card). That didn't work, but I've 
attached the log. I've also attached the outputs from lspci, 
superiotool, and flashrom, for good measure.

What needs to be done and what's a good place to start?

Christian
Attachment (coreboot-boot.log): application/octet-stream, 74 KiB
-[0000:00]-+-00.0  NVIDIA Corporation MCP55 Memory Controller [10de:0369]
           +-01.0  NVIDIA Corporation MCP55 LPC Bridge [10de:0360]
           +-01.1  NVIDIA Corporation MCP55 SMBus Controller [10de:0368]
           +-02.0  NVIDIA Corporation MCP55 USB Controller [10de:036c]
           +-02.1  NVIDIA Corporation MCP55 USB Controller [10de:036d]
           +-04.0  NVIDIA Corporation MCP55 IDE [10de:036e]
           +-05.0  NVIDIA Corporation MCP55 SATA Controller [10de:037f]
           +-05.1  NVIDIA Corporation MCP55 SATA Controller [10de:037f]
           +-05.2  NVIDIA Corporation MCP55 SATA Controller [10de:037f]
           +-06.0-[01]----00.0  Advanced Micro Devices, Inc. [AMD/ATI] RV100 [Radeon 7000 / Radeon VE] [1002:5159]
           +-08.0  NVIDIA Corporation MCP55 Ethernet [10de:0373]
           +-09.0  NVIDIA Corporation MCP55 Ethernet [10de:0373]
           +-0a.0-[02]--
           +-0b.0-[03]--
           +-0c.0-[04]--
           +-0d.0-[05]--
           +-0e.0-[06]--
           +-0f.0-[07]--
           +-18.0  Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology
Configuration [1022:1100]
           +-18.1  Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
           +-18.2  Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
           \-18.3  Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
superiotool r4.0-8138-gd15bdda
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=0x0400, id=0x6888
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 0x20e...
  Failed. Returned data: id=0xffff, rev=0xf
Probing for ITE Super I/O (init=it8502e) at 0x20e...
  Failed. Returned data: id=0xffff, rev=0xf
Probing for ITE Super I/O (init=it8761e) at 0x20e...
  Failed. Returned data: id=0xffff, rev=0xf
Probing for ITE Super I/O (init=it8228e) at 0x20e...
  Failed. Returned data: id=0xffff, rev=0xf
Probing for ITE Super I/O (init=0x87,0x87) at 0x20e...
  Failed. Returned data: id=0xffff, rev=0xf
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=0xffff, rev=0xf
Probing for ITE Super I/O (init=it8502e) at 0x2e...
  Failed. Returned data: id=0xffff, rev=0xf
Probing for ITE Super I/O (init=it8761e) at 0x2e...
  Failed. Returned data: id=0xffff, rev=0xf
Probing for ITE Super I/O (init=it8228e) 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=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=0x8868, 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=0x8868
Probing for Nuvoton Super I/O (sid=0xfc) at 0x4e...
  Failed. Returned data: sid=0xff, id=0x8868, rev=0x00
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...
Found Winbond W83627EHF/EF/EHG/EG (id=0x88, rev=0x68) at 0x4e
Register dump:
idx 20 21 22 23 24 25 26 27  28 29 2a 2b 2c 2d 2e 2f
val 88 68 ff 00 04 00 40 ff  50 05 00 00 02 21 00 ff
def 88 MM ff 00 MM 00 MM RR  50 04 00 RR 00 21 00 00
LDN 0x00 (Floppy)
idx 30 60 61 70 74 f0 f1 f2  f4 f5
val 00 00 00 00 04 8e 00 ff  00 00
def 01 03 f0 06 02 8e 00 ff  00 00
LDN 0x01 (Parallel port)
idx 30 60 61 70 74 f0
val 00 00 00 00 04 3f
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 00 00 00 00 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 82
def 01 00 60 00 64 01 0c 83
LDN 0x06 (Serial flash interface)
idx 30 62 63
val 00 ff ff
def 00 00 00
LDN 0x07 (GPIO 1, GPIO 6, game port, MIDI port)
idx 30 60 61 62 63 70 f0 f1  f2 f3 f4 f5 f6 f7
val 01 00 00 00 00 00 47 c7  00 00 ff ff ff 00
def 00 02 01 03 30 09 ff 00  00 00 ff 00 00 00
LDN 0x08 (WDTO#, PLED)
idx 30 f5 f6 f7
val 00 ff 00 ff
def 00 00 00 00
LDN 0x09 (GPIO 2, GPIO 3, GPIO 4, GPIO 5, SUSLED)
idx 30 e0 e1 e2 e3 e4 e5 f0  f1 f2 f3 f4 f5 f6 f7
val 02 ff ff ff ff ff ff 5c  bf a3 09 ff ff ff ff
def 00 ff 00 00 ff 00 00 ff  00 00 00 ff 00 00 00
LDN 0x0a (ACPI)
idx 30 70 e0 e1 e2 e3 e4 e5  e6 e7 e8 f2 f3 f4 f6 f7
val 01 00 01 00 38 00 00 00  1c 00 09 7c 00 00 00 00
def 00 00 01 00 ff 08 00 RR  00 00 RR 7c 00 00 00 00
LDN 0x0b (Hardware monitor)
idx 30 60 61 70 f0 f1
val 01 0a 10 00 c1 3f
def 00 00 00 00 c1 00
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 AMD EC Super I/O at 0xaa...
Probing for Server Engines Super I/O at 0x2e...
  Failed. Returned data: id=0xffff, rev=0xff
Probing for Infineon Super I/O at 0x2e...
  Failed. Returned data: id=0xff, rev=0xff
Probing for Infineon Super I/O at 0x4e...
  Failed. Returned data: id=0xff, rev=0xff
flashrom v0.9.7-r1711 on Linux 3.10.60-std441-amd64 (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org

flashrom was built with libpci 3.2.1, GCC 4.4.7, little endian
Command line (3 args): flashrom -p internal -V
Calibrating delay loop... OS timer resolution is 2 usecs, 1292M loops per second, 10 myus = 11 us, 100 myus =
100 us, 1000 myus = 1002 us, 10000 myus = 10001 us, 8 myus = 9 us, OK.
Initializing internal programmer
No coreboot table found.
DMI string system-manufacturer: "MSI"
DMI string system-product-name: "MS-7250"
DMI string system-version: "2.0"
DMI string baseboard-manufacturer: "MSI"
DMI string baseboard-product-name: "MS-7250"
DMI string baseboard-version: "2.0"
DMI string chassis-type: "Desktop"
Found Winbond Super I/O, id 0x88
Found chipset "NVIDIA MCP55" with PCI ID 10de:0360. Enabling flash write... OK.
Enabling full flash access for board "MSI MS-7250 (K9N SLI)"... OK.
The following protocols are supported: Non-SPI.
Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT49(H)F010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Atmel AT49F080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for Atmel AT49F080T, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for ESMT F49B002UA, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0xffff, id2 0x00ff
Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
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 Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0x1b, id2 0xaf, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity
violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity
violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS.
probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS.
probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0x71, id2 0xea, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST39VF080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default
10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content,
id2 is normal flash content
Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for ST M29F400BB, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff
Probing for ST M29F400BT, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff
Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0x71, id2 0xea, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x1b, id2 0xaf, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal
flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0x1b, id2 0xaf, id1 parity violation, id1 is
normal flash content, id2 is normal flash content
Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old Winbond W29* probe method
disabled because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c
W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip.
Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB: probe_jedec_common: id1 0xda,
id2 0x54
Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39F010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39L010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39L020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.
Lockout bits:
Hardware bootblock locking (#TBL) is not active.
Hardware remaining chip locking (#WP) is not active..
Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Found Winbond flash chip "W39V040FB" (512 kB, FWH) at physical address 0xfff80000.
Lockout bits:
Hardware bootblock locking (#TBL) is not active.
Hardware remaining chip locking (#WP) is not active..
Lock status of block at 0x00000000 is Full Access.
Lock status of block at 0x00010000 is Full Access.
Lock status of block at 0x00020000 is Full Access.
Lock status of block at 0x00030000 is Full Access.
Lock status of block at 0x00040000 is Full Access.
Lock status of block at 0x00050000 is Full Access.
Lock status of block at 0x00060000 is Full Access.
Lock status of block at 0x00070000 is Full Access.
Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1
is normal flash content, id2 is normal flash content
Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xda, id2 0x54
Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation,
id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xda, id2 0x54
Multiple flash chip definitions match the detected chip(s): "W39V040B", "W39V040FB"
Please specify which chip definition to use with the -c <chipname> option.
Restoring PCI config space for 00:01:0 reg 0x6d
Restoring PCI config space for 00:01:0 reg 0x90
Restoring PCI config space for 00:01:0 reg 0x8c
Restoring PCI config space for 00:01:0 reg 0x88
--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Carl-Daniel Hailfinger | 19 Feb 00:14 2015
Picon
Picon

Automated test system: Nominations wanted

Hi,

I am currently planning to set up a test system with 5 (later up to 10)
machines boot testing each new coreboot commit. This test system will be
serviced (i.e. recovery from bricking) Mo-Fr during CET/CEST office hours.

Current goals for every commit:
- Check if coreboot + SeaBIOS are able to boot Linux to a point where
network is up and running

Current goals for every work day:
- Check if screen, keyboard and touchpad/mouse work
- Check if USB works and has the expected transfer speed (i.e. if USB
High and Super Speed both work)

Future goals for every work day:
- Run memtest86+ (short run)
- Run GRUB2 and boot Linux
- Check if USB works (see above)

Once any test running once per work day can be automated with reasonable
effort (i.e. not requiring robots or human interaction), it can be moved
to a per-commit goal.

The selection of target systems should include:
1. at least one x86 laptop without an active ME (present but inactive
would be OK)
2. at least one x86 laptop which can boot x86-blob-free (except microcode)
3. at least one x86 board or laptop which needs neither blobs (except
microcode) nor ME
4. at least one x86 board with reasonable (past or present) business
market penetration
5. if the first two laptops use the same CPU vendor, a board using a
different x86 CPU vendor

1+2 are designed to partially remove the potential for nasty surprises,
3 should remove nasty surprises completely, 4 is the one I need to show
that the test system is actually relevant for our goals, 5 should give
us better coverage outside the most common systems used by coreboot
developers.

Please nominate machines (e.g. "Thinkpad T60 with Intel graphics") and
tell me to which category they belong. If a system fits into multiple
categories, please specify that as well.
I will try to consolidate the recommendations and buy those machines.
Once the system is up and running (hopefully in May), I will add more
machines suggested by the community as time permits.

The time window for suggestions will close at the end of February.

Fire away!

Regards,
Carl-Daniel

--

-- 
coreboot mailing list: coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot


Gmane