All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rogelio M. Serrano Jr." <rogelio@evoserve.com>
To: mtd@infradead.org
Subject: Re: Has MTD production quality support for DOC2000?
Date: Fri, 11 Aug 2000 17:53:18 +0800	[thread overview]
Message-ID: <3993CD0E.84A9B5B@evoserve.com> (raw)
In-Reply-To: ylbvgx88b7i.fsf@ganglot.ifi.uio.no

Sigurd Urdahl wrote:

> David Woodhouse <dwmw2@redhat.com> writes:
> > sigurdur@ifi.uio.no said:
> > >  I'm quite new at embedding my penguin, and will have to embedd it on
> > > a DOC2000. But since I'm new at this I am quite confused... I am
> > > considering going with MTD instead of m-sys drivers, but after
> > > searching the archives I'm still not sure on wether MTD is stable
> > > enough for production or not, so please help:=)
> >
> > Not yet, if you want to write to the device. Nobody at the moment seems to
> > be working very fast on it, and I've been busy with JFFS recently.
>

I have been writing to the DOC for weeks now under jffs. I have given up
on NFTL
completely. I have patches here but I will not submit them because I
have not
tested them with NFTL except for the multipage read write support.
Anyone who is
interested can email me. I got a little lost in the middle of all the
activity on
both MTD and JFFS. I have to get in sync with all the developments and
all.


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  parent reply	other threads:[~2000-08-11  9:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-10 12:33 Has MTD production quality support for DOC2000? Sigurd Urdahl
2000-08-10 12:44 ` David Woodhouse
2000-08-10 23:56   ` Re[2]: " Mike Kilburn
2000-08-11  1:17     ` Jon Burford
2000-08-14  8:02     ` Stuart Lynne
2000-08-11  8:16   ` Sigurd Urdahl
2000-08-11  9:09     ` Ollie Lho
2000-08-11  9:53     ` Rogelio M. Serrano Jr. [this message]
2000-08-14  8:00     ` Stuart Lynne

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=3993CD0E.84A9B5B@evoserve.com \
    --to=rogelio@evoserve.com \
    --cc=mtd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.