diff options
| author | Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> | 2007-12-31 01:49:00 +0000 |
|---|---|---|
| committer | Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> | 2007-12-31 01:49:00 +0000 |
| commit | ae8afa9ddb709985bfd5bce38c30610cc3e47abe (patch) | |
| tree | 6d4c9d27ad37db63a247647d01ec92d20a663033 /flashchips.c | |
| parent | c2a18452b14481adffcbc894c1342404f8e737a5 (diff) | |
| download | flashrom-ae8afa9ddb709985bfd5bce38c30610cc3e47abe.tar.gz flashrom-ae8afa9ddb709985bfd5bce38c30610cc3e47abe.tar.bz2 flashrom-ae8afa9ddb709985bfd5bce38c30610cc3e47abe.zip | |
Add continuation ID support to jedec.c
The continuation ID code does not go further than checking for IDs of
the type 0x7fXX, but does this for vendor and product ID. The current
published JEDEC spec has a list where the largest vendor ID is 7 bytes
long, but all leading bytes are 0x7f. The list will grow in the future,
and using a 64bit variable will not be enough anymore.
Besides that, it seems that the location of the ID byte after the first
continuation ID byte is very vendor specific, so we may have to revisit
that code some time in the future.
(Suggestion for a new encoding:
Use a two-byte data type for the ID, the lower byte contains the only
non-0x7f byte, the upper byte contains the number of 0x7f bytes used as
prefix, which is the bank number minus 1 the vendor ID appears in.)
Add support for EON EN29F002AT.
Corresponding to flashrom svn r171 and coreboot v2 svn r3030.
Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Acked-by: Corey Osgood <corey.osgood@gmail.com>
Diffstat (limited to 'flashchips.c')
| -rw-r--r-- | flashchips.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/flashchips.c b/flashchips.c index 2bd039d72..71f2d8ef9 100644 --- a/flashchips.c +++ b/flashchips.c @@ -42,6 +42,9 @@ struct flashchip flashchips[] = { probe_jedec, erase_chip_jedec, write_jedec}, {"At49F002(N)T",ATMEL_ID, AT_49F002NT, 256, 256, probe_jedec, erase_chip_jedec, write_jedec}, + /* The EN29F002AT can do byte program at arbitrary boundaries. */ + {"EN29F002AT", EON_ID, EN_29F002AT, 256, 256, + probe_jedec, erase_chip_jedec, write_jedec}, {"MBM29F400TC", FUJITSU_ID, MBM29F400TC_STRANGE, 512, 64 * 1024, probe_m29f400bt, erase_m29f400bt, write_linuxbios_m29f400bt}, {"MX29F002", MX_ID, MX_29F002, 256, 64 * 1024, |