Re: [flashrom] new bios to support

[Joe Tym]

Hi Carl Daniel,
Sorry this has taken so long, I did as you said and it looks promising.
Output is attached. I'll hold off rebooting till you give me the all
clear. :)

Also the second part of the patch needed to be manually added for some
reason,
I guess trunk has been updated since the patch.

Pass my thanks onto Josh. Also I had a quick nose at your website and
noticed
you studyed bioinformatics. Funny coincidence because I started a job a few
months ago in bioinformatics (as a perl developer).
I work at a place called ICR in London doing cancer research.
Quite an interesting field. Do you still work at it ? Would be interested to
hear more.

cheers,

Joe Tym

On 5 October 2010 13:58, Carl-Daniel Hailfinger <
[e-mail]> wrote:
> Hi Joe,
>
> any updates on whether this patch works for you?
>
> On 10.09.2010 12:11, Joe Tym wrote:
> > Thanks for your work on this. I'm on holiday at the moment for the next
>
> week
> > but I'll get this tested as soon as I get back and update you on the
> > outcome.
> >
> > On 9 September 2010 20:44, Joshua Roys  wrote:
> > > On 07/28/2010 06:36 PM, Joe Tym wrote:
> > > > my motherboard is an aopen i975xa-ydg
> > >
> > > I have an experimental board enable here for you to try...  please get
> > > the latest flashrom from SVN, apply the attached patch, compile and run:
> > > ./flashrom -p internal:boardenable=force -Vw bios.bin
> > >
> > > Please let us know if that works or not and attach the output from the
> > > above command in your reply.  *NOTE*:  There is a chance that the chip
> > > will be only partially unlocked.  Make a backup first (./flashrom -r
> > > backup.bin), and if the erase step fails you will be able to verify if
> > > the BIOS is OK or not (via ./flashrom -v backup.bin).  If the chip ends
> > > up in a bad state, join the IRC channel again :)
> > >
> > > Some technical notes of why this may only partially unlock the
> > > protection are in the patch, but I will duplicate them here in case some
> > > archive strips attachments completely:
> > >
> > > vendor BIOS ends up in LDN6... maybe the board enable is wrong,
> > >  or perhaps it's not needed at all?
> > >  the regs it tries to touch are 0xF0, 0xF1, 0xF2 which means if it
> > >  were in the right LDN, it would have to be GPIO1 or GPIO3
> > >
> > > Good luck,
> > >
> > > Josh
>
> Regards,
> Carl-Daniel