summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/labs.c
diff options
context:
space:
mode:
authoradrian <adrian@FreeBSD.org>2015-10-30 23:00:47 +0000
committeradrian <adrian@FreeBSD.org>2015-10-30 23:00:47 +0000
commit401d1e9afaddb14f0a2e64edb2da1d634436ac35 (patch)
tree31bda916274d46003781e0fb546bb6be5dd82715 /lib/libc/stdlib/labs.c
parentea415f2530c9870200e69a1f93ebc3f69c3cf919 (diff)
downloadFreeBSD-src-401d1e9afaddb14f0a2e64edb2da1d634436ac35.zip
FreeBSD-src-401d1e9afaddb14f0a2e64edb2da1d634436ac35.tar.gz
arge_mdio: add explicit read barriers for MDIO_READs.
The mips74k programmers guide notes that reads can be re-ordered, even uncached ones, so we need an explicit SYNC between them. Yes, this is a case of a driver author actively doing a bus barrier operation. This ends up being necessary when the mips74k core is run in write-back mode rather than write-through mode. That's coming in an upcoming commit. Tested: * mips74k, QCA9558 SoC (AP135 reference board), arge<->arge interface routing traffic tests.
Diffstat (limited to 'lib/libc/stdlib/labs.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud