From: grarpamp <grarpamp@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Need to match driver to microcode?
Date: Wed, 5 Feb 2014 17:58:16 -0500 [thread overview]
Message-ID: <CAD2Ti2-Q8-km40GPZ+pZ2v4cBkUN3vLM_a+2mCLOOtgZ=jdOxg@mail.gmail.com> (raw)
For the same core number, is it necessary to update
the b43 driver when a new microcode is added? Or
does the API/addressing into the microcode stay
the same across microcode updates?
ie: Were any updates to the driver needed to support
the span from say 478.104 to 784.2 of the microcode
for any of the cores already present in 478.104?
I'm not seeing anything obvious to that effect in the
short summaries here:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/net/wireless/b43
next reply other threads:[~2014-02-05 22:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 22:58 grarpamp [this message]
2014-02-05 23:57 ` Need to match driver to microcode? Larry Finger
2014-02-06 0:54 ` grarpamp
2014-02-06 1:50 ` Larry Finger
2014-02-06 4:34 ` grarpamp
2014-02-06 6:10 ` Rafał Miłecki
2014-02-06 8:19 ` grarpamp
2014-02-06 8:47 ` Rafał Miłecki
2014-02-06 7:22 ` Larry Finger
2014-02-06 9:01 ` grarpamp
2014-02-06 16:54 ` Larry Finger
2014-02-06 20:02 ` grarpamp
2014-02-06 20:19 ` Chris Adams
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='CAD2Ti2-Q8-km40GPZ+pZ2v4cBkUN3vLM_a+2mCLOOtgZ=jdOxg@mail.gmail.com' \
--to=grarpamp@gmail.com \
--cc=b43-dev@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).