Re: [PATCH v5 0/7] can: refactoring of can-dev module and of Kbuild

Oliver Hartkopp <socketcan@xxxxxxxxxxxx> · Tue, 7 Jun 2022 22:51:54 +0200

On 07.06.22 22:27, Marc Kleine-Budde wrote:
On 07.06.2022 22:12:46, Oliver Hartkopp wrote:
So what about:

   symbol: CONFIG_NETDEVICES
   |
   +-> CAN Device Drivers
       symbol: CONFIG_CAN_DEV
       |
       +-> software/virtual CAN device drivers
       |   (at time of writing: slcan, vcan, vxcan)
       |
       +-> hardware CAN device drivers with Netlink support
           symbol: CONFIG_CAN_NETLINK (matches previous CONFIG_CAN_DEV)
           |
           +-> CAN bit-timing calculation (optional for all drivers)
           |   symbol: CONFIG_CAN_BITTIMING
           |
           +-> CAN rx offload (optional but selected by some drivers)
           |   symbol: CONFIG_CAN_RX_OFFLOAD
           |
           +-> CAN devices drivers
               (some may select CONFIG_CAN_RX_OFFLOAD)

(I also added 'hardware' to CAN device drivers with Netlink support) to have
a distinction to 'software/virtual' CAN device drivers)

The line between hardware and software/virtual devices ist blurry, the
new can327 driver uses netlink and the slcan is currently being
converted....

Right, which could mean that slcan and can327 should be located in the 
'usual' CAN device driver section and not in the sw/virtual device section.

The slcan and can327 need some kind of hardware - while vcan and vxcan 
don't.

Best regards,
Oliver