Return-path: Received: from 80-190-117-144.ip-home.de ([80.190.117.144]:44931 "EHLO bu3sch.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753311Ab1AQK4c (ORCPT ); Mon, 17 Jan 2011 05:56:32 -0500 Subject: Re: Merging SSB and HND/AI support From: Michael =?ISO-8859-1?Q?B=FCsch?= To: Jonas Gorski Cc: linux-mips@linux-mips.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org In-Reply-To: (sfid-20110117_114654_053644_FFFFFFFF84F9C750) References: (sfid-20110117_114654_053644_FFFFFFFF84F9C750) Content-Type: text/plain; charset="UTF-8" Date: Mon, 17 Jan 2011 11:56:23 +0100 Message-ID: <1295261783.24530.3.camel@maggie> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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? Is there really a lot of shared code between SSB and HND/AI? It's true that there's currently a lot of device functionality built into ssb. Like pci bridge, mips core, extif, etc... If you take all that code out, you're probably not left with anything. So why do we need to replace or merge SSB in the first place? Can't it co-exist with HND/AI? -- Greetings Michael.