From: Zhu Yi <yi.zhu@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Michael Buesch <mb@bu3sch.de>, Jeff Garzik <jgarzik@pobox.com>,
jketreno@linux.intel.com, Netdev list <netdev@vger.kernel.org>,
linville@tuxdriver.com,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
Date: Wed, 12 Jul 2006 12:39:58 +0800 [thread overview]
Message-ID: <1152679198.3496.99.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20060711133227.GA1650@elf.ucw.cz>
On Tue, 2006-07-11 at 15:32 +0200, Pavel Machek wrote:
> Probably not. This (very dirty) hack implements that (with some level
> of success -- ifconfig down/ifconfig up is enough to get wireless
> working).
You just need to
$ iwpriv ethX reset
Thanks,
-yi
next prev parent reply other threads:[~2006-07-12 4:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 15:20 [patch] do not allow IPW_2100=Y or IPW_2200=Y Pavel Machek
2006-07-10 17:53 ` Jeff Garzik
2006-07-10 18:29 ` Auke Kok
2006-07-10 18:47 ` David Miller
2006-07-10 18:51 ` Arjan van de Ven
2006-07-10 20:56 ` Joel Becker
2006-07-11 14:42 ` Arjan van de Ven
2006-07-11 21:53 ` Joel Becker
2006-07-11 11:27 ` Pavel Machek
2006-07-11 14:42 ` Arjan van de Ven
2006-07-10 21:05 ` Michael Buesch
2006-07-11 11:53 ` Daniel Drake
2006-07-11 20:39 ` Michael Buesch
2006-07-11 20:59 ` Daniel Drake
2006-07-11 13:32 ` Pavel Machek
2006-07-12 4:39 ` Zhu Yi [this message]
2006-07-27 14:43 ` John W. Linville
2006-07-11 13:34 ` [patch] cleanup // comments from ipw2200 Pavel Machek
2006-07-10 22:21 ` [patch] do not allow IPW_2100=Y or IPW_2200=Y Jan Engelhardt
[not found] <6x7TQ-87H-17@gated-at.bofh.it>
[not found] ` <6x8df-8wm-13@gated-at.bofh.it>
[not found] ` <6xbaZ-4NX-1@gated-at.bofh.it>
[not found] ` <6xyhj-5Fq-19@gated-at.bofh.it>
2006-07-12 20:56 ` Bodo Eggert
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=1152679198.3496.99.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=jgarzik@pobox.com \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.