From: Pavel Roskin <proski@gnu.org> To: James Ketrenos <jketreno@linux.intel.com> 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 18:17:20 -0500 [thread overview] Message-ID: <1171063040.7039.16.camel@dv> (raw) In-Reply-To: <45CCF318.2020503@linux.intel.com> On Fri, 2007-02-09 at 14:18 -0800, James Ketrenos wrote: > Updated and tested 'git clone' and its working now (I use cg-clone) Thanks. It's working for me too. > > grep: /lib/modules/2.6.20/build//include/linux/netdevice.h: No such file > > or directory > > > > Apparently it should be looking into /lib/modules/2.6.20/source as well. > > That was a problem with the official ipw3945 drivers as well. > > 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. Anyway, I'm cheating here - my kernel does include d80211 support. "build" is still hardcoded in iwlwifi's Makefile. It's interesting that D80211_INC is defined twice in Makefile. That must be wrong. I'm going to try everything on a more traditional build in the tree and without d80211. And then I'll try to break some assumptions. -- Regards, Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org> To: James Ketrenos <jketreno-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, ipw3945-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG Date: Fri, 09 Feb 2007 18:17:20 -0500 [thread overview] Message-ID: <1171063040.7039.16.camel@dv> (raw) In-Reply-To: <45CCF318.2020503-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> On Fri, 2007-02-09 at 14:18 -0800, James Ketrenos wrote: > Updated and tested 'git clone' and its working now (I use cg-clone) Thanks. It's working for me too. > > grep: /lib/modules/2.6.20/build//include/linux/netdevice.h: No such file > > or directory > > > > Apparently it should be looking into /lib/modules/2.6.20/source as well. > > That was a problem with the official ipw3945 drivers as well. > > 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. Anyway, I'm cheating here - my kernel does include d80211 support. "build" is still hardcoded in iwlwifi's Makefile. It's interesting that D80211_INC is defined twice in Makefile. That must be wrong. I'm going to try everything on a more traditional build in the tree and without d80211. And then I'll try to break some assumptions. -- Regards, Pavel Roskin - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-02-09 23:17 UTC|newest] Thread overview: 75+ 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 21:12 ` James Ketrenos 2007-02-09 22:14 ` Alon Bar-Lev 2007-02-09 22:26 ` Neil Brown 2007-02-09 22:26 ` Neil Brown 2007-02-09 21:52 ` James Ketrenos 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:37 ` Stefan Schmidt 2007-02-09 22:43 ` Pavel Roskin 2007-02-09 22:43 ` Pavel Roskin 2007-02-09 22:18 ` James Ketrenos 2007-02-09 22:18 ` James Ketrenos 2007-02-09 23:17 ` Pavel Roskin [this message] 2007-02-09 23:17 ` Pavel Roskin 2007-02-09 22:45 ` James Ketrenos 2007-02-09 22:45 ` James Ketrenos 2007-02-09 22:48 ` dragoran dragoran 2007-02-10 0:46 ` [ipw3945-devel] " Norbert Preining 2007-02-10 0:46 ` Norbert Preining 2007-02-10 0:46 ` [ipw3945-devel] " Norbert Preining 2007-02-13 23:23 ` James Ketrenos 2007-02-13 23:23 ` James Ketrenos 2007-02-13 23:23 ` James Ketrenos 2007-02-10 13:23 ` Hesse, Christian 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-12 18:35 ` James Ketrenos 2007-02-13 12:18 ` Hesse, Christian 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:22 ` Theodore Tso 2007-02-10 16:39 ` John W. Linville 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 17:53 ` [ipw3945-devel] " Pavel Roskin 2007-02-10 22:41 ` John W. Linville 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 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 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-13 23:18 ` James Ketrenos 2007-02-14 0:16 ` [ipw3945-devel] " James Ketrenos 2007-02-14 0:16 ` 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-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 7:32 ` Randy Dunlap 2007-02-21 19:38 ` Pavel Machek 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=1171063040.7039.16.camel@dv \ --to=proski@gnu.org \ --cc=ipw3945-devel@lists.sourceforge.net \ --cc=jketreno@linux.intel.com \ --cc=linux-wireless@vger.kernel.org \ --cc=netdev@vger.kernel.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: linkBe 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.