On Sun, Feb 16, 2014 at 6:37 PM, peter green <plugw...@p10link.net> wrote: > Reinhard Tartler wrote: >> >> Dear ARM porters, >> >> Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738981 >> for full context. I've uploaded a patch proposed by Riku that AFAIUI >> makes mpg123 really slow on all arm targets, while unbreaking it on >> some others. >> >> As one of the maintainers of the mpg123 without familiarity about the >> scope of the Debian arm port > > Debian has TWO official arm ports. > > Armel has a minimum CPU requirement of armv4t with no gaurantee that there > will be any floating point hardware at all. > Armhf has a minimum CPU requirement of armv7-a with vfpv3-d16, neon is not > gauranteed to be available (but it is very likely to be in pratice). > > As well as the two official arm ports there is also Raspbian which targets > armv6 with vfpv2, raspbian also uses the armhf architecture name but can be > distinguished by using dpkg-vendor.
With this explanation, I think it would help a lot to all armhf users if the following line was restricted to the armel port: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/mpg123.git;a=blob;f=debian/rules;h=afb018502621352914e757338a2dace6b65522cb;hb=HEAD#l25 Does anyone disagree that this is a good move, at least until something like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738981#25 is implemented? -- regards, Reinhard _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers