From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: wireless <linux-wireless@vger.kernel.org>,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>
Subject: [RFC 0/6] ssb and friends: Change layout and naming of SPROM data
Date: Tue, 06 Nov 2007 13:12:56 -0600 [thread overview]
Message-ID: <4730BCB8.900@lwfinger.net> (raw)
In the various Broadcom devices that are supported, several revisions of the SPROM have been
encountered. Current code takes advantage of the fact that Revision 2 inherits all the data of
1, and that Revision 3 inherits from 2. This scheme breaks down with revision 4, which does not
inherit from the earlier models. In deciding how best to implement the new design, a fresh approach
is warranted. Furthermore, we decided not to include any SPROM variables not used in b44, b43 or
b43legacy, the supported drivers. To keep the patches small while preserving compilation and correct
execution during bisection, the change has been split into the following pieces:
1. Introduce new structure while maintaining the old.
2. Convert the ssb module to the new structure.
3. Convert the b44 driver.
4. Convert b43.
5. convert b43legacy.
6. Remove the old structures from ssb.
Larry
reply other threads:[~2007-11-06 19:12 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=4730BCB8.900@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).