- 08 Dec, 2008 1 commit
-
-
FENG yu ning authored
Corresponding to flashrom svn r363 and coreboot v2 svn r3804. Signed-off-by:
FENG yu ning <fengyuning1984@gmail.com> Acked-by:
Stefan Reinauer <stepan@coresystems.de>
-
- 06 Dec, 2008 1 commit
-
-
Peter Stuge authored
Looks like this: Supported flash chips: Tested OK operations: Known BAD operations: AMD Am29F002(N)BB AMD Am29F002(N)BT PROBE READ ERASE WRITE AMD Am29F016D AMD Am29F040B PROBE READ ERASE WRITE AMD Am29LV040B Atmel AT45CS1282 READ Corresponding to flashrom svn r362 and coreboot v2 svn r3803. Signed-off-by:
Peter Stuge <peter@stuge.se> Acked-by:
Uwe Hermann <uwe@hermann-uwe.de>
-
- 05 Dec, 2008 3 commits
-
-
Niels Ole Salscheider authored
This patch adds SB700 support to flashrom. The code for enabling the flash rom is the same as for SB600. It was tested (read, write, verify) with an ASUS M3A-H/HDMI which contains a Macronix MX25L8005. Corresponding to flashrom svn r361 and coreboot v2 svn r3799. Signed-off-by:
Niels Ole Salscheider <niels_ole@salscheider-online.de> Acked-by:
Peter Stuge <peter@stuge.se>
-
Peter Stuge authored
Thanks to Niels Ole Salscheider for the problem report. Corresponding to flashrom svn r360 and coreboot v2 svn r3798. Signed-off-by:
Peter Stuge <peter@stuge.se> Acked-by:
Peter Stuge <peter@stuge.se>
-
Peter Stuge authored
Flashrom used to exit 0 even if erase failed. Not anymore. Corresponding to flashrom svn r359 and coreboot v2 svn r3797. Signed-off-by:
Peter Stuge <peter@stuge.se> Acked-by:
Stefan Reinauer <stepan@coresystems.de>
-
- 04 Dec, 2008 1 commit
-
-
Carl-Daniel Hailfinger authored
SST_25VF512A_REMS SST_25VF010_REMS SST_25VF020_REMS SST_25VF040_REMS SST_25VF040B_REMS SST_25VF080_REMS SST_25VF080B_REMS SST_25VF032B_REMS SST_26VF016 SST_26VF032 W_25X16 W_25X32 W_25X64 Straight from the data sheets. The REMS IDs help in case the RDID opcode is unavailable (due to opcode lockdown) or unsupported by the chip. Some day, we need to pair probe functions together with IDs. Multiple pairs can exist per chip and duplicating chip definitions does not really make sense. Corresponding to flashrom svn r358 and coreboot v2 svn r3793. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
-
- 03 Dec, 2008 3 commits
-
-
Peter Stuge authored
Bug from r3791. Corresponding to flashrom svn r357 and coreboot v2 svn r3792. Signed-off-by:
Peter Stuge <peter@stuge.se> Acked-by:
Peter Stuge <peter@stuge.se>
-
Peter Stuge authored
If flashbase was set before probe_flash() it would only ever be used once, for the very first flash chip probe. Corresponding to flashrom svn r356 and coreboot v2 svn r3791. Signed-off-by:
Peter Stuge <peter@stuge.se> Acked-by:
Peter Stuge <peter@stuge.se>
-
Stefan Reinauer authored
Fixes #109 Corresponding to flashrom svn r355 and coreboot v2 svn r3790. Signed-off-by:
Stefan Reinauer <stepan@coresystems.de> Signed-off-by:
Peter Stuge <peter@stuge.se> Acked-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
-
- 29 Nov, 2008 1 commit
-
-
Jason Wang authored
Corresponding to flashrom svn r354 and coreboot v2 svn r3782. Signed-off-by:
Jason Wang <Qingpei.wang@amd.com> Reviewed-by:
Joe, Bao <Zheng.Bao@amd.com> Acked-by:
Stefan Reinauer <stepan@coresystems.de>
-
- 28 Nov, 2008 5 commits
-
-
Carl-Daniel Hailfinger authored
Corresponding to flashrom svn r353 and coreboot v2 svn r3781. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
-
Carl-Daniel Hailfinger authored
If a chip has any TEST_BAD_* flag set, we don't even list the unsupported functions, giving the user the impression that the unsupported functions are tested. Corresponding to flashrom svn r352 and coreboot v2 svn r3780. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Peter Stuge <peter@stuge.se>
-
Jason Wang authored
This has been tested by Uwe Hermann on an RS690/SB600 board. Corresponding to flashrom svn r351 and coreboot v2 svn r3779. Signed-off-by:
Jason Wang <Qingpei.Wang@amd.com> Reviewed-by:
Joe Bao <zheng.bao@amd.com> Acked-by:
Uwe Hermann <uwe@hermann-uwe.de>
-
Jason Wang authored
This is the first chip which uses the infrastructure for alternative erase commands, namely spi_chip_erase_60_c7(). Corresponding to flashrom svn r350 and coreboot v2 svn r3776. Signed-off-by:
Jason Wang <Qingpei.Wang@amd.com> Reviewed-by:
Joe Bao <zheng.bao@amd.com> Acked-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
-
Carl-Daniel Hailfinger authored
- probe_spi_rdid with opcode 0x9f, usually 3 bytes ID - probe_spi_res with opcode 0xab, usually 1 byte ID We are missing the following probe function: - probe_spi_rems with opcode 0x90, usually 2 bytes ID RDID provides best specifity (manufacturer, device class and device) and RES is supported by quite a few old chips. However, RES only returns one byte and there are multiple flash chips with different sizes on the market and all of them have the same RES ID. REMS is from the same age as RES, but it provides a manufacturer and a device ID. It is therefore on par with the probing for parallel flash chips and specific enough. The order in which chips should be detected is as follows: 1. RDID 2. REMS 3. RES Corresponding to flashrom svn r349 and coreboot v2 svn r3775. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Peter Stuge <peter@stuge.se>
-
- 27 Nov, 2008 1 commit
-
-
Carl-Daniel Hailfinger authored
The existing check in probe_spi_res() was right for SPI controllers which support all commands, but may not exist. For controllers which support only a subset of commands, it will fail in unexpected ways. Even if a command is supported by the controller, it may be unavailable if the controller is locked down. The new logic checks if RDID could be issued and its return values made sense (not 0xff 0xff 0xff). In that case, RES probing is not performed. Otherwise, we try RES. There is one drawback: If RDID returned unexpected values, we don't issue a RES probe. However, in that case we should try to match RDID anyway. Corresponding to flashrom svn r348 and coreboot v2 svn r3774. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
FENG yu ning <fengyuning1984@gmail.com>
-
- 24 Nov, 2008 1 commit
-
-
Tero O Peippola authored
Tested on gigabyte m57sli. File util/flashrom/flash.h already had correct ID for that part. Corresponding to flashrom svn r347 and coreboot v2 svn r3769. Signed-off-by:
Tero O Peippola <xeropp@gmail.com> Acked-by:
Peter Stuge <peter@stuge.se>
-
- 18 Nov, 2008 3 commits
-
-
Carl-Daniel Hailfinger authored
Currently flashrom assumes every vendor BIOS shares our view about which SPI opcodes should be placed in which location. Move to a less optimistic implementation and actually use the generic SPI read functions. They're useful for abstracting exactly this stuff and that makes them the preferred choice. Corresponding to flashrom svn r346 and coreboot v2 svn r3758. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Stefan Reinauer <stepan@coresystems.de>
-
Carl-Daniel Hailfinger authored
Although SPI itself does not have a mechanism to signal command failure, the SPI host may be unable to send a given command over the wire due to security or hardware limitations. The current code ignores these mechanisms completely and simply assumes almost every command succeeds. Complain if SPI command execution fails. Since locked down Intel chipsets (like the one we had problems with earlier) only allow a small subset of commands, find the common subset of commands between the chipset and the ROM in the chip erase case. That is accomplished by the new spi_chip_erase_60_c7() which can be used for chips supporting both 0x60 and 0xc7 chip erase commands. Both parts of the patch address problems seen in the real world. The increased verbosity for the error case will help us diagnose and address problems better. Corresponding to flashrom svn r345 and coreboot v2 svn r3757. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Otherwise: Acked-by: Stefan Reinauer <stepan@coresystems.de>
-
Carl-Daniel Hailfinger authored
AT25DF021 AT25DF041A AT25DF081 AT25DF161 AT25DF321A AT25DF641 AT25F512B AT25FS010 AT25FS040 AT26DF041 AT26DF081A AT26DF161 AT26DF161A AT26DF321 AT26F004 I double-checked the data sheets and am confident this will work. Corresponding to flashrom svn r344 and coreboot v2 svn r3756. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Stefan Reinauer <stepan@coresystems.de>
-
- 17 Nov, 2008 1 commit
-
-
Mart Raudsepp authored
Tested fully on a ThinCan DBE61A Corresponding to flashrom svn r343 and coreboot v2 svn r3755. Signed-off-by:
Mart Raudsepp <mart.raudsepp@artecdesign.ee> Acked-by:
Mart Raudsepp <mart.raudsepp@artecdesign.ee>
-
- 15 Nov, 2008 1 commit
-
-
Carl-Daniel Hailfinger authored
The AT45 series SPI chips are DataFlash EEPROMs which means they have odd (non-power-of-two) sector sizes, but some of the DataFlash chips can be configured or ordered with power-of-two sector sizes. Add probe support for the following Atmel SPI chips: AT25DF021 AT25DF041A AT25DF081 AT25DF161 AT25DF321A AT25DF641 AT25F512B AT25FS010 AT25FS040 AT26DF041 AT26DF081A AT26DF161 AT26DF161A AT26DF321 AT26F004 AT45CS1282 AT45DB011D AT45DB021D AT45DB041D AT45DB081D AT45DB161D AT45DB321C AT45DB321D AT45DB642D Add an explanation why the following chips can't be probed: AT45BR3214B AT45D011 AT45D021A AT45D041A AT45D081A AT45D161 AT45DB011 AT45DB011B AT45DB021A AT45DB021B AT45DB041A AT45DB081A AT45DB161 AT45DB161B AT45DB321 AT45DB321B AT45DB642 Add the ID, but no probing function for this chip: AT25F512A Corresponding to flashrom svn r342 and coreboot v2 svn r3754. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Tested-by:
Jesse Brandeburg <jesse.brandeburg@intel.com> Tested-by:
Andriy Gapon <avg@icyb.net.ua> Acked-by:
Myles Watson <mylesgw@gmail.com>
-
- 08 Nov, 2008 1 commit
-
-
Peter Stuge authored
Per report from Mario Rogen. Thanks! Corresponding to flashrom svn r341 and coreboot v2 svn r3736. Signed-off-by:
Peter Stuge <peter@stuge.se> Acked-by:
Peter Stuge <peter@stuge.se>
-
- 05 Nov, 2008 1 commit
-
-
Carl-Daniel Hailfinger authored
This has been confirmed by Stéphan Guilloux. Corresponding to flashrom svn r340 and coreboot v2 svn r3731. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
-
- 04 Nov, 2008 1 commit
-
-
Carl-Daniel Hailfinger authored
Replace age-old TODO comments with real explanations. Fixed chips: Fujitsu MBM29F400TC (ID definition) Macronix MX29F002T (chip name) New chips: Fujitsu MBM29F004BC Fujitsu MBM29F004TC Fujitsu MBM29F400BC Macronix MX25L512 Macronix MX25L1005 Macronix MX25L2005 Macronix MX25L6405 Macronix MX29F002B Straight from the data sheets, compile tested only. Corresponding to flashrom svn r339 and coreboot v2 svn r3730. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Uwe Hermann <uwe@hermann-uwe.de>
-
- 03 Nov, 2008 2 commits
-
-
Carl-Daniel Hailfinger authored
This helps a lot if we have to track down configuration weirdnesses. Corresponding to flashrom svn r338 and coreboot v2 svn r3723. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Stefan Reinauer <stepan@coresystems.de>
-
Carl-Daniel Hailfinger authored
Not all chips support all commands, so allow the implementer to select the matching function. Fix a layering violation in ICH SPI code to be less bad. Still not perfect, but the new code is shorter, more generic and architecturally more sound. TODO (in a separate patch): - move the generic sector erase code to spi.c - decide which erase command to use based on info about the chip - create a generic spi_erase_all_sectors function which calls the generic sector erase function Thanks to Stefan for reviewing and commenting. Corresponding to flashrom svn r337 and coreboot v2 svn r3722. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by:
Stefan Reinauer <stepan@coresystems.de>
-
- 02 Nov, 2008 2 commits
-
-
Stefan Reinauer authored
This is slightly slower (ha, ha), but works on boards with a locked opmenu. Tested on ICH7 and works. Corresponding to flashrom svn r336 and coreboot v2 svn r3721. Signed-off-by:
Stefan Reinauer <stepan@coresystems.de> Acked-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
-
Carl-Daniel Hailfinger authored
Identification only, erase/write are not implemented. Corresponding to flashrom svn r335 and coreboot v2 svn r3717. Signed-off-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> tested and Acked-by:
Elia Yehuda <z4ziggy@gmail.com>
-
- 30 Oct, 2008 1 commit
-
-
Uwe Hermann authored
- SST SST39SF010A - Winbond W29C011 Tested by me on actual hardware, all operations. Corresponding to flashrom svn r334 and coreboot v2 svn r3708. Signed-off-by:
Uwe Hermann <uwe@hermann-uwe.de> Acked-by:
Uwe Hermann <uwe@hermann-uwe.de>
-
- 29 Oct, 2008 2 commits
-
-
Stefan Reinauer authored
Using block erase d8 as discussed with Peter Stuge Corresponding to flashrom svn r333 and coreboot v2 svn r3707. Signed-off-by:
Stefan Reinauer <stepan@coresystems.de> Acked-by:
Stefan Reinauer <stepan@coresystems.de>
-
Ed Swierk authored
Corresponding to flashrom svn r332 and coreboot v2 svn r3706. Signed-off-by:
Ed Swierk <eswierk@aristanetworks.com> Acked-by:
Ed Swierk <eswierk@aristanetworks.com>
-
- 28 Oct, 2008 2 commits
-
-
Uwe Hermann authored
Tested by Martin Stecklum <stecky@gmx.net> (both write and erase). The tests were done on an MSI MS-7065 board, so that's supported now too. Corresponding to flashrom svn r331 and coreboot v2 svn r3697. Signed-off-by:
Uwe Hermann <uwe@hermann-uwe.de> Acked-by:
Uwe Hermann <uwe@hermann-uwe.de>
-
Uwe Hermann authored
Untested, but should work just as well as the other *PIIX* southbridges according to the datasheets. Corresponding to flashrom svn r330 and coreboot v2 svn r3696. Signed-off-by:
Uwe Hermann <uwe@hermann-uwe.de> Acked-by:
Uwe Hermann <uwe@hermann-uwe.de>
-
- 26 Oct, 2008 1 commit
-
-
Uwe Hermann authored
Tested on PIIX3 hardware. Corresponding to flashrom svn r329 and coreboot v2 svn r3694. Signed-off-by:
Uwe Hermann <uwe@hermann-uwe.de> Acked-by:
Corey Osgood <corey.osgood@gmail.com>
-
- 25 Oct, 2008 1 commit
-
-
Uwe Hermann authored
Corresponding to flashrom svn r328 and coreboot v2 svn r3693. Signed-off-by:
Uwe Hermann <uwe@hermann-uwe.de> Acked-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
-
- 21 Oct, 2008 1 commit
-
-
Uwe Hermann authored
This has been tested on hardware by me. Corresponding to flashrom svn r327 and coreboot v2 svn r3682. Signed-off-by:
Uwe Hermann <uwe@hermann-uwe.de> Acked-by:
Uwe Hermann <uwe@hermann-uwe.de>
-
- 18 Oct, 2008 2 commits
-
-
Uwe Hermann authored
Corresponding to flashrom svn r326 and coreboot v2 svn r3669. Signed-off-by:
Uwe Hermann <uwe@hermann-uwe.de> Acked-by:
Uwe Hermann <uwe@hermann-uwe.de>
-
Urja Rannikko authored
Based on the 5595 datasheet and uniflash 1.40 sources, only looking for info about SiS620. Corresponding to flashrom svn r325 and coreboot v2 svn r3668. Signed-off-by:
Urja Rannikko <urjaman@gmail.com> Acked-by:
Peter Stuge <peter@stuge.se>
-
- 15 Oct, 2008 1 commit
-
-
Marc Jones authored
It is not possible to write enable that area once the register is set so print a warning. Corresponding to flashrom svn r324 and coreboot v2 svn r3659. Signed-off-by:
Marc Jones <marcj.jones@amd.com> Acked-by:
Ronald G. Minnich <rminnich@gmail.com> Acked-by:
Peter Stuge <peter@stuge.se> Acked-by:
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
-