OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Version Control Commit by rusty


Author: rusty
Date: 2014-02-10 10:30:06 +0000 (Mon, 10 Feb 2014)
New Revision: 213
Web View: https://tools.oasis-open.org/version-control/browse/wsvn/virtio/?rev=213&sc=1

Modified:
   content.tex
Log:
PCI Section Rework

1) Minor changes from must to MUST etc.
2) More references using \ref.
3) Move section on capabilities first, before we talk about the common
   config layout.  The previous order made sense for legacy.
4) Make explicit subsections for each type of capability and move more
   information into them.
5) Make it clear that there must be one or more.
6) Include 'struct virtio_pci_cap cap;' in struct virtio_pci_cfg_cap to
   match virtio_pci_notify_cap.
7) Explicitly note there's no way to negotiate the queue size for a
   legacy device.
8) Fix old language on config change event: config is not in the pci
   configuration space.
9) Explicitly state what the driver should do to use virtio_pci_cfg_cap.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]