linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: ikorot@earthlink.net
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: [PATCH 1/4] b43: N-PHY: update init tables
Date: Tue, 07 Dec 2010 14:00:35 -0600	[thread overview]
Message-ID: <4CFE9263.4060108@lwfinger.net> (raw)
In-Reply-To: <5001512.1291751372533.JavaMail.root@elwamui-cypress.atl.sa.earthlink.net>

On 12/07/2010 01:49 PM, ikorot@earthlink.net wrote:
>> One reason is that these tables changed from non-zero to zero values between
>> Broadcom driver 4.174.64.19 and 5.10.56.46. As they might change again, I think
>> we should retain the full version.
> 
> Is there a way to check for version of the driver?
> This way whoever uses old one won't be screwed...

That will not be a problem as no older version of b43 works at all with b43. To
help you understand this change, when the 4.174.64.19 Broadcom driver was
reverse-engineered, the tables had non-zero values. Rafel later compared the
trace dumps of b43 with the latest version of wl and found that the values are
now zero. When I rechecked driver 5.10.56.46, I found them to be zero there as
well and changed the specs.

Larry

  reply	other threads:[~2010-12-07 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 19:49 [PATCH 1/4] b43: N-PHY: update init tables ikorot
2010-12-07 20:00 ` Larry Finger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-10 21:54 ikorot
2010-12-10 22:03 ` Rafał Miłecki
2010-12-10 19:09 ikorot
2010-12-10 19:33 ` Rafał Miłecki
2010-12-10  2:26 ikorot
2010-12-10  6:36 ` Rafał Miłecki
2010-12-08  1:55 ikorot
2010-12-09 14:06 ` Rafał Miłecki
2010-12-07  8:42 Rafał Miłecki
2010-12-07 19:08 ` Hauke Mehrtens
2010-12-07 19:19   ` Larry Finger

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=4CFE9263.4060108@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=hauke@hauke-m.de \
    --cc=ikorot@earthlink.net \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).