Hi,
(Guy, I wrote you a separate email about that nearly 2 years ago and got
side tracked for that long on other stuff).
A number of Ethernet switches from Broadcom, Marvell, Microchip,
Qualcomm, Lantiq/Intel, etc. utilize proprietary tags that are processed
by these switches in-line with the Eth
On Jan 17, 2019, at 2:39 PM, Florian Fainelli wrote:
> A number of Ethernet switches from Broadcom, Marvell, Microchip,
> Qualcomm, Lantiq/Intel, etc. utilize proprietary tags that are processed
> by these switches in-line with the Ethernet frame being sent/received.
>
> These tags are inserted
On 1/17/19 3:41 PM, Guy Harris wrote:
> On Jan 17, 2019, at 2:39 PM, Florian Fainelli wrote:
>
>> A number of Ethernet switches from Broadcom, Marvell, Microchip,
>> Qualcomm, Lantiq/Intel, etc. utilize proprietary tags that are processed
>> by these switches in-line with the Ethernet frame being
On Jan 17, 2019, at 4:56 PM, Florian Fainelli wrote:
> These Ethernet adapters can be regular/normal Ethernet adapters, e.g:
> e1000e/igb/ixgbe on a PC connected to an Ethernet switch via GMII (for
> data path), and controlled by that PC through GPIO/SPI/I2C/MDIO for
> instance. If the switch is
Le 1/17/19 à 5:24 PM, Guy Harris a écrit :
> On Jan 17, 2019, at 4:56 PM, Florian Fainelli wrote:
>
>> These Ethernet adapters can be regular/normal Ethernet adapters, e.g:
>> e1000e/igb/ixgbe on a PC connected to an Ethernet switch via GMII (for
>> data path), and controlled by that PC through G
On Jan 17, 2019, at 6:01 PM, Florian Fainelli wrote:
> Correct. The other ports are exposed as regular Ethernet network devices.
OK, I've updated a comment in the pull request for that.
So, in any pre-4.19 kernels, does the directory /sys/class/net/{device}/dsa
exist even if there's no tagging
On Jan 17, 2019, at 2:39 PM, Florian Fainelli wrote:
> DSA currently supports the following tagging protocols (details can be
> found under net/dsa/tag_*.c in Linux source for exactly length and offset
> within the Ethernet frame):
Unfortunately, tag_brcm.c, for example, doesn't give *enough* de
Le 1/17/19 à 6:29 PM, Guy Harris a écrit :
> On Jan 17, 2019, at 6:01 PM, Florian Fainelli wrote:
>
>> Correct. The other ports are exposed as regular Ethernet network devices.
>
> OK, I've updated a comment in the pull request for that.
>
> So, in any pre-4.19 kernels, does the directory /sys/
On Jan 17, 2019, at 7:49 PM, Florian Fainelli wrote:
> Le 1/17/19 à 6:29 PM, Guy Harris a écrit :
>> On Jan 17, 2019, at 6:01 PM, Florian Fainelli wrote:
>>
>>> Correct. The other ports are exposed as regular Ethernet network devices.
>>
>> OK, I've updated a comment in the pull request for th
On 1/17/2019 6:56 PM, Guy Harris wrote:
> On Jan 17, 2019, at 2:39 PM, Florian Fainelli wrote:
>
>> DSA currently supports the following tagging protocols (details can be
>> found under net/dsa/tag_*.c in Linux source for exactly length and offset
>> within the Ethernet frame):
>
> Unfortunate
On Jan 17, 2019, at 8:22 PM, Florian Fainelli wrote:
> On 1/17/2019 6:56 PM, Guy Harris wrote:
>> On Jan 17, 2019, at 2:39 PM, Florian Fainelli wrote:
>>
>>> DSA currently supports the following tagging protocols (details can be
>>> found under net/dsa/tag_*.c in Linux source for exactly length
On 1/17/2019 8:12 PM, Guy Harris wrote:
> On Jan 17, 2019, at 7:49 PM, Florian Fainelli wrote:
>
>> Le 1/17/19 à 6:29 PM, Guy Harris a écrit :
>>> On Jan 17, 2019, at 6:01 PM, Florian Fainelli wrote:
>>>
Correct. The other ports are exposed as regular Ethernet network devices.
>>>
>>> OK,
On Jan 17, 2019, at 9:16 PM, Florian Fainelli wrote:
> On 1/17/2019 8:12 PM, Guy Harris wrote:
>
>> But if /sys/class/net/{device}/dsa doesn't exist in pre-4.19 kernels, how
>> can you determine, from userland, whether a device is a DSA management-port
>> NIC or not, in a system with a pre-4.1
13 matches
Mail list logo
