public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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 18:12:10 -0800	[thread overview]
Message-ID: <200512211812.10597.dsp@llnl.gov> (raw)
In-Reply-To: <m38xueqnin.fsf@maxwell.lnxi.com>

On Wednesday 21 December 2005 11:05, Eric W. Biederman wrote:
> > What does "cached flash chip" mean?  I have very little familiarity
> > with how these flash chips operate.
>
> The flash chips contents being cached in the cpus cache.
> cat /proc/mtrr and see if covers the 0xfff80000 - 0xffffffff
> range where your flash chip lives.

The MTRR setup looks ok:

    # cat /proc/mtrr
    reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
    #

> > How do I determine whether there is motherboard-specific magic?
>
> Usually I see if I can read out the id on the flash chip.  That
> tests to see if writes make it to the device because you have
> to write a command.

How do I do this?

> > 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.
>
> Ok.  That sounds sane.  Are you running linuxbios right now or something
> else?

Yes, I'm using linuxbios.

  reply	other threads:[~2005-12-22  2:12 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
2005-12-21 19:05     ` Eric W. Biederman
2005-12-22  2:12       ` Dave Peterson [this message]
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=200512211812.10597.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