Hi,
A couple of simple patches to generate the random mac address
if none is found. And enabling the driver for mips.
Based on v4.8-rc4.
These were part of a larger series but that series is growing
wildly. Splitting and submitting the net subsystem patches separately.
Hence the v5.
Regards,
ZubairLK
Zubair Lutfullah Kakakhel (2):
net: ethernet: xilinx: Generate random mac if none found
net: ethernet: xilinx: Enable emaclite for MIPS
drivers/net/ethernet/xilinx/Kconfig | 4 ++--
drivers/net/ethernet/xilinx/xilinx_emaclite.c | 8 +++++---
2 files changed, 7 insertions(+), 5 deletions(-)
--
1.9.1
At the moment, if the emaclite device doesn't find a mac address
from any source, it simply uses 0x0 with a warning printed.
Instead of using a 0x0 mac address, use a randomly generated one.
Signed-off-by: Zubair Lutfullah Kakakhel <redacted>
---
V3 -> V4
Curly braces after if check for correct styling
V2 -> V3
No change
V1 -> V2
New patch
---
drivers/net/ethernet/xilinx/xilinx_emaclite.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
@@ -1131,11 +1131,13 @@ static int xemaclite_of_probe(struct platform_device *ofdev)lp->rx_ping_pong=get_bool(ofdev,"xlnx,rx-ping-pong");mac_address=of_get_mac_address(ofdev->dev.of_node);-if(mac_address)+if(mac_address){/* Set the MAC address. */memcpy(ndev->dev_addr,mac_address,ETH_ALEN);-else-dev_warn(dev,"No MAC address found\n");+}else{+dev_warn(dev,"No MAC address found. Generating Random one\n");+eth_hw_addr_random(ndev);+}/* Clear the Tx CSR's in case this is a restart */__raw_writel(0,lp->base_addr+XEL_TSR_OFFSET);
A couple of simple patches to generate the random mac address
if none is found. And enabling the driver for mips.
Based on v4.8-rc4.
These were part of a larger series but that series is growing
wildly. Splitting and submitting the net subsystem patches separately.
Hence the v5.
A couple of simple patches to generate the random mac address
if none is found. And enabling the driver for mips.
Based on v4.8-rc4.
These were part of a larger series but that series is growing
wildly. Splitting and submitting the net subsystem patches separately.
Hence the v5.