From owner-freebsd-mips@FreeBSD.ORG Sat Feb 8 14:44:41 2014 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27236A45 for ; Sat, 8 Feb 2014 14:44:41 +0000 (UTC) Received: from mail.lhr1.as41113.net (mail.lhr1.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id DB90E11EA for ; Sat, 8 Feb 2014 14:44:40 +0000 (UTC) Received: from [10.193.246.16] (unknown [91.208.177.186]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.lhr1.as41113.net (Postfix) with ESMTPS id 3fLwvX2yz0z7vXM for ; Sat, 8 Feb 2014 14:37:28 +0000 (UTC) Message-ID: <52F64128.7010000@rewt.org.uk> Date: Sat, 08 Feb 2014 14:37:28 +0000 From: Joe Holden User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-mips@freebsd.org Subject: Re: FreeBSD 10.0 image and build script for EdgeRouter Lite References: <20140125210308.GA6936@rtfm.net> <52EE7183.1070806@pix.net> <20140205190456.GA15313@plebeian.afflictions.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Feb 2014 14:44:41 -0000 On 08/02/2014 00:23, Juli Mallett wrote: > On Fri, Feb 7, 2014 at 4:20 PM, Outback Dingo wrote: > >> On Wed, Feb 5, 2014 at 2:04 PM, Damian Gerow >> wrote: >> >>> Nathan Dorfman wrote: >>>>> Looking at the '/var/log/dmesg' from one of these running the linux >>>>> system, I didn't see anything related to a RTC/TOD clock, but I might >>>>> have just missed it in my quick scan of the devices. >>>> >>>> I don't think there is a hardware clock on the device, though I could >>>> be wrong. >>> >>> There doesn't appear to be one. 'hwclock' can't find a clock at >>> /dev/rtc0?, >>> and there's nothing in the dmesg relating to any form of hardware clock. >>> >>> As well, looking at the board, there's no battery present. So even if >>> there >>> was a clock, it would be reset anytime the board lost power. >>> >>>> I bet the vendor firmware has NTP on by default, though. >>> >>> They do, using n.ubnt.pool.ntp.org. >>> >> >> i see this is working on the edgerouter lite version, any chance it will >> also work on the pro version??? > > > The most likely scenario is that very minor changes will be required to > support the additional model, possibly as little as just recognizing its > model identifier. > > Juli.... IIRC the bigger variants are Octeon II with hardware switches (likely marvell/broadcom) - what are the chances of getting support for either given the NDA requirements?