All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Michael Büsch" <mb@bu3sch.de>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Henry Ptasinski" <henryp@broadcom.com>,
	"John Linville" <linville@tuxdriver.com>,
	"George Kashperko" <george@znau.edu.ua>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: new utility kernel module for detecting cores in newer chipsets
Date: Mon, 21 Mar 2011 16:05:27 +0100	[thread overview]
Message-ID: <op.vso77ddp3ri7v4@arend-laptop> (raw)
In-Reply-To: <AANLkTi=1eGo7uvP8Uy32yQezhGJTHYkHpEyX9vF=PujF@mail.gmail.com>

On Mon, 21 Mar 2011 15:27:49 +0100, Rafał Miłecki <zajec5@gmail.com> wrote:

> The case is, we discussed ssb/ai driver layout few days ago. George
> shared idea of layout I agree with, nobody shared any objections. If
> everything goes fine, we should have nicely modularized driver/project
> supporting Broadcom's buses.

Hi Rafał,

Does this give us one module supporting both buses or does it provide two  
kernel modules (my preference)? I did ask you and George this question  
earlier but I seem to have missed the response from you or George.

> In this situation I'm not really interested is simple ai driver
> stripped from brcm80211. According to me, it would led to harder
> maintenance and harder implementation of support for such a driver in
> b43.

I can imagine from b43 perspective the only good implementation would be  
to stick with the current b43<->ssb interface. So what will you do when  
another type of SoC interconnect is introduced. Forcing that in the same  
API as well? If you and George propose a new carefully considered API  
covering the functional capabilities of the current (and possibly future)  
interconnect buses I am all for that.

To summarize this, my main issue (and Michael's, I think) is with the  
dependency being imposed between ai and ssb. Having two completely  
independent modules really makes more sense.

Gr. AvS
-- 
"The most merciful thing in the world, I think, is the inability of the  
human
mind to correlate all its contents." - "The Call of Cthulhu"


  parent reply	other threads:[~2011-03-21 15:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <op.vslagcb13ri7v4@arend-laptop>
2011-03-19 12:13 ` new utility kernel module for detecting cores in newer chipsets Arend van Spriel
2011-03-20  9:55   ` Rafał Miłecki
2011-03-20 13:07     ` George Kashperko
2011-03-20 17:04       ` Arend van Spriel
     [not found] ` <1300538338.11949.12.camel@maggie>
     [not found]   ` <20110319214234.GA5152@kroah.com>
     [not found]     ` <1300573336.11949.25.camel@maggie>
     [not found]       ` <20110319234524.GA7493@kroah.com>
     [not found]         ` <op.vsmyhmei3ri7v4@arend-laptop>
     [not found]           ` <20110320145421.GA13962@kroah.com>
     [not found]             ` <op.vsnd1a1i3ri7v4@arend-laptop>
     [not found]               ` <20110320162200.GA17030@kroah.com>
     [not found]                 ` <op.vsng7q1j3ri7v4@arend-laptop>
     [not found]                   ` <20110320185216.GD19375@kroah.com>
2011-03-21 10:12                     ` Rafał Miłecki
2011-03-21 14:05                       ` Greg KH
2011-03-21 14:27                         ` Rafał Miłecki
2011-03-21 14:46                           ` Greg KH
2011-03-21 14:52                             ` Rafał Miłecki
2011-03-21 15:16                               ` Greg KH
2011-03-21 15:33                                 ` Rafał Miłecki
2011-03-21 15:05                           ` Arend van Spriel [this message]
2011-03-21 15:14                             ` John W. Linville
2011-03-21 15:30                             ` Rafał Miłecki
2011-03-21 16:25                               ` George Kashperko
2011-03-21 16:24                             ` Michael Büsch
2011-03-21 16:28                               ` Michael Büsch

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=op.vso77ddp3ri7v4@arend-laptop \
    --to=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=george@znau.edu.ua \
    --cc=henryp@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --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 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.