flashrom

flashrom@flashrom.org

3 participants
9189 discussions

Sharing info about flashrom HW seq code refactoring https://review.coreboot.org/q/topic:PCH_HW_SEQ_Cleanup
by Subrata Banik 31 Mar '22

31 Mar '22

Hello Team, Hope you are doing well. I would like bring this activity in your notice https://review.coreboot.org/q/topic:PCH_HW_SEQ_Cleanup and seek help to review the code. The reason for this refactoring of HW sequencing SPI driver code are: 1. We (Chrome OS team) recently ran into a firmware update issue on dogfooders (test device utilise by real users and share feedback) systems, where the attempt to perform SPI flash update operation from host-cpu (using underlying flashrom utility) is silently failing. Furthermore, we debug the issue with help of Intel and figure out the problem is related to multiple master is accessing the SPI flash and operation triggered by host-cpu side using flashrom (write and erase operation) is getting timed out (due to given lesser timeout boundary) due to underlying SPI bus is occupied by other master. This is the special case, starting from Tiger Lake Chrome Platform, where we have enable the PVAP (Protected Audio Video Path) which request CSE to perform some erase and write operation as needed. Now an attempt to perform firmware update from host-cpu side might coincide with the CSE performing SPI operations. The recommendation that coming out from Intel is to account the multiple master SPI operation while we are issuing the timeout from flashrom side. We are also expecting a doc update from Intel to share the exact timeout calculation (although I have attempted to document that early here https://review.coreboot.org/c/flashrom/+/62867/1/ichspi.c#35). 2. Maintain the code symmetry between coreboot and flashrom SPI hardware sequencing operations. From the testing side, I have tested this code on Alderlake `Brya`, Tigerlake `volteer` and Kabylake `eve` devices, and looking for help from community to check on other systems as well (if possible). Furthermore, I have attempted to increase the timeout which won't impact the flashrom performance on the older and/or existing systems. Looking forward for your help on this request. Thanks, Subrata

3 7

Inquiry about a required task for GSOC.
by Israa Odeh 31 Mar '22

31 Mar '22

Dear Flashrom Org, While I was looking for a GSOC contribution that appeals to my interests and attracts my attention. I noticed your GSOC project ideas for Flashrom, and specifically, the task labeled as "Modernize the flashrom website", which I found quite interesting. Generally, I enjoy web development using CSS, HTML, JavaScript, and PHP, and I'm willing to learn new skills, work with various frameworks, and learn about other helping platforms to enhance my abilities. However, I would like to gain more details about what this project idea requires in minute details so that I could prepare an appropriate proposal and a good plan if it is suitable to me. Please Kindly, provide me with additional information about the requirements. Examples of a bunch of details that I need to know: - Who will be the mentors? (This isn't clarified for each task separately). - What are the expected outcomes you hope to accomplish with this task? - Do you mean specifically that you need to improve the front-end? (Is it specifically a front-end improvement?) - Must the design be responsive? - Are there any predetermined languages or frameworks to use? - Could you clarify what do you mean by saying "However, we have to find out what we need and which framework supports what. Then, various frameworks need to be evaluated and we need a plan on how to migrate to the new site." I'd appreciate hearing the required details from you. Kind Regards Israa Odeh. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

2 1

SPI flashing is the future! :-)
by Stefan Zett 27 Mar '22

27 Mar '22

Hi, i am no developer and spi flashing is very interesting for me. Please can someone write a short explanation about the status registers and block protect? Just for the usual hacker. Thanks Stefan

1 0

Board Asus P7P55D-E Chipset intel P55 reading works
by Stefan Zett 26 Mar '22

26 Mar '22

sudo flashrom -V -p internal -c "MX25L1605" -r 4d.rom flashrom v1.2 on Linux 5.4.0-91-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.6.4, GCC 9.2.1 20200304, little endian Command line (7 args): flashrom -V -p internal -c MX25L1605 -r 4d.rom Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer /sys/class/mtd/mtd0 does not exist No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "P7P55D-E" DMI string baseboard-version: "Rev 1.xx" Found chipset "Intel P55" with PCI ID 8086:3b02. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Root Complex Register Block address = 0xfed1c000 GCS = 0xc65: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap: not enabled 0x7fffffff/0x7fffffff FWH IDSEL: 0x0 0x7fffffff/0x7fffffff FWH IDSEL: 0x0 0x7fffffff/0x7fffffff FWH IDSEL: 0x1 0x7fffffff/0x7fffffff FWH IDSEL: 0x1 0x7fffffff/0x7fffffff FWH IDSEL: 0x2 0x7fffffff/0x7fffffff FWH IDSEL: 0x2 0x7fffffff/0x7fffffff FWH IDSEL: 0x3 0x7fffffff/0x7fffffff FWH IDSEL: 0x3 0x7fffffff/0x7fffffff FWH IDSEL: 0x4 0x7fffffff/0x7fffffff FWH IDSEL: 0x5 0x7fffffff/0x7fffffff FWH IDSEL: 0x6 0x7fffffff/0x7fffffff FWH IDSEL: 0x7 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled Maximum FWH chip size: 0x100000 bytes SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x0b: BIOS Lock Enable: enabled, BIOS Write Enable: enabled Warning: Setting Bios Control at 0xdc from 0x0a to 0x09 failed. New value is 0x0b. SPIBAR = 0x00007fc4c1fbd000 + 0x3800 0x04: 0x6008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=0 Programming OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x000f0000 FREG0: Flash Descriptor region (0x00000000-0x0000ffff) is read-write. 0x58: 0x01ff0000 FREG1: BIOS region (0x00000000-0x001fffff) is read-write. 0x5C: 0x002f0010 FREG2: Management Engine region (0x00010000-0x0002ffff) is read-write. 0x64: 0x01ff0050 FREG4: Platform Data region (0x00050000-0x001fffff) is read-write. 0x90: 0x04 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf87f10 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=63, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05200302 (OPMENU) 0x9c: 0xc79f0190 (OPMENU+4) 0xa0: 0x00000000 (BBAR) 0xc4: 0x00000000 (LVSCC) LVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=0 0xc8: 0x00002001 (UVSCC) UVSCC: BES=0x1, WG=0, WSR=0, WEWS=0, EO=0x20 0xd0: 0x00000000 (FPB) OK. The following protocols are supported: FWH, SPI. Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2015 Found Macronix flash chip "MX25L1605" (2048 kB, SPI) mapped at physical address 0x00000000ffe00000. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: 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 Reading flash... done. Restoring MMIO space at 0x7fc4c1fc08a0 Restoring MMIO space at 0x7fc4c1fc0874 Restoring MMIO space at 0x7fc4c1fc089c Restoring MMIO space at 0x7fc4c1fc0898 Restoring MMIO space at 0x7fc4c1fc0896 Restoring MMIO space at 0x7fc4c1fc0894 Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

flashrom and ASUS PRIME_X370-PRO
by Andrew Grzegorek 26 Mar '22

26 Mar '22

sudo flashrom --programmer internal flashrom v1.2 on Linux 5.11.22-100.fc32.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x59 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. ----------------------------------------------------- lspci -nnvx 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450] Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: fast devsel 00: 22 10 50 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit [1022:1451] Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: fast devsel, IRQ 27 Capabilities: <access denied> 00: 22 10 51 14 00 04 10 00 00 00 06 08 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 00 00 00 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 0 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 1 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe900000-fe9fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 53 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f1 01 00 00 20: 90 fe 90 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 2 Bus: primary=00, secondary=02, subordinate=09, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fe400000-fe6fffff [size=3M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 53 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 02 09 00 e1 e1 00 20 20: 40 fe 60 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] DeviceName: Onboard IGD Flags: fast devsel, IOMMU group 3 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 4 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 30, IOMMU group 5 Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0 I/O behind bridge: 0000d000-0000dfff [size=4K] Memory behind bridge: fe800000-fe8fffff [size=1M] Prefetchable memory behind bridge: 00000000e0000000-00000000efffffff [size=256M] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 53 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 0a 0a 00 d1 d1 00 20 20: 80 fe 80 fe 01 e0 f1 ef 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 1a 00 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 6 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 7 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 8 Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe100000-fe3fffff [size=3M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 54 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 0b 0b 00 f1 01 00 00 20: 10 fe 30 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 9 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 32, IOMMU group 10 Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe700000-fe7fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 54 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 0c 0c 00 f1 01 00 00 20: 70 fe 70 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59) Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: 66MHz, medium devsel, IOMMU group 11 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00: 22 10 0b 79 03 04 20 02 59 00 05 0c 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 11 00: 22 10 0e 79 0f 00 20 02 51 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460] Flags: fast devsel, IOMMU group 12 00: 22 10 60 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461] Flags: fast devsel, IOMMU group 12 00: 22 10 61 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462] Flags: fast devsel, IOMMU group 12 00: 22 10 62 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463] Flags: fast devsel, IOMMU group 12 Kernel driver in use: k10temp Kernel modules: k10temp 00: 22 10 63 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464] Flags: fast devsel, IOMMU group 12 00: 22 10 64 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465] Flags: fast devsel, IOMMU group 12 00: 22 10 65 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466] Flags: fast devsel, IOMMU group 12 00: 22 10 66 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467] Flags: fast devsel, IOMMU group 12 00: 22 10 67 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] (prog-if 02 [NVM Express]) Subsystem: Samsung Electronics Co Ltd Device [144d:a801] Flags: bus master, fast devsel, latency 0, IRQ 70, NUMA node 0, IOMMU group 13 Memory at fe900000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: nvme Kernel modules: nvme 00: 4d 14 08 a8 06 04 10 00 00 02 08 01 10 00 00 00 10: 04 00 90 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 4d 14 01 a8 30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller [1022:43b9] (rev 02) (prog-if 30 [XHCI]) Subsystem: ASMedia Technology Inc. Device [1b21:1142] Flags: bus master, fast devsel, latency 0, IRQ 25, IOMMU group 14 Memory at fe6a0000 (64-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: xhci_hcd 00: 22 10 b9 43 06 04 10 00 02 30 03 0c 10 00 80 00 10: 04 00 6a fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 21 1b 42 11 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00 02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller [1022:43b5] (rev 02) (prog-if 01 [AHCI 1.0]) Subsystem: ASMedia Technology Inc. Device [1b21:1062] Flags: bus master, fast devsel, latency 0, IRQ 42, IOMMU group 14 Memory at fe680000 (32-bit, non-prefetchable) [size=128K] Expansion ROM at fe600000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: ahci 00: 22 10 b5 43 06 04 10 00 02 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 68 fe 00 00 00 00 21 1b 62 10 30: 00 00 60 fe 50 00 00 00 00 00 00 00 0a 02 00 00 02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port [1022:43b0] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 33, IOMMU group 14 Bus: primary=02, secondary=03, subordinate=09, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fe400000-fe5fffff [size=2M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b0 43 07 04 10 00 02 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 02 03 09 00 e1 e1 00 00 20: 40 fe 50 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0f 03 12 00 03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 14 Bus: primary=03, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 04 04 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 12 00 03:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 35, IOMMU group 14 Bus: primary=03, secondary=05, subordinate=05, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 05 05 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0f 01 12 00 03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 37, IOMMU group 14 Bus: primary=03, secondary=06, subordinate=06, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 06 06 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 12 00 03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 38, IOMMU group 14 Bus: primary=03, secondary=07, subordinate=07, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe500000-fe5fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 07 07 00 f1 01 00 00 20: 50 fe 50 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 12 00 03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 39, IOMMU group 14 Bus: primary=03, secondary=08, subordinate=08, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fe400000-fe4fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 08 08 00 e1 e1 00 00 20: 40 fe 40 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0f 01 12 00 03:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 14 Bus: primary=03, secondary=09, subordinate=09, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 09 09 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 12 00 07:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller [1b21:1343] (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:86f2] Flags: bus master, fast devsel, latency 0, IRQ 25, IOMMU group 14 Memory at fe500000 (64-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: xhci_hcd 00: 21 1b 43 13 06 04 10 00 00 30 03 0c 10 00 00 00 10: 04 00 50 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 f2 86 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00 08:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:85f0] Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 14 Memory at fe400000 (32-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=32] Memory at fe420000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: igb Kernel modules: igb 00: 86 80 39 15 07 04 10 00 03 00 00 02 10 00 00 00 10: 00 00 40 fe 00 00 00 00 01 e0 00 00 00 00 42 fe 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 f0 85 30: 00 00 00 00 40 00 00 00 00 00 00 00 0f 01 00 00 0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] [1002:6613] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:8094] Flags: bus master, fast devsel, latency 0, IRQ 97, IOMMU group 15 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at fe800000 (64-bit, non-prefetchable) [size=256K] I/O ports at d000 [size=256] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon, amdgpu 00: 02 10 13 66 07 04 10 00 87 00 00 03 10 00 80 00 10: 0c 00 00 e0 00 00 00 00 04 00 80 fe 00 00 00 00 20: 01 d0 00 00 00 00 00 00 00 00 00 00 62 14 94 80 30: 00 00 84 fe 48 00 00 00 00 00 00 00 0e 01 00 00 0a:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] [1002:aab0] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:aab0] Flags: bus master, fast devsel, latency 0, IRQ 99, IOMMU group 15 Memory at fe860000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 02 10 b0 aa 07 04 10 00 00 00 03 04 10 00 80 00 10: 04 00 86 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 b0 aa 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 02 00 00 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a] Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a] Flags: fast devsel, IOMMU group 16 Capabilities: <access denied> 00: 22 10 5a 14 00 00 10 00 00 00 00 13 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 5a 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 00 00 00 0b:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456] Flags: bus master, fast devsel, latency 0, IRQ 72, IOMMU group 17 Memory at fe200000 (32-bit, non-prefetchable) [size=1M] Memory at fe300000 (32-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: ccp Kernel modules: ccp 00: 22 10 56 14 06 04 10 00 00 00 80 10 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 20 fe 00 00 00 00 20: 00 00 00 00 00 00 30 fe 00 00 00 00 22 10 56 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 02 00 00 0b:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller [1022:145f] (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: bus master, fast devsel, latency 0, IRQ 61, IOMMU group 18 Memory at fe100000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: xhci_hcd 00: 22 10 5f 14 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 10 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 48 00 00 00 00 00 00 00 0f 03 00 00 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455] Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455] Flags: fast devsel, IOMMU group 19 Capabilities: <access denied> 00: 22 10 55 14 00 00 10 00 00 00 00 13 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 55 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 00 00 00 0c:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: bus master, fast devsel, latency 0, IRQ 44, IOMMU group 20 Memory at fe708000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: ahci 00: 22 10 01 79 07 04 10 00 51 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 80 70 fe 00 00 00 00 43 10 47 87 30: 00 00 00 00 48 00 00 00 00 00 00 00 0f 02 00 00 0c:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457] Subsystem: ASUSTeK Computer Inc. Device [1043:8733] Flags: bus master, fast devsel, latency 0, IRQ 101, IOMMU group 21 Memory at fe700000 (32-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 22 10 57 14 06 04 10 00 00 00 03 04 10 00 80 00 10: 00 00 70 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 33 87 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 03 00 00 ----------------------------------------------------- Best Regards, Andrew

1 0

Re: Questions About Flashrom Of Gsoc
by Anastasia Klimchuk 25 Mar '22

25 Mar '22

Hi Hui, First of all, I wanted to say, you replied to me only and not to the mailing list (and I only noticed now). Most likely you clicked the "Reply" button instead of "Reply All". I am adding the mailing list back, but for future please keep in mind to Reply All. The most important reason is that if you send your questions to the mailing list, then everyone in our community can help you! Which is really good. You will have various questions, and you never know who is the best person to answer. So, pay attention that the mailing list is on the To line ;) Some things I can answer: >> The platform Gerrit is mentioned in the "Development Guidelines." All I know about it is that it is a code management tool. Are there any tutorial videos or articles that I can use to learn more about Gerrit? Gerrit is also a code review tool. Gerrit has an official website with lots of presentations, look here https://www.gerritcodereview.com/presentations.html , hopefully that's useful! >> I went to GitHub's official Flashrom mirror. You can browse all code on GitHub, no problem, and yes it can be a convenient way to browse. Just keep in mind GitHub is a mirror, so that's pretty much only for browsing code. When you start with trying to make changes by yourself, you need to set up flashrom git repository locally. When you come to that point, open https://review.coreboot.org/admin/repos/flashrom and choose your desired method to clone the repository. Supported methods are HTTPS and SSH. The same method will also be used when you push your changes to Gerrit later. >> My current devices are a Windows 11 laptop (processor 11370H, Tiger Lake-H35) and a Mac. Is it possible for me to try out some patches on my computer? Also, could you provide me with any resources or introductions to chip packaging (DIP32, PLCC32, DIP8...)? I am wondering if someone else can take these questions? We need community help on this :) Thanks! On Thu, Mar 10, 2022 at 6:59 AM Hui Xiang <zavier2001(a)outlook.com> wrote: > Dear Anastasia, > > > > Thank you for your response. I read the "Contributor Guidelines" and have > some questions. > > > > >> "work with our git repository." > > I went to GitHub's official Flashrom mirror. The repository contains a > large number of files. Which file would you recommend I start with if I > want to familiarize myself with the current codes on GitHub? The platform > Gerrit is mentioned in the "Development Guidelines." All I know about it is > that it is a code management tool. Are there any tutorial videos or > articles that I can use to learn more about Gerrit? > > > > >> "downloaded and built flashrom as well as applied some patches." > > My current devices are a Windows 11 laptop (processor 11370H, Tiger > Lake-H35) and a Mac. Is it possible for me to try out some patches on my > computer? Also, could you provide me with any resources or introductions to > chip packaging (DIP32, PLCC32, DIP8...)? I looked them up on Google, but > there is not much information about them. > > > > >> "Check Easy projects or ask for simple tasks on the mailing list or on > IRC." > > I went to the "Easy projects" page and decided to start my job with "Find > chips without voltage data." What can I do about it? Could you provide me > with any tips and advice? Thank you very much. > > > > I joined the IRC channel through Libera. Chat. My nickname is Hui_Xiang. > Is it necessary for me to install an IRC client on my computer? Thank you > for looking into this for me. I appreciate it. > > > > Best Regards, > > Hui > > > > > > *From:* Anastasia Klimchuk <aklm(a)chromium.org> > *Sent:* 09 March 2022 01:50 > *To:* flashrom(a)flashrom.org; Hui Xiang <zavier2001(a)outlook.com> > *Subject:* Re: [flashrom] Questions About Flashrom Of Gsoc > > > > Hello Hui, > > Nice to meet you! Great to know that you are interested to work with us > this Summer of Code! > > It is very good that you looked into the list of project ideas and are > interested in one of them, and your experience in C is very relevant. > > > What resources can I use to learn more about it? > > First thing, please have a read of our Contributor Guidelines > https://www.flashrom.org/GSoC especially the “Contributor commitments & > requirements” section, and see if you can gradually start with p.1 “Prior > to project acceptance, you need to demonstrate that you can work with the > flashrom codebase”. It is important that you complete all steps from 1 to 5. > Definitely tell us how it goes! You can reply to this email, tell us what > steps you did successfully, or if not, what are the problems. > > Also look into the “How to contact us” section, join our IRC channel and > say hello! :) > > Just in case, if you haven’t read these already, here are official > guidelines for gsoc program: > https://google.github.io/gsocguides/student/ > Rules https://summerofcode.withgoogle.com/rules (at least check p.7 from > here) > > > What skills do I need to improve to get accepted from Flashrom? > > For the project you are interested in, good knowledge of C language is a > critical skill. > > Thank you! > > Anastasia. > > > -- Anastasia.

