From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: new iwlwifi 6030 uCode available
Date: Fri, 17 Dec 2010 14:30:36 -0800 [thread overview]
Message-ID: <1292625036.22230.21.camel@wwguy-ubuntu> (raw)
In-Reply-To: <AANLkTi=LmzQVzUruEQAjcSOEjy+x3U_9DqF4tLHENAcU@mail.gmail.com>
Hi Daniel,
On Fri, 2010-12-17 at 14:19 -0800, Daniel Halperin wrote:
> 2010/12/17 Rafał Miłecki <zajec5@gmail.com>:
> > 2010/12/17 Guy, Wey-Yi <wey-yi.w.guy@intel.com>:
> >> Version 17.168.5.1 of uCode for Intel Intel@ 6030 Series Wi-Fi Adapters
> >> is now available for download from
> >> http://intellinuxwireless.org/?n=Downloads
> >
> > I want uCode for 5100 to resolve
> > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2214 !
> >
> > Damn, do you want us to RE Intel's firmware or what? Is that your policy?
>
> Hi Wey-Yi,
>
> I noticed from this bug report that the workaround is to disable
> 802.11n. Is it not possible to instead force-stop all queues, restart
> the firmware and driver similar to when uCode crashes? This might
> tide Rafal over for a little while. It looks like he's not planning
> to stop trolling every few days despite your giving the same answer
> that the issue is out of your control.
>
> Alternatively, Rafal, you might try to implement this type of fix.
>
I thought about that and I even have the patch for it, but it works
sometime and not the other and it is not stable, that is why I did not
push upstream, I might need to spend more time to figure out what is
going on there. Just don't have much time in the past few weeks/months.
Thank
Wey
next prev parent reply other threads:[~2010-12-17 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 21:08 new iwlwifi 6030 uCode available Guy, Wey-Yi
2010-12-17 22:12 ` Rafał Miłecki
2010-12-17 22:19 ` Daniel Halperin
2010-12-17 22:30 ` Guy, Wey-Yi [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-11 0:40 Guy, Wey-Yi
2012-01-21 15:59 Guy, Wey-Yi
2012-01-21 21:42 ` Richard Farina
2012-01-22 15:31 ` Guy, Wey-Yi
2012-01-22 18:03 ` Richard Farina
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=1292625036.22230.21.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=dhalperi@cs.washington.edu \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).