summaryrefslogtreecommitdiffstats
path: root/sys/boot
diff options
context:
space:
mode:
authorgrehan <grehan@FreeBSD.org>2005-11-07 06:55:48 +0000
committergrehan <grehan@FreeBSD.org>2005-11-07 06:55:48 +0000
commit0a9e3aee3535cf3561f560600680c21b8b9ce8d8 (patch)
tree1cdb8a3ccd2c4fbd27983332d76ebd15712b9122 /sys/boot
parent5ae83a3b6a9bfa94da179b38c43a4c8c64267994 (diff)
downloadFreeBSD-src-0a9e3aee3535cf3561f560600680c21b8b9ce8d8.zip
FreeBSD-src-0a9e3aee3535cf3561f560600680c21b8b9ce8d8.tar.gz
Finally (!?) get to the bottom of the mysterious G3 boot-time panics.
After a number of tests using nop's to change the alignment, it was confirmed that the mtibat instructions should be cache-aligned. FreeScale app note AN2540 indicates that the isync before and after the mtdbat is the right thing to do, but sync/isync isn't required before the mtibat so it has been removed. Fix by using a ".balign 32" to pull the code in question to the correct alignment. MFC after: 3 days
Diffstat (limited to 'sys/boot')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud