package/brcm-patchram-plus: Add new package
PATCH v4 1/1 package/brcm-patchram-plus: Add new package
Add tool which allows to setup broadcom bluetooth
device via UART.
---
v4:
1) Wrongly specified license files [Yann E. Morin]
2) Fix APACHE-2.0 -> Apache-2.0 [Yann E. Morin]
v3:
1) Specify src/main.c as license file [Yann E. Morin]
v2:
1) Add link to the github in Config.in help section [Yann E. Morin]
2) Use autoreconf instaed of direct call to autogen.sh [Yann E. Morin]
DEVELOPERS | 3 +++ package/Config.in | 1 + package/brcm-patchram-plus/Config.in | 7 +++++++ package/brcm-patchram-plus/brcm-patchram-plus.hash | 2 ++ package/brcm-patchram-plus/brcm-patchram-plus.mk | 13 +++++++++++++ 5 files changed, 26 insertions(+) create mode 100644 package/brcm-patchram-plus/Config.in create mode 100644 package/brcm-patchram-plus/brcm-patchram-plus.hash create mode 100644 package/brcm-patchram-plus/brcm-patchram-plus.mk
DEVELOPERS +3 -0
@@ -2141,6 +2141,9 @@ N: Tzu-Jung Lee <[email protected]> F: package/dropwatch/ F: package/tstools/ +N: Vadim Kochan <[email protected]> +F: package/brcm-patchram-plus/ + N: Valentin Korenblit <[email protected]> F: package/clang/ F: package/clinfo/
package/Config.in +1 -0
@@ -1819,6 +1819,7 @@ menu "Networking applications" source "package/bmon/Config.in" source "package/boa/Config.in" source "package/boinc/Config.in" + source "package/brcm-patchram-plus/Config.in" source "package/bridge-utils/Config.in" source "package/bwm-ng/Config.in" source "package/c-icap/Config.in"
package/brcm-patchram-plus/Config.in new file +7 -0
@@ -0,0 +1,7 @@ +config BR2_PACKAGE_BRCM_PATCHRAM_PLUS + bool "brcm-patchram-plus" + help + Broadcom utility to flash Bluetooth firmwares, extended with + per-device Low Power Mode configuration. + + https://github.com/AsteroidOS/brcm-patchram-plus
package/brcm-patchram-plus/brcm-patchram-plus.hash new file +2 -0
@@ -0,0 +1,2 @@ +# locally computed +sha256 7d63f3a0c79cb5d187a0f2647734601f9c97d4eb8e545ce9ace7653c1f3f9a58 brcm-patchram-plus-94fb127e614b19a9a95561b8c1a0716e2e1e6293.tar.gz
package/brcm-patchram-plus/brcm-patchram-plus.mk new file +13 -0
@@ -0,0 +1,13 @@ +################################################################################ +# +# brcm-patchram-plus +# +################################################################################ + +BRCM_PATCHRAM_PLUS_VERSION = 94fb127e614b19a9a95561b8c1a0716e2e1e6293 +BRCM_PATCHRAM_PLUS_SITE = $(call github,AsteroidOS,brcm-patchram-plus,$(BRCM_PATCHRAM_PLUS_VERSION)) +BRCM_PATCHRAM_PLUS_LICENSE = Apache-2.0 +BRCM_PATCHRAM_PLUS_LICENSE_FILES = src/main.c +BRCM_PATCHRAM_PLUS_AUTORECONF = YES + +$(eval $(autotools-package))
Signature · 1 line
2.14.1
PATCH v4 1/1 package/brcm-patchram-plus: Add new package
On 24/12/2018 18:28, Vadim Kochan wrote:
[snip]
package/brcm-patchram-plus/brcm-patchram-plus.hash line 2
Quoted 4 lines
+++ b/package/brcm-patchram-plus/brcm-patchram-plus.hash
package/brcm-patchram-plus/brcm-patchram-plus.hash new file +2
-0@@ -0,0 +1,2 @@ +# locally computed +sha256 7d63f3a0c79cb5d187a0f2647734601f9c97d4eb8e545ce9ace7653c1f3f9a58 brcm-patchram-plus-94fb127e614b19a9a95561b8c1a0716e2e1e6293.tar.gz
Normally, we also require a hash for the license file. However, in this case,
it's pretty likely that the main.c file (and thus the hash) will change with every version bump... So maybe a license file hash is inappropriate here?
Regards,
Arnout
Quoted 20 lines
package/brcm-patchram-plus/brcm-patchram-plus.mk new file +13
-0@@ -0,0 +1,13 @@ +################################################################################ +# +# brcm-patchram-plus +# +################################################################################ + +BRCM_PATCHRAM_PLUS_VERSION = 94fb127e614b19a9a95561b8c1a0716e2e1e6293 +BRCM_PATCHRAM_PLUS_SITE = $(call github,AsteroidOS,brcm-patchram-plus,$(BRCM_PATCHRAM_PLUS_VERSION)) +BRCM_PATCHRAM_PLUS_LICENSE = Apache-2.0 +BRCM_PATCHRAM_PLUS_LICENSE_FILES = src/main.c +BRCM_PATCHRAM_PLUS_AUTORECONF = YES + +$(eval $(autotools-package))