From: Peter Hurley <peter@hurleysoftware.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>, Jiri Kosina <jkosina@suse.cz>
Cc: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi-driver card doesn't work with 3.19-rc2+
Date: Tue, 30 Dec 2014 09:34:47 -0500 [thread overview]
Message-ID: <54A2B807.1020202@hurleysoftware.com> (raw)
In-Reply-To: <CANUX_P0=wJiKrR4cUgEN=LO+eQ2byprz0K9m9QxzJc+kf4+_bA@mail.gmail.com>
On 12/30/2014 09:23 AM, Emmanuel Grumbach wrote:
> On Tue, Dec 30, 2014 at 3:33 PM, Jiri Kosina <jkosina@suse.cz> wrote:
>>
>> Hi,
>>
>> I just booted current Linus' tree (5faa0154fe33) on my x200s thinkpad, and
>> wifi doesn't work. iwconfig is telling me that wlan0 interface has no
>> wireless extensions.
>>
>
> So why do you used them?
> They have been deprecated for a couple of years now. You should be
> using nl80211 based tools such as iw.
A couple of years is not very long where userspace is concerned.
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-12-30 14:34 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 13:33 iwlwifi-driver card doesn't work with 3.19-rc2+ Jiri Kosina
2014-12-30 14:23 ` Emmanuel Grumbach
2014-12-30 14:34 ` Peter Hurley [this message]
2014-12-30 14:38 ` Grumbach, Emmanuel
2014-12-30 14:38 ` Grumbach, Emmanuel
2014-12-30 15:21 ` Jiri Kosina
2014-12-30 20:28 ` Grumbach, Emmanuel
2014-12-30 20:28 ` Grumbach, Emmanuel
2014-12-30 20:41 ` Jiri Kosina
2014-12-30 21:23 ` Borislav Petkov
2014-12-30 22:35 ` Larry Finger
2014-12-30 22:42 ` Jiri Kosina
2014-12-30 22:52 ` [PATCH] Revert "cfg80211: make WEXT compatibility unselectable" Jiri Kosina
2014-12-31 7:44 ` Grumbach, Emmanuel
2014-12-31 11:09 ` Arend van Spriel
2014-12-31 11:10 ` Grumbach, Emmanuel
2014-12-31 11:45 ` Arend van Spriel
2014-12-31 14:07 ` Jiri Kosina
2014-12-31 15:02 ` Arend van Spriel
2014-12-31 17:31 ` Theodore Ts'o
2014-12-31 17:44 ` Linus Torvalds
2014-12-31 20:32 ` Arend van Spriel
2014-12-31 21:44 ` Theodore Ts'o
2014-12-31 21:57 ` Linus Torvalds
2014-12-31 22:19 ` Theodore Ts'o
2014-12-31 22:41 ` Arend van Spriel
2015-01-01 0:22 ` David Lang
2015-01-01 11:32 ` Richard Weinberger
2015-01-01 19:44 ` Lennart Sorensen
2015-01-01 20:14 ` Linus Torvalds
2015-01-02 4:04 ` Lennart Sorensen
2015-01-05 7:26 ` Michal Kubecek
2014-12-31 22:30 ` Arend van Spriel
2014-12-31 15:14 ` Andreas Hartmann
2014-12-31 19:48 ` Arend van Spriel
2015-01-01 10:56 ` Andreas Hartmann
2015-01-01 12:25 ` Arend van Spriel
2014-12-31 13:10 ` Jiri Kosina
2014-12-31 13:26 ` Grumbach, Emmanuel
2014-12-31 13:49 ` Peter Hurley
2014-12-31 14:40 ` Julian Calaby
2014-12-31 14:46 ` Borislav Petkov
2014-12-31 14:56 ` Julian Calaby
2014-12-31 15:03 ` Jiri Kosina
2014-12-31 15:11 ` Borislav Petkov
2015-01-02 5:11 ` Pavel Machek
2014-12-31 16:43 ` Paul Bolle
2014-12-31 7:50 ` iwlwifi-driver card doesn't work with 3.19-rc2+ Grumbach, Emmanuel
2014-12-31 8:05 ` Sujith Manoharan
2014-12-31 13:54 ` Borislav Petkov
2014-12-30 15:03 ` Jiri Kosina
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=54A2B807.1020202@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=egrumbach@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=jkosina@suse.cz \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.