ia64: update docs to indicate current tier status
Based on https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html ia64 will be dropping to tier 4 (unsuppored) status with FreeBSD 11. Document this.
This commit is contained in:
Eitan Adler
parent
41fda4af24
commit
ebbcf2cb41
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46616
3 changed files with 4 additions and 144 deletions
|
|
@ -7,7 +7,7 @@
|
|||
.include "../Makefile.inc"
|
||||
.endif
|
||||
|
||||
DOCS= index.xml machines.xml refs.xml todo.xml
|
||||
DOCS= index.xml machines.xml refs.xml
|
||||
DATA= i2inside.png mckinley-die.png merced-die.png montecito-die.png
|
||||
|
||||
.include "${DOC_PREFIX}/share/mk/web.site.mk"
|
||||
|
|
|
|||
|
|
@ -33,9 +33,6 @@
|
|||
<li>
|
||||
<a href="#status">Current status</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="todo.html">What Needs To Be Done</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="machines.html">Hardware List</a>
|
||||
</li>
|
||||
|
|
@ -53,17 +50,8 @@
|
|||
|
||||
<h3><a name="status">Current status</a></h3>
|
||||
|
||||
<p>The ia64 port is still considered a tier 2 platform. This boils
|
||||
down to not being fully supported by our security officer, release
|
||||
engineers and toolchain maintainers. In practice however the
|
||||
distinction between a tier 1 platform (which is fully supported)
|
||||
and a tier 2 platform is not as strict as it seems. In almost all
|
||||
aspects the ia64 port is a tier 1 platform.
|
||||
<br/>
|
||||
From a developer point of view there's an advantage to have the ia64
|
||||
port be a tier 2 platform for a while longer. We still have a couple
|
||||
of ABI breaking changes in the pipeline and having to maintain
|
||||
backward compatibility this early in a ports life is less than
|
||||
ideal.</p>
|
||||
<p>The ia64 port is considered a tier 2 platform until
|
||||
FreeBSD 10. After this it will no longer be
|
||||
supported.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -1,128 +0,0 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
|
||||
"http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [
|
||||
<!ENTITY email "freebsd-ia64">
|
||||
<!ENTITY title "FreeBSD/ia64 Project">
|
||||
]>
|
||||
|
||||
<html xmlns="http://www.w3.org/1999/xhtml">
|
||||
<head>
|
||||
<title>&title;</title>
|
||||
|
||||
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
|
||||
</head>
|
||||
|
||||
<body class="navinclude.developers">
|
||||
|
||||
<img align="right" alt="Montecito die" src="montecito-die.png"/>
|
||||
|
||||
<p>Search the FreeBSD/ia64 PR database:</p>
|
||||
|
||||
<form action="http://www.FreeBSD.org/cgi/query-pr-summary.cgi"
|
||||
method="get">
|
||||
<input type="hidden" name="category" value="ia64"/>
|
||||
<input type="hidden" name="sort" value="none"/>
|
||||
<input type="text" name="text"/>
|
||||
<input type="submit" value="Go"/>
|
||||
</form>
|
||||
|
||||
<h3>
|
||||
What needs to be done
|
||||
</h3>
|
||||
<p>
|
||||
This page tries to be the starting point for people trying to find
|
||||
anything that can be done. The order of the items on this page are
|
||||
not strictly an indication of priority, but it is a good indication.
|
||||
There are in all likelihood tasks that are not mentioned here, but
|
||||
that should be done nonetheless. A typical example is the maintenance
|
||||
of the ia64 web pages... unfortunately.
|
||||
</p>
|
||||
|
||||
<h4>
|
||||
Becoming a tier 1 platform
|
||||
</h4>
|
||||
<p>
|
||||
With two releases as a tier 2 platform, it is time to work towards
|
||||
becoming a tier 1 platform. This involves tasks as varied as:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
Improve the installation process to take into account that
|
||||
there is already a GPT with an EFI partition, including other
|
||||
operating systems. The ability to add a FreeBSD entry to the
|
||||
EFI boot menu is also a nice thing.
|
||||
</li>
|
||||
<li>
|
||||
Port the GNU debugger. It is sorely missed on a development
|
||||
machine and required on tier 1 platforms.
|
||||
</li>
|
||||
<li>
|
||||
Port the X server (ports/x11/XFree86-4-Server). Not really
|
||||
required for tier 1 status, but one cannot truly do without
|
||||
if one wants to use ia64 as a desktop machine.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h4>
|
||||
Ports and packages
|
||||
</h4>
|
||||
<p>
|
||||
A very important task for the success of FreeBSD on ia64 is making
|
||||
sure that users have something to run besides ls(1). Our huge ports
|
||||
collection has been targeting ia32 for the most part, so it is not
|
||||
surprising that there are a lot of ports that do not build or do not
|
||||
work on ia64. Look
|
||||
<a href="http://pointyhat.FreeBSD.org/errorlogs/ia64-8-latest/">
|
||||
here
|
||||
</a>
|
||||
for the most up-to-date list of ports that fail to build for some
|
||||
reason or another. Note that if there are ports depending on one or
|
||||
more ports that fail, those are not built and are not counted. A good
|
||||
way to help out here is to work on those ports that have a lot of
|
||||
ports depending on it (see the "Aff." column in the table).
|
||||
</p>
|
||||
|
||||
<h4>
|
||||
Sharpening the saw
|
||||
</h4>
|
||||
<p>
|
||||
There are plenty functions (especially assembly routines) that
|
||||
have been written to provide the missing functionality without any
|
||||
consideration for speed and/or robustness. Reviewing those functions
|
||||
and replacing them if necessary is a good task that can be done
|
||||
concurrently and independently from other activity and does not
|
||||
necessarily require huge amounts of knowledge and/or experience.
|
||||
</p>
|
||||
|
||||
<h4>
|
||||
Core development
|
||||
</h4>
|
||||
<p>
|
||||
On top of the high-level things that do not work or do not exist,
|
||||
there is also some rather involved rewriting to be done at the
|
||||
foundation and can potentially affect all other platforms as well.
|
||||
This includes:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
Improve UP and SMP stability by revamping the PMAP module.
|
||||
The low-level handling of VM translations needs to be improved.
|
||||
This involves both correctness as well as performance.
|
||||
</li>
|
||||
<li>
|
||||
Basic device drivers such as sio(4) and syscons(4) do not
|
||||
work on ia64 machines that do not have support for legacy
|
||||
devices. This is a rather big issue, because it affects all
|
||||
platforms and may involve rewriting (big) parts of certain
|
||||
subsystems. Clearly a task that needs wholesale support and
|
||||
coordination.
|
||||
</li>
|
||||
<li>
|
||||
Better handling of sparse (physical) memory configurations
|
||||
by not creating VM tables that span the whole address space,
|
||||
but rather cover the memory "chunks" that are present. We are
|
||||
currently forced to ignore memory because of this.
|
||||
</li>
|
||||
</ul>
|
||||
</body>
|
||||
</html>
|
||||
Loading…
Add table
Add a link
Reference in a new issue