[joern@wohnheim.fh-wedel.de] [ANNOUNCE] New kernel tree for embedded linux

["Jörn Engel" <joern@wohnheim.fh-wedel.de>]

Even though this belongs on linux-kernel, there might be more
interested people on this list.

----- Forwarded message from Jörn Engel <joern@wohnheim.fh-wedel.de> -----

From: Jörn Engel <joern@wohnheim.fh-wedel.de>
To: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] New kernel tree for embedded linux

Hi!

Some days ago, I've started a -je [*] tree which will focus on memory
reduction for the linux kernel.

The RATIONALE is that on a ppc with some flash, memory, network and
nothing much else, I don't feel like parsing MS-DOS partitions,
offering IPX networking etc., but that junk is still included in
2.[45].current - unconditionally. And there is more...

My first GOAL is to add config options that rip the code out for any
platform that doesn't need, yet keeps it in for everyone that does. If
I don't know what the code is needed for, I'll just rip it out and
wait for bug reports - hopefully.

If I feel that any particular patch is clean enough for mainline, I'll
forward it to Linus/Marcello.

WHO should use this tree:
- Anyone concerned about memory footprint of the linux kernel, both of
the image and during runtime. This will mainly be embedded developers,
I guess.
- Anyone. :)
Bugreports of any kind will help me to clean up the patches and get
them included in mainline. I personally run them on my PIII notebook,
right now, and things didn't break. (Yet?)

HOW can you help:
- Any patch that reduces the memory footprint on _any_ platform is
welcome. Even the worst hacks should be cleaned up over time to work
for everyone.
- Test the patches and:
 - Send bugreports. They will help to clean up the patches.
 - Send works-for-me reports with a rough outline of the hardware
 used.  When things start to work for many people on many platforms,
 it may be time for mainline.
- Send any other patches and convince me that they help embedded
people by my definition (whichever that may be at that time).

WHAT patches will I ignore/reject:
- Anything that does not help embedded (my definition, see above).
That stuff should go into -ac, -dj, -mm, -aa or whereever.

Finallly, WHERE can you get it:
http://wh.fh-wedel.de/~joern/software/kernel/je/24/patch-2.4.20-je1
http://wh.fh-wedel.de/~joern/software/kernel/je/25/patch-2.5.66-je1

DISCLAIMER:
No, the server does not support directory browsing, there is no
mailing list and there are currently only three patches in the 2.4
tree and two in the 2.5 tree. 2.5 is untested, looks broken and I
should put some work in it.
These patches may cost you time, money and precious hardware, I don't
guarantee for anything and IANAL. Anything else?

Jörn

[*] Obviously, je stands for "just embedded", which means I only take
patches that help some embedded platform. What have you thought?

-- 
A surrounded army must be given a way out.
-- Sun Tzu

----- End forwarded message -----

Jörn

-- 
When people work hard for you for a pat on the back, you've got
to give them that pat.
-- Robert Heinlein