pmaports/device/community/firmware-asus-me176c/APKBUILD
Minecrell 4724b0f9c1
firmware/*: move community firmware packages to device/community (MR 1362)
Right now we have all firmware packages under firmware/*.
This is problematic for mainly two reasons:

  - It's not immediately clear which firmware packages we need to keep
    when forking a new stable branch. (Where we delete testing devices
    at the moment...) We might end up deleting firmware packages that
    are actually used by one of the devices in community.

  - When backporting devices to the stable we cannot just cherry-pick
    the commit that moved the device to community (since it does not
    contain the firmware package). Instead we need to cherry-pick
    earlier commits as well, which may touch a lot of deleted files
    in the testing directory.

Let's make this consistent by also placing the firmware packages in
the device/* directory. We already have the common firmware- prefix
to distinguish them from device/kernel packages, which are already
both under the device/* directory.
2020-07-07 15:48:57 +02:00

24 lines
847 B
Text

pkgname=firmware-asus-me176c
pkgver=12.10.1.36
pkgrel=1
arch="x86_64"
pkgdesc="Firmware for ASUS MeMO Pad 7 (ME176C(X))"
url="https://dlcdnets.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-$pkgver-user.zip"
license="unknown"
options="!check !strip !archcheck"
source="$url"
_fwdir="/lib/firmware/postmarketos"
package() {
cd "$srcdir"
# WiFi
install -Dm644 system/vendor/firmware/bcm43362/fw_bcmdhd.bin "$pkgdir/$_fwdir"/brcm/brcmfmac43362-sdio.bin
install -Dm644 system/etc/nvram.txt "$pkgdir/$_fwdir"/brcm/brcmfmac43362-sdio.txt
# Bluetooth
install -Dm644 system/etc/firmware/BCM2076B1_002.002.004.0132.0141_reduced_2dB.hcd "$pkgdir/$_fwdir"/brcm/BCM2076B1.hcd
}
sha512sums="4bfb30fcc872b9e3d57f251bff7a3fe9349d90a02c2c9ef8af938fad9d84ff3367723a2fee0dc7a5a10c3df1d4e28a766ae69f967b6a45e1835f284e61762404 UL-K013-WW-12.10.1.36-user.zip"