&title;

Index: head/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xml (revision 46615) +++ head/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xml (nonexistent) @@ -1,128 +0,0 @@ - - - -]> - - - - &title; - - $FreeBSD$ - - - - - Montecito die

- -

Search the FreeBSD/ia64 PR database:

- - - -

- What needs to be done -

- 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. -

- -

- Becoming a tier 1 platform -

- 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: -

- 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. -
- Port the GNU debugger. It is sorely missed on a development - machine and required on tier 1 platforms. -
- 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. -

- -

- Ports and packages -

- 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 - - here - - 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). -

- -

- Sharpening the saw -

- 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. -

- -

- Core development -

- 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: -

- 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. -
- 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. -
- 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. -

- - Property changes on: head/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xml ___________________________________________________________________ Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Index: head/en_US.ISO8859-1/htdocs/platforms/ia64/Makefile =================================================================== --- head/en_US.ISO8859-1/htdocs/platforms/ia64/Makefile (revision 46615) +++ head/en_US.ISO8859-1/htdocs/platforms/ia64/Makefile (revision 46616) @@ -1,13 +1,13 @@ # $FreeBSD$ .if exists(../Makefile.conf) .include "../Makefile.conf" .endif .if exists(../Makefile.inc) .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" Index: head/en_US.ISO8859-1/htdocs/platforms/ia64/index.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/platforms/ia64/index.xml (revision 46615) +++ head/en_US.ISO8859-1/htdocs/platforms/ia64/index.xml (revision 46616) @@ -1,69 +1,57 @@ ]> &title; $FreeBSD$ McKinley die

Search the ia64 mailing list archives:

Introduction

The FreeBSD/ia64 project pages contain information about the FreeBSD port to Intel's IA-64 architecture; officially known as the Intel Itanium® Processor Family (IPF). As with the port itself, these pages are still mostly a work in progress.

Current status

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. -
- 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.

The ia64 port is considered a tier 2 platform until + FreeBSD 10. After this it will no longer be + supported.