1. 09 10月, 2020 2 次提交
  2. 02 10月, 2020 4 次提交
  3. 21 7月, 2020 1 次提交
  4. 08 5月, 2020 5 次提交
  5. 24 4月, 2020 4 次提交
  6. 27 3月, 2020 8 次提交
  7. 24 3月, 2020 1 次提交
  8. 18 3月, 2020 12 次提交
  9. 04 1月, 2020 3 次提交
    • L
      iwlwifi: add device name to device_info · 0b295a1e
      Luca Coelho 提交于
      We have a lot of mostly duplicated data structures that are repeated
      only because the device name string is different.  To avoid this, move
      the string from the cfg to the trans structure and add it
      independently from the rest of the configuration to the PCI mapping
      tables.
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      0b295a1e
    • L
      iwlwifi: implement a new device configuration table · 2a612a60
      Luca Coelho 提交于
      Add a new device table that contains information that can be checked
      at runtime in order to decide which configuration to use.  This allows
      us to map the full cfg independently from the tran-specific
      configuration.
      
      This is the first step in creating the new table.  Subsequent patches
      will add the possibility of checking different values at runtime in
      order to make the decision.
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      2a612a60
    • L
      iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg · b3bd6416
      Luca Coelho 提交于
      With the new concept of separating the trans-specific (trans_cfg) data
      from the rest of the cfg, we will start mapping only the trans_cfg
      part to the PCI device ID/subsystem device ID.  So we can assume that
      the data passed to the probe function contains the trans_cfg, but
      since the full cfg still contains the trans_cfg at the beginning, we
      can allow a full cfg to be passed as well.  This makes it easier to
      convert the existing tables one by one.
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      b3bd6416