[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220607202706.7fbongzs3ixzpydm@pengutronix.de>
Date: Tue, 7 Jun 2022 22:27:06 +0200
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Oliver Hartkopp <socketcan@...tkopp.net>
Cc: Vincent MAILHOL <mailhol.vincent@...adoo.fr>,
linux-can <linux-can@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Max Staudt <max@...as.org>, netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v5 0/7] can: refactoring of can-dev module and of Kbuild
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....
> At least this would help me to understand the new configuration setup.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists