From: Thomas Gleixner <tglx@linutronix.de>
To: ian@brightstareng.com
Cc: linux-mtd@lists.infradead.org
Subject: RE: JFFS2 Support for Large Flash Designs
Date: Wed, 07 Mar 2007 18:48:07 +0100 [thread overview]
Message-ID: <1173289687.24738.654.camel@localhost.localdomain> (raw)
In-Reply-To: <200703071223.07485.ian@brightstareng.com>
On Wed, 2007-03-07 at 12:23 -0500, ian@brightstareng.com wrote:
> 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.
There is an important difference between userland tools which have
kernel knowledge and drivers:
The user space interface is _STABLE_ - the kernel interfaces are _NOT_
That's the reason why out of tree drivers, filesystems ... are often out
of sync and contain more #ifdefs than code to cope with the dozens of
kernel versions.
SoC devices out of tree are a seperate steaming pile of ... I have seen
too many chip vendor kernels explode when you just try to do anything
else than run "hello world" on them.
I share Joerns distrust fully.
tglx
next prev parent reply other threads:[~2007-03-07 17:42 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 ` JFFS2 Support for Large Flash Designs ian
2007-03-07 17:48 ` Thomas Gleixner [this message]
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=1173289687.24738.654.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=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