On Wed, Mar 12, 2025 at 02:36:05PM +0100, Marc Kleine-Budde wrote: > On 12.03.2025 14:28:10, Matias Ezequiel Vara Larsen wrote: > > On Wed, Mar 12, 2025 at 11:41:26AM +0100, Marc Kleine-Budde wrote: > > > On 12.03.2025 11:31:12, Matias Ezequiel Vara Larsen wrote: > > > > On Thu, Feb 01, 2024 at 07:57:45PM +0100, Harald Mommer wrote: > > > > > Hello, > > > > > > > > > > I thought there would be some more comments coming and I could address > > > > > everything in one chunk. Not the case, besides your comments silence. > > > > > > > > > > On 08.01.24 20:34, Christophe JAILLET wrote: > > > > > > > > > > > > Hi, > > > > > > a few nits below, should there be a v6. > > > > > > > > > > > > > > > > I'm sure there will be but not so soon. Probably after acceptance of the > > > > > virtio CAN specification or after change requests to the specification are > > > > > received and the driver has to be adapted to an updated draft. > > > > > > > > > What is the status of this series? > > > > > > There has been no movement from the Linux side. The patch series is > > > quite extensive. To get this mainline, we need not only a proper Linux > > > CAN driver, but also a proper VirtIO specification. > > > > Thanks for your answer. AFAIK the spec has been merged (see > > https://github.com/oasis-tcs/virtio-spec/tree/virtio-1.4). > > Yes, the spec was merged. I think it was written with a specific > use-case (IIRC: automotive, Linux on-top of a specific hypervisor) in > mind, in Linux we have other use cases that might not be covered. What use-case you have in Linux? > > > > This whole project is too big for me to do it as a collaborative > > > effort. > > > > What do you mean? > > I mean the driver is too big to review on a non-paid community based > effort. > I think I can help reviewing it. I will try to spend some time in the next weeks. Matias
