We announced ABI changes to remove iomem and ioport mapping in
igb_uio. But it has potential backward compatibility issue: cannot
run old version DPDK on modified igb_uio.
The purpose of this changes was to fix a bug: when DPDK app crashes,
those devices by igb_uio are not stopped either DPDK PMD driver or
igb_uio driver. We need to figure out new way to fix this bug.
Fixes: 3bac1dbc1ed ("doc: announce iomem and ioport removal from igb_uio")
Suggested-by: Stephen Hemminger <step...@networkplumber.org>
Signed-off-by: Jianfeng Tan <jianfeng....@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 5 -----
1 file changed, 5 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst
b/doc/guides/rel_notes/deprecation.rst
index 755dc65..0f039dd 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -8,11 +8,6 @@ API and ABI deprecation notices are to be posted here.
Deprecation Notices
-------------------
-* igb_uio: iomem mapping and sysfs files created for iomem and ioport in
- igb_uio will be removed, because we are able to detect these from what Linux
- has exposed, like the way we have done with uio-pci-generic. This change
- targets release 17.02.
-
* ABI/API changes are planned for 17.02: ``rte_device``, ``rte_driver`` will be
impacted because of introduction of a new ``rte_bus`` hierarchy. This would
also impact the way devices are identified by EAL. A bus-device-driver model
--
2.7.4
