summaryrefslogtreecommitdiff
path: root/target/linux
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2017-02-07 18:11:17 +0100
committerRafał Miłecki <rafal@milecki.pl>2017-03-03 11:39:49 +0100
commit0c05cadeb775f83fa40fbdd13941a5e7396505f5 (patch)
tree22eb26812ab3ce5f786506fb29dd1ce25f8d95b0 /target/linux
parentf4fc12f0230b9c99b4140a1b4700d42010b86609 (diff)
downloadmtk-20170518-0c05cadeb775f83fa40fbdd13941a5e7396505f5.zip
mtk-20170518-0c05cadeb775f83fa40fbdd13941a5e7396505f5.tar.gz
mtk-20170518-0c05cadeb775f83fa40fbdd13941a5e7396505f5.tar.bz2
bcm53xx: include Broadcom PHY driver in the kernel
Initial idea was to use package with this PHY driver for devices that need it. Unfortunately this can't work as bgmac is built-in and PHY probing happens before loading modules - it results in PHY subsystem picking default (generic) PHY driver. There were two ways of solving this: 1) Making bcm53xx use bgmac as module xor 2) Built-in Broadcom PHY driver After some quick discussion it seems we can simply built-in the driver as increased kenel size is relatively small (1805 B). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Diffstat (limited to 'target/linux')
-rw-r--r--target/linux/bcm53xx/config-4.42
1 files changed, 2 insertions, 0 deletions
diff --git a/target/linux/bcm53xx/config-4.4 b/target/linux/bcm53xx/config-4.4
index bde8be9..723d16a 100644
--- a/target/linux/bcm53xx/config-4.4
+++ b/target/linux/bcm53xx/config-4.4
@@ -70,10 +70,12 @@ CONFIG_BCMA_HOST_PCI=y
CONFIG_BCMA_HOST_PCI_POSSIBLE=y
CONFIG_BCMA_HOST_SOC=y
CONFIG_BCMA_SFLASH=y
+CONFIG_BCM_NET_PHYLIB=y
CONFIG_BGMAC=y
CONFIG_BGMAC_BCMA=y
# CONFIG_BGMAC_PLATFORM is not set
CONFIG_BOUNCE=y
+CONFIG_BROADCOM_PHY=y
CONFIG_CACHE_L2X0=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_CLKDEV_LOOKUP=y