os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add a new section of embedded projects suggested by Warner.

Browse source 
Submitted by:	  imp@
This commit is contained in:
Murray Stokely 2008-03-18 04:24:39 +00:00
parent feed0db4d1
commit 46c40b29c8
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=31681
1 changed files with 95 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

96
en/projects/ideas/ideas.xml
View file

@ -15,10 +15,104 @@ Ideas//EN"
<ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.48 2008/03/18 00:12:12 rwatson Exp $
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.49 2008/03/18 04:08:21 murray Exp $
</cvs:keyword>
</cvs:keywords>
<category>
<title>Embedded</title>
<idea id="reduced-size-freebsd" class="soc">
<title>Reduced FreeBSD for Embedded</title>
<desc><p><strong>Technical Contact</strong>: <a
href="mailto:imp@FreeBSD.org">Warner Losh</a></p>
<p>This project would take Sam Leffler's scripts, picobsd,
and/or tinybsd and create a reproducible build of FreeBSD for
a tiny footprint. 16MB is a good side to target, although 8MB
would be better. Most Linux distributions boot using uboot or
redboot. In this environment, the kernel is loaded,
decompressed and away you go. There's also a step for
compressed ram disks. This is basically openwrt for embedding
FreeBSD.</p>
</desc>
</idea>
<idea id="nand-flash" class="soc">
<title>NAND Flash driver support</title>
<desc><p><strong>Technical Contact</strong>: <a
href="mailto:imp@FreeBSD.org">Warner Losh</a></p>
<p>Add support for nand flash support.</p>
</desc>
</idea>
<idea id="bus-abstraction" class="soc">
<title>Make creating a bus easier</title>
<desc><p><strong>Technical Contact</strong>: <a
href="mailto:imp@FreeBSD.org">Warner Losh</a></p>
<p>There's about a dozen busses in the tree now that manage resources and
activate children. They are far too hard to create. We need to
abstract out the basics for these buses and provide a way to allow
these buses to be a subclass of this new base class.</p>
</desc>
</idea>
<idea id="variable-hints" class="soc">
<title>Variable hints</title>
<desc><p><strong>Technical Contact</strong>: <a
href="mailto:imp@FreeBSD.org">Warner Losh</a></p>
<p>Often times in the embedded world, you know what kind of
built-in devices are on a SoC (System on a Chip) only because
you know the specific model of that SoC. It is desirable to
have a mechanism that code on these machines can use to load
one of several sets of hints, which can then be used to
populate the bus.</p>
</desc>
</idea>
<idea id="arm-cleanup" class="soc">
<title>ARM cleanup</title>
<desc><p><strong>Technical Contact</strong>: <a
href="mailto:imp@FreeBSD.org">Warner Losh</a></p>
<p>Adding a new board to the arm code is a lot harder than it
needs to be. A lot of benefit could be had by creating tables
for memory ranges, etc, and having more generic initialization
code. Much of this can also be Machine Independent (MI).</p>
</desc>
</idea>
<idea id="ppc-bringup" class="soc">
<title>PPC/ARM/MIPS bring up</title>
<desc><p><strong>Technical Contact</strong>: <a
href="mailto:imp@FreeBSD.org">Warner Losh</a></p>
<p>There's a number of SoCs that are in consumer grade routers,
etc that have chips that are supported by FreeBSD, or nearly
supported by FreeBSD. Pick one and bring FreeBSD up on it.
Integrate it into the tree.</p>
</desc>
</idea>
<idea id="overhaul-config" class="soc">
<title>Overhaul the config system</title>
<desc><p><strong>Technical Contact</strong>: <a
href="mailto:imp@FreeBSD.org">Warner Losh</a></p>
<p>Right now the kernel is built twice: once for the static
modules in the kernel, and once for the dynamically loaded.
There's also inconsistent dependency tracking. We should fix
this. Bikeshed included, along with three colors of
paint.</p>
</desc>
</idea>
</category>
<category>
<title>File System</title>