From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev@lists.infradead.org
Subject: Re: [PATCH 1/2] ssb: define boardflags
Date: Sat, 23 Jul 2011 10:54:58 +0200 [thread overview]
Message-ID: <20110723105458.61ed2073@maggie> (raw)
In-Reply-To: <CACna6rxZqmC-n1iQGX+KnoPDFRx4gY1gV+td0gPi2wu_WnT1XQ@mail.gmail.com>
On Sat, 23 Jul 2011 10:49:55 +0200
Rafał Miłecki <zajec5@gmail.com> wrote:
> W dniu 23 lipca 2011 10:37 użytkownik Michael Büsch <m@bues.ch> napisał:
> > On Sat, 23 Jul 2011 11:10:11 +0200
> > Rafał Miłecki <zajec5@gmail.com> wrote:
> >
> >> They are SPROM specific, so all should be defined in ssb code.
> >
> > Oh, well. I'm not sure.
> > Most of these currently are defined in b43 code, because they are b43-specific
> > and _not_ ssb specific. If we decide to define them in ssb, they need to be
> > removed from b43, at least.
>
> Well, SPROM is board specific (not 80211 core specific), so I believe
> the same applies to boardflags, doesn't it? Boardflags are read from
> SPROM, so it makes sense for me.
No. Most of these flags are specific to the whole device (the board).
Most flags are invalid or have another meaning for b44, for instance.
--
Greetings, Michael.
next prev parent reply other threads:[~2011-07-23 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 9:10 [PATCH 0/2] ssb: start cleaning boardflags Rafał Miłecki
2011-07-23 9:10 ` [PATCH 1/2] ssb: define boardflags Rafał Miłecki
2011-07-23 8:37 ` Michael Büsch
2011-07-23 8:49 ` Rafał Miłecki
2011-07-23 8:54 ` Michael Büsch [this message]
2011-07-23 9:10 ` [PATCH 2/2] bcma: use boardflags define from ssb code 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=20110723105458.61ed2073@maggie \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).