linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <mb@bu3sch.de>
To: George Kashperko <george@znau.edu.ua>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	driverdevel <devel@driverdev.osuosl.org>,
	"Henry Ptasinski" <henryp@broadcom.com>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Roland Vossen" <rvossen@broadcom.com>,
	"Arend Van Spriel" <arend@broadcom.com>
Subject: Re: [RFC] AI support
Date: Fri, 18 Feb 2011 23:21:39 +0100	[thread overview]
Message-ID: <1298067699.23801.9.camel@maggie> (raw)
In-Reply-To: <1298032787.25739.2.camel@dev.znau.edu.ua> (sfid-20110218_134828_009719_FFFFFFFFC55A831E)

On Fri, 2011-02-18 at 14:39 +0200, George Kashperko wrote: 
> Does this mean RFC subject in its current state is rejected ?

I am not in charge to reject anything.

But I just noticed that you sent the patches to the list. So I'll
have a look at it. You should improve your CC lists in general
for all your mails. Most of us don't have the time to read all
mail on the list, so it's always a good idea to maintain a CC list
of people who already commented on the RFC for patch submissions.

> > So I'm supporting Henry in that SSB is legacy and EOL. Let's simply
> > start over and don't carry old cruft over.
> > 
> > Note that this does not mean that we need to duplicate the MIPS,
> > common and probably pci core drivers. A hybrid module can be done,
> > if that's desired to avoid code duplication.
> Well, any plans or even maybe ETA on this ?

No.

> > And I also think that you're worrying _way_ too much about a few
> > if/else statements in the drivers. (Look at the TMSLOW discussion).
> > The SSB/AI->driver interface is trivial and tiny. There will be maybe
> > 10 if/else statements. It's really _not_ worth introducing major
> > abstraction code in the SSB and AI code to avoid a few if/else
> > statements in the drivers.
> > The bulk of the SSB->driver interface _is_ already abstracted inside
> > of the drivers (b43_read/write...). The rest is negligible.
> Well, not like I really worry alot about those if/elses :)
> Just in this particular case of SSB in its current design I don't really
> see much differences in where bus implementation-specific management
> must be abstracted if only AI support over SSB is implemented. If there
> will be just b43 relying on such an abstraction then no doubt lets do it
> in b43 driver. But its not.

You should also look into the future.
I don't know what broadcom's plans are, but a rough guess would be
that AI will diverge more and more from SSB, so that more and more
hacks will be needed.
So I'm in favor of making a clean cut.

-- 
Greetings Michael.


  reply	other threads:[~2011-02-18 22:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 15:58 [RFC] AI support George Kashperko
2011-02-17 22:01 ` Michael Büsch
2011-02-17 22:06   ` [RFC] AI support (1/14 ssb admatch redefine) George Kashperko
2011-02-17 22:08   ` [RFC] AI support (2/14 ssb helpers) George Kashperko
2011-02-18 22:29     ` Michael Büsch
2011-02-18 23:15       ` George Kashperko
2011-02-18 23:29         ` Michael Büsch
2011-02-18 23:27           ` George Kashperko
2011-02-17 22:10   ` [RFC] AI support (3/14 ssb irqflag mips core op) George Kashperko
2011-02-17 22:12   ` [RFC] AI support (4/14 ssb mips core irqflag treatment) George Kashperko
2011-02-17 22:14   ` [RFC] AI support (5/14 ssb core control and state helpers) George Kashperko
2011-02-17 22:16   ` [RFC] AI support (6/14 ssb propagate core control and state helpers usage) George Kashperko
2011-02-17 22:18   ` [RFC] AI support (7/14 ssb bus_check_core routine) George Kashperko
2011-02-17 22:20   ` [RFC] AI support (8/14 ssb ssb_bus_detect routine) George Kashperko
2011-02-18 22:35     ` Michael Büsch
2011-02-17 22:23   ` [RFC] AI support (9/14 ssb SB-specific bus scan routine) George Kashperko
2011-02-17 22:25   ` [RFC] AI support (10/14 ssb bus implementation-specific io unmap) George Kashperko
2011-02-17 22:27   ` [RFC] AI support (11/14 ssb separate SB-specific code) George Kashperko
2011-02-17 22:29   ` [RFC] AI support (12/14 ssb mips74k core defs) George Kashperko
2011-02-17 22:31   ` [RFC] AI support (13/14 ssb add AI support) George Kashperko
2011-02-18 22:45     ` Michael Büsch
2011-02-18 23:07       ` George Kashperko
2011-02-18 23:27         ` Michael Büsch
2011-02-18 23:42           ` George Kashperko
2011-02-18 23:54             ` Michael Büsch
2011-02-18 23:51               ` George Kashperko
2011-02-18 23:46           ` Larry Finger
2011-02-18 23:47             ` George Kashperko
2011-02-19  0:06               ` Larry Finger
2011-02-19  0:08                 ` George Kashperko
2011-02-19  0:22                   ` Larry Finger
2011-02-17 22:35   ` [RFC] AI support (14/14 ssb AI on pci host (untested)) George Kashperko
2011-02-18  2:43 ` [RFC] AI support Henry Ptasinski
2011-02-18  7:39   ` George Kashperko
2011-02-18 11:53     ` Michael Büsch
2011-02-18 12:39       ` George Kashperko
2011-02-18 22:21         ` Michael Büsch [this message]
2011-02-18 22:52           ` George Kashperko

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=1298067699.23801.9.camel@maggie \
    --to=mb@bu3sch.de \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=george@znau.edu.ua \
    --cc=henryp@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rvossen@broadcom.com \
    --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).