3 7

flashrom dev meeting notes 23.03.22
by Felix Singer 24 Mar '22

24 Mar '22

# Decisions on 23th March 2022: * Meeting times from not until November will alternate between two different times (to be voted upon) so that no one group will be excluded from every meeting. Time1 is EU+AU, Time2 is EU+US. * In the short term, any money collected for the Flashrom project, will be given to the coreboot project. coreboot will maintain a ledger for flashrom money. * We want a single build system (either Make or Meson). Anastasia will set up a separate meeting to discuss the “Makefile vs Meson” topic. * Next meeting will be in 2 weeks since there's still so much on the agenda. # 23th March 2022, 21:00-22:00 UTC+0 **Attendees: **Thomas, Michal, Felix, Anastasia, David, Nico, Patrick, Edward, Martin, Carl-Daniel **Agenda:** * [FelixS] Before we start discussing new topics, anything we need to discuss from the last meeting? * Leadership question is relevant to the item below, about fiscal sponsorship * [aklm] Reminder: daylight saving time is approaching. Next time we will use this time (21.00-22.00 UTC+0) in November. * For the next occurrence of dev meeting, Felix will send a poll to vote on days/times for the interval Apr-Sept. * In October we can have a vacation from each other (because there is a month diff when DST happens in different locations). * Martin: Can we have a schedule where the bad time rotates? So one out of every 3 times is poor for 1 group, but better for the other two. * Will do alternating times until november. Alternating between EU+AU and EU+US. * [Martinr] Should flashrom look for a fiscal sponsor so that it can accept donations? * [aklm] (possibly related) As an organization we can get some money per successful gsoc project (around 500 USD IIRC). Where do we put it? A bank account? * That's exactly the issue. In the past, before coreboot joined the SFC, the coreboot project had no way to accept donations, so the money was just donated directly to the SFC. By joining a fiscal sponsor, that allows money to be donated to the flashrom project to be used for purchasing test equipment, boards, servers, or whatever is needed. * [https://opensource.com/article/19/1/fiscal-sponsors-open-source](https://op… * [aklm] I just (10/03) got this comms from gsoc orgs: “For orgs who need to change their financial details for GSoC 2022, the deadline to have all of your Payoneer account information completed is July 15, 2022 as described in the Program Rules. We will not pay out stipends to any orgs who miss this hard deadline. We'll send more details about receiving stipends etc. in May so you'll have 2 months to get everything in order.” * It takes a long time to join a fiscal sponsor, so if flashrom is going to join a group, we're probably looking at 2023. * [FelixS] Since there is no legal entity around flashrom, we would have to create one first or a private person needs to take the money for now. In any case, this brings a lot of complicated implications and work (e.g. taxes). Can we just transfer the money to coreboot? * Since flashrom currently shares the coreboot infrastructure, in the short term, combining the financial interests makes sense. In the long term, we might want to look at having the projects be more separate, and getting a fiscal sponsorship for flashrom itself. * aklm will ask gsoc organizers on a mailing list, to get official reply whether 2 orgs can have the same account. * [Patrick] SFC needs some point of contact that can make decisions (e.g. about spending project money), so that's where the "leadership" thing came from in coreboot. They also strongly suggest to have at least 3 people and to avoid having outsized impact of any particular company contributing which informed how we defined our leadership group make up. * [aklm] Meson and Makefile. For upstream, Makefile is officially supported and used by developers, Meson is only used for unit tests. For chromium, Meson is officially supported and used for everything, including tests. Logically, these two should be in sync, since they are building the same code. Each side is interested in one build system (the one they are using). Can we join forces and keep two build systems in sync? * [FelixS] Thomas is about cleaning up both build systems and bringing them closer. * [Thomas] I’m working on getting the Makefile in a readable and usable state. A lot of configuration was / is done by C preprocessor macros. I’m trying to get rid of those. Since the meson.build is mostly a copy of the Makefile I want to update it when the Makefile is in a good shape. Currently the meson.build lags support for non Linux systems. I personally would prefer meson as a single build system, but we are not at this point yet. * [Edward and Martin] we need to test builds in both build systems until a single build system is selected. * [David] Are there any fundamental differences between the two build systems that cannot be resolved? We need to do gap analysis * [FelixS] I think Thomas mentioned a few things that can’t be done with Meson, or which are harder to do, but AFAIK he is working on it adding this functionality to upstream Meson. * [aklm] Do we all agree that we ideally have one build system? * YES! * Why did googlers decide to use meson? * [Edward] we want to use libflashrom instead of subprocessing, and that was supported well by meson. Also I have experience with both, and IMO meson is easier to maintain. Makefile is more ugly to do configurations for boards. * [Nico] secunet uses it in combination with FILO for firmware updates * [Thomas] I did lots of readability improvements and rework, but would like to switch to meson completely. It would be good to work with google to implement meson as the primary (and eventually only) build system. * Aklm to set up meeting (in 2 weeks from now) about meson and Makefile work, google will happily join this effort. Aklm is a google point of contact for the effort. * [Nico] Is meson capable of doing everything that Makefile is doing? Is ninja available on all platforms? * [CDH] if everything works for meson, I have no preference. But if not everything is working, then everyone will be unhappy. * [David] if we can cross-compile to DOS with meson, that would be a POC * [aklm] we do cross-compile with meson, just not for DOS * [Edward] How do we make it easy for new contributors to get involved in the project and grow the community to have more resources? * Improvements to community guidelines, * Improvements to developer documentation and expectations, * Convey appreciation to contributors and make them feel like no contribution is too small, * [aklm] Good news: this is exactly what we are doing right now! Literally, all of that starting from “How do we make it easy ….” to “.... no contribution is too small”. Importantly, these are not just words, but _lots of tasks to be done._ Since we got accepted to gsoc, already 6 people contacted us, they want to contribute. I really encourage everyone who can, to talk, respond to people, answer their questions, review their patches. I can quote myself from a previous meeting: “If you want to help and don’t know what to do, contact Anastasia or Felix.” * [dhendrix] Better automation. Git precommit hooks for style checks, etc. so that we don't waste review time telling newcomers where to put their braces, how to write a commit message, etc. * [FelixS] In my opinion, the website needs to be reworked. From my view, it’s not really inviting or motivating to read it. Also, many texts are outdated. * [David] What do we do about the GitHub mirror? Many issues and pull requests there, people are waiting for responses. * Edward suggests using [PRBot](https://github.com/ajdlinux/PRBot) * Martin: Do we want to add checks similar to coreboot's linters to the jenkins build? * Edward: Clang-format would be good. * [dhendrix]: revisit [https://review.coreboot.org/c/flashrom/+/44095](https://review.coreboot.org… ? * CDH: An automated message is much better than nothing. We need some sort of onboarding, and onboarding is always hard. * [aklm] Easy projects page, we need more easy projects for new people, please add if you have ideas. * [Nico] we have checkpatch set up for coreboot, I think this is a good thing, * [Martin] I think I can set this up. * [Martin] I can set up scan-build too * [Edward] we can display coverage in gerrit, contributors will see the progress for the changes in their patch? * [Thomas] note: tests are only for meson * [Martinr] The tests need to generate an output file, and a gerrit plugin needs to be added. coreboot currently has the files output, but the plugin isn't integrated yet. * [Felix] upstream pull requests as easy projects? * [Nico] These are not very easy projects, but there are unmerged patches on [patchwork](https://patchwork.coreboot.org/project/flashrom/list). We can see if there is some useful stuff there.

1 0

flashrom dev meeting notes 9.03.22
by Felix Singer 24 Mar '22

24 Mar '22

# Decisions 9th March 2022 * Will make this meeting bi-weekly until we've worked our way through the issues listed here. # 9th March 2022, 21:00-22:00 UTC+0 Attendees: Anastasia Klimchuk, Felix Singer, Thomas Heijligen, Stefan Reinauer, Edward O’Callaghan, Maciej Pijanowski, Miklos Marton, Martin Roth, Nico, Carl-Daniel, Piotr, Angel Pons Agenda: * [FelixS] First flashrom meeting. Let’s introduce ourselves and say what we are working on at flashrom. * [FelixS] flashrom has been accepted to GSoC * [GSoC project page](https://summerofcode.withgoogle.com/programs/2022/organizations/flash… ) * [Official announcement](https://mail.coreboot.org/hyperkitty/list/flashrom@flashrom.o… ) * Current tasks? What is left to do? * [aklm] Respond to GSoC candidates, help and guide them * [aklm] Help improve [Development Guidelines](https://www.flashrom.org/Development_Guidelines), [Easy Projects](https://www.flashrom.org/Easy_projects) pages. * If you want to help and don’t know what to do, contact Anastasia or Felix. * [Martinr] Who is the flashrom leadership and how is that decided? * [Nico] For the last years this was rather implicitly who was maintaining the code to be safe and sound. And helping users on IRC and the ML and such. * Is this how the project wants to continue? It seems somewhat disorganized. Just because someone is a good coder doesn't necessarily make them a good leader. * Who decides "safe and sound"? Are there any metrics for this? * The coreboot project has 3 people who actually make the decisions. This was set up when we joined the SFC. Also the 3 leaders need to be from different companies. * SFC has a requirement that organisation defines its leadership. What exactly the leadership is, it is up to organisation, but there should be some leadership". And that's how coreboot got leadership: coreboot wanted to join SFC, so needed to define leadership. * Which means, if flashrom wants to join SFC we need leadership too * Nico: In the past there wasn't much to decide, so there was no need for official leadership. * [Anastasia] We need someone to make decisions after a discussion on the mailing list if there isn't a clear direction. * [Edward] Some kind of election process, [Martin] organized the vote system for coreboot. * [Nico] There are currently two different projects in one repo, so if the leadership picks one, there might end up being two projects? * [Martinr] How are decisions made in the flashrom project? In this meeting, on the mailing list, something else? * [Nico] So far for smaller topics on IRC. For bigger topics, I suggest the mailing list. * [Thomas and Felix] Before deciding on leadership we need to talk more to each other. This is the first meeting we see each other and talk. We need to talk more about development, code, need to know more what we are doing. * Conclusion: let’s everyone think about it and continue discussion later. Topic added to Ongoing Items. * [Martin/Nico] Should we split flashrom into two separate projects? * Nico when I started, the project was for everyone, and stability was a priority. * Now we're trying to add the google fork, which has different objectives. * Edward: This isn't a different objective. * Quality is degrading. * Is code even tested? * Edward: yes, there's a strong emphasis on testing and improving tests. * Felix: what is tested? Is this unit testing? * Google tests any paths that they have available for testing. * Intel, AMD, Linux, mtd, Dediprog, raiden debug. * In the past, we kept all the code working for generic systems, so when support was added for a chip, it works for all of them, or bails out early. * New code is for specific boards, but not documented * [Martin] So let's focus on testing and make stability branches. * Nico: There's nobody to do that testing. * Felix: with the jenkins replacement, I'm thinking about how to add hardware tests as a part of the CI. * Miklos: There was someone who had boards with spi roms on boards with multiplexers for testing. \ Referred to this [document about the Chromium team’s hardware test setup.](https://docs.google.com/document/d/1IoBR7rHXJFiahC6dGnNKqaNFfg-q89_… ) * [Edward] Exactly this has come up between a discussion originally Martin and latter with Nikolai Artemiev to get CI coverage for writeprotect changes. * [Edward] We need to document testing what testing is done on the wiki. * Google is working on testing and making sure that the tests can be run by anyone. * [Edward]: First part of this is upstream-first unit-testing efforts, second part harder. * [Edward]: We need to get boards hooked for E2E tests, looking at what is happening for coreboot CI? * [Piotr] aklm on IRC just received commit rights without any previous discussion [[1]](https://matrix.to/#/!SAlNdlJiEjYGbpbVfu:libera.chat/$eKIApfMuImHqA9T0TowmUaTylyfJAOWTn9iK0q7itQk?via=matrix.org&via=libera.chat&via=nixos.dev ) * [Martinr] Anastasia has earned her commit rights with 125 commits over the past 2 years, more than anyone else. She is active in the community. She has done more than 82 reviews, more than anyone but Angel, Edward, and Nico. If she doesn't deserve her commit rights, Angel, Edward and Nico are the only ones who do. The discussion about commit rights is listed below, but as mentioned there, IMO, Thomas is the only other person who has earned commit rights. * [Nico] Edward’s history in the project is quite unique. He got the submit rights before he landed a single patch and with close to 0 prior activity in the project. So we can’t really put him above or below anyone in this matter. * We can absolutely look at commits and reviews that he's done since then. * [Nico] I don’t think we can decide this matter simply on the amount of patches / reviews. * [Martin] So what are your thoughts on how people should get +2? Is this also the "safe and sound" rule? You don't give any suggestions here. * [Piotr] How to get patch submitting rights in flashrom? We have 4 patches in +2 for some time: [[1]](https://review.coreboot.org/c/flashrom/+/55713/), [[2]](https://review.coreboot.org/c/flashrom/+/55714), [[3]](https://review.coreboot.org/c/flashrom/+/55714), [[4]](https://review.coreboot.org/c/flashrom/+/55848/) * Current Submitters * Anastasia Klimchuk * Angel Pons * Carl-Daniel Hailfinger * David Hendricks * Edward O'Callaghan * Idwer Vollering * Nico Huber * Patrick Georgi * Stefan T * Urja Rannikko * The only other person that has a significant number of commits in the last 5 years is Thomas Heijligen with 83 commits since July 2019. Thomas seems like a good candidate for getting submit rights. * What are the criteria for giving someone +2? When is someone ready, and who makes that decision? * coreboot has a relatively loose criteria for adding people, but decisions are made by the leadership. * Felix: Change the process about how patches are merged * Maybe require 2 +2s? * In case patches are merged too early, request that patches stay on gerrit for greater than 2 days or so? * [Carl-Daniel] We have different strategies, availability. Reviews are harder than writing code. We need to give people time to do reviews. Maybe we need to give 2 weeks time for reviewers. Unless some really bad bug which kills machines. * We have different modes of working on code, different goals. * Nico: 2 weeks is probably too long. * [Angel] too many patches sometimes, too little time. Very stressful. Patches pile up, not enough time to review and respond to everything. A feeling that if I miss something and do not respond in time then things will go wrong (e.g. errors missed during review). * [Anastasia] maybe if reviewer is busy, they can send a message to gerrit saying “sorry I am busy for next X weeks, I will get back to you after X weeks, thanks”, and this gives information to patch owner. Makes a big difference.

