Skip to content
Snippets Groups Projects
Commit 66e5f3f6 authored by Andreas Gnau's avatar Andreas Gnau :speech_balloon:
Browse files

bcmkernel: bcm_git: Find wlan* tarballs by BCM naming convention

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.
parent ba8d6f69
No related branches found
No related tags found
1 merge request!6bcmkernel: bcm_git: Improvements, mainly for handling wifi drivers
......@@ -294,7 +294,15 @@ add_release ()
for module in $bcm_modules
do
tar="bcm963xx_${version}_${module}.tar.gz"
case "$module" in
wlan-all-src-* | wlan-bin-all-*)
# WiFi drivers have their own naming convention like wlan-all-src-17.10.157.2802.cpe5.04L.02.tgz.
tar="${module}.cpe${version}.tgz"
;;
*)
tar="bcm963xx_${version}_${module}.tar.gz"
;;
esac
if ! [ -f ${tar_dir}/${tar} ]
then
echo -e "\ttar not found. skipping $tar"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment