From: "Michael Büsch" <mb@bu3sch.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev <b43-dev@lists.infradead.org>
Subject: ChipCommon as independent driver?
Date: Fri, 01 Apr 2011 18:15:30 +0200 [thread overview]
Message-ID: <1301674530.5219.25.camel@maggie> (raw)
In-Reply-To: <BANLkTin2ZaBVbum9Y=iqWTwW4kzkdKAJnA@mail.gmail.com> (sfid-20110401_120617_934926_1F9732B2)
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 <mb@bu3sch.de> 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.
next prev parent reply other threads:[~2011-04-01 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 14:49 ChipCommon as independent driver? Rafał Miłecki
2011-04-01 16:00 ` Michael Büsch
2011-04-01 16:06 ` Rafał Miłecki
2011-04-01 16:15 ` Michael Büsch [this message]
2011-04-01 16:21 ` Rafał Miłecki
2011-04-01 16:30 ` Michael Büsch
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=1301674530.5219.25.camel@maggie \
--to=mb@bu3sch.de \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).