linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: J Igrap <jigrap.code@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Carl9170 Firmware
Date: Wed, 14 Sep 2011 11:50:30 +0200	[thread overview]
Message-ID: <201109141150.30247.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAEh_CyWdC+-mV+YhmoxS6dubWVN10utDim+GWmDLYCX9K9AkkQ@mail.gmail.com>

On Tuesday, September 13, 2011 11:18:23 PM J Igrap wrote:
> While using the past days the carl9170 firmware with a USB card under a
> linux guest running different kernel and driver versions I kept running into
> the issue of a usb disconnect when the card was put under load:
linux guest? You are not using carl9170 in a VM, are you?

>  usb 1-1: no command feedback received (-110).
>  carl9170 cmd: 08 01 00 00 f0 36 1c 00 00 24 00 00              .....6...$..
>  usb 1-1: restart device (6)
> 
> No matter what kernel driver/firmware I tried I will still get it. I decided
> to look into it a bit more and I narrowed it down to be a firmware issue
> with the following code snippet:
Or it could be a problem with the USB PHY. However, the driver
seems to be able to handle the situation and restarts the device
accordingly.
 
> void handle_cmd(struct carl9170_rsp *resp) in src/cmd.c
> 
>         case CARL9170_CMD_WREG:
> esp->hdr.len = 0;
>                 for (i = 0; i < (cmd->hdr.len / 8); i++)
>                         set(cmd->wreg.regs[i].addr, cmd->wreg.regs[i].val);
>                 break;
> 
> That code appears to handle event 1 which is a write into a register. In
> some cases that write appeared to cause a failure and a reset into the card.
> I added a simple delay loop before the switch statement and that seemed to
> fix the issue and I don't lose the card anymore even under a lot of load.
> Obviously that's not a real fix and something else more reliable needs to be
> in place.
Any idea what this "something" else might be?

Regards,
	Chr

       reply	other threads:[~2011-09-14  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEh_CyWdC+-mV+YhmoxS6dubWVN10utDim+GWmDLYCX9K9AkkQ@mail.gmail.com>
2011-09-14  9:50 ` Christian Lamparter [this message]
2011-09-14 13:09   ` Carl9170 Firmware J Igrap
2011-09-14 17:00     ` Christian Lamparter
2012-04-11 13:20       ` J Igrap
2012-04-11 16:54         ` Christian Lamparter
2012-04-11 17:24           ` J Igrap
2012-04-17 17:25 carl9170 firmware Larry Finger
2012-04-17 18:35 ` Christian Lamparter
2012-04-17 19:27   ` Larry Finger
2012-04-18 18:26     ` Christian Lamparter
2012-04-18 19:09       ` Larry Finger
  -- strict thread matches above, loose matches on Subject: below --
2011-09-13 21:21 Carl9170 firmware J Igrap

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=201109141150.30247.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=jigrap.code@gmail.com \
    --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 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).