Context
I used to configure can0 and can1 on my Raspberry PI running Debian Buster like
[all]
dtparam=spi=on
dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=24
dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=25
dtoverlay=spi-bcm2835
Since support for seeed-can-fd-hat in regular raspberry pi kernel became available using Debian Bullseye I started using
[all]
dtoverlay=seeed-can-fd-hat-v2
Question
I noticed that can0 and can1 were switched around. When I connect a cable to a CAN port that is wired to can0, I get traffic on can1 when I do candump can1. With the first configuration above the traffic arrived as expected to candump can0. I would expect the same with the latter configuration.
How come?
(Let me know if you need more context to be able to help me.)