From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Rainer Weikusat <rainer.weikusat@sncag.com>
Cc: Andrew Carlisle <ACarlisle@acmepacket.com>,
linux-mtd@lists.infradead.org,
Rainer Weikusat <rweikusat@sncag.com>
Subject: Re: Multiple banks of flash?
Date: Wed, 1 Dec 2004 14:22:40 +0100 [thread overview]
Message-ID: <20041201132240.GA9138@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <87is7oaxx8.fsf@farside.sncag.com>
On Tue, 30 November 2004 03:11:15 +0100, Rainer Weikusat wrote:
> Josh Boyer <jdub@us.ibm.com> writes:
> >> > Joern Engel wrote a mphysmap driver some time ago. It works fairly
> >> > well. You might be able to find it if you google for it. Not sure why
> >> > it wasn't included in MTD CVS.
> >>
> >> Various people have written something like this at different times
> >> :->.
> >
> > Indeed. Joern's just happened to be the one I am most familiar with.
> > But since lots of different implementations have been written, it makes
> > one wonder why none are in CVS...
>
> Open Source Mantra: 'Not my problem'.
And embedded seems to be extremely devoted to that mantra. It was
quite a learning experience (buzzword of the year) to figure that one
out. Writing code is just 1% of the work. Debugging it is 9%.
Getting it into some standard (Linux kernel, libc, whatever) is 90%.
And with the 'Not my problem.' mentality, the whole 90% are left to
the original author, who finally gives up and moves on to something
less frustrating. Or at least gets a job and has someone pay for it.
Jörn
--
He that composes himself is wiser than he that composes a book.
-- B. Franklin
prev parent reply other threads:[~2004-12-01 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 15:15 Multiple banks of flash? Andrew Carlisle
2004-11-29 15:38 ` Josh Boyer
2004-11-29 16:23 ` Jörn Engel
2004-11-29 16:29 ` Rainer Weikusat
2004-11-29 17:26 ` Josh Boyer
2004-11-30 2:11 ` Rainer Weikusat
2004-12-01 13:22 ` Jörn Engel [this message]
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=20041201132240.GA9138@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=ACarlisle@acmepacket.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rainer.weikusat@sncag.com \
--cc=rweikusat@sncag.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