From: Michael Wu <flamingice@sourmilk.net>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Daniel Drake <dsd@gentoo.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] zd1211rw-mac80211: debug output for mac80211 ops
Date: Mon, 30 Jul 2007 22:06:20 -0700 [thread overview]
Message-ID: <200707302206.25489.flamingice@sourmilk.net> (raw)
In-Reply-To: <20070730225205.GA17252@deine-taler.de>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
On Monday 30 July 2007 15:52, Ulrich Kunitz wrote:
> John W. Linville wrote:
> > On Sun, Jul 29, 2007 at 08:21:31PM -0700, Michael Wu wrote:
> > > On Sunday 29 July 2007 19:31, Daniel Drake wrote:
> > > > This patch adds debug output to mac80211 operations. This is
> > > > intended to sort out the issues with the interface semantics.
> > >
> > > Ugh. I really hate enter/exit and especially these since they are open
> > > coded. What do you need clarified about mac80211 interface semantics?
> >
> > I agree, these are a bit ugly. Do you intend them to be permanent?
>
> Guys, actually I looked into iwl-base.c and there are also leave
> and enter statements for exactly the same mac80211 operations. I
> would appreciate, if somebody could explain me the difference.
>
None. I didn't like the ones in iwlwifi either.
> Please notify that the messages will only be compiled into the
> driver if ZD1211_DEBUG is set. I could agree to take them out,
> after we have fixed the multiple interface issues, but right now
> they help to make the logfile quite readable. They help also to
> check my understanding of the struct ieee80211_ops functions.
>
I would prefer if you kept it in your tree.
> Asked what I don't understand about the mac80211 interfaces, I
> have following questions:
>
> Why does WIPHY has only a single MAC address?
>
That is for the mac address stored in the eeprom.
> Though ZD1211 has only one RF chip and one baseband processor --
> which represents a single PHY device in my opinion -- it can
> support two MAC addresses. Sure MAC80211 can give different IP
> addresses to different interfaces, but currently I'm not sure, how
> they relate to the address in the WIPHY.
>
The proper address to use is given in add_interface. Don't worry about the
address in wiphy.
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-31 5:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070730023128.99E927B409F@zog.reactivated.net>
2007-07-30 3:21 ` [PATCH] zd1211rw-mac80211: debug output for mac80211 ops Michael Wu
2007-07-30 14:51 ` John W. Linville
2007-07-30 22:52 ` Ulrich Kunitz
2007-07-30 23:05 ` Michael Buesch
2007-07-30 23:25 ` Andy Green
2007-07-31 21:12 ` Jiri Benc
2007-07-31 21:30 ` Michael Buesch
2007-07-31 21:42 ` Andy Green
2007-07-31 21:50 ` Andy Green
2007-07-31 5:22 ` Michael Wu
2007-07-31 9:39 ` Michael Buesch
2007-07-31 21:06 ` Jiri Benc
2007-07-31 21:39 ` Michael Buesch
2007-07-31 5:06 ` Michael Wu [this message]
2007-07-31 21:00 ` Jiri Benc
2007-07-31 21:37 ` Michael Buesch
2007-07-31 22:10 ` Jiri Benc
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=200707302206.25489.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=dsd@gentoo.org \
--cc=kune@deine-taler.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).