[LinuxBIOS] [RFC] [PATCH] ST M29F040

[Leon Woestenberg]

Hello LinuxBIOS developers,

I had to patch flashrom to work with my FlashROM as per the supplied patch.

How exactly do I find out what probe/write/verify function triplet is 
needed. I copied from the AMD part, as to my knowledge the devices are 
fully compatible.

Tested to work on EPIA-M; write/verify and boot LinuxBIOS.

Regards,

Leon.

Index: flash.h
===================================================================
--- flash.h	(revision 2177)
+++ flash.h	(working copy)
@@ -55,6 +55,7 @@
 #define W_49F002U         0x0B	/* Winbond w29c020c device code */

#define ST_ID       	  0x20
+#define ST_M29F040B       0xE2
 #define ST_M29F400BT      0xD5

#define MSYSTEMS_ID       0x156f
Index: flashchips.c
===================================================================
--- flashchips.c	(revision 2177)
+++ flashchips.c	(working copy)
@@ -73,6 +73,8 @@
     probe_jedec, 	erase_chip_jedec, write_jedec,	NULL},
    {"W49F002U", 	WINBOND_ID, 	W_49F002U,	NULL, 256, 128,
     probe_jedec,	erase_chip_jedec, write_49f002, NULL},
+	{"M29F040B",	ST_ID, 		ST_M29F040B,	NULL, 512, 64 * 1024,
+	 probe_29f040b, erase_29f040b,	write_29f040b,	NULL},
    {"M29F400BT",	ST_ID,		ST_M29F400BT,	NULL, 512, 64 * 1024,
     probe_m29f400bt, erase_m29f400bt, write_linuxbios_m29f400bt, NULL},
    {"82802ab",	137,		173,		NULL, 512, 64 * 1024,

[Richard Smith]

> How exactly do I find out what probe/write/verify function triplet is
> needed. I copied from the AMD part, as to my knowledge the devices are
> fully compatible.

The data sheet.

I suspect that the device is compatible.  Especially if its billed as
a direct cross.  Do you have the datasheet?

[Leon Woestenberg]

Hello Richard et al,

Richard Smith wrote:
> > How exactly do I find out what probe/write/verify function triplet is
> > needed. I copied from the AMD part, as to my knowledge the devices are
> > fully compatible.
>
> The data sheet.
>
> I suspect that the device is compatible.  Especially if its billed as
> a direct cross.  Do you have the datasheet?

Sure, I do, for both the AMD and ST part.

But I do not have the time to fully cross-reference it against all 
timing specs though.

Regards,

Leon.

[Stefan Reinauer]

* Leon Woestenberg  [060224 13:25]:
> Sure, I do, for both the AMD and ST part.
>
> But I do not have the time to fully cross-reference it against all 
> timing specs though.

That part is uncritical. Make sure the block layout is the same. There
are different parts that have a "boot block" in the top (T) or bottom
(b) of the address range.

When you test flashing on your system and it works, everything except
the block sizes will be ok.

Stefan

[Leon Woestenberg]

Hello all,

Stefan Reinauer wrote:
> Leon Woestenberg  [060224 13:25]:
> > Sure, I do, for both the AMD and ST part.
> >
> > But I do not have the time to fully cross-reference it against all 
> > timing specs though.
>
> That part is uncritical. Make sure the block layout is the same. There
> are different parts that have a "boot block" in the top (T) or bottom
> (b) of the address range.
>
> When you test flashing on your system and it works, everything except
> the block sizes will be ok.

I checked and can confirm that both parts use eight uniform erase blocks 
of 64kByte each, from the datasheets.
These parts have no boot blocks BTW.

With this, I think my patch is OK for inclusion.

Regards, Leon.

[Stefan Reinauer]

* Leon Woestenberg  [060224 14:26]:
> I checked and can confirm that both parts use eight uniform erase blocks 
> of 64kByte each, from the datasheets.
> These parts have no boot blocks BTW.
>
> With this, I think my patch is OK for inclusion.

commited.

Stefan