From owner-freebsd-arm@freebsd.org Wed Apr 13 15:39:01 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 E2430B0EF54 for ; Wed, 13 Apr 2016 15:39:01 +0000 (UTC) (envelope-from tuexen@fh-muenster.de) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 767D11B00; Wed, 13 Apr 2016 15:39:00 +0000 (UTC) (envelope-from tuexen@fh-muenster.de) Received: from [192.168.1.200] (p508F1437.dip0.t-ipconnect.de [80.143.20.55]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 96ED8721E280E; Wed, 13 Apr 2016 17:38:55 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: No usable event timer found on RPI2 From: Michael Tuexen In-Reply-To: <1460558484.52955.21.camel@freebsd.org> Date: Wed, 13 Apr 2016 17:38:17 +0200 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: 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> <1460558484.52955.21.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3124) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de 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: Wed, 13 Apr 2016 15:39:02 -0000 > On 13 Apr 2016, at 16:41, Ian Lepore wrote: > > On Wed, 2016-04-13 at 16:34 +0200, Michael Tuexen wrote: >>> On 10 Apr 2016, at 00:29, Ian Lepore wrote: >>> >>> On Sat, 2016-04-09 at 11:17 -0700, bob prohaska wrote: >>>> On Sat, Apr 09, 2016 at 10:53:34AM -0600, Ian Lepore wrote: >>>>> >>>>> 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). >>>>> >>>>> >>>> >>>> What inhibits making the copy to FAT part of kernel install? >>>> >>> >>> 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 >>> >>> At least, I think that should work. >> Hi Ian, >> >> I'm running into the same problem. I updated the source on a RPI2 >> today, >> build a new kernel (with modules), installed it, manually copied >> /boot/dtb/rpi2.dtb >> to /boot/msdos/ (which is mounted) and rebooted. >> The dtb files have the correct date, but the kernel panics. Do I need >> to copy more? >> >> Thanks for your help! >> > > Sorry, I don't have any particular insight into this one (I don't have > an rpi2). I was just chiming in on the previous question about the > specific issue of where the .dtb file lives and how it gets loaded (and > it turns out I was a bit wrong about that: it's actually the rpi > firmware (in the gpu) that loads the dtb file and passes it to u-boot). OK. Could it be that I need a newer version of uboot: > ls -l /boot/msdos/ total 7320 -rwxr-xr-x 1 root wheel 17900 May 8 2015 BOOTCODE.BIN -rwxr-xr-x 1 root wheel 103 May 8 2015 CONFIG.TXT -rwxr-xr-x 1 root wheel 6161 May 8 2015 FIXUP.DAT -rwxr-xr-x 1 root wheel 2366 May 8 2015 FIXUP_CD.DAT -rwxr-xr-x 1 root wheel 9214 May 8 2015 FIXUP_X.DAT -rwxr-xr-x 1 root wheel 1447 May 8 2015 LICENCE.BRO -rwxr-xr-x 1 root wheel 607 May 8 2015 README -rwxr-xr-x 1 root wheel 9153 Apr 13 14:37 RPI2.DTB -rwxr-xr-x 1 root wheel 2664088 May 8 2015 START.ELF -rwxr-xr-x 1 root wheel 567672 May 8 2015 START_CD.ELF -rwxr-xr-x 1 root wheel 3621768 May 8 2015 START_X.ELF -rwxr-xr-x 1 root wheel 301876 May 8 2015 U-BOOT.BIN -rwxr-xr-x 1 root wheel 261721 May 8 2015 UBLDR Best regards Michael > > -- Ian > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"