1. 08 4月, 2017 1 次提交
    • A
      mei: drop amthif internal client · 394a77d0
      Alexander Usyskin 提交于
      AMTHIF has special support in the mei drive, it handles multiplexing
      multiple user space connection above single me client connection.
      Since there is no additional addressing information there is a strict
      requirement on the traffic order on each connection and on the "read
      after write" order within the connection. This creates a lot of
      complexity mostly because the other client types do not necessarily fall
      under the same restriction.    After carefully studying the use of the
      AMTHIF client, we came to conclusion that the multiplexing is not really
      utilized by any application and we may safely remove that support and
      significantly simplify the driver.
      Signed-off-by: NAlexander Usyskin <alexander.usyskin@intel.com>
      Signed-off-by: NTomas Winkler <tomas.winkler@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      394a77d0
  2. 31 1月, 2017 2 次提交
  3. 20 1月, 2017 2 次提交
  4. 10 11月, 2016 1 次提交
  5. 30 8月, 2016 2 次提交
  6. 08 2月, 2016 5 次提交
  7. 07 2月, 2016 1 次提交
  8. 21 9月, 2015 1 次提交
  9. 04 8月, 2015 3 次提交
  10. 25 5月, 2015 4 次提交
  11. 03 4月, 2015 1 次提交
  12. 25 3月, 2015 1 次提交
  13. 02 3月, 2015 6 次提交
  14. 26 1月, 2015 1 次提交
  15. 29 9月, 2014 1 次提交
  16. 24 9月, 2014 4 次提交
  17. 18 3月, 2014 2 次提交
  18. 01 3月, 2014 1 次提交
  19. 27 9月, 2013 1 次提交