Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Apertis CI robot authored 1 month ago and Dylan Aïssi committed 1 month ago

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Apertis CI robot authored 1 year ago and Ritesh Raj Sarraf committed 1 year ago

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Apertis CI robot authored 1 year ago and Ritesh Raj Sarraf committed 1 year ago

Signed-off-by: Apertis CI robot <noreply+not_a_robot@apertis.org>

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Merge remote-tracking branch 'origin/apertis/v2023dev3' into proposed-updates/debian/bookworm/2a3a155f

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Apertis has moved to using external references in the CI config path setting
for the packaging repositories, so the gitlab-ci.yml embedded in the
repository is no longer needed.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Apertis CI authored 3 years ago and Denis Pynkin committed 3 years ago

Conflicts resolved:
	debian/changelog

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

For Apertis we can't use `dosfstools` package for minimal
images type due licensing issues.
We do not expect the mount of firmware partition in runtime, since it
contains static data only: firmware blobs, U-Boot binary and
configuration file. So there is no need to have FAT FS checking tool.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Install script is aimed for kernel/initramfs setup, however in Apertis
we don't boot the kernel directly from `config.txt` file but use
U-Boot bootloader.
So by disabling the install/remove scripts we avoid the copying of
unneded files to firmware partition and incorrect boot configuration.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Apertis package maintainers authored 4 years ago and Denis Pynkin committed 4 years ago

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

raspi-firmware (1.20200212-1) unstable; urgency=medium

  * New upstream version 1.20200212
  * debian/copyright: Exclude .github/ISSUE_TEMPLATE/bug_report.md

raspi-firmware (1.20200114-2) unstable; urgency=medium

  * Fix dtb names mismatch in z50-raspi-firmware and add new option
    upstream_kernel=1 to the config.txt. These two changes allow for the
    correct boot on RPi families 1 and 0. Thanks to Valentin Vidic for the
    fix! (no BTS bugs fixed, refer to Salsa merge request 12)
  * Fixes the serial console in models that lack wireless
    communication. Again, thanks to Valentin Vidic! (Salsa merge request 13)

raspi-firmware (1.20200114-1) unstable; urgency=medium

  * New upstream version 1.20200114
  * Updated standards-version 4.3.0 → 4.5.0 (no changes needed)
  * Replaced tabs with spacs throughout debian/copyright to comply with
    DEP-5 and keep lintian happy 

