Skip to content
Snippets Groups Projects
  • Andreas Gnau's avatar
    66e5f3f6
    bcmkernel: bcm_git: Find wlan* tarballs by BCM naming convention · 66e5f3f6
    Andreas Gnau authored
    There can be multiple WLAN tarballs per release and the WLAN drivers are
    versioned independently and there can be multiple implementations at the
    same time. For now, support adding something like
    "wlan-all-src-17.10.157.2802" to bcm_modules, so that tarball
    wlan-all-src-17.10.157.2802.cpe5.04L.02.tgz gets imported.
    
    WLAN binaries and sources are versioned separately. So, the "module" is
    something like wlan-all-src-17.10.157.2802 for a tarball like
    wlan-all-src-17.10.157.2802.cpe5.04L.02.tgz.  There can be multiple WLAN
    drivers implementations (impls) applied to the same release.  When
    having two version numbers, if the first three components of the version
    number are identical, then that tarball most likely contains the same
    impl, but that is just an observation.
    66e5f3f6
    History
    bcmkernel: bcm_git: Find wlan* tarballs by BCM naming convention
    Andreas Gnau authored
    There can be multiple WLAN tarballs per release and the WLAN drivers are
    versioned independently and there can be multiple implementations at the
    same time. For now, support adding something like
    "wlan-all-src-17.10.157.2802" to bcm_modules, so that tarball
    wlan-all-src-17.10.157.2802.cpe5.04L.02.tgz gets imported.
    
    WLAN binaries and sources are versioned separately. So, the "module" is
    something like wlan-all-src-17.10.157.2802 for a tarball like
    wlan-all-src-17.10.157.2802.cpe5.04L.02.tgz.  There can be multiple WLAN
    drivers implementations (impls) applied to the same release.  When
    having two version numbers, if the first three components of the version
    number are identical, then that tarball most likely contains the same
    impl, but that is just an observation.