Differences between revisions 1 and 6 (spanning 5 versions)
Revision 1 as of 2007-08-07 08:37:51
Size: 4312
Editor: ?SuneVuorela
Comment:
Revision 6 as of 2007-10-29 09:05:01
Size: 4150
Comment:
Deletions are marked like this. Additions are marked like this.
Line 32: Line 32:
None currently. Wookey has planned to setup a machine.
Line 38: Line 39:

 1. Wookey
 2. Riku Voipio (nchip) (not that familiar yet..)
 3. Lennert Buytenhek (buytenh)
 1. Riku Voipio
 2. Joeyh Hess
 3. Aurelien Jarno
 4. Wookey
Line 48: Line 49:
 1. foo: xx machines, yy users, personal workstations
 2. bar: 1 machine, yyy users, development server
 3. ...
 1.
 2.
 3.
Line 52: Line 53:
Popcon says armel : 8 as of 7th august 2007, but it is expected to gain some users from arm. 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.
Line 56: Line 60:
The installer is being maintained by Martin Michlmayr and it's currently working effectively. Successful installation reports are available at: ... The installer is being maintained by Joeyh Hess and it's currently working effectively.
Line 77: Line 81:
 * The port is currently at xx% up to date according to [http://buildd.debian.org/stats/graph2-week.png the buildd stats] (95% cut off)
* The port has currently built xx% of the archive according to [http://buildd.debian.org/stats/graph-week.png the buildd 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)
Line 89: Line 92:
  * foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...   * '''This suite does not exist for armel'''.
Line 91: Line 94:
  * foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...   * '''This suite does not exist for armel'''.
adminned by ...
Line 93: Line 97:
  * foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...   * '''This suite does not exist for armel'''.
Line 95: Line 99:
  * foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...   * 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.

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:

  1. [http://www.aleph1.co.uk/armlinux/devboards/balloon/index.html Aleph One] (Balloonboard)

  2. [http://www.simtec.co.uk/ Simtec] (CATS, Bast, ...)

  3. [http://www.applieddata.net/ ADS] (Bitsyx, VGX, AGX, ...)

  4. [http://www.linksys.com Linksys] (NSLU2)

  5. [http://www.arcom.com/pc104-xscale-viper.htm Arcom] (Viper, ...)

  6. [http://www.arm.com/ ARM Corp] (Integrator?)

  7. [http://www.europe.nokia.com/nokia/0,,74866,00.html Nokia] (770)

  8. [http://www.iriver.com/ iRiver] PMP-120/140, [ftp://ftp.gpl-devices.org/pub/vendors/iRiver/PMP-1xx/ GPL'd firmware]

  9. [http://www.intel.com/ Intel] (IXDP240x, IXP28xx, ...)

  10. [http://www.radisys.com/ Radisys] (ENP-2611, ENP-2605, ...)

  11. [http://www.peplink.com/ PePLink] (MANGA, MANGA Mini, ...)

  12. [http://www.iyonix.com/ Castle] (Iyonix)

  13. [http://www.giantshoulderinc.com/ Loft] (IXP42x)

  14. [http://www.glomationinc.com/ Glomation] (GESBC-9312-sc, ...)

  15. [http://www.embeddedarm.com/ Technologic Systems] (TS-7200, TS-7250, TS-7260, ...)

  16. [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:

  1. Riku Voipio
  2. Joeyh Hess
  3. Aurelien Jarno
  4. 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

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


CategoryLennyReleaseRecertification