Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	"George Kashperko" <george@znau.edu.ua>
Cc: "Greg KH" <greg@kroah.com>,
	linuxdriverproject <devel@linuxdriverproject.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"Michael Büsch" <mb@bu3sch.de>
Subject: Re: new utility kernel module for detecting cores in newer chipsets
Date: Sun, 20 Mar 2011 18:04:18 +0100	[thread overview]
Message-ID: <op.vsni1gbi3ri7v4@arend-laptop> (raw)
In-Reply-To: <1300626438.16689.21.camel@dev.znau.edu.ua>

On Sun, 20 Mar 2011 14:07:18 +0100, George Kashperko <george@znau.edu.ua>
wrote:

>> I don't want to have support for AI in 10 places, even if this is
>> about staging area.
>>
> Agree here completely. The only arguable point here I think could be
> that AXI and SB should be different drivers but honestly they are too
> much similar softwire-wise to even be placed in separate directories if
> only bus managing code model is designed well.

Agree and a valid point at that as one would typically need either ssb or
axi support. If with a little refactoring the ssb tree can provide two
separate drivers that is fine by me if the axi flavour is not burdened by
shortcomings of the the ssb driver, which you are said to have pointed out
(I missed most of the discussion about this, sorry). In brcm80211 we have
two drivers and one typically needs the ssb support and the other axi
support. We abstracted the core access (not judging how well we did that)
with an additional layer but there is actually no need when having
separate drivers requiring either one or the other interconnect support.

Depending on the driver it may depend on one of them or both, but with two
separate modules this choice is up to the driver which makes most sense to
me.

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"


  reply	other threads:[~2011-03-20 17:04 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 [this message]
     [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
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.vsni1gbi3ri7v4@arend-laptop \
    --to=arend@broadcom.com \
    --cc=devel@linuxdriverproject.org \
    --cc=george@znau.edu.ua \
    --cc=greg@kroah.com \
    --cc=linux-wireless@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox