From: James Ketrenos <jketreno@linux.intel.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG
Date: Fri, 09 Feb 2007 14:45:22 -0800 [thread overview]
Message-ID: <45CCF982.6090207@linux.intel.com> (raw)
In-Reply-To: <1171063040.7039.16.camel@dv>
Pavel Roskin wrote:
> On Fri, 2007-02-09 at 14:18 -0800, James Ketrenos wrote:
>>> grep: /lib/modules/2.6.20/build//include/linux/netdevice.h: No such file
>>> or directory
...
>> I'll look into it. Does it work if you explicitly set KSRC to point to
>> your kernel sources?
>>
>> $ make KSRC=/lib/modules/2.6.20/source
>
> That works. At least it doesn't report errors. But it doesn't create a
> single object file.
'make' builds a set of sources compatible with the running kernel (or
the one pointed to via KSRC=).
'make patch_kernel' will then install the sources into your kernel tree.
You then build d80211 as part of your main kernel (either as a module
or static) The changes 'patch_kernel' makes do not require a full
kernel rebuild (you can just build the 80211 modules).
We'll want to add the ability to build as out-of-tree .ko's (similar to
what iwlwifi does) but I wanted to get the project announced.
> "build" is still hardcoded in iwlwifi's Makefile. It's interesting that
> D80211_INC is defined twice in Makefile. That must be wrong.
Now that you point it out, I hadn't tried using KSRC w/ the iwlwifi
build, just d80211. I'll have to fix that :)
Thanks,
James
next prev parent reply other threads:[~2007-02-09 23:28 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 21:12 [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG James Ketrenos
2007-02-09 22:14 ` Alon Bar-Lev
2007-02-09 22:26 ` Neil Brown
2007-02-09 21:52 ` James Ketrenos
2007-02-10 3:26 ` Nick Kossifidis
2007-02-09 22:37 ` Stefan Schmidt
2007-02-09 22:43 ` Pavel Roskin
2007-02-09 22:18 ` James Ketrenos
2007-02-09 23:17 ` Pavel Roskin
2007-02-09 22:45 ` James Ketrenos [this message]
2007-02-10 0:46 ` [ipw3945-devel] " Norbert Preining
2007-02-10 0:46 ` Norbert Preining
2007-02-13 23:23 ` James Ketrenos
2007-02-13 23:23 ` James Ketrenos
2007-02-10 13:23 ` Hesse, Christian
2007-02-10 14:25 ` Hesse, Christian
2007-02-12 16:32 ` [ipw3945-devel] " dragoran
2007-02-12 16:32 ` dragoran
2007-02-12 18:35 ` James Ketrenos
2007-02-13 12:18 ` Hesse, Christian
2007-02-11 0:55 ` Pavel Roskin
2007-02-11 13:17 ` Hesse, Christian
2007-02-13 6:47 ` Pavel Roskin
2007-02-13 10:41 ` Hesse, Christian
2007-02-11 13:19 ` Johannes Berg
2007-02-10 16:22 ` Theodore Tso
2007-02-10 16:39 ` John W. Linville
2007-02-10 17:53 ` [ipw3945-devel] " Pavel Roskin
2007-02-10 17:53 ` Pavel Roskin
2007-02-10 22:41 ` John W. Linville
2007-02-10 18:42 ` Michael Buesch
2007-02-13 13:58 ` Ismail Dönmez
2007-02-13 15:10 ` Jeff Chua
2007-02-13 15:10 ` Jeff Chua
2007-02-13 16:57 ` Ismail Dönmez
2007-02-13 16:57 ` Ismail Dönmez
2007-02-13 22:55 ` James Ketrenos
2007-02-13 22:55 ` James Ketrenos
2007-02-13 18:13 ` Pavel Machek
2007-02-13 18:36 ` Johannes Berg
2007-02-13 23:18 ` James Ketrenos
2007-02-14 0:16 ` [ipw3945-devel] " James Ketrenos
2007-02-14 0:16 ` James Ketrenos
2007-02-19 22:44 ` Pavel Machek
2007-02-19 22:44 ` Pavel Machek
2007-02-21 6:23 ` iwlwifi warnings Stephen Hemminger
2007-02-21 6:23 ` Stephen Hemminger
2007-02-21 7:32 ` Randy Dunlap
2007-02-21 19:38 ` Pavel Machek
2007-02-23 5:44 ` Pavel Roskin
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=45CCF982.6090207@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=proski@gnu.org \
/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.