raspi-firmware (1.20190925-1) unstable; urgency=medium

  * New upstream version 1.20190925
  * Transitional package should not have Architecture: all (Closes: #947804)

raspi-firmware (1.20190819-2) unstable; urgency=medium

  * Fix serial console output sent to bluetooth port with kernel 5.x.
    Thanks to Thorsten Glaser (Closes: #941971)

raspi-firmware (1.20190819-1) unstable; urgency=medium

  * New upstream version 1.20190819 (Closes: #935919)

raspi-firmware (1.20190718-1) unstable; urgency=medium

  [ Romain Perier ]
  * New upstream version 1.20190718-1
  * Rename package to raspi-firmware

  [ Cyril Brulebois ]
  * Add support for bcm2837-rpi-cm3-io3.dtb (as generated by the Linux
    kernel build system) aka. bcm2710-rpi-cm3.dtb (as expected by the
    bootloader), designed to work for:
     - Raspberry Pi Compute Module 3 (CM3);
     - Raspberry Pi Compute Module 3 Lite (CM3L);
     - Raspberry Pi Compute Module IO Board V3.
    With many thanks to Charles Fendt for the tests (Closes: #932158).
  * The DTB addition in the linux source package is tracked in #932157.

  [ Gunnar Wolf ]
  * Added Rules-Require-Root: no to debian/control (plus section and
    priority to a binpkg section)
  * Rename conffiles to reflect package name change
  * Transitional package should be in the oldlibs section
  * Add code to handle custom kernel options (Closes: #934833)
  * Renamed repository dropping the "3" after raspi; reflected it in Vcs-
    Git and Vcs-Browser

raspi3-firmware (1.20190620+1-1) unstable; urgency=medium

  * New upstream version 1.20190620+1
  * d/copyright: Exclude pre-built kernel images from boot (Closes: #924315)
  * d/raspi3-firmware.lintian-overrides: Override new rules regarding embedded
    libraries into binaries, statically linked new binaries and binaries from
    other architectures. These are required for the addition of the tnew first
    level bootloader binaries blobs for the pi 4.

raspi3-firmware (1.20190215-2) unstable; urgency=medium

  * z50-raspi3-firmware: Change to use arm_64bit=1 (Closes: #925062)
  * z50-raspi3-firmware: Make consoles configurable for cmdline.txt
   (Closes: #926325)

raspi3-firmware (1.20190215-2~exp1) experimental; urgency=medium

  * Switch to package.maintscript

raspi3-firmware (1.20190215-1) unstable; urgency=medium

  [ Gunnar Wolf ]
  * New upstream version 1.20190215
  * Added armel as a build architecture
  * Added Romain Perier as an uploader
  * Updated standards-version 3.9.8 → 4.3.0 (no changes needed)

  [ Romain Perier ]
  * d/kernel/postinst.d/z50-raspi3-firmware: Allow the kernel image and the
    initramfs usage to be configurable from /etc/default/raspi3-firmware
  * z50-raspi3-firmware: Add RPI 1 RPI Zero W DTBs when booting linux directly
  * Add support for the armel architecture

raspi3-firmware (1.20181112-1) unstable; urgency=medium

  [ Gunnar Wolf ]
  * Added support for installing the 3B+ firmware
  * Add configurable options for cmdline.txt (Closes: #903543)
  * Add brcm80211/brcmfmac43430-sdio.txt,
    brcm80211/brcmfmac43455-sdio.txt  and brcm80211/brcmfmac43455.clm_blob
    via a quilt patch, to solve the issue of uscan not providing a full
    tarball to work from. Thanks to Romain Perier for his help! (Closes: #897234)
  * Make sure that firmware hooks get triggered after initrd hooks
    (Closes: #910790). Thanks to Matthias Lüscher!

  [ Ondřej Nový ]
  * d/copyright: Use https protocol in Format field
  * d/rules: Remove trailing whitespaces

  [ Romain Perier ]
  * Encode the files to be excluded from the orig.tar.gz in d/copyright so
    that uscan produces a suitable tarball

raspi3-firmware (1.20180619-1) unstable; urgency=medium

  * New upstream version 1.20180619-1
  * Added myself as an uploader
  * Updated the VCS URLs to salsa.debian.org
  * Differentiated the two proprietary licenses in debian/copyright to
    please Lintian

raspi3-firmware (1.20180316-3) unstable; urgency=medium

  * correct path in postinst script

raspi3-firmware (1.20180316-2) unstable; urgency=medium

  * Rename hooks to 50raspi3-firmware (Closes: #848101)

raspi3-firmware (1.20180316-1) unstable; urgency=medium

  * New upstream version 1.20180316
    (for compatibility with the Raspberry Pi 3 B+)

raspi3-firmware (1.20171201-4) unstable; urgency=medium

  [ Matthias Lüscher ]
  * Do not check mount point if virtualization gets detected.
  * Copy and rename all possible device tree binaries.
  * Added missing dosfstools dependency.
  * Increase cma memory to 64M to allow proper vc4 GPU initialization.
  * Adjusted package description.

raspi3-firmware (1.20171201-3) unstable; urgency=medium

  * Ensure /boot/firmware exists (Closes: #887062)

raspi3-firmware (1.20171201-2) unstable; urgency=medium

  * postinst: also trigger hook on upgrades, not just first installation

raspi3-firmware (1.20171201-1) unstable; urgency=medium

  * New upstream version 1.20171201
    (git revision 9426e18b87b343b84280ad2e4151863e36595c4a)
  * Add the Raspberry Pi 3-specific firmware file brcmfmac43430-sdio.txt

raspi3-firmware (1.20171006-2) unstable; urgency=medium

  * Fix serial console on Linux ≥ 4.14
  * Add console=tty0 for boot messages on the attached monitor (if any)

raspi3-firmware (1.20171006-1) unstable; urgency=medium

  * Fix sort order for newer kernel versions (Patch by Martin Schitter)
  * Avail package on armhf (patch by Vagrant Cascadian) (Closes: #858428)
  * Add kernel/postrm.d/raspi3-firmware to clean up after kernel removal
    (Patch by Martin Schitter)
  * New upstream version 1.20171006
    (git revision 2669578d1449255edf23f38ed98d208ab73faed7)
  * set net.ifnames=0 in cmdline
  * Add missing dpkg-maintscript-helper call to postinst, postrm
  * experimental to unstable as the freeze is over

raspi3-firmware (1.20170317-4) experimental; urgency=medium

  * Add XS-Autobuild: yes, as non-free packages are not automatically built by default

raspi3-firmware (1.20170317-3) experimental; urgency=medium

  * fix hook location: s/initramfs-tools/initramfs/
  * hook: ignore temporary .dpkg-bak files
  * cmdline: mount root fs read/write for resizing
  * add raspi3-firmware-fsck initramfs-tools hook
  * remove old conffile for users who upgrade in-place

raspi3-firmware (1.20170317-2) experimental; urgency=medium

  * initramfs-tools: move raspi3-firmware from hooks to post-update.d

raspi3-firmware (1.20170317-1) experimental; urgency=medium

  * New upstream version 1.20170317
    (git revision 509beaab0e102cf6decf209922669700c9ac5576)
  * Upload to experimental during the freeze
  * The new upstream version populates the device tree with the ethernet MAC
    address, so the MAC address will persist across reboots.
  * Add /etc/initramfs-tools/hooks/raspi3-firmware to also update the files in
    /boot/firmware/ when only the initramfs is being updated (as opposed to
    kernel and initramfs).
  * Switch from Conflicts+Replaces to Breaks+Replaces, as per the lintian
    warning conflicts-with-version.

raspi3-firmware (1.20161123-2) unstable; urgency=medium

  * Rename package to raspi3-firmware to be consistent with the remaining
    *-firmware packages (Thanks Ben Hutchings for the hint)

linux-firmware-raspi3 (1.20161123-1) unstable; urgency=medium

  * Initial upload of the package to Debian, based on the
    linux-firmware-raspi2 work in Ubuntu (Thanks!) (Closes: #845488)
  * Rename package to linux-firmware-raspi3
  * s/armhf/arm64/ for the Raspberry Pi 3
  * postinst: allow sync to fail
  * add kernel postinst.d hook to copy images and update configs
  * change maintainer to newly-created pkg-raspi
  * bump debhelper compat to 10, bump standards-version to 3.9.8
  * add lintian-overrides for binary package
  * package description: add trademark acknowledgement
  * add Vcs-* tags
  * New upstream version 1.20161123
    (git revision 18b5b6977d021937d82fb94010c99d84b403a08a)

linux-firmware-raspi2 (1.20151118+b70b451-0ubuntu1) xenial; urgency=low

  * Switch package naming to fall into the linux-firmware-* hierachy.
  * Move to section multiverse/misc.
  * Update standards version to 3.9.7 no changes required.
  * Check that /boot/firmware is a mount point (or that we are in a chroot).
  * We do not need to install LICENCE.broadcom.

raspberrypi2-firmware (4.1.15-b70b451-0ubuntu1) xenial; urgency=medium

  * Initial upload to Ubuntu.
  * Add lintian overrides to suppress errors about known binary-only firmware.
  * Set upload component to restricted.
  * Fix inconsistency between upstream LICENSE file and debian/copyright.

raspberrypi2-firmware (4.1.15-b70b451-1) xenial; urgency=medium

  * Update to version 4.1.15 @ b70b451

raspberrypi2-firmware (4.1.10-ba7a8fb-1) wily; urgency=low

  * Initial import - https://github.com/raspberrypi/firmware / master @ ba7a8fb