arm Release Recertification

Purpose

The purpose of this page is to collate the info necessary to demonstrate that arm meets the [http://release.debian.org/etch_arch_criteria.html architecture recertification criteria for etch].

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) oh, and about 100 others.

Developer machines

The following machines are available to developers:

  1. foo.debian.org - maintained by ..., connectivity via ....

  2. Vince Sanders (Kyllikki) maintains a machine to which developers can be given specific access. General availability access box is wating for DSA to set up, at whcih point it will become jennifer.debian.org.

In the meantime it is jennifer.kyllikki.org port 1022 mail vince@debian.org to ask for an account.

  1. europa.debian.org, a netwinder(233Mhz), hosted at Xandros, adminned by Woody Suwalski <woody@xandros.com>. Ex-buildd machine.

  2. elara.debian.org, a netwinder(233Mhz), hosted at Xandros, adminned by Woody Suwalski <woody@xandros.com>. Ex-buildd machine.

  3. Bill Gatliff (bgat) maintains arm9el.billgatliff.com. 200Mhz machine.

mail bgat@billgatliff.com to ask for an account. Available from 2005.11.07.

  1. Nokia has also offered to put up a suitable machine - in progress (but they are a big corp so it could be a while before it actually happens...)

Ask on debian-arm@l.d.o or on irc.debian.org#debian-arm if you need access.

Port maintainers

The Debian port is maintained by the following developers, who are familiar with arch-specific issues for this port

  1. Vince Sanders (kylliki)
  2. Phil Blundell (pb)
  3. Wookey
  4. Riku Voipio (nchip) (not that familiar yet..)
  5. Lennert Buytenhek (buytenh)
  6. Kenshi Muto (kmuto) (not so familiar, but is running experimental/non-free/volatile/testing-secure buildd and d-i autobuilder)
  7. GuillemJover (guillem)

  8. ...

Users

The port is being actively used at the following sites:

  1. Kyllikki:
  2. Simtec Ltd: "This is insane...Simtec alone can say we have several thousand users just from our dev. boards..."
  3. Wookey at home: 1 netwinder, 2 users, firewall/P2P server
  4. Aleph One Ltd: 2 machines, 2 users, various
  5. Martin Michlmayr: 1 netwinder, 1 user?
  6. ADS maintains a Debian board farm with currently 7 machines and at least 4 regular users.
  7. Adam Powell at home: 1 netwinder, 2 users
  8. Movial, Iyonix machine for scratchbox cpu transparency, ~20 active users, and a pile of arm tablets running a debian fork
  9. Company X, several Iyonix and Simtec CATS machines, tens of users.
  10. Jeroen Massar; Currently 2 NSLU2's for devel + storage etc, 2 other NLSU's optionally for dedicated debian usage + 1 iRiver PMP-140 (debian support is in the pipe! :)

  11. Lennert at home: 1 enp2611
  12. LIACS, NL: 2 enp2611s, 1 enp2605, 1 ixdp2850, 10 users total
  13. PAMurray, US: 1 Manga, 2 users total
  14. PePLink customer poll: [http://forum.peplink.com/viewtopic.php?t=140] currently shows 1 user so far

  15. UCSD Extension, US: Embedded Linux course, recommended hardware
  16. Silas Bennett: Currently use a PePLink Manga running Debian for my primary Firewall/Router.
  17. Peter Teichmann: Simtec Bast is used as Router/Server, Iyonix machine for development (1 user)
  18. Bdale Garbee: Netwinder, Manga Balance Plus, various embedded target boards (2 users)
  19. wiDrone : 3 nslu2; hosting backup for charity webhost (15 users), slush diskspace served thru samba (4 users), devhost for testing (1 user)

Popcon indicates 9 systems (arm) of the architecture as of 2005/11/34. Popcon indicates 20 systems running armeb as of 2005/11/10

'User' is difficult to define for arm: We have a range of users with varying degrees of 'purity' in terms of their Debian usage. Which ones count?

For NSLU2 usage, see: [http://www.nslu2-linux.org/wiki/Info/WhatPeopleAreReallyUsingTheirSlugsFor What People Are Using Their Slugs For], note that this page mentions Unslung/Openslug. The latter branch will most likely go up into a full Debian install over time. Of course, this is only possible when Debian community supports it. Have a look at [http://www.debonaras.org/wiki/Info/OpenDebianSlugUsers this] to see people who are running a 'debian based' os on their armeb nslu2.

Installer

The installer is being maintained by kyllikki and it's currently working effectively. Successful installation reports are available at: ...

Upstream support

Upstream support is provided by:

Archive coverage and Autobuilder support

The port has currently only built 94% of the archive due to various regressions with gcc4, java breakage on 2.6 kernels and porters having been slack for most of 2005. The issues are being addressed now that attention has been drawn to the fact that the port has fallen behind.

This page monitors the current state of problematic packages: [http://wiki.debian.org/ArmBuilddWatch ArmBuilddWatch] (Anyone wanting to help should look here for things that need working on)

Archive cleanliness

The port builds from unmodified Debian source.

Autobuilders

The following machines run buildds for the port:

Key

Offered:

Vetoes

The security team have noted the following problems in supporting the architecture:

The Debian admin team have noted the following problems in supporting the architecture:

The release team have noted the following problems in supporting the architecture:


CategoryEtchReleaseRecertification