netdev - Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1171063040.7039.16.camel@dv>
Date:	Fri, 09 Feb 2007 18:17:20 -0500
From:	Pavel Roskin <proski@....org>
To:	James Ketrenos <jketreno@...ux.intel.com>
Cc:	linux-wireless@...r.kernel.org,
	ipw3945-devel@...ts.sourceforge.net, netdev@...r.kernel.org
Subject: Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG

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 netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html