I'm trying the taprio example provided in the Real-time Edge Software User Guide (Rev. 2.7 — 18 December 2023) in section 6.1.4.1.2.4 on an LS1028ARDB.
I have a source device connected to swp0 and a sink device connected to swp1
Following the example, it is expected that with
```
tc qdisc replace dev swp1 parent root handle 100 taprio num_tc 8 map 0 1 2 3 4 5 6 7 queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 base-time 0 sched-entry S 01 300000 flags 0x2
```
I'm able to ping the sink device, while, with
```
tc qdisc replace dev swp1 parent root handle 100 taprio num_tc 8 map 0 1 2 3 4 5 6 7 queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 base-time 0 sched-entry S 02 300000 flags 0x2
```
the ping should be dropped. Indeed, so it is.
However, changing the mapping in
```
tc qdisc replace dev swp1 parent root handle 100 taprio num_tc 8 map 1 0 2 3 4 5 6 7 queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 base-time 0 sched-entry S 01 300000 flags 0x2
```
I should not be able to ping the sink device (since now the default priority 0 is mapped to TC 1), but instead, I'm able to do it. It seem that the mapping is ignored and by default traffic is always mapped to TC 0.
I want to remark that the above mapping works as expected in an Intel i225-based device.
Have you any suggestions on this? Am I missing something?
Best regards,
Alberto Morato