From: Dave Peterson <dsp@llnl.gov>
To: ebiederman@lnxi.com (Eric W. Biederman)
Cc: linux-mtd@lists.infradead.org
Subject: Re: ichxrom driver question
Date: Wed, 21 Dec 2005 10:37:17 -0800 [thread overview]
Message-ID: <200512211037.17680.dsp@llnl.gov> (raw)
In-Reply-To: <m3vexjqlc2.fsf@maxwell.lnxi.com>
On Tuesday 20 December 2005 17:40, Eric W. Biederman wrote:
> Hmm. Immediately after the erase operation you should see all f's.
I tried it a few times. My recollection is that after the first
attempt at erasing, the first part of the flash memory contained
all f's and the rest contained data that appeared to be the old BIOS.
On a subsequent attempt, I saw all zeros, and this is what I still
see when I try to flash the BIOS again.
> The only thing I can think of that might trigger what you are seeing
> is a cached flash chip.
What does "cached flash chip" mean? I have very little familiarity
with how these flash chips operate.
> The ICH3-S is more of a conduit. The usual questions are:
>
> Is there motherboard specific magic that denies writes?
> What is the actual flash chip you are flashing.
How do I determine whether there is motherboard-specific magic?
The motherboard is a Supermicro P4DPR-iGM and the flash chip is an
Intel 82802AB.
> Except for the possibility of bad cache I can't think of anything
> that would cause the wrong data to be written. Are you certain
> you have a good flash image?
The flash image I tried to install was an exact duplicate of the
currently installed flash image, obtained as follows:
# dd if=/dev/mtd0 of=bios_image
I was just testing the BIOS flashing mechanism to see if it worked.
next prev parent reply other threads:[~2005-12-21 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 0:42 ichxrom driver question Dave Peterson
2005-12-21 1:40 ` Eric W. Biederman
2005-12-21 18:37 ` Dave Peterson [this message]
2005-12-21 19:05 ` Eric W. Biederman
2005-12-22 2:12 ` Dave Peterson
2005-12-23 8:26 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200512211037.17680.dsp@llnl.gov \
--to=dsp@llnl.gov \
--cc=ebiederman@lnxi.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox