4147
Comment:
|
4150
|
Deletions are marked like this. | Additions are marked like this. |
Line 55: | Line 55: |
This port will eventually replace the arm port. Please see armelLennyReleaseRecertification for potential users. | This port will eventually replace the arm port. Please see ["armLennyReleaseRecertification"] for potential users. |
Line 81: | Line 81: |
* The port has currently built 90,0% of the archive according to [http://unstable.buildd.net/buildd/armel_stats](90% cut off) | * The port has currently built 90,0% of the archive according to [http://unstable.buildd.net/buildd/armel_stats] (90% cut off) |
Purpose
The purpose of this page is to demonstrate that armel meets the [http://release.debian.org/lenny_arch_policy.html architecture recertification criteria for lenny].
If some of these requirements are irrelevant or implausible for the port, please add a waiver request indicating why and how this isn't a problem for the arch in bold.
Availability
The architecture is publicly available without NDAs via:
[http://www.aleph1.co.uk/armlinux/devboards/balloon/index.html Aleph One] (Balloonboard)
[http://www.simtec.co.uk/ Simtec] (CATS, Bast, ...)
[http://www.applieddata.net/ ADS] (Bitsyx, VGX, AGX, ...)
[http://www.linksys.com Linksys] (NSLU2)
[http://www.arcom.com/pc104-xscale-viper.htm Arcom] (Viper, ...)
[http://www.arm.com/ ARM Corp] (Integrator?)
[http://www.europe.nokia.com/nokia/0,,74866,00.html Nokia] (770)
[http://www.iriver.com/ iRiver] PMP-120/140, [ftp://ftp.gpl-devices.org/pub/vendors/iRiver/PMP-1xx/ GPL'd firmware]
[http://www.intel.com/ Intel] (IXDP240x, IXP28xx, ...)
[http://www.radisys.com/ Radisys] (ENP-2611, ENP-2605, ...)
[http://www.peplink.com/ PePLink] (MANGA, MANGA Mini, ...)
[http://www.iyonix.com/ Castle] (Iyonix)
[http://www.giantshoulderinc.com/ Loft] (IXP42x)
[http://www.glomationinc.com/ Glomation] (GESBC-9312-sc, ...)
[http://www.embeddedarm.com/ Technologic Systems] (TS-7200, TS-7250, TS-7260, ...)
[http://www.logicpd.com/ LogicPD] (PXA270 Card Engine) oh, and about 100 others.
Developer machines
The following machines are available to developers:
None currently. Wookey has planned to setup a machine.
Port maintainers
The Debian port is maintained by the following developers, who actively work on architecture specific issues:
- Riku Voipio
- Joeyh Hess
- Aurelien Jarno
- Wookey
Users
The port is being actively used at the following sites:
Popcon indicates 12 users of the architecture as at 2007/10/28.
This port will eventually replace the arm port. Please see ["armLennyReleaseRecertification"] for potential users.
Installer
The installer is being maintained by Joeyh Hess and it's currently working effectively.
Upstream support
Upstream support is provided by:
- binutils: codesourcery (Paul Brook)
- glibc: codesourcery (Paul Brook)
- gcc: codesourcery (Paul Brook)
- g++: codesourcery (Paul Brook)
kernel: [http://www.arm.linux.org.uk/ Russell King and others],kyllikki, buytenh
- boot loader: there are lots of these for different machines
- blob - blob.sf.net
- able - Simtec Ltd
- bootldr - handhelds.org
- uboot -
- redboot - Redhat Ltd
- apex -
Archive coverage and Autobuilder support
The port has currently built 90,0% of the archive according to [http://unstable.buildd.net/buildd/armel_stats] (90% cut off)
Archive cleanliness
The port builds from unmodified Debian source.
Autobuilders
The following machines run buildds for the port:
- oldstable (oldstable-proposed-updates, oldstable-security)
This suite does not exist for armel.
- stable (proposed-updates, stable-security)
This suite does not exist for armel.
adminned by ...
- testing (testing-proposed-updates, testing-security)
This suite does not exist for armel.
- unstable
- armel.kos.to - connectivity via ADSL, hosted by Riku Voipio, buildd logs checked and administrated by Riku Voipio.
- armel2.kos.to - connectivity via ADSL, hosted by Riku Voipio, buildd logs checked and administrated by Riku Voipio.
Vetoes
The security team have noted the following problems in supporting the architecture:
- None
The Debian admin team have noted the following problems in supporting the architecture:
- None
The stable release team have noted the following problems in supporting the architecture:
- None
The release team have noted the following problems in supporting the architecture:
- None