summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdio
diff options
context:
space:
mode:
authoryongari <yongari@FreeBSD.org>2012-05-09 01:55:23 +0000
committeryongari <yongari@FreeBSD.org>2012-05-09 01:55:23 +0000
commit62a24888237bd813997b2923ac098f311a35609b (patch)
tree6758d1c830cf49f24f615fd4f30260cd1f98fbc4 /lib/libc/stdio
parentcf039ecfbba42330c58deb861dd983ccbabde733 (diff)
downloadFreeBSD-src-62a24888237bd813997b2923ac098f311a35609b.zip
FreeBSD-src-62a24888237bd813997b2923ac098f311a35609b.tar.gz
Implement basic remote PHY support. Remote PHY allows the
controller to perform MDIO type accesses to a remote transceiver using message pages defined through MRBE(multirate backplane ethernet). It's used in blade systems(e.g Dell Blade m610) which are connected to pass-through blades rather than traditional switches. This change directly manipulates firmware's mailboxes to control remote PHY such that it does not use mii(4). Alternatively, as David said, it could be implemented in brgphy(4) by creating a fake PHY and let brgphy(4) do necessary mii accesses and bce(4) can implement mailbox accesses based on the type of brgphy(4)'s mii accesses. Personally, I think it would make brgphy(4) hard to maintain since it would have to access many bce(4) registers in brgphy(4). Given that there are users who are suffering from lack of remote PHY support, it would be better to get working system rather than waiting for complete/perfect implementation. Tested by: Jan Winter ( jan.winter <> kantarmedia dot de ) Reviewed by: davidch (initial version) MFC after: 2 weeks
Diffstat (limited to 'lib/libc/stdio')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud