netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Joseph Jezak <josejx-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: [PATCH] bcm43xx: Fix code for spec changes of 2/7/2007
Date: Fri, 09 Feb 2007 13:26:25 -0600	[thread overview]
Message-ID: <45CCCAE1.9080901@lwfinger.net> (raw)
In-Reply-To: <45CCC5DF.8010001-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>

Joe,

Joseph Jezak wrote:

> 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?

As my 4306 is a rev 1 and is likely a version dropped in the V4 driver, I have a special interest in
this question.

My plan is to continue to maintain bcm43xx-SoftMAC for at least the BPHY and 4306 revisions even
after d80211 becomes the in-kernel driver. Of course, I hope that we will have found the killer bugs
by that time, and that maintenance will only require following kernel API changes.

As the work will be yours, you should decide if you would rather maintain the V3 and V4 pages
separately, or denote the special requirements of each firmware flavor in a combined set of pages.

Larry
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2007-02-09 19:26 UTC|newest]

Thread overview: 31+ 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
     [not found] ` <45cca236.+lL/rsW3DbM3elnk%Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2007-02-09 17:11   ` Michael Buesch
     [not found]     ` <200702091811.40683.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-02-09 18:11       ` Larry Finger
2007-02-09 22:22     ` Joseph Jezak
2007-02-09 17:29       ` Michael Buesch
     [not found]         ` <200702091829.51002.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-02-09 18:21           ` Larry Finger
2007-02-09 18:48             ` Michael Buesch
2007-02-09 19:05             ` Joseph Jezak
     [not found]               ` <45CCC5DF.8010001-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2007-02-09 19:17                 ` Michael Buesch
2007-02-09 19:55                   ` Joseph Jezak
2007-02-09 20:30                     ` Michael Buesch
2007-02-14 12:52                     ` Johannes Berg
2007-02-09 19:26                 ` Larry Finger [this message]
2007-02-09 21:32                   ` Matthew Garrett
     [not found]                     ` <20070209213239.GA11650-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2007-02-09 22:52                       ` Martin Langer
2007-02-10  5:55                       ` Michael Buesch
     [not found]                         ` <200702100655.51495.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-02-10 12:57                           ` Matthew Garrett
     [not found]                             ` <20070210125707.GA21803-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2007-02-27 17:00                               ` Gavin McCullagh
2007-02-14 13:18                           ` Johannes Berg
2007-02-14 21:40                             ` Michael Buesch
     [not found]                               ` <200702142240.01494.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-02-15 15:07                                 ` Johannes Berg
     [not found]                                   ` <1171552024.5220.4.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-02-15 15:13                                     ` Michael Buesch
     [not found]                                       ` <200702151613.20746.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-02-15 15:19                                         ` Johannes Berg
     [not found]                                           ` <1171552753.5220.10.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-02-15 16:51                                             ` Martin Langer
2007-02-15 16:53                                               ` Johannes Berg
2007-02-11 13:21                       ` Johannes Berg
2007-02-09 18:45   ` Michael Buesch
     [not found]     ` <200702091945.25187.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-02-09 19:17       ` Joseph Jezak
     [not found]         ` <45CCC8B5.3060108-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2007-02-09 19:26           ` Michael Buesch
     [not found]             ` <200702092026.43006.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-02-09 19:58               ` 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=45CCCAE1.9080901@lwfinger.net \
    --to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
    --cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=josejx-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).