Skip to content
Snippets Groups Projects
  1. Dec 12, 2016
  2. Dec 10, 2016
  3. Dec 09, 2016
    • Jo-Philipp Wich's avatar
      build: support adding version code to file names (FS#323) · 9791fb2a
      Jo-Philipp Wich authored
      
      Now that the VERSION_NUMBER variable holds the human friendly name and not
      the commit ID anymore, we need to support adding the revision ID as well.
      
      Introduce a new config variable CONFIG_VERSION_CODE_FILENAMES which, if set,
      causes the resulting file names to contain a commit ID designation as printed
      by scripts/getver.sh.
      
      Also sanitize the input variables to ensure that the resulting strings are
      lowercased and no not contain spaces.
      
      Signed-off-by: default avatarJo-Philipp Wich <jo@mein.io>
      9791fb2a
  4. Dec 08, 2016
    • Mathias Kresin's avatar
      lantiq: simplify ath9k eeprom extraction script · ee5a6c10
      Mathias Kresin authored
      
      Add an extra function to patch the mac and fixup the checksum
      afterwards. Calculate the checksum position automatically. The offset
      to the mac address is the same for all checksum protected EEPROMs.
      
      No EEPROM requires a byte swapped mac address. The mac byte swap code
      was required due to an bug in the script that is now fixed.
      
      Signed-off-by: default avatarMathias Kresin <dev@kresin.me>
      ee5a6c10
    • Martin Blumenstingl's avatar
      lantiq: fix ath9k EEPROM data swapping for some devices · afa37092
      Martin Blumenstingl authored
      
      The EEPROM data in the flash of the ARV7518PW, ARV8539PW22,
      BTHOMEHUBV2B and BTHOMEHUBV3A is stored byte-swapped (swab16), meaning
      that for example the ath9k base_eep_header fields "version" (high and
      low byte), "opCapFlags" and "eepMisc" are swapped (the latter ones are
      just 1 byte wide, thus their position is swapped).
      
      The old "ath,eep-endian" property enabled the corresponding swapping
      logic in the ath9k driver (swab16 in ath9k_hw_nvram_swap_data, which is
      based on the magic bytes in the EEPROM data which have nothing to do
      with the calibration data - thus this logic should not be used
      anymore).
      Since we have switched to the upstream ath9k devicetree bindings there
      is no binding anymore which enables swab16 in ath9k (as this logic is
      not recommended anymore as explained above), leading to ath9k
      initialization errors:
      ath: phy0: Bad EEPROM VER 0x0001 or REV 0x00e0
      (this shows that the version field is swapped, expected values are VER
      0x000E and REV 0x0001)
      
      Swapping the ath9k calibration data when extracting it from the flash
      fixes the devices listed above (all other devices do not require
      additional swapping, since the position of the fields is already as
      expected by ath9k). This allows ath9k to read the version correctly
      again, as well as the more important "eepmisc" field (which is used for
      determining whether the data inside the EEPROM is Big or Little Endian
      which is required to parse the EEPROM contents correctly).
      
      Fixes: a2061686 ("lantiq: use ath9k device tree bindings
      binding/owl-loader")
      
      Signed-off-by: default avatarMartin Blumenstingl <martin.blumenstingl@googlemail.com>
      afa37092
  5. Dec 07, 2016
  6. Dec 06, 2016
  7. Dec 05, 2016
  8. Dec 04, 2016
Loading