1 0

Flashrom Dev Meeting once a month?
by Anastasia Klimchuk 22 Mar '22

22 Mar '22

Hello Everyone, One good idea came up recently: to organize a “Flashrom Developers Meeting” so that we can talk to each other, discuss current development and future plans! The idea is, specifically, to have it regularly - and once a month seems just about right. The attendance will be, obviously, entirely optional, however one thing is important: to take notes from what has been discussed (and notes should be public). The main two questions are: when? (time) and which software to use. Time is a tricky question, and it depends on who is going to attend the meeting. We can optimize either for EU-US or for EU-AU. I can say for sure, we have at least one person from AU who is going to attend ;) (that’s me). If it turns out that we have people all over the planet who want to attend, and there is no one time that suits all, then as a plan B we can alternate between two options. That will be time1 and time2 alternating. Software. What do people use and like? I am used to Google Meet, and don’t know much about other options. What do people think of the idea? Let’s discuss! -- Anastasia.

5 18

Adding some details to the dev guidelines wiki page
by Nikolai Artemiev 21 Mar '22

21 Mar '22

Hi everyone! As a follow up to https://review.coreboot.org/c/flashrom/+/58477 and https://review.coreboot.org/c/flashrom/+/58480, I want to update the section "Adding/reviewing a new flash chip" of the dev guidelines <http://flashrom.org/Development_Guidelines> with documentation for two new chip data fields that were added: - `.reg_bits` stores information about what configuration bits the chip has and where they are found. For example,`.cmp = {STATUS2, 6, RW}` indicates that the chip has a complement bit (CMP) and it is the 6th bit of the 2nd status register. See `struct reg_bit_info` in flash.h for details on each of the structure's fields. Note that some chips have configuration bits that function like TB/SEC/CMP but are called something else in the datasheet (e.g. BP3/BP4/...). These bits should be assigned to a field according their function and the datasheet name should be noted in a comment, for example: ``` .sec = {STATUS1, 6, RW}, /* Called BP4 in datasheet, acts like SEC */ ``` - `.decode_range` points to a function that determines what protection range will be selected by particular configuration bit values. It is required for writeprotect operations on the chip. Let me know if the text is alright, thanks! Cheers, Nik

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom