All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Theodore Tso <tytso@mit.edu>,
	James Ketrenos <jketreno@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [ipw3945-devel] [ANNOUNCE] d80211 based driver for Intel  PRO/Wireless 3945ABG
Date: Sat, 10 Feb 2007 12:53:51 -0500	[thread overview]
Message-ID: <20070210125351.05uo0o0sgw0w0ckc@webmail.spamcop.net> (raw)
In-Reply-To: <20070210163933.GA17140@tuxdriver.com>

Quoting "John W. Linville" <linville@tuxdriver.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

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Theodore Tso <tytso@mit.edu>,
	James Ketrenos <jketreno@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [ipw3945-devel] [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG
Date: Sat, 10 Feb 2007 12:53:51 -0500	[thread overview]
Message-ID: <20070210125351.05uo0o0sgw0w0ckc@webmail.spamcop.net> (raw)
In-Reply-To: <20070210163933.GA17140@tuxdriver.com>

Quoting "John W. Linville" <linville@tuxdriver.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

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Theodore Tso <tytso@mit.edu>,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net,
	James Ketrenos <jketreno@linux.intel.com>
Subject: Re: [ANNOUNCE] d80211 based driver for Intel	PRO/Wireless 3945ABG
Date: Sat, 10 Feb 2007 12:53:51 -0500	[thread overview]
Message-ID: <20070210125351.05uo0o0sgw0w0ckc@webmail.spamcop.net> (raw)
In-Reply-To: <20070210163933.GA17140@tuxdriver.com>

Quoting "John W. Linville" <linville@tuxdriver.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

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2007-02-10 17:53 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
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     ` Pavel Roskin [this message]
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=20070210125351.05uo0o0sgw0w0ckc@webmail.spamcop.net \
    --to=proski@gnu.org \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.