From: ebiederman@lnxi.com (Eric W. Biederman)
To: Alice Hennessy <ahennessy@mvista.com>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: Problem with cfi_probe.c and Intel chip
Date: 11 Jan 2002 13:27:36 -0700 [thread overview]
Message-ID: <m3ita83a6f.fsf@DLT.linuxnetworx.com> (raw)
In-Reply-To: <3C3E48B6.C9FF834D@mvista.com>
Alice Hennessy <ahennessy@mvista.com> writes:
> array
> mode (0xff) would be necessary before the query command so I'm not sure why
> my board is having problems. Even if the bios has issued a command to the
> flash
> between power up and cfi_probe, I don't think read array command is necessary
> between commands.
> If my board is the only Intel with a problem, then I need to investigate it
> further.
That would certainly be useful. My real suspicion is that this code hasn't
been utilized all that much, and we are entering it's first real
stabalization phase. Since all I did was comment out what looked like
redundant code, I actually think you are the second person to notice
this. Personally I have deal with boot block type flash memory,
which may have different characteristics than other intel product lines.
Having a couple of people get a firm grasp on what things cause
problems, is probably needed right now. So if you come up with
anything interesting I'd be glad to hear it.
Eric
next prev parent reply other threads:[~2002-01-11 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 22:26 Problem with cfi_probe.c and Intel chip Alice Hennessy
2002-01-10 22:47 ` David Woodhouse
2002-01-11 1:03 ` Eric W. Biederman
2002-01-11 2:06 ` Alice Hennessy
2002-01-11 20:27 ` Eric W. Biederman [this message]
2002-01-11 21:53 ` Alice Hennessy
2002-01-11 7:57 ` Jonas Holmberg
2002-01-10 23:05 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 10:27 Jonas Holmberg
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=m3ita83a6f.fsf@DLT.linuxnetworx.com \
--to=ebiederman@lnxi.com \
--cc=ahennessy@mvista.com \
--cc=dwmw2@infradead.org \
--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