From owner-freebsd-arm@FreeBSD.ORG Tue Oct 21 22:28:05 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5B3C89C8 for ; Tue, 21 Oct 2014 22:28:05 +0000 (UTC) Received: from mail.FoxValley.net (mail.FoxValley.net [64.135.192.34]) by mx1.freebsd.org (Postfix) with SMTP id 0C3FC8FA for ; Tue, 21 Oct 2014 22:28:04 +0000 (UTC) Received: (qmail 22652 invoked from network) for freebsd-arm@freebsd.org; 21 Oct 2014 17:27:58 -0500 Received: from marengo.foxvalley.net (draymond@64.135.192.25) by mail.foxvalley.net with SMTP; 21 Oct 2014 17:27:58 -0500 Received: from sp7.qualcomm.com (sp7.qualcomm.com [199.106.103.57]) by webmail.FoxValley.net (Horde MIME library) with HTTP; Tue, 21 Oct 2014 17:27:58 -0500 Message-ID: <20141021172758.2ael7skaydlwwcco@webmail.FoxValley.net> Date: Tue, 21 Oct 2014 17:27:58 -0500 From: draymond@FoxValley.net To: freebsd-arm@freebsd.org Subject: new support for Raspberry Pi B+ MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2014 22:28:05 -0000 There was a recent update to the Raspberry Pi wiki here: https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi The update is as follows: 2014-10-18: The firmware included in the official images has been updated to support B+ model. However, when I look at the ftp site that contains the binary snapshots I see no new images. The newest images are dated 2014-09-19: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/11.0 Was this an oversight or am I looking in the wrong place?