Date: Thu, 30 Oct 2014 20:23:57 -0700 From: Rui Paulo <rpaulo@me.com> To: Daisuke Aoyama <aoyama@peach.ne.jp> Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD 11-CURRENT on Raspberry Pi 512MB Message-ID: <09F2506B-11E9-43A2-A783-784AA6E39976@me.com> In-Reply-To: <840772A7305444C1B1AF7CE31A89BD7D@ad.peach.ne.jp> References: <0A8390C3FC2B444B9AA8AC934B79DCD6@ad.peach.ne.jp> <C9E25385-E665-4895-96CE-DCC71B36FF3B@me.com> <DF85948EF6CF4FF28BA12309FEFA1B67@ad.peach.ne.jp> <7946CCA3-26D0-4B6E-AEBB-8623CAAA9725@me.com> <840772A7305444C1B1AF7CE31A89BD7D@ad.peach.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 30, 2014, at 03:35, Daisuke Aoyama <aoyama@peach.ne.jp> wrote: >=20 >> This code is now up for review at: >> https://reviews.freebsd.org/D1025 >=20 > There is some comment. >=20 > About build error: > It requires the patch of bcm2835_mbox.h in > = http://www.peach.ne.jp/archives/rpi/patch/src-r273303-20141026.patch.gz > for build dependency and the patch of bcm2835_mbox.c for run = dependency. That patch has a lot of unrelated changes. Could you produce a patch = with svn that is just related to cpufreq and its mbox changes? > Showing boot settings: > The initial values are intended to use for manual tuning via = hw.cpufreq. > Especially, using it in the turbo state ON. (force_turbo=3D1 in = config.txt before booting) > This is different from other cpufreq drivers. Okay, but why does it need to show up in the dmesg when it boots? > Writing core clock twice: > I didn't know a reason. At least, very long delay is not worked. OK. > DELAY: > It is put on various places for safety after set property. > (power consumption may change. don't want change without interval) Ok, let's just leave it like that for now. Thanks, -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?09F2506B-11E9-43A2-A783-784AA6E39976>