[flashrom] flashrom Digest, Vol 12, Issue 35

Thu May 20 20:31:59 CEST 2010

Hello Guenter,

Thank you for taking the time to look for info about my MB. It is very
similar to the one in the picture that you asked me to look at.

I guess I have found the chip that you need to know about. It was covered by
a heatsink and that's why I didn't see it. I hope this is the one. If it is
not I will ask a friend to take a good picture of my MB. Please let me know.

The chip that I uncovered says:

Intel
*NH82801IR*
L7395128
SLA9N

On the board I can also read:
Foxconn DG33M03
SE0709
Rev A00

Hope that this helps.

Thank you!
Julio

On 20 May 2010 18:12, <flashrom-request at flashrom.org> wrote:

> Send flashrom mailing list submissions to
>        flashrom at flashrom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://www.flashrom.org/mailman/listinfo/flashrom
> or, via email, send a message with subject or body 'help' to
>        flashrom-request at flashrom.org
>
> You can reach the person managing the list at
>        flashrom-owner at flashrom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of flashrom digest..."
>
>
> Today's Topics:
>
>   1. Re: disaster (Carl-Daniel Hailfinger)
>   2. Re: disaster (Julio Barrios)
>   3. Re: disaster (Carl-Daniel Hailfinger)
>   4. Re: disaster (Julio Barrios)
>   5. Re: disaster (Guenter)
>   6. TYAN s3992 (Alessandro Gervaso)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 20 May 2010 12:50:39 +0200
> From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006 at gmx.net>
> To: Julio Barrios <jvbn.barrios at yahoo.co.uk>, flashrom
>        <flashrom at flashrom.org>
> Subject: Re: [flashrom] disaster
> Message-ID: <4BF513FF.60006 at gmx.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Julio,
>
> it seems flashrom at flashrom.org was left out of the conversation by
> accident. I've added it back, please use the "reply all" button in the
> future.
>
> On 20.05.2010 12:12, Julio Barrios wrote:
> > Hi Carl-Daniel, Joseph and Michael,
> >
> > Many thanks for your replies. I very much appreciate it. I'm not sure if
> a
> > flash chip is the same as the BIOS chip (I'm a complete newbie here and
> am
> > just learning a bit, and destroying computers along the way it seems
> LOL!).
> > Anyway, my BIOS is a Phoenix D686 and my PC is a Dell Inspiron 530.
> >
>
> "Phoenix D686" is probably written on a sticker. Can you peel off the
> sticker and tell us what's written on the BIOS flash chip?
>
>
> > By the look of things, I guess that I will need to buy a new motherboard.
> If
> > that is the case, then I will need to buy one that is compatible with
> linux
> > because I'm not prepared to give up Ubuntu and go back to Windows.
> >
> > If you need any more information so that you can help me, please let me
> > know.
> >
>
> Some people/companies in the UK offer services to reflash mainboards.
> That might be what you want, but I'm not sure if the shipping cost is
> worth it.
> Besides that, some vendors might offer top hat flash solutions for your
> board, but I'm not 100% sure about this.
>
>
> > Again, guys, thanks a lot.
> >
> > Julio
> >
>
> Good luck!
>
> Regards,
> Carl-Daniel
>
>
> > On 20 May 2010 09:45, Carl-Daniel Hailfinger <
> > c-d.hailfinger.devel.2006 at gmx.net> wrote:
> >
> >
> >> Hi Julio,
> >>
> >> please note that the method in the link can destroy your mainboard if
> >> your flash chip uses a different interface (very likely). See below for
> >> details.
> >>
> >> On 20.05.2010 09:37, Carl-Daniel Hailfinger wrote:
> >>
> >>> On 20.05.2010 00:44, Joseph Smith wrote:
> >>>
> >>>
> >>>> On 05/19/2010 06:38 PM, Michael Karcher wrote:
> >>>>
> >>>>
> >>>>> IIRC, we recently had a link showing two stacked flash chips (but I
> >>>>> think they were parallel, not LPC/FWH) with some control signals only
> >>>>> connected to the top one - the idea was to mount a working flash chip
> >>>>>
> >> on
> >>
> >>>>> top of the one with damaged/wrong contents without removing the lower
> >>>>> one from the system. Anyone knows what I'm talking about and still
> has
> >>>>> the link?
> >>>>>
> >>>>>
> >>>> http://www.coreboot.org/pipermail/linuxbios/2007-April/020384.html
> >>>>
> >>>>
> >>> The back-to-back socket solution (sometimes also marketed as top hat
> >>> flash) would be the one which does not require soldering on the board
> >>> and thus has a lower risk.
> >>>
> >>>
> >> The best way to figure this out is to find out which flash chip you have
> >> and tell us. Then we can try to find out which pins need to be bent and
> >> disconnected.
> >>
> >> Regards,
> >> Carl-Daniel
> >>
> >> --
> >> http://www.hailfinger.org/
> >>
> >>
> >>
> >
> >
>
>
> --
> http://www.hailfinger.org/
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 20 May 2010 12:15:15 +0100
> From: Julio Barrios <jvbn.barrios at yahoo.co.uk>
> To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006 at gmx.net>
> Cc: flashrom <flashrom at flashrom.org>
> Subject: Re: [flashrom] disaster
> Message-ID:
>        <AANLkTilTQN-bhH1p9ZNKpaKoM1lPNpMhkpFINbRb6RaK at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Carl-Daniel,
>
> Sorry about not sending my message in the correct way.
>
> I have now peeled off the sticker. This is what is on the flash chip:
>
> iTE
> IT8718F-S
> 2M24MA L
>
> I hope this means something to you.
>
> Best regarsd,
>
> Julio
>
> On 20 May 2010 11:50, Carl-Daniel Hailfinger <
> c-d.hailfinger.devel.2006 at gmx.net> wrote:
>
> > Hi Julio,
> >
> > it seems flashrom at flashrom.org was left out of the conversation by
> > accident. I've added it back, please use the "reply all" button in the
> > future.
> >
> > On 20.05.2010 12:12, Julio Barrios wrote:
> > > Hi Carl-Daniel, Joseph and Michael,
> > >
> > > Many thanks for your replies. I very much appreciate it. I'm not sure
> if
> > a
> > > flash chip is the same as the BIOS chip (I'm a complete newbie here and
> > am
> > > just learning a bit, and destroying computers along the way it seems
> > LOL!).
> > > Anyway, my BIOS is a Phoenix D686 and my PC is a Dell Inspiron 530.
> > >
> >
> > "Phoenix D686" is probably written on a sticker. Can you peel off the
> > sticker and tell us what's written on the BIOS flash chip?
> >
> >
> > > By the look of things, I guess that I will need to buy a new
> motherboard.
> > If
> > > that is the case, then I will need to buy one that is compatible with
> > linux
> > > because I'm not prepared to give up Ubuntu and go back to Windows.
> > >
> > > If you need any more information so that you can help me, please let me
> > > know.
> > >
> >
> > Some people/companies in the UK offer services to reflash mainboards.
> > That might be what you want, but I'm not sure if the shipping cost is
> > worth it.
> > Besides that, some vendors might offer top hat flash solutions for your
> > board, but I'm not 100% sure about this.
> >
> >
> > > Again, guys, thanks a lot.
> > >
> > > Julio
> > >
> >
> > Good luck!
> >
> > Regards,
> > Carl-Daniel
> >
> >
> > > On 20 May 2010 09:45, Carl-Daniel Hailfinger <
> > > c-d.hailfinger.devel.2006 at gmx.net> wrote:
> > >
> > >
> > >> Hi Julio,
> > >>
> > >> please note that the method in the link can destroy your mainboard if
> > >> your flash chip uses a different interface (very likely). See below
> for
> > >> details.
> > >>
> > >> On 20.05.2010 09:37, Carl-Daniel Hailfinger wrote:
> > >>
> > >>> On 20.05.2010 00:44, Joseph Smith wrote:
> > >>>
> > >>>
> > >>>> On 05/19/2010 06:38 PM, Michael Karcher wrote:
> > >>>>
> > >>>>
> > >>>>> IIRC, we recently had a link showing two stacked flash chips (but I
> > >>>>> think they were parallel, not LPC/FWH) with some control signals
> only
> > >>>>> connected to the top one - the idea was to mount a working flash
> chip
> > >>>>>
> > >> on
> > >>
> > >>>>> top of the one with damaged/wrong contents without removing the
> lower
> > >>>>> one from the system. Anyone knows what I'm talking about and still
> > has
> > >>>>> the link?
> > >>>>>
> > >>>>>
> > >>>> http://www.coreboot.org/pipermail/linuxbios/2007-April/020384.html
> > >>>>
> > >>>>
> > >>> The back-to-back socket solution (sometimes also marketed as top hat
> > >>> flash) would be the one which does not require soldering on the board
> > >>> and thus has a lower risk.
> > >>>
> > >>>
> > >> The best way to figure this out is to find out which flash chip you
> have
> > >> and tell us. Then we can try to find out which pins need to be bent
> and
> > >> disconnected.
> > >>
> > >> Regards,
> > >> Carl-Daniel
> > >>
> > >> --
> > >> http://www.hailfinger.org/
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> > --
> > http://www.hailfinger.org/
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://www.flashrom.org/pipermail/flashrom/attachments/20100520/31fd4566/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Thu, 20 May 2010 13:24:55 +0200
> From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006 at gmx.net>
> To: Julio Barrios <jvbn.barrios at yahoo.co.uk>
> Cc: flashrom <flashrom at flashrom.org>
> Subject: Re: [flashrom] disaster
> Message-ID: <4BF51C07.6070004 at gmx.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Julio,
>
> On 20.05.2010 13:15, Julio Barrios wrote:
> > Sorry about not sending my message in the correct way.
> >
> > I have now peeled off the sticker. This is what is on the flash chip:
> >
> > iTE
> > IT8718F-S
> >
>
> This is not your flash chip.
>
> Regards,
> Carl-Daniel
>
> --
> http://www.hailfinger.org/
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 20 May 2010 12:28:53 +0100
> From: Julio Barrios <jvbn.barrios at yahoo.co.uk>
> To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006 at gmx.net>
> Cc: flashrom <flashrom at flashrom.org>
> Subject: Re: [flashrom] disaster
> Message-ID:
>        <AANLkTikN-r-3boptV_c0VqU22ahcn3ujsquj6DBxpnIu at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Well, that shows you how much I know!! lol Could you tell me how to find
> the
> flash chip, please?
>
>
>
> On 20 May 2010 12:24, Carl-Daniel Hailfinger <
> c-d.hailfinger.devel.2006 at gmx.net> wrote:
>
> > Hi Julio,
> >
> > On 20.05.2010 13:15, Julio Barrios wrote:
> > > Sorry about not sending my message in the correct way.
> > >
> > > I have now peeled off the sticker. This is what is on the flash chip:
> > >
> > > iTE
> > > IT8718F-S
> > >
> >
> > This is not your flash chip.
> >
> > Regards,
> > Carl-Daniel
> >
> > --
> > http://www.hailfinger.org/
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://www.flashrom.org/pipermail/flashrom/attachments/20100520/fe24eabf/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 5
> Date: Thu, 20 May 2010 14:35:22 +0200
> From: Guenter <lists at gknw.net>
> To: flashrom at flashrom.org
> Subject: Re: [flashrom] disaster
> Message-ID: <4BF52C8A.8070506 at gknw.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> JUlio,
> Am 20.05.2010 13:28, schrieb Julio Barrios:
> > Well, that shows you how much I know!! lol Could you tell me how to find
> > the flash chip, please?
> please take a look here - I guess this is your MB:
>
> http://www.foxconnchannel.com/product/motherboards/detail_spec.aspx?ID=en-us0000319
>
> then look at this picture - does your MB look like that?
>
> http://www.foxconnchannel.com/product/Lookimage.aspx?/Upload/Mainboard/200705160543230218_G337MA-8KS2H.jpg
>
> If so I guess the chip you thought you identified is in this picture at
> right bottom corner?
> Can you tell us what's written on the chip at the left edge near the
> left PCI slot?
>
> Or, even better: take a photo of your MB with a higher resolution than
> the above pic so that we can better see chips ...
>
> G?n.
>
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 20 May 2010 16:17:47 +0200
> From: Alessandro Gervaso <gervaso at appliedgenomics.org>
> To: flashrom at flashrom.org
> Subject: [flashrom] TYAN s3992
> Message-ID: <1FD12AB5-AF83-4C92-A559-AACD0FA34887 at appliedgenomics.org>
> Content-Type: text/plain; charset=us-ascii
>
> Here's the output.
>
> Cheers
>
> [root at refosco ~]# flashrom -Vw 3992V205.ROM
> flashrom v0.9.1-r995 on Linux 2.6.18-194.3.1.el5 (x86_64), built with
> libpci 2.2.3, GCC 4.1.2 20080704 (Red Hat 4.1.2-48)
> No coreboot table found.
> DMI string system-manufacturer: "empty"
> DMI string system-product-name: "empty"
> DMI string system-version: "empty"
> DMI string baseboard-manufacturer: "TYAN Computer Corporation"
> DMI string baseboard-product-name: "S3992"
> DMI string baseboard-version: "empty"
> DMI string chassis-type: "Desktop"
> Found chipset "Broadcom HT-1000", enabling flash write... OK.
> This chipset supports the following protocols: Non-SPI.
> Calibrating delay loop... 1296M loops per second, 10 myus = 12 us, 100 myus
> = 101 us, 1000 myus = 1002 us, 10000 myus = 10004 us, OK.
> Probing for AMD Am29F010A/B, 128 KB: probe_jedec_common: id1 0xff, 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 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec_common: id1 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for AMD Am29F016D, 2048 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 AMD Am29F040B, 512 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0x6b, id2
> 0xbc, 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 Am29LV040B, 512 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0x6b, id2
> 0xbc, id1 is normal flash content, id2 is normal flash content
> Probing for AMD Am29LV081B, 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 ASD AE49F2008, 256 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Atmel AT25DF021, 256 KB: skipped.
> Probing for Atmel AT25DF041A, 512 KB: skipped.
> Probing for Atmel AT25DF081, 1024 KB: skipped.
> Probing for Atmel AT25DF161, 2048 KB: skipped.
> Probing for Atmel AT25DF321, 4096 KB: skipped.
> Probing for Atmel AT25DF321A, 4096 KB: skipped.
> Probing for Atmel AT25DF641, 8192 KB: skipped.
> Probing for Atmel AT25F512B, 64 KB: skipped.
> Probing for Atmel AT25FS010, 128 KB: skipped.
> Probing for Atmel AT25FS040, 512 KB: skipped.
> Probing for Atmel AT26DF041, 512 KB: skipped.
> Probing for Atmel AT26DF081A, 1024 KB: skipped.
> Probing for Atmel AT26DF161, 2048 KB: skipped.
> Probing for Atmel AT26DF161A, 2048 KB: skipped.
> Probing for Atmel AT26F004, 512 KB: skipped.
> Probing for Atmel AT29C512, 64 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Atmel AT29C010A, 128 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Atmel AT29C020, 256 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Atmel AT29C040A, 512 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Atmel AT45CS1282, 16896 KB: skipped.
> Probing for Atmel AT45DB011D, 128 KB: skipped.
> Probing for Atmel AT45DB021D, 256 KB: skipped.
> Probing for Atmel AT45DB041D, 512 KB: skipped.
> Probing for Atmel AT45DB081D, 1024 KB: skipped.
> Probing for Atmel AT45DB161D, 2048 KB: skipped.
> Probing for Atmel AT45DB321C, 4224 KB: skipped.
> Probing for Atmel AT45DB321D, 4096 KB: skipped.
> Probing for Atmel AT45DB642D, 8192 KB: skipped.
> Probing for Atmel AT49BV512, 64 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Atmel AT49F002(N), 256 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for AMIC A25L40PT, 512 KB: skipped.
> Probing for AMIC A25L40PU, 512 KB: skipped.
> Probing for AMIC A29002B, 256 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for AMIC A29002T, 256 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for AMIC A29040B, 512 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0x6b, id2
> 0xbc, id1 is normal flash content, id2 is normal flash content
> Probing for AMIC A49LF040A, 512 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for EMST F49B002UA, 256 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Eon EN25B05, 64 KB: skipped.
> Probing for Eon EN25B05T, 64 KB: skipped.
> Probing for Eon EN25B10, 128 KB: skipped.
> Probing for Eon EN25B10T, 128 KB: skipped.
> Probing for Eon EN25B20, 256 KB: skipped.
> Probing for Eon EN25B20T, 256 KB: skipped.
> Probing for Eon EN25B40, 512 KB: skipped.
> Probing for Eon EN25B40T, 512 KB: skipped.
> Probing for Eon EN25B80, 1024 KB: skipped.
> Probing for Eon EN25B80T, 1024 KB: skipped.
> Probing for Eon EN25B16, 2048 KB: skipped.
> Probing for Eon EN25B16T, 2048 KB: skipped.
> Probing for Eon EN25B32, 4096 KB: skipped.
> Probing for Eon EN25B32T, 4096 KB: skipped.
> Probing for Eon EN25B64, 8192 KB: skipped.
> Probing for Eon EN25B64T, 8192 KB: skipped.
> Probing for Eon EN25D16, 2048 KB: skipped.
> Probing for Eon EN25F05, 64 KB: skipped.
> Probing for Eon EN25F10, 128 KB: skipped.
> Probing for Eon EN25F20, 256 KB: skipped.
> Probing for Eon EN25F40, 512 KB: skipped.
> Probing for Eon EN25F80, 1024 KB: skipped.
> Probing for Eon EN25F16, 2048 KB: skipped.
> Probing for Eon EN25F32, 4096 KB: skipped.
> Probing for Eon EN29F010, 128 KB: probe_jedec_common: id1 0xff, 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 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec_common: id1 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec_common: id1 0x6b, id2
> 0xbc, id1 is normal flash content, id2 is normal flash content
> Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec_common: id1 0x6b, id2
> 0xbc, id1 is normal flash content, id2 is normal flash content
> Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0x6b, id2
> 0x49
> Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0x6b, id2
> 0x49
> Probing for Intel 28F001BX-B, 128 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Intel 28F001BX-T, 128 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Intel 28F004S5, 512 KB: probe_82802ab: id1 0x6b, id2 0xbc, id1
> is normal flash content, id2 is normal flash content
> Probing for Intel 28F004BV/BE-B, 512 KB: probe_82802ab: id1 0x6b, id2 0xbc,
> id1 is normal flash content, id2 is normal flash content
> Probing for Intel 28F004BV/BE-T, 512 KB: probe_82802ab: id1 0x6b, id2 0xbc,
> id1 is normal flash content, id2 is normal flash content
> Probing for Intel 28F400BV/CV/CE-B, 512 KB: probe_82802ab: id1 0x6b, id2
> 0x49, id1 is normal flash content, id2 is normal flash content
> Probing for Intel 28F400BV/CV/CE-T, 512 KB: probe_82802ab: id1 0x6b, id2
> 0x49, id1 is normal flash content, id2 is normal flash content
> Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x6b, id2 0xbc, 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 MX25L512, 64 KB: skipped.
> Probing for Macronix MX25L1005, 128 KB: skipped.
> Probing for Macronix MX25L2005, 256 KB: skipped.
> Probing for Macronix MX25L4005, 512 KB: skipped.
> Probing for Macronix MX25L8005, 1024 KB: skipped.
> Probing for Macronix MX25L1605, 2048 KB: skipped.
> Probing for Macronix MX25L1635D, 2048 KB: skipped.
> Probing for Macronix MX25L3205, 4096 KB: skipped.
> Probing for Macronix MX25L3235D, 4096 KB: skipped.
> Probing for Macronix MX25L6405, 8192 KB: skipped.
> Probing for Macronix MX25L12805, 16384 KB: skipped.
> Probing for Macronix MX29F001B, 128 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 Macronix MX29F001T, 128 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 Macronix MX29F002B, 256 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for Macronix MX29F002T, 256 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for Macronix MX29LV040, 512 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0x6b, id2
> 0xbc, id1 is normal flash content, id2 is normal flash content
> Probing for Numonyx M25PE10, 128 KB: skipped.
> Probing for Numonyx M25PE20, 256 KB: skipped.
> Probing for Numonyx M25PE40, 512 KB: skipped.
> Probing for Numonyx M25PE80, 1024 KB: skipped.
> Probing for Numonyx M25PE16, 2048 KB: skipped.
> Probing for PMC Pm25LV010, 128 KB: skipped.
> Probing for PMC Pm25LV016B, 2048 KB: skipped.
> Probing for PMC Pm25LV020, 256 KB: skipped.
> Probing for PMC Pm25LV040, 512 KB: skipped.
> Probing for PMC Pm25LV080B, 1024 KB: skipped.
> Probing for PMC Pm25LV512, 64 KB: skipped.
> Probing for PMC Pm29F002T, 256 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xcb, id2
> 0x4d, 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 0xcb, id2
> 0x4d, id1 is normal flash content, id2 is normal flash content
> Probing for PMC Pm39LV010, 128 KB: probe_jedec_common: id1 0xff, 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 0xcb, id2 0x4d,
> id1 is normal flash content, id2 is normal flash content
> Probing for PMC Pm39LV040, 512 KB: probe_jedec_common: id1 0x6b, id2 0xbc,
> id1 is normal flash content, id2 is normal flash content
> Probing for PMC Pm49FL002, 256 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Sanyo LF25FW203A, 2048 KB: skipped.
> 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 Spansion S25FL008A, 1024 KB: skipped.
> Probing for Spansion S25FL016A, 2048 KB: skipped.
> Probing for SST SST25VF016B, 2048 KB: skipped.
> Probing for SST SST25VF032B, 4096 KB: skipped.
> Probing for SST SST25VF040.REMS, 512 KB: skipped.
> Probing for SST SST25VF040B, 512 KB: skipped.
> Probing for SST SST25VF040B.REMS, 512 KB: skipped.
> Probing for SST SST25VF080B, 1024 KB: skipped.
> Probing for SST SST28SF040A, 512 KB: probe_82802ab: id1 0x6b, id2 0xbc, id1
> is normal flash content, id2 is normal flash content
> Probing for SST SST29EE010, 128 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST29LE010, 128 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST29EE020A, 256 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST29LE020, 256 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39SF512, 64 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39SF010A, 128 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39SF020A, 256 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39SF040, 512 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39VF512, 64 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39VF010, 128 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39VF020, 256 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39VF040, 512 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST39VF080, 1024 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST49LF002A/B, 256 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x6b, id2 0xbc, id1
> is normal flash content, id2 is normal flash content
> Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> 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 0xbf, id2 0x5b
> Probing for SST SST49LF020A, 256 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST49LF040, 512 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST49LF040B, 512 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for SST SST49LF080A, 1024 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xbf, id2 0x5b
> Found chip "SST SST49LF080A" (1024 KB, LPC) at physical address 0xfff00000.
> 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 M25P05-A, 64 KB: skipped.
> Probing for ST M25P05.RES, 64 KB: skipped.
> Probing for ST M25P10-A, 128 KB: skipped.
> Probing for ST M25P10.RES, 128 KB: skipped.
> Probing for ST M25P20, 256 KB: skipped.
> Probing for ST M25P40, 512 KB: skipped.
> Probing for ST M25P40-old, 512 KB: skipped.
> Probing for ST M25P80, 1024 KB: skipped.
> Probing for ST M25P16, 2048 KB: skipped.
> Probing for ST M25P32, 4096 KB: skipped.
> Probing for ST M25P64, 8192 KB: skipped.
> Probing for ST M25P128, 16384 KB: skipped.
> Probing for ST M29F002B, 256 KB: probe_jedec_common: id1 0xcb, id2 0x4d,
> id1 is normal flash content, id2 is normal flash content
> Probing for ST M29F002T/NT, 256 KB: probe_jedec_common: id1 0xcb, id2 0x4d,
> id1 is normal flash content, id2 is normal flash content
> Probing for ST M29F040B, 512 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0x6b, id2
> 0xbc, id1 is normal flash content, id2 is normal flash content
> Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x6b, id2 0x49
> Probing for ST M29W010B, 128 KB: probe_jedec_common: id1 0xff, 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 0x6b, id2 0xbc,
> id1 is normal flash content, id2 is normal flash content
> Probing for ST M29W512B, 64 KB: probe_jedec_common: id1 0xd0, id2 0x9d, id1
> is normal flash content, id2 is normal flash content
> Probing for ST M50FLW040A, 512 KB: probe_82802ab: id1 0x6b, id2 0xbc, id1
> is normal flash content, id2 is normal flash content
> Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x6b, id2 0xbc, 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 0xcb, id2 0x4d, 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 0x6b, id2 0xbc, 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 S29C31004T, 512 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for SyncMOS S29C51001T, 128 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for SyncMOS S29C51002T, 256 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for SyncMOS S29C51004T, 512 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for TI TMS29F002RB, 256 KB: probe_jedec_common: id1 0xcb, id2 0x4d,
> id1 is normal flash content, id2 is normal flash content
> Probing for TI TMS29F002RT, 256 KB: probe_jedec_common: id1 0xcb, id2 0x4d,
> id1 is normal flash content, id2 is normal flash content
> Probing for Winbond W25Q80, 1024 KB: skipped.
> Probing for Winbond W25Q16, 2048 KB: skipped.
> Probing for Winbond W25Q32, 4096 KB: skipped.
> Probing for Winbond W25x10, 128 KB: skipped.
> Probing for Winbond W25x20, 256 KB: skipped.
> Probing for Winbond W25x40, 512 KB: skipped.
> Probing for Winbond W25x80, 1024 KB: skipped.
> Probing for Winbond W25x16, 2048 KB: skipped.
> Probing for Winbond W25x32, 4096 KB: skipped.
> Probing for Winbond W25x64, 8192 KB: skipped.
> Probing for Winbond W29C011, 128 KB: probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Winbond W29C020C, 256 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W29C040P, 512 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W29EE011, 128 KB: Probing disabled for Winbond W29EE011
> because the probing sequence puts the AMIC A49LF040A in a funky state. Use
> 'flashrom -c W29EE011' if you have a board with this chip.
> Probing for Winbond W39V040A, 512 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W39V040B, 512 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W39V040C, 512 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W39V080A, 1024 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W49F002U, 256 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W49V002A, 256 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0xbf, id2
> 0x5b
> Probing for Winbond W39V080FA, 1024 KB: Chip lacks correct probe timing
> information, using default 10mS/40uS. probe_jedec_common: id1 0xbf, id2 0x5b
> Probing for Winbond W39V080FA (dual mode), 512 KB: Chip lacks correct probe
> timing information, using default 10mS/40uS. probe_jedec_common: id1 0xbf,
> id2 0x5b
> Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped.
> Probing for EON unknown EON SPI chip, 0 KB: skipped.
> Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped.
> Probing for PMC unknown PMC SPI chip, 0 KB: skipped.
> Probing for SST unknown SST SPI chip, 0 KB: skipped.
> Probing for ST unknown ST SPI chip, 0 KB: skipped.
> Probing for Sanyo unknown Sanyo SPI chip, 0 KB: skipped.
> Probing for Generic unknown SPI chip (RDID), 0 KB: skipped.
> Probing for Generic unknown SPI chip (REMS), 0 KB: skipped.
> ===
> This flash part has status UNTESTED for operations: ERASE WRITE
> Please email a report to flashrom at flashrom.org if any of the above
> operations
> work correctly for you with this flash part. Please include the flashrom
> output with the additional -V option for all operations you tested (-V,
> -rV,
> -wV, -EV), and mention which mainboard or programmer you tested.
> Thanks for your help!
> ===
> Flash image seems to be a legacy BIOS. Disabling checks.
> Writing flash chip... Erasing flash chip... Looking at blockwise erase
> function 0... trying... 0x000000-0x000fff, 0x001000-0x001fff,
> 0x002000-0x002fff, 0x003000-0x003fff, 0x004000-0x004fff, 0x005000-0x005fff,
> 0x006000-0x006fff, 0x007000-0x007fff, 0x008000-0x008fff, 0x009000-0x009fff,
> 0x00a000-0x00afff, 0x00b000-0x00bfff, 0x00c000-0x00cfff, 0x00d000-0x00dfff,
> 0x00e000-0x00efff, 0x00f000-0x00ffff, 0x010000-0x010fff, 0x011000-0x011fff,
> 0x012000-0x012fff, 0x013000-0x013fff, 0x014000-0x014fff, 0x015000-0x015fff,
> 0x016000-0x016fff, 0x017000-0x017fff, 0x018000-0x018fff, 0x019000-0x019fff,
> 0x01a000-0x01afff, 0x01b000-0x01bfff, 0x01c000-0x01cfff, 0x01d000-0x01dfff,
> 0x01e000-0x01efff, 0x01f000-0x01ffff, 0x020000-0x020fff, 0x021000-0x021fff,
> 0x022000-0x022fff, 0x023000-0x023fff, 0x024000-0x024fff, 0x025000-0x025fff,
> 0x026000-0x026fff, 0x027000-0x027fff, 0x028000-0x028fff, 0x029000-0x029fff,
> 0x02a000-0x02afff, 0x02b000-0x02bfff, 0x02c000-0x02cfff, 0x02d000-0x02dfff,
> 0x02e000-0x02efff, 0x02f000-0x02ffff, 0x030000-0x030fff, 0x031000-0x031fff,
> 0x032000-0x032fff, 0x033000-0x033fff, 0x034000-0x034fff, 0x035000-0x035fff,
> 0x036000-0x036fff, 0x037000-0x037fff, 0x038000-0x038fff, 0x039000-0x039fff,
> 0x03a000-0x03afff, 0x03b000-0x03bfff, 0x03c000-0x03cfff, 0x03d000-0x03dfff,
> 0x03e000-0x03efff, 0x03f000-0x03ffff, 0x040000-0x040fff, 0x041000-0x041fff,
> 0x042000-0x042fff, 0x043000-0x043fff, 0x044000-0x044fff, 0x045000-0x045fff,
> 0x046000-0x046fff, 0x047000-0x047fff, 0x048000-0x048fff, 0x049000-0x049fff,
> 0x04a000-0x04afff, 0x04b000-0x04bfff, 0x04c000-0x04cfff, 0x04d000-0x04dfff,
> 0x04e000-0x04efff, 0x04f000-0x04ffff, 0x050000-0x050fff, 0x051000-0x051fff,
> 0x052000-0x052fff, 0x053000-0x053fff, 0x054000-0x054fff, 0x055000-0x055fff,
> 0x056000-0x056fff, 0x057000-0x057fff, 0x058000-0x058fff, 0x059000-0x059fff,
> 0x05a000-0x05afff, 0x05b000-0x05bfff, 0x05c000-0x05cfff, 0x05d000-0x05dfff,
> 0x05e000-0x05efff, 0x05f000-0x05ffff, 0x060000-0x060fff, 0x061000-0x061fff,
> 0x062000-0x062fff, 0x063000-0x063fff, 0x064000-0x064fff, 0x065000-0x065fff,
> 0x066000-0x066fff, 0x067000-0x067fff, 0x068000-0x068fff, 0x069000-0x069fff,
> 0x06a000-0x06afff, 0x06b000-0x06bfff, 0x06c000-0x06cfff, 0x06d000-0x06dfff,
> 0x06e000-0x06efff, 0x06f000-0x06ffff, 0x070000-0x070fff, 0x071000-0x071fff,
> 0x072000-0x072fff, 0x073000-0x073fff, 0x074000-0x074fff, 0x075000-0x075fff,
> 0x076000-0x076fff, 0x077000-0x077fff, 0x078000-0x078fff, 0x079000-0x079fff,
> 0x07a000-0x07afff, 0x07b000-0x07bfff, 0x07c000-0x07cfff, 0x07d000-0x07dfff,
> 0x07e000-0x07efff, 0x07f000-0x07ffff, 0x080000-0x080fff, 0x081000-0x081fff,
> 0x082000-0x082fff, 0x083000-0x083fff, 0x084000-0x084fff, 0x085000-0x085fff,
> 0x086000-0x086fff, 0x087000-0x087fff, 0x088000-0x088fff, 0x089000-0x089fff,
> 0x08a000-0x08afff, 0x08b000-0x08bfff, 0x08c000-0x08cfff, 0x08d000-0x08dfff,
> 0x08e000-0x08efff, 0x08f000-0x08ffff, 0x090000-0x090fff, 0x091000-0x091fff,
> 0x092000-0x092fff, 0x093000-0x093fff, 0x094000-0x094fff, 0x095000-0x095fff,
> 0x096000-0x096fff, 0x097000-0x097fff, 0x098000-0x098fff, 0x099000-0x099fff,
> 0x09a000-0x09afff, 0x09b000-0x09bfff, 0x09c000-0x09cfff, 0x09d000-0x09dfff,
> 0x09e000-0x09efff, 0x09f000-0x09ffff, 0x0a0000-0x0a0fff, 0x0a1000-0x0a1fff,
> 0x0a2000-0x0a2fff, 0x0a3000-0x0a3fff, 0x0a4000-0x0a4fff, 0x0a5000-0x0a5fff,
> 0x0a6000-0x0a6fff, 0x0a7000-0x0a7fff, 0x0a8000-0x0a8fff, 0x0a9000-0x0a9fff,
> 0x0aa000-0x0aafff, 0x0ab000-0x0abfff, 0x0ac000-0x0acfff, 0x0ad000-0x0adfff,
> 0x0ae000-0x0aefff, 0x0af000-0x0affff, 0x0b0000-0x0b0fff, 0x0b1000-0x0b1fff,
> 0x0b2000-0x0b2fff, 0x0b3000-0x0b3fff, 0x0b4000-0x0b4fff, 0x0b5000-0x0b5fff,
> 0x0b6000-0x0b6fff, 0x0b7000-0x0b7fff, 0x0b8000-0x0b8fff, 0x0b9000-0x0b9fff,
> 0x0ba000-0x0bafff, 0x0bb000-0x0bbfff, 0x0bc000-0x0bcfff, 0x0bd000-0x0bdfff,
> 0x0be000-0x0befff, 0x0bf000-0x0bffff, 0x0c0000-0x0c0fff, 0x0c1000-0x0c1fff,
> 0x0c2000-0x0c2fff, 0x0c3000-0x0c3fff, 0x0c4000-0x0c4fff, 0x0c5000-0x0c5fff,
> 0x0c6000-0x0c6fff, 0x0c7000-0x0c7fff, 0x0c8000-0x0c8fff, 0x0c9000-0x0c9fff,
> 0x0ca000-0x0cafff, 0x0cb000-0x0cbfff, 0x0cc000-0x0ccfff, 0x0cd000-0x0cdfff,
> 0x0ce000-0x0cefff, 0x0cf000-0x0cffff, 0x0d0000-0x0d0fff, 0x0d1000-0x0d1fff,
> 0x0d2000-0x0d2fff, 0x0d3000-0x0d3fff, 0x0d4000-0x0d4fff, 0x0d5000-0x0d5fff,
> 0x0d6000-0x0d6fff, 0x0d7000-0x0d7fff, 0x0d8000-0x0d8fff, 0x0d9000-0x0d9fff,
> 0x0da000-0x0dafff, 0x0db000-0x0dbfff, 0x0dc000-0x0dcfff, 0x0dd000-0x0ddfff,
> 0x0de000-0x0defff, 0x0df000-0x0dffff, 0x0e0000-0x0e0fff, 0x0e1000-0x0e1fff,
> 0x0e2000-0x0e2fff, 0x0e3000-0x0e3fff, 0x0e4000-0x0e4fff, 0x0e5000-0x0e5fff,
> 0x0e6000-0x0e6fff, 0x0e7000-0x0e7fff, 0x0e8000-0x0e8fff, 0x0e9000-0x0e9fff,
> 0x0ea000-0x0eafff, 0x0eb000-0x0ebfff, 0x0ec000-0x0ecfff, 0x0ed000-0x0edfff,
> 0x0ee000-0x0eefff, 0x0ef000-0x0effff, 0x0f0000-0x0f0fff, 0x0f1000-0x0f1fff,
> 0x0f2000-0x0f2fff, 0x0f3000-0x0f3fff, 0x0f4000-0x0f4fff, 0x0f5000-0x0f5fff,
> 0x0f6000-0x0f6fff, 0x0f7000-0x0f7fff, 0x0f8000-0x0f8fff, 0x0f9000-0x0f9fff,
> 0x0fa000-0x0fafff, 0x0fb000-0x0fbfff, 0x0fc000-0x0fcfff, 0x0fd000-0x0fdfff,
> 0x0fe000-0x0fefff, 0x0ff000-0x0fffff,
> SUCCESS.
> Programming page: DONE!ss: 0x000ff000
> COMPLETE.
> Verifying flash... VERIFIED.
>
>
>
>
> ------------------------------
>
> _______________________________________________
> flashrom mailing list
> flashrom at flashrom.org
> http://www.flashrom.org/mailman/listinfo/flashrom
>
> End of flashrom Digest, Vol 12, Issue 35
> ****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.flashrom.org/pipermail/flashrom/attachments/20100520/398c749b/attachment.html>