b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	b43-dev-list <b43-dev@lists.infradead.org>
Subject: [RFC] bcma: replace ssb_sprom structure with bcma_sprom structure
Date: Tue, 6 Mar 2012 14:42:27 +0100	[thread overview]
Message-ID: <4F561443.1040506@broadcom.com> (raw)
In-Reply-To: <CACna6rx5_wds1gMA+9Yg4hMS1NCankwEqN3ixMUaktLAhw9ERw@mail.gmail.com>

On 03/06/2012 02:27 PM, Rafa? Mi?ecki wrote:
> 2012/3/6 Arend van Spriel<arend@broadcom.com>:
>> BCMA shared a structure with SSB in which sprom data was stored. This
>> could have been appropriate but with upcoming srom revisions that are
>> of no interest to SSB it is better to have own definitions with BCMA.
>>
>> This patch adds support for srom revisions 8 and 9.
>
> Does b43 even compile with that?
>

Nope. It does not. That is why I was asking b43 developers for feedback 
in this RFC. By moving to another structure there is more work involved 
that needs good b43 knowledge (which I am lacking). What I can do is 
provide a function that maps bcma_sprom structure members to ssb_sprom 
structure members to make the transition easier.

Gr. AvS

  reply	other threads:[~2012-03-06 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 12:26 [RFC] bcma: replace ssb_sprom structure with bcma_sprom structure Arend van Spriel
2012-03-06 13:27 ` Rafał Miłecki
2012-03-06 13:42   ` Arend van Spriel [this message]
2012-03-06 23:23 ` Hauke Mehrtens
2012-03-07  7:45   ` Arend van Spriel

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=4F561443.1040506@broadcom.com \
    --to=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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).