This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5K2E0x: separate network interfaces on K2E

Hi,

I have studied the MCSDK user guide and specifically the network driver. K2E has multiple SGMII ports on an internal ethernet switch. Can the switch be configured sort of in "bypass" mode so that each SGMII port can become an individual network interface from the Linux kernel standpoint, like eth0, eth1, eth2, ...?

It would be great if this could be done without VLAN IDs.

Please let me know.

 

Thanks,

--Gunter

 

  • Hi, Gunter,

    Don't quite get your question. Current Linux kernel already supports 8 ethernet ports on K2E, eth0 through eth7. Doesn't this satisfy what you want?

    Rex

  • Hello -- I am replying to help clarify what we are intending to do with the K2E.

    We will have eth0, eth2, eth3 and eth4 attached to the K2E (sgmii forced link interfaces).

    What we need to do is ensure that the K2E "switch" does not "flood", "bcast", or "switch based on mac da lookup" to any of the other interfaces. We want to lock in a 1:1 releationship of ethX to/from CPU.

    In a sense, we want to disable the "switch" aspect or at least ensure that eth0 only goes to and from the CPU.
    Likewise, eth2, eth3 and eth4 would only flow from the interface to the CPU without the possibility of flooding frames out an adjacent interface.

    Hope this helps to clarify, Thanks !

    Andy
  • Hi, Andy,

    The kernel default configuration has each prot being separated. The switch function is disabled and ALE bypass is enabled.

    Rex