Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

firmware: set the download filename #84

Merged
merged 1 commit into from
Nov 26, 2024

Conversation

ndechesne
Copy link
Contributor

The boot firmware files published by Qualcomm, even if they are versioned properly, are pusblished as
_bootbinaries.zip. Bitbake expects the version to be there in the downloaded filenames, since all downloads are placed in the same location (DL_DIR). As such installing different versions of the boot binaries will override them each time, and bitbake complains about that (and it causes unnecessary warnings and re-fetch).

We can customize the download file name using the 'downloadfilename' attribute in SRC_URI. With this patch, the firmware is downloaded as:

downloads/QCM6490_bootbinaries_r1.0_00005.0.zip

The boot firmware files published by Qualcomm, even if they are
versioned properly, are pusblished as
<platform>_bootbinaries.zip. Bitbake expects the version to be there
in the downloaded filenames, since all downloads are placed in the
same location (DL_DIR). As such installing different versions of the
boot binaries will override them each time, and bitbake complains
about that (and it causes unnecessary warnings and re-fetch).

We can customize the download file name using the 'downloadfilename'
attribute in SRC_URI. With this patch, the firmware is downloaded as:

downloads/QCM6490_bootbinaries_r1.0_00005.0.zip

Signed-off-by: Nicolas Dechesne <[email protected]>
Copy link
Contributor

@ricardosalveti ricardosalveti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, we can have this workaround in place until we fix the release issue internally.

@lumag
Copy link
Contributor

lumag commented Nov 21, 2024

2c from my side: when I had to face similar issue for other firmware files, I ended up basically adding ${PN}/${PV}/, so that all binaries end up in the subdir rather than putting them into ${DL_DIR} directly.

@ndechesne
Copy link
Contributor Author

2c from my side: when I had to face similar issue for other firmware files, I ended up basically adding ${PN}/${PV}/, so that all binaries end up in the subdir rather than putting them into ${DL_DIR} directly.

I don't see any specific reason why we would need to do that. DL_DIR already has pretty much all tarballs for all recipes. Is there anything in particular that would justify that?

@lumag
Copy link
Contributor

lumag commented Nov 22, 2024

In woa case it was easier to keep downloaded files organised. In this case it probably doesn't make such a difference.

@quic-vkraleti quic-vkraleti merged commit 32dbdef into qualcomm-linux:main Nov 26, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

5 participants