From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] brcm-patchram-plus: new package
Date: Sat, 22 Jul 2017 15:25:11 +0200 [thread overview]
Message-ID: <20170722152511.4ffc8dd3@windsurf> (raw)
In-Reply-To: <20170721144520.14683-1-alexey.roslyakov@gmail.com>
Hello,
On Fri, 21 Jul 2017 21:45:20 +0700, Alexey Roslyakov wrote:
> Many of Broadcom BCM43XX WiFi/Bluetooth combo chips have pretty tricky initialization.
> Broadcom patchram utility has been released to address the issue.
>
> Signed-off-by: Alexey Roslyakov <alexey.roslyakov@gmail.com>
Thanks for this contribution! See a few comments below.
> diff --git a/DEVELOPERS b/DEVELOPERS
> index 7b7c5ab4e6..45466591da 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -73,6 +73,9 @@ N: Alexandre Esse <alexandre.esse.dev@gmail.com>
> F: package/kvazaar/
> F: package/v4l2loopback/
>
> +N: Alexey Roslyakov <alexey.roslyakov@gmail.com>
> +F: package/brcm-patchram-plus
Please end the package path with a /, like all other entries in the
DEVELOPERS file.
> diff --git a/package/brcm-patchram-plus/Config.in b/package/brcm-patchram-plus/Config.in
> new file mode 100644
> index 0000000000..f7df21d2b2
> --- /dev/null
> +++ b/package/brcm-patchram-plus/Config.in
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_BRCM_PATCHRAM_PLUS
> + bool "brcm-patchram-plus"
> + help
> + Utility's to configure and test Broadcom Bluetooth chips on Linux.
> +
> + https://code.google.com/archive/p/broadcom-bluetooth/
Indentation for the help text is one tab + two spaces. I would
recommend you to run utils/check-package on your new package to catch
such coding style issues.
> +BRCM_PATCHRAM_PLUS_VERSION = 0.1.1
> +BRCM_PATCHRAM_PLUS_SOURCE = brcm-patchram-plus_$(BRCM_PATCHRAM_PLUS_VERSION).tar.gz
> +BRCM_PATCHRAM_PLUS_SITE = https://launchpad.net/ubuntu/+archive/primary/+files
Perhaps using the git repository at
https://chromium.googlesource.com/chromiumos/third_party/broadcom would
be a more "official" upstream ?
> +define BRCM_PATCHRAM_PLUS_BUILD_CMDS
> + $(TARGET_CC) -o $(@D)/brcm_patchram_plus $(@D)/brcm_patchram_plus.c
> +endef
> +
> +define BRCM_PATCHRAM_PLUS_INSTALL_TARGET_CMDS
> + $(INSTALL) -D -m 0755 $(@D)/brcm_patchram_plus $(TARGET_DIR)/usr/bin/brcm_patchram_plus
> +endef
What about using the Makefile that comes inside the package ? At least
in the Git repository I pointed to, there is a Makefile that seems
suitable.
Thanks!
Thoma
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-22 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 14:45 [Buildroot] [PATCH 1/1] brcm-patchram-plus: new package Alexey Roslyakov
2017-07-22 13:25 ` Thomas Petazzoni [this message]
2017-07-22 19:34 ` Arnout Vandecappelle
2017-07-28 6:39 ` Alexey Roslyakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170722152511.4ffc8dd3@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.