From: "Michael Büsch" <mb@bu3sch.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: George Kashperko <george@znau.edu.ua>,
linux-wireless@vger.kernel.org,
b43-dev <b43-dev@lists.infradead.org>
Subject: [RFC] How to rename SSB_TMSLOW_*, B43_TMSLOW_*?
Date: Thu, 17 Feb 2011 23:00:18 +0100 [thread overview]
Message-ID: <1297980018.13554.4.camel@maggie> (raw)
In-Reply-To: <AANLkTi=sVaeizU3xJQQwwKXB5saPgdn9VxNQv0-aoiV7@mail.gmail.com> (sfid-20110217_131436_086343_78318A6B)
On Thu, 2011-02-17 at 13:14 +0100, Rafa? Mi?ecki wrote:
> That's why I wanted to introduce some SSBAI_CORECTL_FOOBAR and make
> b43 unaware it that flags are going to be written in register A or B.
> I wanted b43 to just pass flags to correct function and do not care
> about place where they are getting written.
Ok, well. That's basically what I am talking about for several
days now.
1) Keep SSB and AI separated.
2) Introduce an additional thin layer on top of this to abstract the
bus to the drivers.
--
Greetings Michael.
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <mb@bu3sch.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: George Kashperko <george@znau.edu.ua>,
linux-wireless@vger.kernel.org,
b43-dev <b43-dev@lists.infradead.org>
Subject: Re: [RFC] How to rename SSB_TMSLOW_*, B43_TMSLOW_*?
Date: Thu, 17 Feb 2011 23:00:18 +0100 [thread overview]
Message-ID: <1297980018.13554.4.camel@maggie> (raw)
In-Reply-To: <AANLkTi=sVaeizU3xJQQwwKXB5saPgdn9VxNQv0-aoiV7@mail.gmail.com> (sfid-20110217_131436_086343_78318A6B)
On Thu, 2011-02-17 at 13:14 +0100, Rafał Miłecki wrote:
> That's why I wanted to introduce some SSBAI_CORECTL_FOOBAR and make
> b43 unaware it that flags are going to be written in register A or B.
> I wanted b43 to just pass flags to correct function and do not care
> about place where they are getting written.
Ok, well. That's basically what I am talking about for several
days now.
1) Keep SSB and AI separated.
2) Introduce an additional thin layer on top of this to abstract the
bus to the drivers.
--
Greetings Michael.
next prev parent reply other threads:[~2011-02-17 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 13:13 [RFC] How to rename SSB_TMSLOW_*, B43_TMSLOW_*? Rafał Miłecki
2011-02-16 13:13 ` Rafał Miłecki
2011-02-16 14:58 ` George Kashperko
2011-02-16 22:17 ` Michael Büsch
2011-02-16 22:17 ` Michael Büsch
2011-02-17 12:14 ` Rafał Miłecki
2011-02-17 12:14 ` Rafał Miłecki
2011-02-17 22:00 ` Michael Büsch [this message]
2011-02-17 22:00 ` Michael Büsch
2011-02-17 22:15 ` Rafał Miłecki
2011-02-17 22:15 ` Rafał Miłecki
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=1297980018.13554.4.camel@maggie \
--to=mb@bu3sch.de \
--cc=b43-dev@lists.infradead.org \
--cc=george@znau.edu.ua \
--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 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.