public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Kashperko <george@znau.edu.ua>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Arend van Spriel <arend@broadcom.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Russell King <rmk@arm.linux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>,
	linuxdriverproject <devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] bcmai: introduce AI driver
Date: Thu, 07 Apr 2011 04:02:19 +0300	[thread overview]
Message-ID: <1302138139.27258.35.camel@dev.znau.edu.ua> (raw)
In-Reply-To: <BANLkTinfM0QLFwcKZXfWQ_jNYfBJg_et-Q@mail.gmail.com>


> W dniu 7 kwietnia 2011 02:00 użytkownik George Kashperko
> <george@znau.edu.ua> napisał:
> > For PCI function description take a look at PCI specs or PCI
> > configuration space description (e. g.
> > http://en.wikipedia.org/wiki/PCI_configuration_space)
> >
> > Sorry for missleading short-ups, w11 - bcm80211 core, under two-head I
> > mean ssb/axi with two functional cores on same interconnect (like w11
> > +w11, not a lot of these exists I guess). Also there were some b43+b44
> > on single PCI ssb host and those where implemented as ssb interconnect
> > on multifunctional PCI host therefore providing separate access windows
> > for each function.
> >
> > Might I mussunderstood something (its late night here at my place) when
> > you where talking about using coreswitching involved for two drivers
> > therefore I remembered about those functions. Seems now you were talking
> > about chipcommon+b43 access sharing same window.
> >
> > As for core switching requirments for earlier SSB interconnects on PCI
> > hosts where there were no direct chipcommon access, that one can be
> > accomplished without spin_lock/mutex for b43 or b44 cores with proper
> > bus design.
> >
> > AXI doesn't need spinlocks/mutexes as both chipcommon and pci bridge are
> > available directly and b43 will be the only one requiring window access.
> 
> Ahh, so while talking about 4 windows, I guess you counted fixes
> windows as well. That would be right, matching my knowledge.
Nop, I mean sliding windows only.

> 
> When asking question about amount of cores we may want to use
> simultaneously I didn't think about ChipCommon or PCIe. The real
> problem would be to support for example two 802.11 cores and one
> ethernet core at the same time. That gives us 3 cores while we have
> only 2 sliding windows. But I would not care for that too much for
> now.
That will give us 3 PCI functions, each with own sliding windows.

> 
> For the rest (PCI function) I have to sleep before reading specs ;)
> 

Have nice day,
George



  reply	other threads:[~2011-04-07  1:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1302033463-1846-1-git-send-email-zajec5@gmail.com>
     [not found] ` <1302032137.3969.10.camel@Joe-Laptop>
     [not found]   ` <BANLkTimTmqop-xzFsWr1=2RXv5z6iTre4Q@mail.gmail.com>
     [not found]     ` <1302035106.1923.7.camel@maggie>
2011-04-05 22:30       ` [PATCH] ssb: Use pr_fmt and pr_<level>, remove CONFIG_SSB_SILENT Joe Perches
2011-04-06 14:18 ` [RFC][PATCH] bcmai: introduce AI driver Arend van Spriel
2011-04-06 18:02   ` Rafał Miłecki
2011-04-06 20:25     ` Arend van Spriel
2011-04-06 20:40       ` Rafał Miłecki
2011-04-06 20:42         ` Rafał Miłecki
2011-04-06 20:57           ` Michael Büsch
2011-04-06 21:01             ` Rafał Miłecki
2011-04-06 21:08               ` Michael Büsch
2011-04-06 21:12                 ` Rafał Miłecki
2011-04-06 21:18                   ` George Kashperko
2011-04-06 23:20                     ` Rafał Miłecki
2011-04-07  0:00                       ` George Kashperko
2011-04-07  0:54                         ` Rafał Miłecki
2011-04-07  1:02                           ` George Kashperko [this message]
2011-04-07  7:54                           ` Michael Büsch
2011-04-07  8:58                             ` Arend van Spriel
2011-04-07 18:50                               ` George Kashperko
2011-04-07  9:55                             ` Rafał Miłecki
2011-04-07 18:36                               ` George Kashperko
2011-04-06 21:20                   ` Michael Büsch
2011-04-08 16:56   ` Rafał Miłecki
2011-04-08 17:09     ` Rafał Miłecki
2011-04-08 17:14       ` Rafał Miłecki
2011-04-08 17:24     ` Arend van Spriel
2011-04-08 17:27       ` Rafał Miłecki
2011-04-08 17:28         ` Arend van Spriel
2011-04-08 17:31           ` Rafał Miłecki
2011-04-09  7:10       ` George Kashperko
2011-04-09 11:01         ` Arend van Spriel
2011-04-10  8:01   ` Pavel Machek
2011-04-10  8:05     ` Rafał Miłecki
2011-04-10  8:24       ` Pavel Machek
2011-04-10  8:30         ` Rafał Miłecki
2011-04-10  9:33           ` Arend van Spriel
2011-04-10 11:32             ` Rafał Miłecki
2011-04-10 14:36               ` Arend van Spriel
2011-04-10 16:11             ` 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=1302138139.27258.35.camel@dev.znau.edu.ua \
    --to=george@znau.edu.ua \
    --cc=Larry.Finger@lwfinger.net \
    --cc=arend@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=b43-dev@lists.infradead.org \
    --cc=devel@linuxdriverproject.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rmk@arm.linux.org.uk \
    --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