Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
To: George Nychis <gnychis@gmail.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: how to configure compat-wireless to force manual firmware load?
Date: Mon, 23 Apr 2012 12:43:19 +0530	[thread overview]
Message-ID: <20373.271.262245.296570@gargle.gargle.HOWL> (raw)
In-Reply-To: <CA+7oygft-wqhnkk5wwondb57WuN2hLkVDKMXwKoaK+p9sZwAcw@mail.gmail.com>

George Nychis wrote:
> I was using an older version of compat-wireless, specifically a build
> from May 2011.  In that release of compat-wireless, the firmware was
> loaded manually using a filesystem mounted in /sys.
> 
> I recently downloaded a newer version of compat-wireless:
> compat-wireless-3.0.9-1.  In this version, it appears to spawn a
> kernel thread to check /lib/firmware for the firmware and load it.  If
> it is present, it loads the firmware, otherwise it fails saying that
> it cannot be found.
> 
> I am having trouble with the automatic load:
> <3>[  178.957584] otg_err: in s5pc110_otghcd_urb_dequeue()::00508
> <3>[  178.958650] => fail to cancel_transfer()
> <7>[  178.959879] usb 1-1.2: hcd_unlink_urb d13aa200 fail -1
> <7>[  178.962510] usb 1-1.2: khubd timed out on ep0out len=0/4096
> <3>[  178.963274] usb 1-1.2: ath9k_htc: Firmware - htc_7010.fw download failed
> <4>[  178.971658] ath9k_htc: probe of 1-1.2:1.0 failed with error -22

The FW is found, but transferring it to the device fails for some reason.
Can you give more details about the platform ?

Sujith

      reply	other threads:[~2012-04-23  7:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  7:00 how to configure compat-wireless to force manual firmware load? George Nychis
2012-04-23  7:13 ` Sujith Manoharan [this message]

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=20373.271.262245.296570@gargle.gargle.HOWL \
    --to=c_manoha@qca.qualcomm.com \
    --cc=gnychis@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