Date: Tue, 24 May 2016 14:35:21 -0700 From: Mark Millard <markmi@dsl-only.net> To: freebsd-arm <freebsd-arm@freebsd.org>, otacilio.neto@bsd.com.br Cc: Ian Lepore <ian@FreeBSD.org> Subject: Re: xorg broken on Beaglebone black revision 300438 Message-ID: <AE62E2F1-1D9F-418F-97E8-6D7F0E6B4B87@dsl-only.net>
index | next in thread | raw e-mail
Quoting from Otacílio Tue May 24 00:06:10 UTC 2016 and its locore-v6.S changes: > - orr r7, #CPU_CONTROL_UNAL_ENABLE > - orr r7, #CPU_CONTROL_AFLT_ENABLE > + bic r7, #CPU_CONTROL_UNAL_ENABLE > + bic r7, #CPU_CONTROL_AFLT_ENABLE -r295256 (2016-Feb-14) changed from: bic r7, #CPU_CONTROL_UNAL_ENABLE to: orr r7, #CPU_CONTROL_UNAL_ENABLE in two places (moving it a few lines down for each example as well). So this much of the proposed changes would be reverting the -r295256 change. The check in comment indicates the bit is RAO/SBOP for armv7. For armv6 the check in comment claims it controls armv5 compatible alignment support. But: orr r7, #CPU_CONTROL_AFLT_ENABLE has been in locore-v6.S since the file's first checkin. So this change to bic here be new. What is the FreeBSD intent for each of the two new settings for armv7? armv6? === Mark Millard markmi@dsl-only.nethelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE62E2F1-1D9F-418F-97E8-6D7F0E6B4B87>