From owner-freebsd-arm@freebsd.org Tue Dec 15 17:26:23 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E275A48AF2 for ; Tue, 15 Dec 2015 17:26:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 800F417B2 for ; Tue, 15 Dec 2015 17:26:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Tue, 15 Dec 2015 17:26:30 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id tBFHQLWs021145; Tue, 15 Dec 2015 10:26:21 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1450200381.25138.54.camel@freebsd.org> Subject: Re: Updating / keeping current strategies? From: Ian Lepore To: Karl Denninger , "freebsd-arm@freebsd.org" Date: Tue, 15 Dec 2015 10:26:21 -0700 In-Reply-To: <567048CF.1000803@denninger.net> References: <5666F37C.4060908@denninger.net> <10BBDDBB-75AA-4034-B494-9EB28D009882@gromit.dlib.vt.edu> <566EEAC4.1060306@denninger.net> <566F0238.9060605@denninger.net> <1450190791.25138.30.camel@freebsd.org> <567031C9.2090109@denninger.net> <1450195123.25138.42.camel@freebsd.org> <56703E2D.8050504@denninger.net> <1450198950.25138.50.camel@freebsd.org> <567048CF.1000803@denninger.net> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2015 17:26:23 -0000 On Tue, 2015-12-15 at 11:07 -0600, Karl Denninger wrote: > [...] > > This is turning into a production .vs. development issue here in that > I'm working on a home automation package that I intend to distribute > and > will run under FreeBSD on the Pi2. It's working extremely well and > will > bring down the price-point of such things in a big way (because the > hardware is so cheap) while allowing all sorts of interesting things > (like direct measurement analog inputs and relay-switched outputs.) > > But to do this and make it workable I have to be able to update a > number > of these machines consistently and, since -CURRENT is not really > recommended for any sort of production anything (and -STABLE won't > run > on the Pi2) I am stuck with "gotta find a way to get 'stable enough' > code" that I can point people at and is able to be reproduced "on > demand." > I can't think of any reason why rpi2 couldn't work on 10-stable other than nobody has MFC'd the changes needed to make that happen, and the only reason for that might be because nobody has asked for it. (I don't have rpi2 hardware myself to test anything.) There is no g'tee it would work or be more stable on 10 at this point though (the ARM_NEW_PMAP code that has been in place on 11 for about a year isn't present on 10, so rpi2 has never been tested with the old code). -- Ian