From owner-freebsd-arm@freebsd.org Sun Apr 10 00:08:15 2016 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 4548BB0A9C8 for ; Sun, 10 Apr 2016 00:08:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0095414D6; Sun, 10 Apr 2016 00:08:14 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id u3A08Eel003515 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 10 Apr 2016 00:08:15 GMT (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id u3A08EIo003514; Sat, 9 Apr 2016 17:08:14 -0700 (PDT) (envelope-from fbsd) Date: Sat, 9 Apr 2016 17:08:13 -0700 From: bob prohaska To: Ian Lepore Cc: freebsd-arm@freebsd.org Subject: Re: No usable event timer found on RPI2 Message-ID: <20160410000813.GI71221@www.zefox.net> References: <20160409020229.GF71221@www.zefox.net> <20160409164903.GG71221@www.zefox.net> <1460220814.1091.338.camel@freebsd.org> <20160409181716.GH71221@www.zefox.net> <1460240966.1091.340.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1460240966.1091.340.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2016 00:08:15 -0000 On Sat, Apr 09, 2016 at 04:29:26PM -0600, Ian Lepore wrote: > The freebsd build process doesn't know anything about filesystems, it > just installs things to DESTDIR (which is / by default). > > If you're doing the kernel build and install native on the rpi, you > could get the effect you want by doing: > > mount -t msdosfs /dev/mmcsd0s1 /boot/dtb > make installkernel > umount /boot/dtb > Not sure I understand this; if the build/install cycle is happening in multi-user isn't it enough to just cp /boot/dtb/rpi2.dtb /boot/msdos ? bob prohaska