From: ian@brightstareng.com
To: linux-mtd@lists.infradead.org
Subject: RE: JFFS2 Support for Large Flash Designs
Date: Wed, 7 Mar 2007 12:23:07 -0500 [thread overview]
Message-ID: <200703071223.07485.ian@brightstareng.com> (raw)
In-Reply-To: <mailman.311.1173272465.2275.linux-mtd@lists.infradead.org>
On Wednesday 07 March 2007 08:01, Joern Engel wrote:
> Code is not in mainline Linux kernel. I generally distrust
> such code; apart from the support question, it is an
> indication of other problems.
There are many software components that have intimate knowledge
of the kernel that are not in "mainline Linux kernel". There is
nothing wrong with this. There are many many drivers that are
outside the "mainline"; much of the support for embedded
processors and their peripherals is not in the "mainline".
There are some positives of having components maintained outside
the context of "linux".
Yaffs actually has a life outside linux. Using "outside the
mainline" as an argument is weak at best. The 2.6 kernel
makefile makes building a module outside the tree trivial -- so
lots of the older build hassles and arguments no longer exist.
Some random programs I build that know about the kernel
internals: busybox, e2fsprogs, genext2fs, Glibc, net-tools,
pthreads, uClibc, util-linux, wireless_tools the list goes on,
with plenty of drivers/modules too.
-imcd
next parent reply other threads:[~2007-03-07 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.311.1173272465.2275.linux-mtd@lists.infradead.org>
2007-03-07 17:23 ` ian [this message]
2007-03-07 17:48 ` JFFS2 Support for Large Flash Designs Thomas Gleixner
2007-03-07 17:54 ` Lennert Buytenhek
2007-03-07 18:17 ` ian
2007-03-07 18:37 ` Thomas Gleixner
2007-03-07 18:07 ` Jörn Engel
2007-03-06 21:34 Johnson, Charles F
2007-03-07 1:36 ` Josh Boyer
2007-03-07 1:38 ` Johnson, Charles F
2007-03-07 1:47 ` Josh Boyer
2007-03-07 11:04 ` Jörn Engel
2007-03-07 6:47 ` Vitaly Wool
2007-03-07 7:09 ` Charles Manning
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=200703071223.07485.ian@brightstareng.com \
--to=ian@brightstareng.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