> From: Michael S. Tsirkin <m...@redhat.com> > Sent: Tuesday, May 16, 2023 6:05 AM
> > SO I propose: > > \item[ACKNOWLEDGE (1)] Indicates that a transport driver has found the > device and recognized it as a valid virtio device transport. > > \item[DRIVER (2)] Indicates that a device type specific driver was found > and will attempt to attach to the device. > Above bisection is a implementation specific example of Linux (though valid and widely used one). The UEFI virtio driver doesn't even have such two drivers. In some OS variant drivers are merged to single kernel binary. Does driver only matter with device_driver structure or module binary?... Driver is largely the software entity that drives the device. I think we can keep the spec simple enough to not mix these details and just call it a "driver". > > BTW somewhat related, I would maybe fix > device-types/mem/description.tex:change > not to say "device driver", just "driver" for brevity. > Ok. will fix. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
