Re: Roll call for porters of architectures in sid and testing (Status update)
On 21-Sep-13, at 7:23 PM, Ben Hutchings wrote: I'll continue testing/software development activity on ia64 for the Jessie cycle, and more generally, until Debian drops ia64. I'm already waiting for Wayland on ia64 and other big updates. So please, keep ia64 in the bandwagon ;-) But I don't think ia64 is well-supported even in wheezy. The kernel doesn't boot on some common machines and no-one seems to be able to fix it. I don't believe this for a minute. This is about Debian and it's ability to attract capable porters. I seem to recall that a recent Wayland build is in the unstable parisc archive... Dave -- John David Anglin dave.ang...@bell.net -- 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/blu0-smtp95e95ff163518fb536728097...@phx.gbl
Re: Roll call for porters of architectures in sid and testing (Status update)
On Sat, 2013-09-21 at 19:36 +0200, Émeric MASCHINO wrote: > Hi, > > I'm a long-time ia64 Debian user (> 10 years). I'm mostly focused on > desktop aspects (GNOME, Iceweasel, LibreOffice, Qt Creator, C++ 3D > software development) while most other ia64 users that I know are more > inclined on server use. > > I'm not a DD/DM, but daily update my ia64 workstation, report bugs and > do my best to provide useful information in order to get them fixed. Thank you for this. > I've also provided a couple of kernel patches in the past. I'm cross > testing with Gentoo to ensure that bugs I report are Debian-specific > or ia64-generic. > > I'll continue testing/software development activity on ia64 for the > Jessie cycle, and more generally, until Debian drops ia64. I'm already > waiting for Wayland on ia64 and other big updates. > > So please, keep ia64 in the bandwagon ;-) But I don't think ia64 is well-supported even in wheezy. The kernel doesn't boot on some common machines and no-one seems to be able to fix it. Ben. -- Ben Hutchings compatible: Gracefully accepts erroneous data from any source signature.asc Description: This is a digitally signed message part
Re: Roll call for porters of architectures in sid and testing
Hi, Although I'm not a DD/DM, I currently do the majority of the Debian unstable package builds for parisc. As noted by Helge, these are available at www.parisc-linux.org . While not fully complete, the archive contains several thousand packages that are constantly being updated. We are close to restarting a parisc buildd... I perform a small amount of porting (e.g., webkitgtk, qt4-x11, ...) and bug reporting. This has reduced the number of packages which need changes to build on parisc. I'm also a parisc GCC and binutils maintainer. In the past year or so, I spent a significant amount of time working on parisc cache related issues in the linux kernel. I support this activity with three parisc servers and one workstation. In my spare time, I do embedded software and electronic design. Regards, John David (Dave) Anglin On 5-Sep-13, at 5:21 PM, Helge Deller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I am not currently a porter but I would like to be one for the architecture parisc/hppa. I currently have lots of parisc hardware (5 workstations and 4 servers), all currently running debian unstable from our own debian repository at www.parisc-linux.org. My involvement for debian-parisc so far: - - I was one of the initiators of parisc-linux port back in 1999. - - I have continuous worked on the ports since then. - - I'm currently one of the two official linux kernel maintainers for the parisc port at kernel.org. - - I've fixed quite some debian bugs reported for parisc in the past, including locking functions in gcc, KDE fixes, udev fixes and many more. - - I do have a strong linux developer background (C/C++, Assembler) and was formerly a developer at a major linux distributor. - - I'm maintaining the parisc-linux website and wikis. I am not a DD/DM but would like to become one. At last, I would be happy if parisc could become again a supported platform in the debian-ports repositories for the lifetime of Jessie. parisc was dropped with debian squeeze, because there were quite some stability issues with the Linux kernel at that time. Currently, upstream kernel 3.10 (stable) and kernel 3.11 do work reliable on all major machines. -- Helge Deller On 09/01/2013 09:33 AM, Niels Thykier wrote: Hi, As we announced in [LAST-BITS], we would like to get a better idea of that status of the ports, to make an informed decision about which port can be released with jessie. One of the steps is to get an overview of which of the porters are (still) active for each port. Once the results from the role-call are in, we will request other information about the status of the ports. In the meantime, feel free to update and collect info about the ports in the Debian wiki[WIKI]. If you are (or intend to become) an active porter for the lifetime of jessie, then please send a signed email explaining your involvement in the port to the Release Team before 1st of October 2013. Please explain the level of your involvement in the port. Feel free to use the following template as your reply: """ Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the jessie release: For , I - test (most|all) packages on this architecture - fix toolchain issues - triage arch-specific bugs - fix arch-related bugs - maintain buildds - ... """ Niels, on behalf of the release team [LAST-BITS] http://lists.debian.org/debian-devel-announce/2013/08/msg6.html [WIKI] https://wiki.debian.org/ArchiveQualification/Jessie -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSKPXJAAoJEIfJwVG1Hjhk1BsH/3nhr6HjGwpGnc6NnQxV3KA2 95LNye6Fi7aOh5NWGrjn8c3fmyJcoHdQFAMOIIulGZW6gLAeu1cX9Y16OAzMKP/H LTCvq0Q8yzl/U75+NKgz9rdozsXds43rmuyBJIZdypGXKjWEIkRz/ISzOL4+hdqh W+HoYWG/fqCsdhJMiUIIUQ7BW6kadJmoi3L5dZBBwLD9bHLY6lCIT4JEdDXKZrQ9 NPIYhEDfCIJl4yS982Q76SwqEkCYG84f0Egez66ADuazCjqGWkrI6EBzOeDvgV26 wdfekcU/Wx3LcFDBnd8clMG/MdmxxQu7c915Uv23DejD0QWVUlimFSTfWI8v59k= =htC/ -END PGP SIGNATURE- -- John David Anglin dave.ang...@bell.net -- 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/blu0-smtp4079aa5b84535dc5ec3a7397...@phx.gbl
Re: Roll call for porters of architectures in sid and testing (Status update)
Hi, I'm a long-time ia64 Debian user (> 10 years). I'm mostly focused on desktop aspects (GNOME, Iceweasel, LibreOffice, Qt Creator, C++ 3D software development) while most other ia64 users that I know are more inclined on server use. I'm not a DD/DM, but daily update my ia64 workstation, report bugs and do my best to provide useful information in order to get them fixed. I've also provided a couple of kernel patches in the past. I'm cross testing with Gentoo to ensure that bugs I report are Debian-specific or ia64-generic. I'll continue testing/software development activity on ia64 for the Jessie cycle, and more generally, until Debian drops ia64. I'm already waiting for Wayland on ia64 and other big updates. So please, keep ia64 in the bandwagon ;-) Émeric 2013/9/20 Lennart Sorensen : > On Fri, Sep 20, 2013 at 11:19:24AM -0400, Federico Sologuren wrote: >> i have a HP Visualize B2000 that i managed to install last night from iso >> distribution that i found after a lot of looking. at this point only >> terminal is working. will keep reading to get debian up and running. >> >> i would like to get involved. will need some additional information on what >> is needed and what skills are required. what does DD/DM stand for? > > DD = Debian Developer > DM = Debian Maintainer > > unless I remember wrong of course. :) > > -- > Len Sorensen > > > -- > To UNSUBSCRIBE, email to debian-ia64-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20130920181059.gj13...@csclub.uwaterloo.ca > -- 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/caa9xbm7xvu5xd4vz1a7h9ccqp0+k+k6k3ondty3rqnp_oex...@mail.gmail.com
Consolidating armhf installer flavours
With the current trunk/experimental 3.11 kernel the separate omap5, mx5 and vexpress flavours have been removed in favour of the armmp flavour which supports all of those. So I think we need to switch the installer over too. Since the 3.10 kernel already has the armmp flavour I don't think we even need wait for 3.11 to be uploaded. I merged the existing mx5 and vexpress mediums so armmp creates all of netboot network-console netboot-gtk. I also retained the efikamx uImage stuff (but using the new kernel) since I guess it is useful? Should we have more of those uImage things for other armmp supported platforms? Ian. commit 7de47649d4f47225f740d262de8d51c83be73688 Author: Ian Campbell Date: Mon Aug 26 11:25:56 2013 +0100 Switch armhf to armmp kernel. The other flavours have been removed in the 3.11 kernel, even in 3.10 the armmp flavour supports mx5 and vexpress. Merge all of the subtypes over. diff --git a/build/config/armhf.cfg b/build/config/armhf.cfg index 73b8a80..0287ef2 100644 --- a/build/config/armhf.cfg +++ b/build/config/armhf.cfg @@ -1,4 +1,4 @@ -SUBARCH_SUPPORTED = mx5 vexpress +SUBARCH_SUPPORTED = armmp MKLIBS = mklibs --ldlib=/lib/ld-linux-armhf.so.3 diff --git a/build/config/armhf/mx5.cfg b/build/config/armhf/armmp.cfg similarity index 69% rename from build/config/armhf/mx5.cfg rename to build/config/armhf/armmp.cfg index a30c0a2..dd24206 100644 --- a/build/config/armhf/mx5.cfg +++ b/build/config/armhf/armmp.cfg @@ -1,4 +1,4 @@ MEDIUM_SUPPORTED = netboot network-console netboot-gtk # The version of the kernel to use. -KERNELVERSION := $(KERNELVERSION)-mx5 +KERNELVERSION := $(KERNELVERSION)-armmp diff --git a/build/config/armhf/mx5/netboot-gtk.cfg b/build/config/armhf/armmp/netboot-gtk.cfg similarity index 81% rename from build/config/armhf/mx5/netboot-gtk.cfg rename to build/config/armhf/armmp/netboot-gtk.cfg index cb0b074..3817048 100644 --- a/build/config/armhf/mx5/netboot-gtk.cfg +++ b/build/config/armhf/armmp/netboot-gtk.cfg @@ -1,6 +1,6 @@ MEDIA_TYPE = netboot image -TARGET = $(TEMP_INITRD) $(TEMP_KERNEL) efikamx +TARGET = $(INITRD) $(KERNEL) efikamx TYPE = netboot/gtk EXTRANAME = netboot/gtk/ @@ -16,8 +16,8 @@ EXTRAUDEBS += cdebconf-gtk-entropy efikamx: mkdir -p $(SOME_DEST)/$(EXTRANAME)/efikamx install -m 744 boot/arm/bootscr.mx5 $(SOME_DEST)/$(EXTRANAME)/efikamx/bootscript - mkimage -A arm -O linux -T kernel -C none -a 0x90008000 -e 0x90008000 -n "Debian kernel" -d $(TEMP_KERNEL) $(SOME_DEST)/$(EXTRANAME)/efikamx/uImage - mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n "debian-installer ramdisk" -d $(TEMP_INITRD) $(SOME_DEST)/$(EXTRANAME)/efikamx/uInitrd + mkimage -A arm -O linux -T kernel -C none -a 0x90008000 -e 0x90008000 -n "Debian kernel" -d $(KERNEL) $(SOME_DEST)/$(EXTRANAME)/efikamx/uImage + mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n "debian-installer ramdisk" -d $(INITRD) $(SOME_DEST)/$(EXTRANAME)/efikamx/uInitrd mkimage -A arm -O linux -a 0 -e 0 -T script -C none -n "Efika MX Boot Script" -d $(SOME_DEST)/$(EXTRANAME)/efikamx/bootscript $(SOME_DEST)/$(EXTRANAME)/efikamx/boot.scr update-manifest $(SOME_DEST)/$(EXTRANAME)/efikamx/uImage "Linux kernel for Efika MX" update-manifest $(SOME_DEST)/$(EXTRANAME)/efikamx/uInitrd "initrd for Efika MX" diff --git a/build/config/armhf/mx5/netboot.cfg b/build/config/armhf/armmp/netboot.cfg similarity index 77% rename from build/config/armhf/mx5/netboot.cfg rename to build/config/armhf/armmp/netboot.cfg index 2456c93..e6886ba 100644 --- a/build/config/armhf/mx5/netboot.cfg +++ b/build/config/armhf/armmp/netboot.cfg @@ -1,7 +1,7 @@ MEDIA_TYPE = netboot image -TARGET = $(TEMP_INITRD) $(TEMP_KERNEL) efikamx -EXTRANAME = $(MEDIUM) +TARGET = $(INITRD) $(KERNEL) efikamx +EXTRANAME = $(MEDIUM)/ MANIFEST-INITRD = "netboot initrd" MANIFEST-KERNEL = "kernel image to netboot" @@ -10,8 +10,8 @@ MANIFEST-KERNEL = "kernel image to netboot" efikamx: mkdir -p $(SOME_DEST)/$(EXTRANAME)/efikamx install -m 744 boot/arm/bootscr.mx5 $(SOME_DEST)/$(EXTRANAME)/efikamx/bootscript - mkimage -A arm -O linux -T kernel -C none -a 0x90008000 -e 0x90008000 -n "Debian kernel" -d $(TEMP_KERNEL) $(SOME_DEST)/$(EXTRANAME)/efikamx/uImage - mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n "debian-installer ramdisk" -d $(TEMP_INITRD) $(SOME_DEST)/$(EXTRANAME)/efikamx/uInitrd + mkimage -A arm -O linux -T kernel -C none -a 0x90008000 -e 0x90008000 -n "Debian kernel" -d $(KERNEL) $(SOME_DEST)/$(EXTRANAME)/efikamx/uImage + mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n "debian-installer ramdisk" -d $(INITRD) $(SOME_DEST)/$(EXTRANAME)/efikamx/uInitrd mkimage -A arm -O linux -a 0 -e 0 -T script -C none -n "Efika MX Boot Script" -d $(SOME_DEST)/$(EXTRANAME)/efikamx/bootscript $(SOME_DEST)/$(EXTRANAME)/efikamx/boot.scr update-manifes
Re: Sheevaplug hangs after u-boot upgrade
* Björn Wetterbom [2013-09-20 18:24]: > So, it would be helpful to add to the upgrade instructions that the > bootargs are reset on upgrade and that they have to be set again according Oh yes, that's a good point. If you upgrade from an ancient version of u-boot, your u-boot environment will be destroyed. This would explain why the wrong kernel is being loaded. -- Martin Michlmayr http://www.cyrius.com/ -- 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/20130921124557.ga8...@jirafa.cyrius.com
Re: Sheevaplug hangs after u-boot upgrade
* willem de jong [2013-09-20 18:18]: > (Re)start USB... > USB: Register 10011 NbrPorts 1 > USB EHCI 1.00 > scanning bus for devices... 2 USB Device(s) found >scanning bus for storage devices... EHCI timed out on TD - > token=0x2008d80 > 1 Storage Device(s) found > > Reset IDE: ide_preinit failed > ## Booting kernel from Legacy Image at 0640 ... >Image Name: Linux-2.6.22.18 >Image Type: ARM Linux Kernel Image (uncompressed) >Data Size:2106696 Bytes = 2 MiB >Load Address: 8000 >Entry Point: 8000 >Verifying Checksum ... OK >Loading Kernel Image ... OK > OK > Uncompressing > Linux > done, booting the kernel. The reason the kernel doesn't boot is because Linux-2.6.22.18 is not compatible with your current u-boot settings. There are two styles of kernels for the SheevaPlug: the old style kernels originally shipped with the SheevaPlug which use one machine id; and the new style which use a different machine id. The u-boot you're using uses the new machine id, so old kernels won't boot. The real question is why you're booting Linux-2.6.22.18 rather than the Debian kernel. What are your u-boot settings? I also see a "time out" error in your u-boot log, so I'm wondering if the Debian kernel fails to load because of that (but I don't see an error message for that) and then it fails back to the old kernel in flash. -- Martin Michlmayr http://www.cyrius.com/ -- 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/20130921122506.gd8...@jirafa.cyrius.com
