[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9786872e-1063-e1ff-dc0d-6be5952a1826@opensynergy.com>
Date: Tue, 18 Apr 2023 11:50:56 +0200
From: Harald Mommer <hmo@...nsynergy.com>
To: Marc Kleine-Budde <mkl@...gutronix.de>,
Mikhail Golubev <Mikhail.Golubev@...nsynergy.com>
Cc: Arnd Bergmann <arnd@...nel.org>,
Jan Kiszka <jan.kiszka@...mens.com>,
Harald Mommer <harald.mommer@...nsynergy.com>,
virtio-dev@...ts.oasis-open.org, linux-can@...r.kernel.org,
Netdev <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>,
stratos-dev@...lists.linaro.org,
Matti Moell <Matti.Moell@...nsynergy.com>
Subject: Re: [virtio-dev] Re: [RFC PATCH 1/1] can: virtio: Initial virtio CAN
driver.
Hello,
there is now an implementation of the device for qemu internally under
review.
The paperwork with the company lawyer to publish source code has also
been done.
At the same time we changed the driver and the specification draft also,
especially the bus off indication is now done by a config space bit
instead of having a dedicated indication queue. Minor updates to some
other structures. This means what we have will match an updated driver
and specification version not yet sent out. Also to be done so that
people can play around.
So an open source qemu device is in the work and we are close to publish
this in our public github repository but until now nothing has been
pushed yet to github.
Regards
Harald
On 14.04.23 21:20, Marc Kleine-Budde wrote:
> On 03.02.2023 16:02:04, Harald Mommer wrote:
>> we had here at OpenSynergy an internal discussion about an open source
>> virtio-can device implementation.
>>
>> The outcome of this is now that an open source virtio-can device is to be
>> developed.
>>
>> It has not yet been decided whether the open source device implementation
>> will be done using qemu or kvmtool (or something else?). Negative or
>> positive feedback for or against one of those is likely to influence the
>> decision what will be used as basis for the development. Using kvmtool may
>> be easier to do for me (to be investigated in detail) but on the other hand
>> we have some people around in the team who have the knowledge to support
>> with qemu.
> It there some code available yet? We as Pengutronix will be on our
> yearly techweek soon and I want to look into the VirtIO CAN stuff.
>
> regards,
> Marc
>
Powered by blists - more mailing lists