From: "Marcin M." <marcin.marcin.m@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: NVRAM autoload for BRCM 43340 chipset
Date: Sun, 09 Aug 2015 17:30:08 +0200 [thread overview]
Message-ID: <55C77200.5090005@gmail.com> (raw)
I reported the bug as here:
https://bugzilla.kernel.org/show_bug.cgi?id=102531
I thought - maybe I could help fixing this, this doesn't seem as
difficult as writing a driver from scratch. Anyway, I'm completely new
to this stuff - could you aid me where I should start looking? The
firmware is all binary and even in the git repo there are only binary blobs.
Please CC me directly so that I receive the replies
--
Marcin
reply other threads:[~2015-08-09 15:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55C77200.5090005@gmail.com \
--to=marcin.marcin.m@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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