Re: [LinuxBIOS] #87: flashrom issues on m57sli-s4

[Harald Gutmann]

Am Mittwoch, 14. November 2007 01:14:52 schrieb Carl-Daniel Hailfinger:
> On 13.11.2007 19:34, Harald Gutmann wrote:
> > Am Dienstag, 13. November 2007 16:53:54 schrieb Carl-Daniel Hailfinger:
> > > Strange. None of the changes in my patch show up in your superiotool
> > > output. That either means these registers are special or some part of
> > > the patch was ineffective or it was not applied.
> >
> > you are right! - it seems that somewhere a mistake happened to me, but i
> > can't say exactly where.
>
> Thanks for retrying manually.
> > i attached a diff between the superiotool output from new linuxbios with
> > your patch and the output from superiotool from an older revision of lb.
> > also a second diff between the new lb version with your patch and the
> > propritary bios is attached. (superiotool outputs)
>
> Thanks! It seems the patch is almost commit-ready.
> > flashrom also don't fail any more with the "old" error message, but it
> > seems to hang on probing for the mx25l4005a:
> > benchvice flashrom # ./flashrom -m gigabyte:m57sli -V
> > Calibrating delay loop... 916M loops per second. OK.
> > Found canidate at: 00000530-00000e44
> > Found LinuxBIOS table at 0x00000530.
> > LinuxBIOS table found at 0x2ac58971e530.
> > LinuxBIOS header(24) checksum: 5897 table(2324) checksum: 0c99 entries:
> > 14 Vendor ID: GIGABYTE, part ID: m57sli
> > Overwritten by command line, vendor ID: gigabyte, part ID: m57sli.
> > Found chipset "NVIDIA MCP55", enabling flash write... OK.
> > Found board "GIGABYTE GA-M57SLI-S4": enabling flash write... Serial flash
> > segment 0xfffe0000-0xffffffff enabled
> > Serial flash segment 0x000e0000-0x000fffff enabled
> > Serial flash segment 0xffee0000-0xffefffff disabled
> > Serial flash segment 0xfff80000-0xfffeffff enabled
> > LPC write to serial flash enabled
> > serial flash pin 29
> > OK.
> > Probing for Am29F040B, 512 KB
> > probe_29f040b: id1 0x7f, id2 0x45
> > Probing for Am29LV040B, 512 KB
> > probe_29f040b: id1 0x7f, id2 0x45
> > Probing for Am29F016D, 2048 KB
> > probe_29f040b: id1 0xff, id2 0xff
> > Probing for AE49F2008, 256 KB
> > probe_jedec: id1 0x7f, id2 0x45
> > Probing for At29C040A, 512 KB
> > probe_jedec: id1 0x7f, id2 0x45
> > Probing for At29C020, 256 KB
> > probe_jedec: id1 0x7f, id2 0x45
> > Probing for MBM29F400TC, 512 KB
> > probe_m29f400bt: id1 0x7f, id2 0x4c
> > Probing for MX29F002, 256 KB
> > probe_29f002: id1 0x7f, id2 0x45
> > Probing for MX25L4005, 512 KB
> >
> > at this point nothing more happens.
>
> Can you abort flashrom with Ctrl-C or does the whole machine hang?

Just flashrom hangs, and i'm able to abort it with Ctrl-C.
> If the machine does not hang, can you give me an Acked-by: tag? That way I
> can commit and improve from there.

Acked-by: Harald Gutmann
> Regards,
> Carl-Daniel

regards,
Harald