summaryrefslogtreecommitdiffstats
path: root/lib/libopie
diff options
context:
space:
mode:
authoryongari <yongari@FreeBSD.org>2010-08-09 01:47:09 +0000
committeryongari <yongari@FreeBSD.org>2010-08-09 01:47:09 +0000
commitf0e5a03c1591762c5e41ee125b56c09ce578e635 (patch)
tree13da83a9dfdc5e08326d52b2b44948d84cda803a /lib/libopie
parentfcb01044827f23ad69069d690a291bff2866683c (diff)
downloadFreeBSD-src-f0e5a03c1591762c5e41ee125b56c09ce578e635.zip
FreeBSD-src-f0e5a03c1591762c5e41ee125b56c09ce578e635.tar.gz
It seems some old Sundace(now IC Plus Corp.) controllers do not
like memory mapped register access. Typical problem from the issue was MII access returned unreliable values. I'm not sure this comes from lack of register flushing in MII access after accessing STE_PHYCTL register though. To address the issue, read hints data that controls which type of memory mapping should be used in driver. ste(4) still prefers memory mapping to io mapping but honor hints entered by user except for controllers that have problems with memory mapping. The hint to use iomapping could be given by adding the following line to /boot/device.hints file. hint.ste.0.prefer_iomap="1" PR: kern/149285 MFC after: 5 days
Diffstat (limited to 'lib/libopie')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud