netdev - Re: [ipw3945-devel] [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]

Date:	Sat, 10 Feb 2007 12:53:51 -0500
From:	Pavel Roskin <proski@....org>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Theodore Tso <tytso@....edu>,
	James Ketrenos <jketreno@...ux.intel.com>,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
	ipw3945-devel@...ts.sourceforge.net, netdev@...r.kernel.org
Subject: Re: [ipw3945-devel] [ANNOUNCE] d80211 based driver for Intel
	PRO/Wireless 3945ABG

Quoting "John W. Linville" <linville@...driver.com>:

> > Very cool!  Is it likely that d80211 and iwlwifi will be pushed into
> > mainline in time for 2.6.21?
>
> Hmmm...I think we need to spend a cycle or so in -mm.  2.6.22 seems
> more likely for mainline.

I think we should take this as a goal.  Last time I checked, d80211 wasn't in
-mm.  Perhaps it should go there.  And by the way, the latest changes from
netdev->class_dev to netdev->dev break d80211.  Perhaps we should rebase
wireless-dev immediately after 2.6.21-rc1, fix all compile issues and submit
the patch to -mm.

And iwlwifi is surprisingly good for a just announced driver.  It worked for me
from the first attempt, and that's the first d80211 driver to do so.  In my
opinion, it should go to wireless-dev as soon as possible so it can go to -mm
toghether with other drivers.  A couple of wrinkles in the standalone build
system are irrelevant to the kernel interation.

--
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