From: Ollie Lho <ollie@sis.com.tw>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Adi Linden <adi@adis.on.ca>, Trevor Woolven <trevw@zentropix.com>,
Matt Hortman <mbhortman@ieee.org>,
mtd@infradead.org
Subject: Re: building M-Sys DOC driver as a module
Date: Fri, 21 Jul 2000 09:29:11 +0800 [thread overview]
Message-ID: <3977A767.EB4AEA86@sis.com.tw> (raw)
In-Reply-To: Pine.LNX.4.10.10007201601430.1064-100000@infradead.org
David Woodhouse wrote:
> Modular drivers and initrd are a horrible waste of space in an embedded
> system, IMO. Far better to cut out module support completely, and even
> also block device support, putting JFFS on the DiskOnChip instead of NFTL.
>
> The free driver isn't far off being usable in production - there's not a
> lot to do, it's just that I haven't had time to do it. Patrick is close to
> having ECC support, now we just need to properly thread the NFTL code and
> make it deal correctly with bad blocks, and for better efficiency, stick
> in the state handling for the individual flash chips, like I did for the
> CFI chips.
>
> Trevor - Did I miss something of the TODO list that we drew up?
>
David,
I think we will have ext2 on NFTL on DoC Millennium configuration
for LinuxBIOS project so I am also working on revisiting the nftl.c Could
you please send me your TODO list on NFTL stuff ??
Ollie
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-07-21 1:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 22:35 building M-Sys DOC driver as a module Matt Hortman
2000-07-20 9:32 ` Trevor Woolven
2000-07-20 14:54 ` Adi Linden
2000-07-20 15:07 ` David Woodhouse
2000-07-21 1:29 ` Ollie Lho [this message]
2000-07-21 15:01 ` David Woodhouse
2000-07-21 9:58 ` Trevor Woolven
2000-07-21 16:03 ` David Woodhouse
2000-07-24 23:43 ` Stuart Lynne
2000-07-24 23:41 ` 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=3977A767.EB4AEA86@sis.com.tw \
--to=ollie@sis.com.tw \
--cc=adi@adis.on.ca \
--cc=dwmw2@infradead.org \
--cc=mbhortman@ieee.org \
--cc=mtd@infradead.org \
--cc=trevw@zentropix.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