Date: Wed, 13 Apr 2016 08:41:24 -0600 From: Ian Lepore <ian@freebsd.org> To: Michael Tuexen <tuexen@fh-muenster.de> Cc: freebsd-arm@freebsd.org Subject: Re: No usable event timer found on RPI2 Message-ID: <1460558484.52955.21.camel@freebsd.org> In-Reply-To: <E8CC4FAA-CD1E-4082-B833-F4D6F558882A@fh-muenster.de> References: <20160409020229.GF71221@www.zefox.net> <CAFHCsPWMqtnOtMRZ9CiL%2B2_1Ox_d_Mh=LdoGMGRHBjZVd12HfA@mail.gmail.com> <20160409164903.GG71221@www.zefox.net> <1460220814.1091.338.camel@freebsd.org> <20160409181716.GH71221@www.zefox.net> <1460240966.1091.340.camel@freebsd.org> <E8CC4FAA-CD1E-4082-B833-F4D6F558882A@fh-muenster.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2016-04-13 at 16:34 +0200, Michael Tuexen wrote: > > On 10 Apr 2016, at 00:29, Ian Lepore <ian@FreeBSD.org> 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). -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1460558484.52955.21.camel>