All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: Joseph Jezak <josejx@gentoo.org>,
	netdev@vger.kernel.org, Larry Finger <larry.finger@lwfinger.net>,
	linux-wireless@vger.kernel.org,
	John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] bcm43xx: Fix code for spec changes of 2/7/2007
Date: Fri, 9 Feb 2007 21:30:38 +0100	[thread overview]
Message-ID: <200702092130.38997.mb@bu3sch.de> (raw)
In-Reply-To: <45CCD1B1.80709@gentoo.org>

On Friday 09 February 2007 20:55, Joseph Jezak wrote:
> Michael Buesch wrote:
> > On Friday 09 February 2007 20:05, Joseph Jezak wrote:
> >>> I'll agree to that as long as there is a clear indication of any differences between V3 and V4 firmware.
> >> That's also part of the problem.  With the v4 driver, Broadcom 
> >> dropped support for a number of older BPHY devices (4301/4303 and 
> >> some 4306 revisions).  Do we still want to support those?  Should I 
> >> continue writing the specs for the uCode revision it's based on or 
> >> should I combine them?
> > 
> > If it's easily possible, please try to combine the old stuff
> > with the new v4 specs.
> > I think it's basically only dropped if() branches, right?
> > 
> 
> Well, here's the problem.  There are a few places where a value is 
> changed (different value written to a register).  Does this mean 
> that the value is different due to the uCode changes (can't tell, no 
> documentation)?  Is it applicable to all revisions (can't tell, some 
> revisions are not supported in this version)?  If the revision 
> number range in a check changes is that because of a difference in 
> supported cards or a bug fix?
> 
> So, it's not as simple as just dropped if() branches.  I can do my 
> best to combine them (I have done some of this already), but I can't 
> promise that it'll be accurate for all revisions or versions of the 
> chipset.

Ok, I see.
How many of these old devices exist and who has access to them?
If we want to combine stuff, we really must test it on these devices then.

-- 
Greetings Michael.

  reply	other threads:[~2007-02-09 20:30 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 16:32 [PATCH] bcm43xx: Fix code for spec changes of 2/7/2007 Larry Finger
2007-02-09 16:32 ` Larry Finger
2007-02-09 17:11 ` Michael Buesch
2007-02-09 17:11   ` Michael Buesch
2007-02-09 18:11   ` Larry Finger
2007-02-09 18:11     ` Larry Finger
2007-02-09 22:22   ` Joseph Jezak
2007-02-09 17:29     ` Michael Buesch
2007-02-09 18:21       ` Larry Finger
2007-02-09 18:21         ` Larry Finger
2007-02-09 18:48         ` Michael Buesch
2007-02-09 19:05         ` Joseph Jezak
2007-02-09 19:17           ` Michael Buesch
2007-02-09 19:17             ` Michael Buesch
2007-02-09 19:55             ` Joseph Jezak
2007-02-09 20:30               ` Michael Buesch [this message]
2007-02-14 12:52               ` Johannes Berg
2007-02-14 19:13                 ` Larry Finger
2007-02-14 19:26                   ` Johannes Berg
2007-02-14 19:27                     ` Johannes Berg
2007-02-14 21:52                       ` Michael Buesch
2007-02-14 22:28                     ` Larry Finger
2007-02-09 19:26           ` Larry Finger
2007-02-09 19:26             ` Larry Finger
2007-02-09 21:32             ` Matthew Garrett
2007-02-09 22:52               ` Martin Langer
2007-02-09 22:52                 ` Martin Langer
2007-02-10  5:55               ` Michael Buesch
2007-02-10  5:55                 ` Michael Buesch
2007-02-10 12:57                 ` Matthew Garrett
2007-02-10 12:57                   ` Matthew Garrett
2007-02-27 17:00                   ` Gavin McCullagh
2007-02-27 17:00                     ` Gavin McCullagh
2007-02-11  2:13                 ` Joseph Jezak
2007-02-14 13:18                 ` Johannes Berg
2007-02-14 13:18                   ` Johannes Berg
2007-02-14 21:40                   ` Michael Buesch
2007-02-15 15:07                     ` Johannes Berg
2007-02-15 15:07                       ` Johannes Berg
2007-02-15 15:13                       ` Michael Buesch
2007-02-15 15:13                         ` Michael Buesch
2007-02-15 15:19                         ` Johannes Berg
2007-02-15 15:19                           ` Johannes Berg
2007-02-15 16:51                           ` Martin Langer
2007-02-15 16:51                             ` Martin Langer
2007-02-15 16:53                             ` Johannes Berg
2007-02-11 13:21               ` Johannes Berg
2007-02-11 13:21                 ` Johannes Berg
2007-02-09 18:45 ` Michael Buesch
2007-02-09 18:45   ` Michael Buesch
2007-02-09 19:17   ` Joseph Jezak
2007-02-09 19:17     ` Joseph Jezak
2007-02-09 19:26     ` Michael Buesch
2007-02-09 19:26       ` Michael Buesch
2007-02-09 19:58       ` Joseph Jezak
2007-02-09 19:58         ` Joseph Jezak
2007-02-09 22:24 ` Joseph Jezak
2007-02-09 22:24   ` Joseph Jezak

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=200702092130.38997.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=josejx@gentoo.org \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.