On Sun, 5 Jun 2022 20:06:41 +0200 Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx> wrote: > On 05.06.2022 19:23:47, Max Staudt wrote: > > This seemingly splits drivers into "things that speak to hardware" > > and "things that don't". Except... slcan really does speak to > > hardware. It just so happens to not use any of BITTIMING or > > RX_OFFLOAD. However, my can327 (formerly elmcan) driver, which is > > an ldisc just like slcan, *does* use RX_OFFLOAD, so where to I put > > it? Next to flexcan, m_can, mcp251xfd and ti_hecc? > > > > Is it really just a split by features used in drivers, and no > > longer a split by virtual/real? > > We can move RX_OFFLOAD out of the "if CAN_NETLINK". Who wants to > create an incremental patch against can-next/master? Yes, this may be useful in the future. But for now, I think I can answer my question myself :) My driver does support Netlink to set CAN link parameters. So I'll just drop it into the CAN_NETLINK -> RX_OFFLOAD category in Kconfig, unless anyone objects. I just got confused because in my mind, I'm still comparing it to slcan, whereas in reality, it's now functionally closer to all the other hardware drivers. Netlink and all. Apologies for the noise! Max
