Date: Sun, 24 Dec 2017 17:38:07 +0700 From: Alexey Dokuchaev <danfe@nsu.ru> To: Sylvain Garrigues <sylgar@gmail.com> Cc: Warner Losh <imp@bsdimp.com>, freebsd-arm@freebsd.org Subject: Re: How to use our stock armv7-RPI2 images with QEMU? Message-ID: <20171224103807.GB98857@regency.nsu.ru> In-Reply-To: <E3F1EBB2-67E0-4B45-AE9A-55831B3FAC53@gmail.com> References: <07FDE656-3DBA-4EB6-80F5-A7E25051DB37@gmail.com> <CANCZdfqmcce%2B%2B=4dbQ07%2B7pGrryE00hfzuPeu%2BAqaa65ZBLznQ@mail.gmail.com> <E3F1EBB2-67E0-4B45-AE9A-55831B3FAC53@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 19, 2017 at 11:11:01PM +0100, Sylvain Garrigues wrote: > Le 19 d??c. 2017 ?? 22:36, Warner Losh <imp@bsdimp.com> a ??crit : > > Any chance the uboot image could be used for the kernel? > > As far as I remember, the current u-boot is stuck in an infinite loop > when run in qemu with -kernel u-boot.bin -machine raspi2, during u-boot > mmc initialization. Hmm, where does one get u-boot.bin file? I don't see it in the FreeBSD RPi2 image anywhere (expected to find under /boot). > The attached ugly patch made u-boot able to go further and recognize > partitions on the sd image attached to qemu in raspi2 configuration. Thanks, might be useful once I get acquainted with all that armish u-boot stuff and such. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171224103807.GB98857>