From: Pavel Roskin <proski@gnu.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Larry Finger <Larry.Finger@lwfinger.net>,
Jiri Benc <jbenc@suse.cz>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: 2.6.25-rc9 -- bcm4306 performance is in the toilet
Date: Wed, 16 Apr 2008 13:55:07 -0400 [thread overview]
Message-ID: <1208368507.2979.4.camel@dv> (raw)
In-Reply-To: <a44ae5cd0804161045h37aafedbk5ff69bbb3c5ff850@mail.gmail.com>
On Wed, 2008-04-16 at 13:45 -0400, Miles Lane wrote:
> Am I required to get the linux-wireless git kernel tree in order to
> get the newer nl80211.h?
You can take the latest compat-wireless, as suggested on the iw page:
http://linuxwireless.org/en/users/Documentation/iw
> I checked in the 2.6.25-rc9 tree and was surprised to find four copies
> of nl80211.h:
> 0 2008-04-14 23:48 ./include/config/nl80211.h
> 10074 2008-04-11 16:32 ./include/linux/nl80211.h
> 510 2008-04-11 16:32 ./net/wireless/nl80211.h
> 10074 2008-04-15 05:50 ./usr/include/linux/nl80211.h
>
> It seems interesting that two copies have the same byte count and that
> one of the files is empty. What's up with that?
Only files in "include" are for external use. Files under
"include/config" indicate kernel configuration. You don't need that.
That leaves include/linux/nl80211.h
Another approach. iw sources include linux/nl80211.h, and defconfig
refers to "include". That gives the same answer.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-04-16 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 2:27 2.6.25-rc9 -- bcm4306 performance is in the toilet Miles Lane
2008-04-16 14:30 ` Larry Finger
2008-04-16 17:12 ` Miles Lane
2008-04-16 17:30 ` Johannes Berg
2008-04-16 17:45 ` Miles Lane
2008-04-16 17:55 ` Pavel Roskin [this message]
2008-04-16 18:01 ` Johannes Berg
2008-04-16 15:55 ` Holger Schurig
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=1208368507.2979.4.camel@dv \
--to=proski@gnu.org \
--cc=Larry.Finger@lwfinger.net \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=miles.lane@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.