From: Larry Finger <Larry.Finger@lwfinger.net>
To: Gheorhios <gheorhios@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>
Cc: Fabian Frederick <fabf@skynet.be>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Stefano Brivio <stefano.brivio@polimi.it>,
Johannes Berg <johannes.berg@intel.com>,
Julian Calaby <julian.calaby@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Intel Linux Wireless <ilw@linux.intel.com>,
Chaoming Li <chaoming_li@realsil.com.cn>,
b43-dev <b43-dev@lists.infradead.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1 net-next] wireless: remove unnecessary sizeof(u8)
Date: Tue, 18 Nov 2014 10:12:26 -0600 [thread overview]
Message-ID: <546B6FEA.1090405@lwfinger.net> (raw)
In-Reply-To: <CAFpvzpxYrjR_tSF99iosMGZTAmt=_6o_aA+iYjNhxRGJ9aJ6oA@mail.gmail.com>
On 11/18/2014 07:34 AM, Gheorhios wrote:
> Anyone could gently send the link for downloading B43 linux drivers for
> this procedure?
>
>
>
> Then transfer it over to your Ubuntu box.
>
> Now in your Ubuntu Box [computer] please make your way to your Home folder.
>
> Once you are at your home folder right click on your home folder and make a
> new folder and call it wireless.
>
> Now that you have made a new folder called wireless in your home directory,
> it is time to move the downloaded file into the new folder called wireless.
>
> Move The Wireless Folder To The Firmware Directory
>
> sudo cp -r ~/wireless/* /lib/firmware/
>
> Now let's double check to make sure the download made it to the firmware
> directory. To do this type this into the terminal:
>
> ls /lib/firmware
>
> Ok so now that the download is in the firmware directory we need to go to
> that directory. To go there open your terminal and type in:
>
> cd /lib/firmware
>
> Now that you have changed directories let's double check to make sure you
> are in the right directory, this next code tells us where we are in the
> computer file directory. This next code stands for "print working
> directory".
>
> pwd
>
> Are you at /lib/firmware if so good if not go back one step.
>
> Now that we are in the firmware directory. We have to extract the download,
> to do this type in:
>
> sudo -s
>
> Then enter your password then:
>
> tar xvf b43-all-fw.tar_.gz
>
> Now is the firmware extracted properly? check by typing:
>
> ls /lib/firmware/b43
>
> or:
>
> ls /lib/firmware/b43legacy
>
> Do you see the ucode files? if so then delete the gz file:
>
> sudo rm *.gz
>
> Then:
>
> exit
>
> Reboot
No, I do not know where that file is found. Even if I knew of such a file,
Broadcom has expressly declined to provide that firmware for redistribution.
Posting such a file could invite legal action. If someone else has violated
Broadcom's directive, I would not facilitate that violation.
Rather than doing that, the link at
http://wireless.kernel.org/en/users/Drivers/b43#firmwareinstallation shows what
to do for Ubuntu installations. Follow those instructions - they refer to a
legal way to get the firmware. I would have thought that asking this question on
an Ubuntu Forum would have been more productive.
By the way, piggybacking your request on this thread is very bad netiquette. You
should not have done a "reply-to".
Larry
prev parent reply other threads:[~2014-11-18 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 20:55 [PATCH 1/1 net-next] wireless: remove unnecessary sizeof(u8) Fabian Frederick
2014-11-16 22:33 ` Julian Calaby
2014-11-17 5:56 ` Fabian Frederick
2014-11-17 13:36 ` John W. Linville
[not found] ` <CAFpvzpxYrjR_tSF99iosMGZTAmt=_6o_aA+iYjNhxRGJ9aJ6oA@mail.gmail.com>
2014-11-18 16:12 ` Larry Finger [this message]
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=546B6FEA.1090405@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=chaoming_li@realsil.com.cn \
--cc=emmanuel.grumbach@intel.com \
--cc=fabf@skynet.be \
--cc=gheorhios@gmail.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=julian.calaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
/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;
as well as URLs for NNTP newsgroup(s).