From owner-freebsd-arm@freebsd.org Mon Apr 24 18:46:40 2017 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 8ED03D4D4F9 for ; Mon, 24 Apr 2017 18:46:40 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AC0E16E9 for ; Mon, 24 Apr 2017 18:46:40 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id u65so4510352wmu.1 for ; Mon, 24 Apr 2017 11:46:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=AAQ0Q2q7nsvxx/uxi7gilIaZzdDB9DkFNutWVv0SXlU=; b=UO/UqJLBwlmk1kq+6OukI+2iCO2Tv5GoSUg0dSCIY6xWEaSRG8hR1lFsxPLmWHUvlm cFhG8jnGZHjS/NAaX6SQKkIEA6mItVTq6IKf0Ejo4YlaXgjRWaxu/kS6lGwg4s+WdTy0 hQwF3VSjMn+f1ZjfkIKYTnDPZmtP0U2i316KFLghj4g/6thZ1rW8Cu2DLdZaqwzuOz4Y oB492OwM6aOeO3uqsAgZ1DQL6tKf1RPs68+/cDhvoUn/YvID/cslvUJ08y3aslCFUEhL W1Y+BFbfZakvQJXCj2KhORAJLdX44NhJx0fMxMEQ455fK+JEzrVDwS1mrfo52/F3rcVJ D9TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=AAQ0Q2q7nsvxx/uxi7gilIaZzdDB9DkFNutWVv0SXlU=; b=JtGREz3e0t2ATQefYjqEiioWCasayn/D1xx/WdjyS2Itj6QtaqRl7+4II0BVnPGbSm Cr3PvWbkemh/L65arMHAh81p6p696/3u1bYApxyjWm18XSe2kp/rVmgwzdFe4RSGDLR2 YlkMC0MQRqTJAxqkxY4GyGwKIlVSrChiCINoRMTfmca79tgzmVIRFrZONjlMZFcVBaWg cUq/T8WFdguX0fZAkKPPWNAypZGYlw3CMs2L2kVwYYt6eoLsxOxPTXN1EBCx/Rvu010G zQ+TzBX9MEgdaknAYEnpmMl9hRN8Qwo5fBrWCmfbndeg7856Xn62OCmmwGD84xrNZm8p TgAA== X-Gm-Message-State: AN3rC/52lNP0bq01WgnJG4iVSjSH4rXfU4SmY2+bcsgSpSS7UoJbajk8 C2EGOpWec2sYms8Q5qiEry9pVoY5fw== X-Received: by 10.80.181.161 with SMTP id a30mr2144015ede.85.1493059598117; Mon, 24 Apr 2017 11:46:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.148.148 with HTTP; Mon, 24 Apr 2017 11:46:37 -0700 (PDT) In-Reply-To: <463b05bf-eed5-485d-9a85-01108b08110c@Spark> References: <463b05bf-eed5-485d-9a85-01108b08110c@Spark> From: Luiz Otavio O Souza Date: Mon, 24 Apr 2017 15:46:37 -0300 Message-ID: Subject: Re: FreeBSD 12.0 Current & hardware clock To: "kronometrix.org" Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2017 18:46:40 -0000 On 24 April 2017 at 08:31, kronometrix.org wrote: > Hi, > > Im currently testing this image: FreeBSD-armv6-12.0-RPI2-310476.img.gz [1= ] > on my RBPI2. I need a hardware clock which will work with this image. Cou= ple > of questions: > > 1. If I understood right I need to recompile the kernel since there is no= hardware > clock support on the mentioned image =E2=80=A6 Right ? Yes, you have to add your RTC device and rebuild the kernel. > > 2. Is there support for Rasclock [2] based on NXP PCF2127AT chipset ? No, we only have the driver for the pcf2123 (spi only RTC), but should not be hard to add support for it. > > 3. Still there the regarding NTP and hardware clock when OS was dying on = such > setup ? (you need to enable sysctl machdep.rtc_save_period=3D0 to workaro= und) Yes, or you can use the gpioiic/gpiospi which don't use interrupts (and will not cause any issues with NTP -> RTC time updates). Luiz