coreboot May 2013

coreboot@coreboot.org

38 participants
91 discussions

OT: Submitted MTRR patches for Linux kernel
by Paul Menzel 06 May '13

06 May '13

Dear coreboot folks, just a note to inform you, that Andy Lutomirski sent some MTRR patches to the Linux kernel lists [1] with the following cover letter. [PATCH 0/7] Clean up write-combining MTRR addition A fair number of drivers (mostly graphics) add write-combining MTRRs. Most ignore errors and most add the MTRR even on PAT systems which don't need to use MTRRs. This series adds new functions mtrr_{add,del}_wc_if_needed and drm_mtrr_{add,del}_wc that report errors and do nothing if PAT is enabled. I've only tested the radeon driver, since I don't have test hardware easily available for the other drivers. Benefits include: - Simpler code - No more complaints about MTRR conflict warnings on PAT systems - Eventual unexporting of the MTRR API? This series eliminates about half of the mtrr_add calls in drivers/. The series is also at: https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=mtrr_cle… Andy Lutomirski (7): x86: Add mtrr_{add,del}_wc_if_needed drm (ast,cirrus,mgag200,nouveau,savage,vmwgfx): Rework drm_mtrr_{add,del} drm: Update drm_addmap and drm_mmap to use PAT WC instead of MTRRs drm: Use drm_mtrr_add_wc for the AGP aperture i915: Use drm_mtrr_{add,del}_wc radeon: Switch to drm_mtrr_add_wc and add a missing drm_mtrr_del_wc uvesafb: Clean up MTRR code I have not looked at them, but maybe some of the ideas can be used for coreboot too. Thanks, Paul [1] http://www.spinics.net/lists/dri-devel/msg38048.html

1 0

Re: [coreboot] On loongson CPU or MIPS ARCH
by li guang 06 May '13

06 May '13

在 2013-04-30二的 10:00 -0700，ron minnich写道： > OK, I took a look at the code. Nice to see such a simple startup, > reminds of linuxbios v1 days. At least if this is the right one: > http://fossies.org/linux/misc/grub-2.00.tar.gz:a/grub-2.00/grub-core/boot/m… > > I don't see a problem pulling this in to coreboot. We'd probably trim > some bits out and let ramstage take over, but for a first cut it could > be used as is. This code is very similar in how it works to many > linuxbios/coreboot platforms and hence should fit into the coreboot > structure with ease. > > The first step remains the same: set up crossgcc. I talked to stefan > yesterday about incorporating extant loongson patches into a gcc build > and he mentioned that the utility is designed to allow you to specify > patches to be pulled at build time. > > So, let's start with crossgcc for mips/loongson. This is a minimum requirement. > AFAIK, patches for gcc has been included, seems a patch for binutil is required, http://sourceware.org/ml/binutils/2009-11/msg00387.html BTW, I have to build mipsel-elf by hand for poor-internet-access-speed.

1 0

Re: [coreboot] ASUS A8AE-LE
by Peter Stuge 05 May '13

05 May '13

PivotMasterD1 . wrote: > Are there any plans to support It is safe to assume that the answer is always 'no'. If you want the code, you have to write it. //Peter

1 0

ASUS A8AE-LE
by PivotMasterD1 . 04 May '13

04 May '13

Are there any plans to support the ASUS A8AE-LE (Amberine M)? According to HP, this board (Socket 939) has an ATI RS480 NB, ATI SB400 SB, and an Asus A8000 Super I/O. lspci: 00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI RS480 Host Bridge (rev 10) 00:02.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS480 PCI-X Root Port 00:12.0 IDE interface: Advanced Micro Devices [AMD] nee ATI IXP SB400 Serial ATA Controller 00:13.0 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB Host Controller 00:13.1 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB Host Controller 00:13.2 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB2 Host Controller 00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI IXP SB400 SMBus Controller (rev 11) 00:14.1 IDE interface: Advanced Micro Devices [AMD] nee ATI IXP SB400 IDE Controller 00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI IXP SB400 PCI-ISA Bridge 00:14.4 PCI bridge: Advanced Micro Devices [AMD] nee ATI IXP SB400 PCI-PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 6570] 01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Turks/Whistler HDMI Audio [Radeon HD 6000 Series] 02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 02:05.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 80) 02:09.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] flashrom --programmer internal -V: flashrom v0.9.6.1-r1564 on Linux 3.8.0 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.10, GCC 4.6.3, little endian Command line (3 args): flashrom --programmer internal -V Calibrating delay loop... OS timer resolution is 3 usecs, 469M loops per second, 10 myus = 11 us, 100 myus = 97 us, 1000 myus = 945 us, 10000 myus = 9444 us, 12 myus = 13 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "ASUSTeK Computer INC." DMI string system-product-name: "RS482-SB400" DMI string system-version: " " DMI string baseboard-manufacturer: "ASUSTek Computer INC." DMI string baseboard-product-name: "Amberine M" DMI string baseboard-version: "1.03" DMI string chassis-type: "Desktop" Found chipset "ATI SB400" with PCI ID 1002:4377. Enabling flash write... OK. Disabling flash write protection for board "ASUS A8AE-LE"... OK. The following protocols are supported: Non-SPI. Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0x00, 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 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0x54, id2 0x75, 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 0x24, id2 0x42, 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 0x00, 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 0x00, 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 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, 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 0x24, id2 0x42, 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 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for EMST F49B002UA, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0x00, 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 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0x54, id2 0x75, 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 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for Fujitsu MBM29F400TC, 512 kB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, 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 0x9d, id2 0x6e Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0x24, id2 0x42, 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 0x24, id2 0x42, 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 0x24, id2 0x42, 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 0x24, id2 0x2d, 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 0x24, id2 0x2d, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x24, id2 0x42, 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 0x00, 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 0x00, 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 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x54, id2 0x75, 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 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0x00, 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 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0x2a, id2 0x42, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH) at physical address 0xfff80000. 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 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e 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 0x9d, id2 0x6e Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x24, id2 0x42, 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 0x9d, id2 0x6e Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e 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 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for ST M29F400BT, 512 kB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0x00, 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 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0x2a, id2 0x42, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x24, id2 0x42, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x24, id2 0x42, 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 0x54, id2 0x75, 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 0x24, id2 0x42, 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 0x9d, id2 0x6e Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0x54, id2 0x75, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0x54, id2 0x75, 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 0x9d, id2 0x6e Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e 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 0x9d, id2 0x6e Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e 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 0x9d, id2 0x6e Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH). No operations were specified. Restoring PCI config space for 00:14:3 reg 0x48 Restoring PCI config space for 00:14:0 reg 0x79

1 0

cooperative multitasking
by Aaron Durbin 03 May '13

03 May '13

Hi, I just uploaded some patches that implement the ability to cooperatively multitask on the boot cpu. The patches still need some cleaning up, but I wanted to start the conversation. Fwiw, Ron claims he needs this. So blame him. This notion does allow for people to write state machines using the callbacks and can still rely on synchronous programming. Patches are here: remote: http://review.coreboot.org/3191 remote: http://review.coreboot.org/3192 remote: http://review.coreboot.org/3193 -Aaron

1 0

Re: [coreboot] UDELAY_IO
by David Hubbard 03 May '13

03 May '13

http://review.coreboot.org/#/c/3178/ Tested the change on F2A85-M with no issues. David

1 0

Re: [coreboot] Question about STACK_SIZE
by Stefan Reinauer 03 May '13

03 May '13

* Marc Jones <marcj303(a)gmail.com> [130502 20:24]: > On Thu, May 2, 2013 at 12:22 PM, Stefan Reinauer > <stefan.reinauer(a)coreboot.org> wrote: > > * Aaron Durbin <adurbin(a)google.com> [130502 17:39]: > >> OK. Thanks for the info. That does make for some huge memory > >> footprints on the AMD machines with a large number of CONFIG_MAX_CPUS. > >> I'd be curious to know why the BSP for the AMD code requires so much > >> while in ramstage. > >> > >> -Aaron > > > > One of the majore things needed on the BSP used to be lzma decompression > > which put a 16K array on the stack. We fixed this a while ago, bringing > > down stack usage on our Intel based boards to about 1K (and giving each > > core a 4K stack) > > > > We fixed the issue by putting that big array in the heap instead. Maybe > > we can fix the AMD code in the same way. > > > > I would like to see some actual stack usage data first though > > > > Stefan > > > > I agree. Can we get a list of boards (I am busy and lazy). We probably > have some of the systems at Sage. Asrock E350M1 (using Agesa) CPU0: stack: 002b0000 - 002c0000, lowest used address 002bf75c, stack used: 2212 bytes CPU1: stack: 002a0000 - 002b0000, lowest used address 002afda8, stack used: 600 bytes So it would work just fine with the default 4K stack size, even if it took almost twice of the above measurement due to more complex hardware in the system (extremely unlikely) Boards with custom stack size: * asrock/e350m1 * asus/f2a85-m * technexion/tim5690 * msi/ms9652_fam10 * tyan/s8226 * supermicro/h8scm * supermicro/h8qgi * supermicro/h8qme_fam10 * amd/inagua * amd/parmer * amd/south_station * amd/thatcher * amd/dinar * amd/torpedo * amd/persimmon * amd/union_station * lippert/frontrunner-af * lippert/toucan-af Regards, Stefan

2 1

Re: [coreboot] GSoC student application period closes Friday, 03.05.2013
by Marc Jones 03 May '13

03 May '13

Less than 20 hours until the deadline closes. Please submit your applications. https://www.google-melange.com/gsoc/org/google/gsoc2013/coreboot On Wed, May 1, 2013 at 2:37 PM, Marc Jones <marcj303(a)gmail.com> wrote: > The deadline for student applications ends 03.05.2013, 19:00 UTC. > Note that the UTC time. I recoemmend that you get the something > submitted by Thursday. > > Please visit the wiki for more information: http://www.coreboot.org/GSoC > > http://www.coreboot.org/GSoC#coreboot_Summer_of_Code_Application > > Marc > > > -- > http://se-eng.com -- http://se-eng.com

1 0

Re: [coreboot] Question about STACK_SIZE
by Patrick Georgi 02 May '13

02 May '13

Am 02.05.2013 16:32, schrieb Aaron Durbin: > I am wondering why the ramstage stack size is so large on a lot of boards: > Is this just an artifact of copy-n-paste? What is driving the > requirement for such large stack sizes? Other than for wakeup-from-suspend, no-one ever cares if that's 4k or 400k, except that things might fail if it is too small. And Google is the first organisation with a huge interest in an optimized wakeup in coreboot. Patrick

3 2

Re: [coreboot] Question about STACK_SIZE
by Stefan Reinauer 02 May '13

02 May '13

* Aaron Durbin <adurbin(a)google.com> [130502 17:39]: > OK. Thanks for the info. That does make for some huge memory > footprints on the AMD machines with a large number of CONFIG_MAX_CPUS. > I'd be curious to know why the BSP for the AMD code requires so much > while in ramstage. > > -Aaron One of the majore things needed on the BSP used to be lzma decompression which put a 16K array on the stack. We fixed this a while ago, bringing down stack usage on our Intel based boards to about 1K (and giving each core a 4K stack) We fixed the issue by putting that big array in the heap instead. Maybe we can fix the AMD code in the same way. I would like to see some actual stack usage data first though Stefan

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot May 2013