From: Johannes Berg <johannes@sipsolutions.net>
To: Tom Gundersen <teg@jklm.no>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
linux-wireless@vger.kernel.org,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: status of ipw2x00
Date: Mon, 30 Jan 2012 06:55:23 -0800 [thread overview]
Message-ID: <1327935323.3630.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAG-2HqUqwHo_xgqC79riQF2DA4DPz1Qy5ZARQK8GT+tf_-UKRg@mail.gmail.com> (sfid-20120130_144316_998822_69311B85)
On Mon, 2012-01-30 at 14:42 +0100, Tom Gundersen wrote:
> I'm the udev maintainer for Arch Linux, and we have been running into
> some problems with the ipw2200 driver[0]. This was most probably
> exposed by changes in recent versions of udev, as outlined here [1]
> (so will eventually hit the other distros when they upgrade).
>
> I see that the ipw2x00 drivers are listed as Orphaned in MANTAINERS,
> and I notice that 2000-series Wireless-N support was added to iwlagn.
>
> Does this mean that we (as a dristro) should drop the ipw2x00 driver
> in favor of iwlagn, or do they actualy support different hardware? I
> was not able to find any reference to 2000-series Wireless-N chips on
> intel.com, so I'm not really sure what hardware this "Intel(R)
> Centrino(R) Wireless-N 2200D BGN" is referring to (if it is not [2].
> Furthermore, I noticed that the modaliases of the two drivers do not
> overlap, which should indicate that they do not support the same
> hardware, is that correct?
Yes, it's unfortunate but true -- ipw 2200 and the current 2200 devices
are completely different hardware, there's no overlap.
johannes
next prev parent reply other threads:[~2012-01-30 14:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 13:42 status of ipw2x00 Tom Gundersen
2012-01-30 14:55 ` Johannes Berg [this message]
2012-01-30 15:08 ` Tom Gundersen
2012-01-30 15:28 ` wwguy
2012-01-30 18:44 ` MAINTAINER NEEDED -- " John W. Linville
2012-01-30 19:55 ` Dan Williams
2012-01-30 20:13 ` Florian Fainelli
2012-01-30 20:23 ` Dan Williams
2012-01-30 21:47 ` Julian Calaby
2012-01-30 21:52 ` Florian Fainelli
2012-01-30 21:59 ` Julian Calaby
2012-02-02 10:42 ` Francois Romieu
2012-02-03 20:58 ` Stanislav Yakovlev
2012-02-07 21:27 ` yao zhao
2012-03-15 11:02 ` Stanislaw Gruszka
2012-03-16 4:02 ` Stanislav Yakovlev
2012-03-17 14:36 ` Henrique de Moraes Holschuh
2012-03-19 22:56 ` Stanislav Yakovlev
2012-03-19 23:01 ` Julian Calaby
2012-03-20 2:11 ` Henrique de Moraes Holschuh
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=1327935323.3630.3.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-wireless@vger.kernel.org \
--cc=teg@jklm.no \
--cc=wey-yi.w.guy@intel.com \
/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).