From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Gettert, Wolfram" <Wolfram.Gettert@fci.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: MTD newbie wants programming a 28F800 with a 2.2.18 kernel
Date: Wed, 6 Nov 2002 10:26:49 +0100 [thread overview]
Message-ID: <20021106092649.GC2193@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <9CFB9DA5261CD611A29B00508B789048380A47@ex-deu-munich02.force.de>
On Wed, 6 November 2002 09:25:25 +0100, Gettert, Wolfram wrote:
> I am completely new to MTD. My job is to program a 28F800 boot block flash
> running a 2.2.18 kernel.
> I am using this patch mtd-patch-2.2.18-20001218-2230GMT. Since there is no
> support for the 28F800 because it has CUI not CFI I need to write the
> driver for the CUI. I found the lart-driver (lart.c) in the 2.5.x sources
> which can manage a 28F160 (which is compatible to 28F800).
>
> Do you know of any implementation of the lart-driver on a 2.2.x kernel?
> Since the mtd_info structure has changed extensively from the 2.2.18-patch
> to 2.5.x there is a lot of work to-do.
As always, bugging the company to finally upgrade to a recent kernel
is a good thing, although unrealistic. :-)
Most of the mtd code in cvs should be running on any kernel from 2.2.0
up to 2.5.current. David has done an excellent job there. So you
should take a peek into cvs, whenever you have a problem.
Apart from that, try to cut down on the number of #ifdefs, consider
sending a patch to David and good luck!
Jörn
--
Everything should be made as simple as possible, but not simpler.
-- Albert Einstein
next prev parent reply other threads:[~2002-11-06 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 8:25 MTD newbie wants programming a 28F800 with a 2.2.18 kernel Gettert, Wolfram
2002-11-06 9:26 ` Jörn Engel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 12:56 Gettert, Wolfram
2002-11-06 15:23 ` Jörn Engel
2002-11-06 15:56 Jeffrey Lim
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=20021106092649.GC2193@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=Wolfram.Gettert@fci.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