From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: sflash: CFI does not contain boot bank location. Assuming top.
Date: Sun, 11 Jul 2004 02:35:21 +0200 [thread overview]
Message-ID: <20040711003526.B6113C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 10 Jul 2004 20:09:53 EDT." <Pine.LNX.4.60.0407102006050.4345@localhost.localdomain>
In message <Pine.LNX.4.60.0407102006050.4345@localhost.localdomain> you wrote:
>
> actually AMD, but the kernel config lists AMD/Fujitsu as a single
> option. is the patch then still relevant?
Not really, as it adds code for the Fujitsu vendor ID. For AMD the
code is already present.
> and another issue is that an older, hacked kernel -- 2.4.22-pre8 that
> we got from embedded planet -- does work with the board, but in
Expect that it contains pretty old MTD code...
> upgrading to the latest 2.4.25 DENX ppc kernel, i have no way of
> knowing if there are any funny, subtle or obscure kernel fixes that we
> got with it that i'm not aware of.
You can always check the CVS logs - either by hand ("cvs log" if you
feel like it) or with some tools that give better formatting (like
"cvsps").
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The most difficult thing in the world is to know how to do a thing
and to watch someone else doing it wrong, without commenting.
-- T.H. White
next prev parent reply other threads:[~2004-07-11 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 22:56 sflash: CFI does not contain boot bank location. Assuming top Wolfgang Denk
2004-07-11 0:09 ` Robert P. J. Day
2004-07-11 0:35 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 17:15 Robert P. J. Day
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=20040711003526.B6113C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=linux-mtd@lists.infradead.org \
--cc=rpjday@mindspring.com \
/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