From: "Michael Büsch" <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
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 12:17:42 +0100 [thread overview]
Message-ID: <1295263062.24530.6.camel@maggie> (raw)
In-Reply-To: <1295262781.3726.6.camel@jlt3.sipsolutions.net> (sfid-20110117_121317_233137_FFFFFFFFECA6016B)
On Mon, 2011-01-17 at 12:13 +0100, Johannes Berg wrote:
> On Mon, 2011-01-17 at 11:56 +0100, Michael Büsch wrote:
>
> > > 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?
> > Is there really a lot of shared code between SSB and HND/AI?
>
> I don't think there's a lot of shared code, but I believe that you need
> b43 to be able to target cores on both? And b43 currently uses the SSB
> APIs only.
Yeah right. That's what I was thinking about, too. Just leave SSB alone
and add bus glues to b43 for HND/AI. There's almost no SSB specific code
in b43. So it should be easily possible to add another probe entry from
the (to be written or derived from brcm80211) HND/AI subsystem.
--
Greetings Michael.
next prev parent reply other threads:[~2011-01-17 11:17 UTC|newest]
Thread overview: 19+ 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 10:56 ` Michael Büsch
2011-01-17 11:13 ` Johannes Berg
2011-01-17 11:13 ` Johannes Berg
2011-01-17 11:17 ` Michael Büsch [this message]
2011-01-17 11:20 ` Florian Fainelli
2011-01-17 11:20 ` Florian Fainelli
2011-01-17 12:00 ` Michael Büsch
2011-01-17 12:00 ` Michael Büsch
2011-01-17 11:21 ` Jonas Gorski
2011-01-17 11:21 ` Jonas Gorski
2011-01-17 11:57 ` Michael Büsch
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 13:54 ` Geert Uytterhoeven
2011-01-17 14:01 ` Jonas Gorski
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=1295263062.24530.6.camel@maggie \
--to=mb@bu3sch.de \
--cc=johannes@sipsolutions.net \
--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 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.