From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] broadpwn (was Spectre and Meltdown)
Date: Thu, 11 Jan 2018 14:19:43 +0000 [thread overview]
Message-ID: <c54b51c34c9a20a512c86710f1d9f9c1@hamnavoe.com> (raw)
In-Reply-To: <20180111003358.4AFE6156E524@mail.bitblocks.com>
> https://github.com/raspberrypi/linux/issues/1342#issuecomment-321221748
>
> Need Linux to run this but does not fix the problem?
No need for linux. If you don't mind installing firmware from random files
on drive.google.com, you can grab the tarball referenced from the url above,
unpack it, and copy brcmfmac43430-sdio.^(bin txt) into /sys/lib/firmware
on your pi3 or pi0w.
You will need to pad the .bin file to a multiple of 2048 bytes (eg by
appending from /dev/zero) otherwise the verify after loading seems to fail.
If you use the piwifi kernel (rootfs from wifi) as opposed to the pi3 kernel
(rootfs from ethernet or sdcard with access to wifi), you'll want to rebuild
the kernel in order to get the updated files into the /boot builtin fs.
There should be a more definitive source for the firmware files somewhere.
> Though there seems to be another unrelated problem that seems
> not quite fixed.
The other two fixes mentioned in that issue (turning off power management
and harcoding packet priority to zero) were already in the plan 9 driver.
next prev parent reply other threads:[~2018-01-11 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 16:59 [9fans] Spectre and Meltdown cinap_lenrek
2018-01-10 19:32 ` Skip Tavakkolian
2018-01-10 19:41 ` Erik Quanstrom
2018-01-10 20:52 ` Skip Tavakkolian
2018-01-10 20:56 ` Erik Quanstrom
2018-01-10 21:30 ` Skip Tavakkolian
2018-01-10 23:46 ` Richard Miller
2018-01-11 0:33 ` Bakul Shah
2018-01-11 14:19 ` Richard Miller [this message]
2018-01-11 0:55 ` Skip Tavakkolian
2018-01-11 9:35 ` hiro
2018-01-11 9:49 ` Rui Carmo
2018-01-11 9:58 ` Richard Miller
2018-01-12 11:45 ` hiro
2018-01-16 0:51 ` Jules Merit
2018-01-16 1:16 ` Jules Merit
2018-01-15 9:57 ` Giacomo Tesio
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=c54b51c34c9a20a512c86710f1d9f9c1@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).