Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Michael Büsch" <mb@bu3sch.de>
To: Florian Fainelli <florian@openwrt.org>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
	linux-mips@linux-mips.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: Merging SSB and HND/AI support
Date: Mon, 17 Jan 2011 13:00:09 +0100	[thread overview]
Message-ID: <1295265609.24530.25.camel@maggie> (raw)
In-Reply-To: <201101171220.52292.florian@openwrt.org> (sfid-20110117_122124_233292_51C2DD96)

On Mon, 2011-01-17 at 12:20 +0100, Florian Fainelli wrote: 
> On Monday 17 January 2011 11:56:23 Michael Büsch wrote:
> > On Mon, 2011-01-17 at 11:46 +0100, Jonas Gorski wrote:
> > > Hello,
> > > 
> > > I am currently looking into adding support for the newer Broadcom
> > > BCM47xx/53xx SoCs. They require having HND/AI support, which probably
> > > means merging the current SSB code and the HND/AI code from the
> > > brcm80211 driver. Is anyone already working on this?
> > > 
> > > As far as I can see, there are two possibilities:
> > > 
> > > a) Merge the HND/AI code into the current SSB code, or
> > > 
> > > b) add the missing code for SoCs to brcm80211 and replace the SSB code
> > > with it.
> > 
> > Why can't we keep those two platforms separated?
> 
> That is also what I am wondering about. Considering that previous BCM47xx 
> platforms use a MIPS4k core and newer one use MIPS74k or later, you would not 
> be able to build a single kernel for both which takes advantages of compile-
> time optimizations targetting MIPS74k. If this ist not a big concern, then 
> let's target a single kernel.

Ok, but it should be easily possible to compile both SSB and HND/AI
bus support into one kernel anyway. Nothing prevents drivers from having
an SSB and an HND/AI probe callback.

-- 
Greetings Michael.

  reply	other threads:[~2011-01-17 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 10:46 Merging SSB and HND/AI support Jonas Gorski
2011-01-17 10:56 ` Michael Büsch
2011-01-17 11:13   ` Johannes Berg
2011-01-17 11:17     ` Michael Büsch
2011-01-17 11:20   ` Florian Fainelli
2011-01-17 12:00     ` Michael Büsch [this message]
2011-01-17 11:21   ` Jonas Gorski
2011-01-17 11:57     ` Michael Büsch
2011-01-17 13:43       ` Jonas Gorski
2011-01-17 13:54         ` Geert Uytterhoeven
2011-01-17 14:01           ` Jonas Gorski

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=1295265609.24530.25.camel@maggie \
    --to=mb@bu3sch.de \
    --cc=florian@openwrt.org \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.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