All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dieter Ries <clip2@gmx.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	Tomas Winkler <tomasw@gmail.com>
Subject: Re: iwl3945 broken in current git
Date: Mon, 20 Oct 2008 14:47:40 +0200	[thread overview]
Message-ID: <48FC7DEC.9060200@gmx.de> (raw)
In-Reply-To: <1224506366.27899.25.camel@johannes.berg>

Johannes Berg schrieb:
> On Mon, 2008-10-20 at 14:35 +0200, Dieter Ries wrote:
>> Johannes Berg schrieb:
>>> On Mon, 2008-10-20 at 14:17 +0200, Dominik Brodowski wrote:
>>>
>>>>> iwl3945: Microcode SW error detected.  Restarting 0x82000008.
>>>>> iwl3945: Error Reply type 0x00000005 cmd REPLY_SCAN_CMD (0x80) seq
>>>>> 0x4416 ser 0x0000004B
>>>>> iwl3945: Can't stop Rx DMA.
>>>> It needs a more recent uCode -- the driver really should scream out loudly
>>>> that the old firmware no longer suffices.
>>> You could try reverting ef224ca2ce55e81acc6c3a74c3e8c00a00941c70, that's
>>> the only commit I can find that seems to be vaguely related to the
>>> problem as Tomas described it. Not that it might not be hidden in some
>>> other commit...
>> The new firmware did it. It works now, but it should really scream out
>> loud ...
> 
> Do you still have the old one? Would you try anyway?

ahem, I don't seem to have ef224ca2ce55e81acc6c3a74c3e8c00a00941c70, are
you sure that is the right hash?

> 
> johannes

cu
Dieter

  parent reply	other threads:[~2008-10-20 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 11:31 iwl3945 broken in current git Dieter Ries
2008-10-20 12:17 ` Dominik Brodowski
2008-10-20 12:33   ` Johannes Berg
2008-10-20 12:35     ` Dieter Ries
2008-10-20 12:39       ` Johannes Berg
2008-10-20 12:41         ` Dieter Ries
2008-10-20 12:47           ` Johannes Berg
2008-10-20 12:47         ` Dieter Ries [this message]
2008-10-20 12:51           ` Johannes Berg

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=48FC7DEC.9060200@gmx.de \
    --to=clip2@gmx.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=tomasw@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 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.