In our use case, we treat vehicle as a virtual device. For example, we send values to it to control the HVAC, and we receive values like car speed from the vehicle. We are not using virtio-can because 1. the vehicle bus does not have to be CAN and 2. we are doing something which more than just a pipe to the car bus (e.g., power management).
Hao On Mon, May 17, 2021 at 11:02 PM Enrico Weigelt, metux IT consult <l...@metux.net> wrote: > > On 17.05.21 21:28, Hao Chen wrote: > > The reason for defining a virtio-parameter-server device is we are > > interacting > > with some devices in a "key-value store" pattern. For example, we interact > > with > > "vehicle device" in Android using this pattern. > > What kind of devices are these ? > > > --mtx > -- > --- > Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert > werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren > GPG/PGP-Schlüssel zu. > --- > Enrico Weigelt, metux IT consult > Free software and Linux embedded engineering > i...@metux.net -- +49-151-27565287 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org > For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org > --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
