Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-21 Thread Christoph Biedl
[ Sorry, that fell off screen ] Roger Shimizu wrote... > [CC Vagrant, u-boot pkg maintainer] > > On Sat, Dec 10, 2016 at 11:31 PM, Christoph Biedl > wrote: > > Paul Wise wrote... > >> > >> Is it possible to put a bootloader like u-boot in the flash partitions > >> and have it load the Linux ker

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-20 Thread Christoph Biedl
Lennart Sorensen wrote... > I actually highly doubt there are that many armv7 boxes running armel. > armhf was a nice performance improvement and worth the hassle to reinstall > if you had such a box in the first place. I think most armel systems > are probably armv5, often the marvell chips. No

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-20 Thread Wouter Verhelst
On Sat, Dec 17, 2016 at 08:15:15PM +0800, Paul Wise wrote: > On Sat, 2016-12-17 at 09:45 +0100, Wouter Verhelst wrote: > > > Yes, but that still says: > > Ack. > > > I think a proper procedure should involve a script that: > > > > - is packaged in Debian; > > Ack. > > > - checks whether the h

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-18 Thread Paul Wise
On Sun, Dec 18, 2016 at 11:22 PM, Roger Shimizu wrote: > Is there any way to simplify? Remove the obsolete armel binaries where they occur and then mark the packages as NFU on armel: https://wiki.debian.org/ftpmaster_Removals https://wiki.debian.org/PackagesArchSpecific -- bye, pabs https://w

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-18 Thread Roger Shimizu
On Sat, Dec 10, 2016 at 12:22 PM, Wookey wrote: > > We can do poor-mans partial arch by just being fairly agressive about > disabling armel for packages that are broken or not suitable. Not very > clever or efficient, but it is easy to do and requires no infra or > tooling changes at all. So long

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-17 Thread Paul Wise
On Sat, 2016-12-17 at 09:45 +0100, Wouter Verhelst wrote: > Yes, but that still says: Ack. > I think a proper procedure should involve a script that: > > - is packaged in Debian; Ack. > - checks whether the hardware it's running on has all the hardware >   requirements for the new architectur

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-17 Thread Wouter Verhelst
On Thu, Dec 15, 2016 at 11:19:34AM +0800, Paul Wise wrote: > On Thu, Dec 15, 2016 at 1:40 AM, Wouter Verhelst wrote: > > > One way in which the need to keep armel around would be reduced is if we > > could somehow upgrade from armel machines to armhf ones, without > > requiring a reinstall. > > T

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-16 Thread Vagrant Cascadian
On 2016-12-16, Roger Shimizu wrote: > On Sat, Dec 10, 2016 at 11:31 PM, Christoph Biedl > wrote: >>> Is it possible to put a bootloader like u-boot in the flash partitions >>> and have it load the Linux kernel and initrd from elsewhere? There's no technical reason this wouldn't be possible, just

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-16 Thread Roger Shimizu
[CC Vagrant, u-boot pkg maintainer] On Sat, Dec 10, 2016 at 11:31 PM, Christoph Biedl wrote: > Paul Wise wrote... >> >> Is it possible to put a bootloader like u-boot in the flash partitions >> and have it load the Linux kernel and initrd from elsewhere? > > That how I've been running my Dockstar

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-14 Thread Paul Wise
On Thu, Dec 15, 2016 at 1:40 AM, Wouter Verhelst wrote: > One way in which the need to keep armel around would be reduced is if we > could somehow upgrade from armel machines to armhf ones, without > requiring a reinstall. There is a script for that here: https://wiki.debian.org/CrossGrading --

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-14 Thread Wouter Verhelst
On Wed, Dec 07, 2016 at 08:50:40PM +0900, Roger Shimizu wrote: [...asking for armel to be retained...] One way in which the need to keep armel around would be reduced is if we could somehow upgrade from armel machines to armhf ones, without requiring a reinstall. After all, armel has been around

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-14 Thread Lennart Sorensen
On Wed, Dec 14, 2016 at 06:40:22PM +0100, Wouter Verhelst wrote: > On Wed, Dec 07, 2016 at 08:50:40PM +0900, Roger Shimizu wrote: > [...asking for armel to be retained...] > > One way in which the need to keep armel around would be reduced is if we > could somehow upgrade from armel machines to ar

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-13 Thread Kurt Roeckx
On Wed, Dec 07, 2016 at 03:53:31PM +, Steve McIntyre wrote: > AFAIK there are potentially still similar problems with ARMv5 - lack > of architcture-defined barrier primitives for C++11 atomics to > work. (I'd love to be corrected on this if people know better!) This > is one of the key points h

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-12 Thread Timo Jyrinki
2016-12-09 0:12 GMT+02:00 Christoph Biedl : > Same here. My Dockstars (orion5x/kirkwood) still work like a charm and > it gives a bad feeling having to trash them some day just because > there's no support any more. > > On the other hand, they face another problem I guess is typical for > that gene

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-09 Thread Wookey
On 2016-12-07 15:53 +, Steve McIntyre wrote: > On Wed, Dec 07, 2016 at 08:50:40PM +0900, Roger Shimizu wrote: > >I'm ARM porter on armel/marvell (orion5x/kirkwood). > >Stretch will be frozen and released soon, which makes me bit depressed, > >because it means armel will be dropped out of unst

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-09 Thread Ben Hutchings
On Fri, 2016-12-09 at 22:14 +0900, Roger Shimizu wrote: > On Fri, 09 Dec 2016 00:53:17 + > > Ben Hutchings wrote: > > > Also, dedicated tiny flash partitions for the kernel and initrd.  I > > wouldn't be surprised to be find that by the time we want to release > > buster we can't build a usef

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-09 Thread Roger Shimizu
On Fri, 09 Dec 2016 00:53:17 + Ben Hutchings wrote: > Also, dedicated tiny flash partitions for the kernel and initrd. I > wouldn't be surprised to be find that by the time we want to release > buster we can't build a useful kernel that fits into the 2 MB partition > that most of these devic

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-08 Thread Christoph Biedl
Roger Shimizu wrote... > I'm ARM porter on armel/marvell (orion5x/kirkwood). > Stretch will be frozen and released soon, which makes me bit depressed, > because it means armel will be dropped out of unstable/testing as the > conclusion of Cape Town BoF. Same here. My Dockstars (orion5x/kirkwood

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-07 Thread Steve McIntyre
On Wed, Dec 07, 2016 at 08:50:40PM +0900, Roger Shimizu wrote: >[ intentionally keep d-d CCed ] > >On Fri, 22 Jul 2016 02:36:05 +0100 >Steve McIntyre wrote: > >> [ Please note the cross-post and Reply-To ] >> >> Hi folks, >> >> As promised, here's a quick summary of what was discussed at the ARM

armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-07 Thread Roger Shimizu
[ intentionally keep d-d CCed ] On Fri, 22 Jul 2016 02:36:05 +0100 Steve McIntyre wrote: > [ Please note the cross-post and Reply-To ] > > Hi folks, > > As promised, here's a quick summary of what was discussed at the ARM > ports BoF session in Cape Town. Thanks for the summary! I'm ARM port