From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/wf111: Fix manufacturer name and url
Date: Sat, 3 Feb 2018 16:40:15 +0100 [thread overview]
Message-ID: <20180203154015.GN2369@scaer> (raw)
In-Reply-To: <20180129082819.13870-1-corjon.j@ecagroup.com>
Julien, All,
On 2018-01-29 09:28 +0100, Julien Corjon spake thusly:
> Signed-off-by: Julien Corjon <corjon.j@ecagroup.com>
> ---
> package/wf111/Config.in | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/package/wf111/Config.in b/package/wf111/Config.in
> index 80109f1b88..081bd960cb 100644
> --- a/package/wf111/Config.in
> +++ b/package/wf111/Config.in
> @@ -6,7 +6,7 @@ config BR2_PACKAGE_WF111
> # dynamically linked against the glibc.
> depends on BR2_TOOLCHAIN_USES_GLIBC
> help
> - BlueGiga WF111 WiFi driver and utilities.
> + Silicon Labs WF111 WiFi driver and utilities.
>
> Warning: CONFIG_WIRELESS_EXT and CONFIG_WEXT_PRIV must be
> selected in the Linux kernel configuration. These are blind
> @@ -17,16 +17,16 @@ config BR2_PACKAGE_WF111
> configuration entry that selects them, for example.
> - By enabling another random WiFi driver that select them.
>
> - http://www.bluegiga.com/en-US/products/wifi-modules/wf111-wifi-module/
> + https://www.silabs.com/products/wireless/wi-fi/wf111-bluegiga-module
>
> if BR2_PACKAGE_WF111
>
> config BR2_PACKAGE_WF111_TARBALL_PATH
> string "Local tarball location"
> help
> - The WF111 tarball can be retrieved on the BlueGiga website
> - after registration. This option specifies the path where the
> - tarball is locally saved.
> + The WF111 tarball can be retrieved on the Silicon Labs
> + website after registration. This option specifies the path
> + where the tarball is locally saved.
As I just replied to your previous patch (but you were dropped from Cc
for whatever reason), this is no longer true: one can very well do the
download without registration nowdays: try to download the URLs from
command line:
wget 'https://www.silabs.com/documents/login/software/wf111-linux-driver-5-2-2-r3-armv5te.tar.gz'
and it magically works now. So we can drop the special local tarball
path now. Care to send a patch?
Regards,
Yann E. MORIN.
> endif
>
> --
> 2.14.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-02-03 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 8:28 [Buildroot] [PATCH 1/1] package/wf111: Fix manufacturer name and url Julien Corjon
2018-01-29 13:40 ` Peter Korsgaard
2018-02-03 15:40 ` Yann E. MORIN [this message]
2018-02-03 17:07 ` Yann E. MORIN
2018-02-03 19:17 ` Peter Korsgaard
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=20180203154015.GN2369@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox