Date: Mon, 11 Aug 2014 15:17:17 -0700 From: Thomas Skibo <ThomasSkibo@sbcglobal.net> To: Ian Lepore <ian@FreeBSD.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: And now for the actual test... [was: Re: What platform do you use?] Message-ID: <53E940ED.9060508@sbcglobal.net> In-Reply-To: <1407724644.56408.469.camel@revolution.hippie.lan> References: <7EC2AB25-5949-40BF-A5AA-BF4C98F3F640@bsdimp.com> <1407724644.56408.469.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/10/2014 07:37 PM, Ian Lepore wrote: > On Tue, 2014-08-05 at 10:26 -0600, Warner Losh wrote: >> Greetings, >> >> I˙d like to know what platforms people use FreeBSD/arm with, and if you˙d have time to test some potentially ´break the kernelˇ sort of changes in the next month? >> >> I have the following boards: boatloads of atmel, BBB, and RPI. This covers the at91, imx6 and broadcom directories. I also have a allwinnner board, but I˙ve never got it booting FreeBSD. Likewise with a rockchip. I have some marvell gear too, but it is buried deep. This leaves a lot of other boards/SoCs to cover... >> >> Warner >> > > So, anybody wanting to do the testing alluded to in this thread-starting > message, here's all you need to do: > > - Add "option ARM_DEVICE_MULTIPASS" to your kernel config. > - Rebuild and install the kernel, boot. > - Everything should still work. > > The only difference you should notice is that devices load in a > different order at boot time. Specifically, you'll see all the busses > listed first, then interrupt controllers, then l2cache, then clocks and > timers, then all the usual stuff after that. > > There's no immediate benefit or speedup or anything, this is to help > pave the way for using fdt data that comes with a board or system > instead of needing our special freebsd dtb files. Right now we count on > devices loading in the order we list them in our dts source. This is a > new way of loading things that should ensure critical devices are loaded > first, even when we can't control the order of things in the fdt data. > > I've tested this on wandboard only so far. > > -- Ian > It works on the Zedboard. I diffed the before and after boot messages and noticed the driver messages changed order slightly. devinfo -v returns the exact same output as before. --Thomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53E940ED.9060508>