linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Bernhard Reiter <bernhard@intevation.de>,
	linux-wireless@vger.kernel.org, Dave <kilroyd@googlemail.com>
Subject: Re: 802.11 pccard, Agere 0x0156,0x0003?
Date: Mon, 23 Jun 2008 12:53:25 -0400	[thread overview]
Message-ID: <1214240005.16075.42.camel@localhost.localdomain> (raw)
In-Reply-To: <878wwwi0zr.fsf@nokia.com>

On Mon, 2008-06-23 at 19:12 +0300, Kalle Valo wrote:
> "Johannes Berg" <johannes@sipsolutions.net> writes:
> 
> >> > Both versions can be found at <http://www.xs4all.nl/~pptp/agere>, which
> >> > also has patched versions for 2.6
> >> 
> >> Cool!
> >> Just to make sure: This is a driver that - despite being unmaintained - should 
> >> work? So could try it with 2.6.17, 2.6.24 and even newer?
> >
> > Just FYI, there are patches in the queue that will most likely make all
> > (out-of-tree) drivers using wireless extensions break, so even if it
> > works now it will probably not with 2.6.27.
> 
> What is breaking out-of-tree drivers in 2.6.27? David Miller's compat
> WEXT stuff, or what?

Yes.

Dan


  reply	other threads:[~2008-06-23 16:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 15:15 802.11 pccard, Agere 0x0156,0x0003? Bernhard Reiter
2008-06-18 15:31 ` Stefanik Gábor
2008-06-18 22:04   ` Dave
2008-06-19  0:03     ` Pavel Roskin
2008-06-19  6:55       ` Holger Schurig
2008-06-19 17:27         ` Dave
2008-06-19  8:23       ` Bernhard Reiter
2008-06-19  9:19         ` Holger Schurig
2008-06-19 12:44           ` Bernhard Reiter
2008-06-19 13:54             ` Holger Schurig
2008-06-19 17:40         ` Dave
2008-06-20  7:35           ` Bernhard Reiter
2008-06-20  7:37             ` Johannes Berg
2008-06-23 16:12               ` Kalle Valo
2008-06-23 16:53                 ` Dan Williams [this message]
2008-06-23 17:01                   ` Kalle Valo

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=1214240005.16075.42.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=bernhard@intevation.de \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@nokia.com \
    --cc=kilroyd@googlemail.com \
    --cc=linux-wireless@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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).