From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Mon, 17 Jan 2011 12:13:07 +0100 (CET) Received: from he.sipsolutions.net ([78.46.109.217]:42767 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S1493384Ab1AQLNE (ORCPT ); Mon, 17 Jan 2011 12:13:04 +0100 Received: by sipsolutions.net with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1Pen1C-000504-KJ; Mon, 17 Jan 2011 12:13:02 +0100 Subject: Re: Merging SSB and HND/AI support From: Johannes Berg To: Michael =?ISO-8859-1?Q?B=FCsch?= Cc: Jonas Gorski , linux-mips@linux-mips.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org In-Reply-To: <1295261783.24530.3.camel@maggie> References: (sfid-20110117_114654_053644_FFFFFFFF84F9C750) <1295261783.24530.3.camel@maggie> Content-Type: text/plain; charset="UTF-8" Date: Mon, 17 Jan 2011 12:13:01 +0100 Message-ID: <1295262781.3726.6.camel@jlt3.sipsolutions.net> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 28925 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: johannes@sipsolutions.net Precedence: bulk X-list: linux-mips 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. johannes From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: Merging SSB and HND/AI support Date: Mon, 17 Jan 2011 12:13:01 +0100 Message-ID: <1295262781.3726.6.camel@jlt3.sipsolutions.net> References: (sfid-20110117_114654_053644_FFFFFFFF84F9C750) <1295261783.24530.3.camel@maggie> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jonas Gorski , linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org, linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Michael =?ISO-8859-1?Q?B=FCsch?= Return-path: In-Reply-To: <1295261783.24530.3.camel@maggie> Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On Mon, 2011-01-17 at 11:56 +0100, Michael B=C3=BCsch wrote: > > As far as I can see, there are two possibilities: > >=20 > > a) Merge the HND/AI code into the current SSB code, or > >=20 > > b) add the missing code for SoCs to brcm80211 and replace the SSB c= ode with it. >=20 > 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. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html