From owner-freebsd-arm@freebsd.org Sat Apr 9 16:53:37 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 7DBDFB099AD for ; Sat, 9 Apr 2016 16:53:37 +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 452E9176B for ; Sat, 9 Apr 2016 16:53:37 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: aaba9e67-fe73-11e5-b278-7d22021d92d7 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Sat, 9 Apr 2016 16:54:04 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u39GrZke009422; Sat, 9 Apr 2016 10:53:35 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1460220814.1091.338.camel@freebsd.org> Subject: Re: No usable event timer found on RPI2 From: Ian Lepore To: bob prohaska , Svatopluk Kraus Cc: "freebsd-arm@freebsd.org" Date: Sat, 09 Apr 2016 10:53:34 -0600 In-Reply-To: <20160409164903.GG71221@www.zefox.net> References: <20160409020229.GF71221@www.zefox.net> <20160409164903.GG71221@www.zefox.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.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2016 16:53:37 -0000 On Sat, 2016-04-09 at 09:49 -0700, bob prohaska wrote: > On Sat, Apr 09, 2016 at 10:59:33AM +0200, Svatopluk Kraus wrote: > > On Sat, Apr 9, 2016 at 4:02 AM, bob prohaska > > wrote: > > > generic_timer0: irq 10000,10001,10002,10003 > > > on ofwbus0 > > > generic_timer0: Unable to alloc int resource. > > > device_attach: generic_timer0 attach returned 6 > > > generic_timer0: irq 10000,10001,10002,10003 > > > on ofwbus0 > > > device_attach: generic_timer0 attach returned 6 > > > > > > The problem is here. Recently, bcm283x interrupt controllers were > > reworked for new interrupt framework and enabled by default. As I > > don't see that local_intc is attached in your dmesg, you use stale > > dts > > (dtb) files. My rpi2 dmesg looks this way: > > > > Dts seems to be a part of u-boot. > > The version of u-boot installed is a year old, but updating ports > suggests > that it hasn't changed. What am I missing? Apologies if it's a lot! > > Thank you! > > bob prohaska The rpi.dtb file lives on the FAT partition where u-boot is, but it's created by the freebsd build process and installing the kernel puts the new dtb into /boot/dtb on the freebsd rootfs. Something else (crochet or some similar script, or you by hand) have to copy from there to the FAT partition on the sdcard. Note that right now all of this is unique to rpi. For other arm boards, u-boot isn't involved in the dtb file loading at all and the file is normally read by ubldr from the freebsd filesystem. There may come a day when all arm boards have to work more like rpi does now (due to the way the u-boot world is evolving). -- Ian