-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello,
(Re-sending with appropriate charset) Find below some bits collected while ARM sprint in Cambridge, UK. < https://wiki.debconf.org/wiki/Miniconf-UK/2013 > If you would like further information or discussion on any of the topics, please follow up at debian-arm or any relevant mailing list. We would like to thank our sponsors: · http://www.arm.com/ · http://www.boston.co.uk/ · http://www.citrix.com/ · http://www.xenproject.org/ · http://www.codethink.co.uk/ · http://www.baserock.com/ and all the staff (Steve, Jo, Lisa, ...) that made possible this event. ━━━━━━━━━━━━━ Bits from DEBIAN-ARM Contents ──────── 1 Buildd and porterbox status .. 1.1 armel buildd status .. 1.2 armhf buildd status 2 ARM Kernel support .. 2.1 armel platform support .. 2.2 armhf platform support 3 Bootloader support .. 3.1 Device tree enablement and u-boot script handling .. 3.2 GRUB on ARM and chain-loading to u-boot or linux 4 Debian installer support 5 arm64 Debian port support .. 5.1 Enable buildd support .. 5.2 Setup arm64 debian-ports 6 Cross toolchain in Debian .. 6.1 Linux based cross toolchain packages .. 6.2 Bare metal cross toolchain packages 7 Debian-Ports integration in Debian .. 7.1 Hand machine over to DSA .. 7.2 Enable unreleased suite handling in archive tools .. 7.3 Merge wanna-build DB into official one .. 7.4 Enable non-DD uploaders for d-ports 8 Emdebian.org server future 9 Cross build-depends discussion for bootstrapping 10 Enable multiarch in buildd software 11 Raspbian port support .. 11.1 Tweak compiler defaults via dpkg-vendor .. 11.2 Discussion on ways to support unstable suite 12 Flashable image generation .. 12.1 Discussion on supporting pre-installed images 13 Make popcon report stats per architecture 1 Buildd and porterbox status ═════════════════════════════ For building current ARM ports, we are maintaining current ARM infrastructure, however we are aiming to renew some of the ARM platforms building armhf port. If ARM server class hardware is possible to get deployed, porters will consider to build both armel and armhf ports in those machines. However during the conference, it was suggested to implement to tool to scan the archive for potential issues (i.e. ARMv4t code build on ARMv5t machine, ARMv7 code not ending up in armel archive). Some discussion on switching armel to ARMv5t was done, but it does not seem to be worth it. 1.1 armel buildd status ─────────────────────── Until better ARM infrastructure is setup in Debian, current build daemons are kept for building armel port. ⁃ currently up 6 buildds on Marvell mv78x00 hardware • pending to extend +1.5GB RAM on those, when possible. None objected to drop old based hardware (iop32x based) ⁃ porterboxes: agricola decommisioned, abel and ipa.d.n will keep being armel porterboxes. 1.2 armhf buildd status ─────────────────────── We are in contact with an ARM server vendor trying to work out a solution that benefits both, Debian and vendor. They know about Debian needs and we are still waiting on them to come back with a proposal. Alternatively, a couple board manufacturers have made a donation offer to Debian. A decission is pending to be made. ⁃ porterboxes: harris and ipa.d.n are kept as armhf porterboxes. 2 ARM Kernel support ════════════════════ There is special interest in relevant Debian teams (DSA,buildd,release) to provide critical Debian infrastructure kernels in the official Debian package archive. Hence, one of primary goals is to support our own infrastructure in the official archive. 2.1 armel platform support ────────────────────────── Linux kernels supported, in armel port, is a long list, some of which do not build or have size requirements issues to fit in machine device. It has been proposed that next time ixp4xx and iop32x kernels fail to build will be disabled (and likely not released in Jessie). Trimming down the list of supported armel platforms is desired. ⁃ supported in wheezy: • iop32x • ixp4xx • kirkwood • mv78xx0 • orion5x • versatile ⁃ jessie supported: • [proposed dropping] [proposed dropping] https://lists.debian.org/debian-arm/2013/06/msg00206.html 2.2 armhf platform support ────────────────────────── The goal for Jessie release is to only build armmp and armmp-lpae kernel (already done in experimental) and drop support for individual platforms. ⁃ supported in wheezy: • mx5 • omap • vexpress ⁃ jessie supported: • added armmp (ARMv7 multiplatform kernel for Marvell Armada 370/xp, Freescale iMX5x/iMX6, Calxeda Highbank) • propose dropping mx5, omap and vexpress (when merged in armmp) • final goal: add two kernels armmp and lpae one. 3 Bootloader support ════════════════════ 3.1 Device tree enablement and u-boot script handling ───────────────────────────────────────────────────── There is a cross-distro effort to standarize where DT files should live in filesystem. ⁃ cross-distro mailing list (Linaro): [http://lists.linaro.org/mailman/listinfo/cross-distro] [http://lists.linaro.org/pipermail/cross-distro/2013-August/thread.html] 3.2 GRUB on ARM and chain-loading to u-boot or linux ──────────────────────────────────────────────────── GRUB with ARM support is planned to go into experimental, real soon now. While GRUB for ARM is potentially more attractive for ARM server devices, it was suggested that it could be used to work-around the issue with devices having small boot ROM and used to chain-load into u-boot or proper Linux, but someone needs to step up and work on the enablement. 4 Debian installer support ══════════════════════════ For Jessie release, armhf d-i targets armmp and armmp-lpae support, which was been recently updated for that. 5 arm64 Debian port support ═══════════════════════════ If Debian is unable to find ARM 64-bit hardware before Jessie gets frozen, it likely won't be Jessie supported. 5.1 Enable buildd support ───────────────────────── ⁃ Fast model system (initial bootstrapping only) ⁃ QEMU support (bootstrapping to the point of a buildd image & recompile it all again) ⁃ Real hardware accessible to Debian (?) ⁃ Qt issues make it hard with emulators. May build, might not work. 5.2 Setup arm64 debian-ports ──────────────────────────── ⁃ arm64 setup as new bootstrapping port ⁃ manual builds could be uploaded but possible lack of space ⁃ 9 more packages needed for a minimal bootstrap 6 Cross toolchain in Debian ═══════════════════════════ 6.1 Linux based cross toolchain packages ──────────────────────────────────────── It is still needed to define which packaging to upload (multi-arch, full bootstrap) and enable buildd's if needed for multi-arch build. Other architecture rather than ARM need to be build and tested. 6.2 Bare metal cross toolchain packages ─────────────────────────────────────── Those have been already uploaded to sid. 7 Debian-Ports integration in Debian ════════════════════════════════════ debian-ports needs a user mailing list. Which mailing list should be used for debian-ports discussion? 7.1 Hand machine over to DSA ──────────────────────────── All that needs to be done to handover machine to DSA: ⁃ Identify services running on d-ports ⁃ Transfer services to DSA machine ⁃ Transfer domain names to DSA 7.2 Enable unreleased suite handling in archive tools ───────────────────────────────────────────────────── Aparently, keeping separated archive for debian-ports would be good, so we can still have waky-hacks in -ports, while do clean bootstrap in Debian archives. 7.3 Merge wanna-build DB into official one ────────────────────────────────────────── ⁃ We want to be able to keep same architecture in both Debian and Debian-ports (Note: Debian-ports packages carry scary hacks, and Debian bootstrap should start from clean start) 7.4 Enable non-DD uploaders for d-ports ─────────────────────────────────────── ⁃ Recognise porting work in the NM process independently of whether individual packages are listed as being maintained by that person. Needs some tools or existing tools adapting to ports structure. 8 Emdebian.org server future ════════════════════════════ ⁃ Figure out dependencies (cross toolchains in the archive, grip support) and plan for end of life (transfer domain to DSA). ⁃ Move website to DSA machine. 9 Cross build-depends discussion for bootstrapping ══════════════════════════════════════════════════ ⁃ build-dependencies which change name when crossing. ⁃ #695287 - sbuild: synthetic cross-build-dependencies for compilers 10 Enable multiarch in buildd software ══════════════════════════════════════ ⁃ danger of apt resolving via the secondary architectures possibly use pinning to never allow secondary arch installation. ⁃ could be used to kill off biarch/multilib. 11 Raspbian port support ════════════════════════ 11.1 Tweak compiler defaults via dpkg-vendor ──────────────────────────────────────────── ⁃ NMU packages which don't support dpkg buildflags. 11.2 Discussion on ways to support unstable suite ───────────────────────────────────────────────── Currently Raspbian builds on Jessie, so keeping up with transitions makes it sort of fun. 12 Flashable image generation ═════════════════════════════ 12.1 Discussion on supporting pre-installed images ────────────────────────────────────────────────── ⁃ Just fix DI to work on the expected platforms. ⁃ Document ways to create images with existing tools. 13 Make popcon report stats per architecture ════════════════════════════════════════════ ⁃ Measure downloads of Packages.gz per architecture as alternative. ⁃ Using popcon stats for such architectures (not installed with d-i) might not show real or accurate results. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCgAGBQJSnRsoAAoJEK8ig6p24qx7hzUQALBWLenugKnC5wCvYMWyS8As 82MpbMYi8vriaka5BThQYdSRQReuPdysNhidFIvxywB8UvFjQu3Y65yaNYe5Dl84 6wWSyJmytwVWpckZno+SaKdNwW9yF7+MOugtCiqrGLxEcQTyvvcsPtXAPMmXxsar /521URE/24q7RwiBy1qcvY3H3IdnAkIylZDlO6MP1b1/hlWPkbmgDL1LA4snx4tg vSRSdFcPc4oWfUz7yJd9ag4FDDZ0IikUx6Yy511F9XGGkdS55Cquj5JHIOf+fnf2 kSpr8YUOplyau74x4+aZcNNDhGjENP9inkpwncCvoqUjsO9dUx/GTqUAbJzGux2W d5GNg2BLMKGhht4n/rSSQ4ezm7u/0L4NUZsoX7FRUMCLgD96XVWERVvQsOG3C/Wn sCqGegQk1PdKcA3wN2e2qoHXKjM+PMSvOlo2smDEZXZjgLoShW1b4XKe7DMZE4Ps mw1udmrrtQG96Pj/jJcJ0b300HjksOtHLtomR8vITC6KfVKCtLhWO+txrdBZnjRW CKg++o/7p9lmWEMI7reaRNXOWNV6y7+acbKkGjjiLBS2XJsxlPEo8rbxwKde2uM4 zr/TNFBxnGAayD5Jx31q/sb/aEKsecFfjbSf84y7jwSLvRVo5SEGX91KpUdHQp9h q2Gbnm4qg6Wh8Z3Gor0N =2TtA -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131202234336.ga8...@polynomio.collabora.co.uk
