From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11141] WF111 package no longer availabe
Date: Tue, 10 Jul 2018 09:43:24 +0000 [thread overview]
Message-ID: <bug-11141-163-haJHAUL5NI@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11141-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11141
--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
Why are they broken? Buildroot should fall back to the copy we have on
sources.buildroot.net:
https://www.silabs.com/documents/login/software/wf111-linux-driver-5-2-2-r3-armv5te.tar.gz
Resolving www.silabs.com (www.silabs.com)... 23.53.20.107
Connecting to www.silabs.com (www.silabs.com)|23.53.20.107|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-07-10 11:33:42 ERROR 404: Not Found.
--2018-07-10 11:33:42--
http://sources.buildroot.net/wf111/wf111-linux-driver-5-2-2-r3-armv5te.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 104.27.167.48,
104.27.166.48, 2400:cb00:2048:1::681b:a730, ...
Connecting to sources.buildroot.net
(sources.buildroot.net)|104.27.167.48|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-07-10 11:33:43 ERROR 404: Not Found.
--2018-07-10 11:33:43--
http://sources.buildroot.net/wf111-linux-driver-5-2-2-r3-armv5te.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 104.27.167.48,
104.27.166.48, 2400:cb00:2048:1::681b:a730, ...
Connecting to sources.buildroot.net
(sources.buildroot.net)|104.27.167.48|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2743425 (2.6M) [application/x-gtar-compressed]
With that said, updating to -4 is also fine. Do notice that they apparently
haven't released a -4 x86 version:
wget
https://www.silabs.com/documents/login/software/wf111-linux-driver-5-2-2-r4-x86.tar.gz
--2018-07-10 11:34:37--
https://www.silabs.com/documents/login/software/wf111-linux-driver-5-2-2-r4-x86.tar.gz
Resolving www.silabs.com (www.silabs.com)... 23.53.20.107
Connecting to www.silabs.com (www.silabs.com)|23.53.20.107|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
What is this wpa-supplicant patch about? Is this something new for -4? Where
can this patch be found?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-07-10 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 14:29 [Buildroot] [Bug 11141] New: WF111 package no longer availabe bugzilla at busybox.net
2018-07-10 9:43 ` bugzilla at busybox.net [this message]
2018-07-10 9:57 ` [Buildroot] [Bug 11141] " bugzilla at busybox.net
2018-07-10 10:21 ` bugzilla at busybox.net
2018-07-10 10:25 ` bugzilla at busybox.net
2018-07-10 16:38 ` bugzilla at busybox.net
2018-08-29 20:10 ` bugzilla at busybox.net
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=bug-11141-163-haJHAUL5NI@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.