Return-path: Received: from 80-190-117-144.ip-home.de ([80.190.117.144]:59361 "EHLO bu3sch.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752984Ab1DAQPg (ORCPT ); Fri, 1 Apr 2011 12:15:36 -0400 Subject: Re: ChipCommon as independent driver? From: Michael =?ISO-8859-1?Q?B=FCsch?= To: =?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?= Cc: linux-wireless@vger.kernel.org, b43-dev In-Reply-To: (sfid-20110401_120617_934926_1F9732B2) References: <1301673646.5219.18.camel@maggie> (sfid-20110401_120617_934926_1F9732B2) Content-Type: text/plain; charset="UTF-8" Date: Fri, 01 Apr 2011 18:15:30 +0200 Message-ID: <1301674530.5219.25.camel@maggie> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, 2011-04-01 at 18:06 +0200, Rafał Miłecki wrote: > W dniu 1 kwietnia 2011 18:00 użytkownik Michael Büsch napisał: > > On Fri, 2011-04-01 at 16:49 +0200, Rafał Miłecki wrote: > >> Do you have idea how we could nicely solve that issue? > > > > Yeah. Just don't share code between ssb and bcmai. > > That's the only clean solution to that mess. > > Do you want to have core drivers separated as well? Really? Should we > have separated pci core? chiccommon core? Yes. Those "drivers" are a mess full of ssb specific workarounds to hardware limitations. > gige core? Are there bcmai devices with gige core? This driver is a _real_ mess. It basically is one huge workaround, because the hardware is incredibly stupid. > 80211 (b43) core? No. The b43 (and b44) driver is pretty much self contained. It will be easy to make it run on both platforms. There are only a few places that need changes. -- Greetings Michael.