[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c2c0ba34-2985-21ea-0809-b96a3aa5e401@siemens.com>
Date: Fri, 4 Nov 2022 16:32:49 +0100
From: Jan Kiszka <jan.kiszka@...mens.com>
To: Harald Mommer <hmo@...nsynergy.com>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Harald Mommer <harald.mommer@...nsynergy.com>
Cc: virtio-dev@...ts.oasis-open.org, linux-can@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Wolfgang Grandegger <wg@...ndegger.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Dariusz Stojaczyk <Dariusz.Stojaczyk@...nsynergy.com>
Subject: Re: [virtio-dev] Re: [RFC PATCH 1/1] can: virtio: Initial virtio CAN
driver.
On 03.11.22 14:55, Harald Mommer wrote:
> Hello,
>
> On 27.08.22 11:39, Marc Kleine-Budde wrote:
>> Is there an Open Source implementation of the host side of this
>> interface?
> there is neither an open source device nor is it currently planned. The
> device I'm developing is closed source.
Likely not helpful long-term /wrt kernel QA - how should kernelci or
others even have a chance to test the driver? Keep in mind that you are
not proposing a specific driver for an Opensynergy hypervisor, rather
for the open and vendor-agnostic virtio spec.
But QEMU already supports both CAN and virtio, thus should be relatively
easy to augment with this new device.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
Powered by blists - more mailing lists